From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Problem with MX27 ASoC audio Date: Wed, 18 Aug 2010 10:02:23 +0100 Message-ID: <20100818090223.GD26804@opensource.wolfsonmicro.com> References: <20100812125625.GA27749@pengutronix.de> <20100812150145.GC11362@sirena.org.uk> <4C690693.80706@eukrea.com> <20100818084137.GA26804@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 8B51324463 for ; Wed, 18 Aug 2010 11:02:06 +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: Randolph Chung Cc: alsa-devel@alsa-project.org, Sascha Hauer , Eric =?iso-8859-1?Q?B=E9nard?= List-Id: alsa-devel@alsa-project.org On Wed, Aug 18, 2010 at 04:58:12PM +0800, Randolph Chung wrote: > The codec (at least the variant of tlv320aic3x that I am using) can > have two pins in the hardware, but it's up to the board whether it's > hooked up that way. The codec driver as currently implemented assumes > the rates are symmetric, but it need not be. In that case the driver should be setting the symmetric_rates flag anyway since it does have this constraint - if it implements support for asymmetric rates then the flag can be removed then. > I see that there is a symmetric_rates flag for the dai_link too. This is still a good idea if your board has a single LRCLK anyway in case someone does do asymmetric rates.