From: Josh Boyer <jwboyer@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
kernel-team@fedoraproject.org
Subject: Re: Thinkpad hda regression in 3.3
Date: Fri, 13 Apr 2012 14:08:14 -0400 [thread overview]
Message-ID: <20120413180814.GG25425@zod.bos.redhat.com> (raw)
In-Reply-To: <s5hk41jty24.wl%tiwai@suse.de>
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?
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.
josh
next prev parent reply other threads:[~2012-04-13 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 12:43 Thinkpad hda regression in 3.3 Josh Boyer
2012-04-13 13:07 ` Takashi Iwai
2012-04-13 13:23 ` Josh Boyer
2012-04-13 13:29 ` Takashi Iwai
2012-04-13 13:37 ` Josh Boyer
2012-04-13 13:41 ` Takashi Iwai
2012-04-13 14:05 ` Josh Boyer
2012-04-13 14:13 ` Takashi Iwai
2012-04-13 13:26 ` Takashi Iwai
2012-04-13 16:07 ` Takashi Iwai
2012-04-13 18:08 ` Josh Boyer [this message]
2012-04-13 19:21 ` Takashi Iwai
2012-04-18 0:23 ` Josh Boyer
2012-04-18 5:49 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120413180814.GG25425@zod.bos.redhat.com \
--to=jwboyer@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).