From: Takashi Iwai Subject: Re: ASoC updates for 3.1 Date: Sun, 21 Aug 2011 18:25:53 +0200 Message-ID: References: <20110821120843.GA12673@opensource.wolfsonmicro.com> <20110821160006.GA13367@opensource.wolfsonmicro.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id B43C324436 for ; Sun, 21 Aug 2011 18:25:56 +0200 (CEST) In-Reply-To: <20110821160006.GA13367@opensource.wolfsonmicro.com> 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: Mark Brown Cc: alsa-devel@alsa-project.org, Liam Girdwood List-Id: alsa-devel@alsa-project.org At Sun, 21 Aug 2011 17:00:07 +0100, Mark Brown wrote: > > On Sun, Aug 21, 2011 at 03:47:45PM +0200, Takashi Iwai wrote: > > At Sun, 21 Aug 2011 13:08:43 +0100, > > Mark Brown wrote: > > > > The biggest change here is cleaning up the ad193x mess - there appear to > > > have been quite a few issues on top of the entertainment with the > > > register I/O. > > > Don't we need a similar fix for cs4271, too? > > Not to my knowledge, this is the first time I've heard anyone mention > it and nobody's reported any problems. Just no one has used 3.0 with the device, as usual :) If you look at a code, you'll see that it obviously has the very same problem as ad193x. Takashi