mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Josh Boyer <jwboyer@redhat.com>
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 15:41:53 +0200	[thread overview]
Message-ID: <s5hd37bvjdq.wl%tiwai@suse.de> (raw)
In-Reply-To: <20120413133721.GE25425@zod.bos.redhat.com>

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

  reply	other threads:[~2012-04-13 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 12:43 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 [this message]
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
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=s5hd37bvjdq.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jwboyer@redhat.com \
    --cc=kernel-team@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    /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

all inboxes | Powered by JetHome®