Re: [RFC PATCH 3/5] pxa: clean up the legacy SSP API

From: Eric Miao <eric.y.miao@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@sirena.org.uk>,
	Philipp Zabel <philipp.zabel@gmail.com>,
	Paul Shen <bshen9@marvell.com>,
	linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
	Daniel Ribeiro <drwyrm@gmail.com>
Subject: Re: [RFC PATCH 3/5] pxa: clean up the legacy SSP API
Date: Wed, 29 Apr 2009 17:14:13 +0800	[thread overview]
Message-ID: <f17812d70904290214g110f2a5ax5da4af478688f3d1@mail.gmail.com> (raw)
In-Reply-To: <20090429084109.GB10541@n2100.arm.linux.org.uk>

On Wed, Apr 29, 2009 at 4:41 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Wed, Apr 29, 2009 at 09:21:53AM +0100, Mark Brown wrote:
>> On Wed, Apr 29, 2009 at 08:27:06AM +0100, Russell King - ARM Linux wrote:
>> > On Tue, Apr 28, 2009 at 08:06:08PM -0300, Daniel Ribeiro wrote:
>>
>> > > The SPI subsystem?
>>
>> > Can the SPI system cope with the other chip being the master of the
>> > interface.  In other words, can SPI sit around primed for a transfer,
>> > and notify the user of SPI that new data has arrived?
>>
>> > If not, the SPI subsystem is totally unsuitable for this.
>>
>> It's slave only at the minute - there's holes in the API someone could
>> fill in but that's not happened yet.
>
> Well, I guess someone else will have to do that; I don't spend much time
> on the LX stuff, and so if it requires any time consuming work, it won't
> be worth trying to get it into mainline.
>

However, the patch itself doesn't looks like to be a SPI slave
(I mean from the view of the processor).

'struct spi_message' does support simultaneous rx/tx transfer
and multiple such transfers being queued.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel