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

From: Eric Miao <eric.y.miao@gmail.com>
To: Daniel Ribeiro <drwyrm@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	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>
Subject: Re: [RFC PATCH 3/5] pxa: clean up the legacy SSP API
Date: Wed, 29 Apr 2009 10:18:32 +0800	[thread overview]
Message-ID: <f17812d70904281918p7a69fd03hd2fd51b1eb024b2@mail.gmail.com> (raw)
In-Reply-To: <1240959968.30410.1.camel@brutus>

On Wed, Apr 29, 2009 at 7:06 AM, Daniel Ribeiro <drwyrm@gmail.com> wrote:
> Em Ter, 2009-04-28 às 23:20 +0100, Russell King - ARM Linux escreveu:
>> On Thu, Apr 23, 2009 at 01:06:12PM +0800, Eric Miao wrote:
>> > Actually, due to the number of possible SSP configurations, it's quite a
>> > difficult job to maintain an API that can be well re-used. The guideline
>> > here is to keep only a list of SSP devices and their basic information,
>> > and it's up to the user driver (like SPI or Audio SSP) to configure the
>> > SSP in a desired way.
>>
>> Hmm, the LX battery driver uses this API for its rudimentary battery
>> communication channel with the PCON.
>>
>> What are you suggesting as the replacement API?  Direct register access?
>
> The SPI subsystem?
>

Yeah, I looked into the patch a bit. It looks like the SSP configuration
falls into the SPI subystem quite well.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel