mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vladimir <vovan888@gmail.com>
To: "Tony Lindgren" <tony@atomide.com>
Cc: "Pavel Machek" <pavel@ucw.cz>,
	"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: Siemens sx1: merge framebuffer support
Date: Tue, 21 Nov 2006 10:06:09 +0300	[thread overview]
Message-ID: <ce55079f0611202306l3cd57e48t68fe28e7e076d39a@mail.gmail.com> (raw)
In-Reply-To: <20061120190404.GD4597@atomide.com>

2006/11/20, Tony Lindgren <tony@atomide.com>:
> * Pavel Machek <pavel@ucw.cz> [061118 18:16]:
> > From: Vladimir Ananiev <vovan888@gmail.com>
> >
> > Framebuffer support for Siemens SX1; this is second big patch. (Third
> > one will be mixer/sound support). Support is simple / pretty minimal,
> > but seems to work okay (and is somehow important for a cell phone :-).
>
> Pushed to linux-omap. I guess you're planning to send the missing
> Kconfig + Makefile patch for this?
>
> Also, it would be better to use omap_mcbsp_xmit_word() or
> omap_mcsbsp_spi_master_xmit_word_poll() instead of OMAP_MCBSP_WRITE as
> it does not do any checking that it worked. The aic23 and tsc2101
> audio in linux-omap tree in general has the same problem.
>
> Regards,
>
> Tony
>

Hmm. McBSP3 in SX1 is used in "GPIO mode". The only line used is CLKX,
so I think OMAP_MCBSP_WRITE would be enough. Am I wrong ?

  reply	other threads:[~2006-11-21  7:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 18:16 Pavel Machek
2006-11-20 19:04 ` Tony Lindgren
2006-11-21  7:06   ` Vladimir [this message]
2006-11-21  8:42     ` Komal Shah
2006-11-21 11:30       ` Pavel Machek
2006-11-21 15:04     ` James Simmons
2006-11-21 15:34       ` Komal Shah
2006-11-21 16:47         ` Tony Lindgren
2006-11-22 12:08           ` Imre Deák
2006-11-24 11:02   ` Pavel Machek
2006-11-28  2:15     ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ce55079f0611202306l3cd57e48t68fe28e7e076d39a@mail.gmail.com \
    --to=vovan888@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®