linux-kernel - Re: Thinkpad hda regression in 3.3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hd37bvjdq.wl%tiwai@suse.de>
Date:	Fri, 13 Apr 2012 15:41:53 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org, kernel-team@...oraproject.org
Subject: Re: Thinkpad hda regression in 3.3

At Fri, 13 Apr 2012 09:37:21 -0400,
Josh Boyer wrote:
> 
> On Fri, Apr 13, 2012 at 03:29:41PM +0200, Takashi Iwai wrote:
> > At Fri, 13 Apr 2012 09:23:52 -0400,
> > Josh Boyer wrote:
> > > > The problem regarding the docking station is basically a BIOS issue.
> > > > ThinkPad BIOS doesn't expose the pins for docking stations at all.
> > > > We have already a workaround for X200, and similar others would be
> > > > needed for T410, T420, etc.
> > > > 
> > > > For testing, you don't need even patch the driver.  When the driver is
> > > > built with CONFIG_SND_HDA_PATCH_LOADER=y, create a file containing the
> > > > below as /lib/firmware/alsa-tp-dock:
> > > > 
> > > > ================================================================
> > > > [codec]
> > > > 0x14f15069 0x17aa21a4 0
> > > > 
> > > > [pincfg]
> > > > 0x1a 0x21a11000
> > > > 0x1c 0x23014250
> > > > ================================================================
> > > 
> > > The above is for the X200 docking station, correct?  So it should work
> > > with an x201 thinkpad in an x200 dock.
> > 
> > It's for T410/T510 dock.  But X201 uses the same codec chip, so this
> > could be used, too.  Just give it a try.
> 
> OK.  I've asked a reporter to test this out.  We'll get back to you.

Thanks.  As mentionted, the difference between two setups (sent in two
posts) is seen in the mixer setup.  I personally don't mind which
setup is taken; it's rather a choice of users.  So, let me know which
setup is preferred by testers.

The reason behind such multiple setups is that the codec chip has only
two DACs while you want to access for three or more outputs (two
headphones, one speaker, etc).  Thus some outputs must share the same
DAC.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/