From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [RFC PATCH 3/5] pxa: clean up the legacy SSP API Date: Thu, 23 Apr 2009 09:24:49 +0100 Message-ID: <20090423082449.GC30105@sirena.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cassiel.sirena.org.uk (cassiel.sirena.org.uk [80.68.93.111]) by alsa0.perex.cz (Postfix) with ESMTP id DCE66103838 for ; Thu, 23 Apr 2009 10:24:49 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Eric Miao Cc: alsa-devel@alsa-project.org, Paul Shen , linux-arm-kernel , Philipp Zabel List-Id: alsa-devel@alsa-project.org 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. This looks fine to me Signed-off-by: Mark Brown