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 16:13:53 +0200	[thread overview]
Message-ID: <s5h62d3vhwe.wl%tiwai@suse.de> (raw)
In-Reply-To: <20120413140548.GF25425@zod.bos.redhat.com>

At Fri, 13 Apr 2012 10:05:49 -0400,
Josh Boyer wrote:
> 
> On Fri, Apr 13, 2012 at 03:41:53PM +0200, Takashi Iwai wrote:
> > At Fri, 13 Apr 2012 09:37:21 -0400,
> > Josh Boyer wrote:
> > 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.
> 
> You're referring to the inclusion of pin 0x19 or not here, right?

Yes.

> > 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.
> 
> I'm guessing when someone undocks the pins are reconfigured back to the
> jacks on the laptop itself somehow?

No, the configuration must be determined at the driver initialization
time.  So, the mixer elements stay unchanged with or without dock.
(For example, if the mixer elements were to change upon the
 dock/undock, this would be really confusing both for users and apps.
 In theory, it's possible to implement like that, but no one wants
 it.)

The jack-detection on the docking station works, yes, i.e. the
auto-muting or the mic changing works.  But it's different from
changing the configuration on the hotplug of docking station itself.


Takashi

  reply	other threads:[~2012-04-13 14:13 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
2012-04-13 14:05           ` Josh Boyer
2012-04-13 14:13             ` Takashi Iwai [this message]
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=s5h62d3vhwe.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®