From: Takashi Iwai <tiwai@suse.de>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
David Henningsson <david.henningsson@canonical.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek - Keep analog bypass muted on ALC892
Date: Thu, 09 Aug 2012 09:02:10 +0200 [thread overview]
Message-ID: <s5hfw7wfszx.wl%tiwai@suse.de> (raw)
In-Reply-To: <1344494839-6942-1-git-send-email-thierry.reding@avionic-design.de>
At Thu, 9 Aug 2012 08:47:19 +0200,
Thierry Reding wrote:
>
> Unmuting the analog bypass causes any input to be directly bypassed to
> the outputs, which is usually not expected by the user.
>
> Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
> ---
> Note that this patch could be generalized to include all codec variants
> that have this second channel. As I don't have access to all the data
> sheets I'll leave that decision up to somebody with more hardware
> available.
Hmm, are you really sure that this is exclusive switch between two?
All Realtek codecs with this mixer widget mixes two sources up.
Otherwise it must not be a "mixer" widget at all but it must be a
"selector" widget.
And I haven't received a bug report regarding this although ALC892 is
no new chip and the auto-parser has been enabled for so long time.
thanks,
Takashi
>
> sound/pci/hda/patch_realtek.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> index 4f81dd4..54d0917 100644
> --- a/sound/pci/hda/patch_realtek.c
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -3752,8 +3752,15 @@ static void alc_auto_set_output_and_unmute(struct hda_codec *codec,
> if (nid_has_mute(codec, mix, HDA_INPUT)) {
> snd_hda_codec_write(codec, mix, 0, AC_VERB_SET_AMP_GAIN_MUTE,
> AMP_IN_UNMUTE(0));
> - snd_hda_codec_write(codec, mix, 0, AC_VERB_SET_AMP_GAIN_MUTE,
> - AMP_IN_UNMUTE(1));
> + /*
> + * On ALC892, the second entry in the connection list is the
> + * analog bypass. Unmuting it will cause any inputs to be
> + * directly forwarded to the corresponding outputs.
> + */
> + if (codec->subsystem_id != 0x10ec0892)
> + snd_hda_codec_write(codec, mix, 0,
> + AC_VERB_SET_AMP_GAIN_MUTE,
> + AMP_IN_UNMUTE(1));
> }
> /* initialize volume */
> nid = alc_look_for_out_vol_nid(codec, pin, dac);
> --
> 1.7.11.4
>
next prev parent reply other threads:[~2012-08-09 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 6:47 Thierry Reding
2012-08-09 7:02 ` Takashi Iwai [this message]
2012-08-09 7:18 ` Thierry Reding
2012-08-09 7:33 ` Takashi Iwai
2012-08-09 7:51 ` Thierry Reding
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=s5hfw7wfszx.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=thierry.reding@avionic-design.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
all inboxes | Powered by JetHome®