public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Luka Guzenko <l.guzenko@web.de>
Cc: tiwai@suse.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Enable mute/micmute LEDs on HP Spectre x360 13-aw0xxx
Date: Tue, 10 Jan 2023 09:36:37 +0100	[thread overview]
Message-ID: <87k01ueqga.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230109235840.26452-1-l.guzenko@web.de>

On Tue, 10 Jan 2023 00:58:40 +0100,
Luka Guzenko wrote:
> 
> The HP Spectre x360 13-aw0xxx devices use the ALC285 codec with GPIO 0x04
> controlling the micmute LED and COEF 0x0b index 8 controlling the mute LED.
> A quirk was added to make these work as well as a fixup entry.
> 
> Signed-off-by: Luka Guzenko <l.guzenko@web.de>
> ---
>  sound/pci/hda/patch_realtek.c | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)
> 
> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> index 3794b522c222..6a76a2eddd3c 100644
> --- a/sound/pci/hda/patch_realtek.c
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -4644,6 +4644,16 @@ static void alc285_fixup_hp_coef_micmute_led(struct hda_codec *codec,
>  	}
>  }
> 
> +static void alc285_fixup_hp_gpio_micmute_led(struct hda_codec *codec,
> +				const struct hda_fixup *fix, int action)
> +{
> +	struct alc_spec *spec = codec->spec;
> +
> +	if (action != HDA_FIXUP_ACT_PRE_PROBE)
> +		spec->micmute_led_polarity = 1;

Is this condition correct?  It's usually other way round; a flag is
set up only once at parsing.


thanks,

Takashi

      reply	other threads:[~2023-01-10  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 23:58 [PATCH] ALSA: hda/realtek: Enable mute/micmute LEDs on HP Spectre x360 13-aw0xxx Luka Guzenko
2023-01-10  8:36 ` 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=87k01ueqga.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=l.guzenko@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --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