From: Takashi Iwai <tiwai@suse.de>
To: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Cc: Raymond Yau <superquad.vortex2@gmail.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Pop noise on startup when headphones are plugged in (Dell XPS13 9333)
Date: Fri, 24 Apr 2015 17:34:57 +0200 [thread overview]
Message-ID: <s5h1tj9o7z2.wl-tiwai@suse.de> (raw)
In-Reply-To: <CABFtUbRvTL2tB3esKUoxYRLmbzQPwa8i+aDyqZkVnaEYXC_0Zg@mail.gmail.com>
At Fri, 24 Apr 2015 17:14:24 +0200,
Gabriele Mazzotta wrote:
>
> 2015-04-24 8:13 GMT+02:00 Takashi Iwai <tiwai@suse.de>:
> > At Thu, 23 Apr 2015 21:12:50 +0200,
> > Gabriele Mazzotta wrote:
> >>
> >> On Sunday 19 April 2015 19:26:58 Gabriele Mazzotta wrote:
> >> > Hi,
> >> >
> >> > I've recently found that commit a551d91473 ("ALSA: hda - Use regmap for
> >> > command verb caches, too") is somehow causing a pop noise on startup
> >> > when headphones are plugged in, but I couldn't figure out the exact
> >> > cause. Was this observed on other systems (mine is a Dell XPS13 9333,
> >> > Realtek ALC3661)? Does anyone have any idea of what the cause might be?
> >>
> >> Hi,
> >>
> >> I don't know why a551d91473 caused the issue, but I found the real
> >> cause of problem.
> >>
> >> On init, create_input_ctls() sets the vref of nid 0x19 to 80 (as
> >> returned by snd_hda_get_default_vref()), but it should be set to HIZ.
> >> This is not so different from the issue addressed by f38663ab5c
> >> ("ALSA: hda - Set internal mic as default input source on Dell XPS 13 9333").
> >>
> >> I made a patch to prevent this from happening.
> >>
> >> Setting the vref is not necessary since alc_update_headset_mode() will
> >> take care of it.
> >>
> >> Should I maybe add a new flag instead of using suppress_hp_mic_detect?
> >
> > Yeah, that's better. Although the flag is currently unused, it's
> > provided for a different purpose (to skip the headphone mic detection;
> > which is different from "headset" mic).
> >
> > I wonder, though, whether the patch below improves anything.
> > A similar patch was in the development series in the past, but I had
> > to drop it because it caused behavior error. But now I tried again,
> > and it seems working.
> >
> >
> > Takashi
>
> The patch did no harm, but didn't solve the problem.
OK, so the problem doesn't seem relevant with the runtime PM, which
was the usual suspect.
My patch should reduce the actual verb writes, so it would be nice to
have even if it doesn't fix your problem. But maybe I'll postpone it
as a 4.2 material.
thanks,
Takashi
next prev parent reply other threads:[~2015-04-24 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 17:26 Pop noise on startup when headphones are plugged in (Dell XPS13 9333) Gabriele Mazzotta
2015-04-20 5:58 ` Takashi Iwai
2015-04-20 7:18 ` Takashi Iwai
2015-04-20 19:51 ` Gabriele Mazzotta
2015-04-20 19:49 ` Gabriele Mazzotta
2015-04-21 2:13 ` Raymond Yau
2015-04-21 9:50 ` Gabriele Mazzotta
2015-04-21 9:58 ` Gabriele Mazzotta
2015-04-21 10:04 ` Takashi Iwai
2015-04-23 19:12 ` Gabriele Mazzotta
2015-04-24 6:13 ` Takashi Iwai
2015-04-24 15:14 ` Gabriele Mazzotta
2015-04-24 15:34 ` Takashi Iwai [this message]
2015-04-25 11:51 ` Gabriele Mazzotta
2015-04-25 13:57 ` Gabriele Mazzotta
2015-04-26 16:26 ` Takashi Iwai
2015-04-26 17:05 ` Gabriele Mazzotta
2015-04-27 8: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=s5h1tj9o7z2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=gabriele.mzt@gmail.com \
--cc=superquad.vortex2@gmail.com \
/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