In message <[EMAIL PROTECTED]> you wrote:
> From: Haavard Skinnemoen <[EMAIL PROTECTED]>
>
> This patch gets rid of the spi_chipsel table and adds a handful of new
> functions that makes the SPI layer cleaner and more flexible.
...
> Signed-off-by: Haavard Skinnemoen <[EMAIL PROTECTED]>
> ---
> b
On Sat, 17 May 2008 12:56:00 +0200
Jean-Christophe PLAGNIOL-VILLARD <[EMAIL PROTECTED]> wrote:
> You've forget ds1722 and AMD Elan cpu which use SPI too
I don't think so. ds1722 uses some sort of home-grown API which I don't
want anything to do with.
Elan seems to be using a different API too...
You've forget ds1722 and AMD Elan cpu which use SPI too
Best Regards,
J.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/dire
On Fri, 16 May 2008, Haavard Skinnemoen wrote:
> The purpose of the spi_xfer flags parameter isn't to gang together
> multiple transfers -- it's to allow more precise chip select control so
> that you can split a transfer into multiple spi_xfer() calls. This is
> useful for devices where you typic
On Fri, 16 May 2008 12:41:04 +0200 (CEST)
Guennadi Liakhovetski <[EMAIL PROTECTED]> wrote:
> On Fri, 16 May 2008, Haavard Skinnemoen wrote:
>
> > From: Haavard Skinnemoen <[EMAIL PROTECTED]>
> >
> > This patch gets rid of the spi_chipsel table and adds a handful of new
> > functions that makes t
On Fri, 16 May 2008, Haavard Skinnemoen wrote:
> From: Haavard Skinnemoen <[EMAIL PROTECTED]>
>
> This patch gets rid of the spi_chipsel table and adds a handful of new
> functions that makes the SPI layer cleaner and more flexible.
Ok, this looks good to me now. And it works too. Just one quest
From: Haavard Skinnemoen <[EMAIL PROTECTED]>
This patch gets rid of the spi_chipsel table and adds a handful of new
functions that makes the SPI layer cleaner and more flexible.
Instead of the spi_chipsel table, each board that wants to use SPI
gets to implement three hooks:
* spi_cs_activate()
