From: Takashi Iwai <tiwai@suse.de>
To: <bo.liu@senarytech.com>
Cc: "'Takashi Iwai'" <tiwai@suse.de>, <perex@perex.cz>,
<tiwai@suse.com>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <feng.liu@senarytech.com>
Subject: Re: 答复: [PATCH V2] ALSA: hda/conexant: fix Z60MR100 startup pop issue
Date: Thu, 28 Nov 2024 09:28:35 +0100 [thread overview]
Message-ID: <87wmgn4v9o.wl-tiwai@suse.de> (raw)
In-Reply-To: <022d01db416f$116441c0$342cc540$@senarytech.com>
On Thu, 28 Nov 2024 09:25:22 +0100,
<bo.liu@senarytech.com> wrote:
>
> > On Thu, 28 Nov 2024 07:08:12 +0100,
> > bo liu wrote:
> > >
> > > When Z60MR100 startup, speaker will output a pop. To fix this issue,
> > > we mute codec by init verbs in bios when system startup, and set GPIO
> > > to low to unmute codec in codec driver when it loaded .
> > >
> > > Signed-off-by: bo liu <bo.liu@senarytech.com>
> > > ---
> > > sound/pci/hda/patch_conexant.c | 35
> > > ++++++++++++++++++++++++++++++++++
> > > 1 file changed, 35 insertions(+)
> > >
> > > diff --git a/sound/pci/hda/patch_conexant.c
> > > b/sound/pci/hda/patch_conexant.c index e851785ff058..62c53e64bcad
> > > 100644
> > > --- a/sound/pci/hda/patch_conexant.c
> > > +++ b/sound/pci/hda/patch_conexant.c
> > > @@ -42,6 +42,7 @@ struct conexant_spec {
> > > unsigned int gpio_led;
> > > unsigned int gpio_mute_led_mask;
> > > unsigned int gpio_mic_led_mask;
> > > + unsigned int gpio_unmute_bit_mask;
> > > bool is_cx8070_sn6140;
> > > };
> > >
> > > @@ -308,6 +309,7 @@ enum {
> > > CXT_FIXUP_HP_MIC_NO_PRESENCE,
> > > CXT_PINCFG_SWS_JS201D,
> > > CXT_PINCFG_TOP_SPEAKER,
> > > + CXT_FIXUP_HP_A_U,
> > > };
> > >
> > > /* for hda_fixup_thinkpad_acpi() */
> > > @@ -762,6 +764,24 @@ static void cxt_setup_mute_led(struct hda_codec
> *codec,
> > > }
> > > }
> > >
> > > +static void cxt_setup_mute_gpio_and_unmute(struct hda_codec *codec,
> > > + unsigned int gpio_mute_mask)
> > > +{
> > > + struct conexant_spec *spec = codec->spec;
> > > +
> > > + if (gpio_mute_mask) {
> > > + spec->gpio_unmute_bit_mask = gpio_mute_mask;
> >
> > Any reason to store this in spec? As far as I see the code below, it's
> used only locally here, so it doesn't have to be stored there.
>
> The purpose of adding this is to differentiate the configuration of the
> LED_MUTE GPIO and to retain debugging information. Of course, this field can
> be removed if desired.
Yes, please remove.
Takashi
prev parent reply other threads:[~2024-11-28 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 6:08 [PATCH V2] ALSA: hda/conexant: fix Z60MR100 startup pop issue bo liu
2024-11-28 7:13 ` Takashi Iwai
2024-11-28 8:25 ` 答复: " bo.liu
2024-11-28 8:28 ` Takashi Iwai [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=87wmgn4v9o.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=bo.liu@senarytech.com \
--cc=feng.liu@senarytech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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