From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Thinkpad hda regression in 3.3 Date: Fri, 13 Apr 2012 21:21:46 +0200 Message-ID: References: <20120413124306.GC25425@zod.bos.redhat.com> <20120413180814.GG25425@zod.bos.redhat.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 9F381104481 for ; Fri, 13 Apr 2012 21:21:47 +0200 (CEST) In-Reply-To: <20120413180814.GG25425@zod.bos.redhat.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: Josh Boyer Cc: kernel-team@fedoraproject.org, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org List-Id: alsa-devel@alsa-project.org At Fri, 13 Apr 2012 14:08:14 -0400, Josh Boyer wrote: > > On Fri, Apr 13, 2012 at 06:07:47PM +0200, Takashi Iwai wrote: > > At Fri, 13 Apr 2012 15:07:07 +0200, > > Takashi Iwai wrote: > > (snip) > > > If the above seem work (again, make sure that you adjust the mixer > > > mutes and levels), I'll make kernel patches to add these fixups > > > statically in the driver so that it works without extra patching. > > > > Looking through alsa-info.sh outputs from various ThinkPad models I've > > gathered, it seems that we can use the same pin setups for all. > > We had a user try the alsa-tp-dock patch on an X201 and it didn't seem > to work for them. See bug > https://bugzilla.redhat.com/show_bug.cgi?id=806217 > > Perhaps the [codec] section isn't set properly for their configuration? Right. This must match with the actual values. Or the recent driver accepts 0 as the the second value. > The alsa-info for their machine is in comment #9 of the bug. > > > Below is a test patch for 3.3 kernel. (Note that it'd give a merge > > conflict for 3.4 kernel.) > > OK, I'll do a scratch build with this and get people to test. In that case, check whether the reported machines have the corresponding PCI SSIDs. thanks, Takashi