Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hui Wang <hui.wang@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, david.henningsson@canonical.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda - Prevent speaker from entering automute on some AIO models
Date: Tue, 14 Jan 2014 13:50:21 +0800	[thread overview]
Message-ID: <52D4D01D.5010203@canonical.com> (raw)
In-Reply-To: <s5h38ksw68l.wl%tiwai@suse.de>

On 01/13/2014 06:01 PM, Takashi Iwai wrote:
> At Mon, 13 Jan 2014 14:52:27 +0800,
> Hui Wang wrote:
>> On some AIO (All In One) models with the codec alc668
>> (Vendor ID: 0x10ec0668) on it, when we plug a headphone into the jack,
>> the system will switch the output to headphone and set the speaker to
>> automute as well as change the speaker Pin-ctls from 0x40 to 0x00,
>> this will bring loud noise to the headphone.
>>
>> I tried to disable the corresponding EAPD, but it did not help to
>> eliminate the noise.
>>
>> So far, the only way to eliminate the noise is preventing the speaker
>> from entering automute.
>>
>> BugLink: https://bugs.launchpad.net/bugs/1268468
>> Cc: David Henningsson <david.henningsson@canonical.com>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Hui Wang <hui.wang@canonical.com>
> What about to use auto_mute_via_amp flag instead like the patch below?
>
>
>
Test has been done on the three AIO models, auto_mute_via_amp flag can 
eliminate the noise and fix the problem.

I am going to send a v2 patch to use auto_mute_via_amp to replace 
suppress_auto_mute.


Thanks,
Hui.

      parent reply	other threads:[~2014-01-14  5:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  6:52 [PATCH] ALSA: hda - Prevent speaker from entering automute on some AIO models Hui Wang
2014-01-13 10:01 ` Takashi Iwai
2014-01-13 10:15   ` Hui Wang
2014-01-14  5:50   ` Hui Wang [this message]

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=52D4D01D.5010203@canonical.com \
    --to=hui.wang@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=stable@vger.kernel.org \
    --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