All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zhang Heng <zhangheng@kylinos.cn>
Cc: perex@perex.cz, tiwai@suse.com, sbinding@opensource.cirrus.com,
	kailang@realtek.com, chris.chiu@canonical.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: add quirk for Acer Nitro ANV15-51
Date: Mon, 09 Feb 2026 16:07:06 +0100	[thread overview]
Message-ID: <87bjhy0xd1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260209134149.3076957-1-zhangheng@kylinos.cn>

On Mon, 09 Feb 2026 14:41:49 +0100,
Zhang Heng wrote:
> 
> fix mute/micmute LEDs and headset microphone for Acer Nitro ANV15-51.
> 
> [ The headset microphone issue is solved by Kailang]
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=220279
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Zhang Heng <zhangheng@kylinos.cn>
> ---
> There is a small issue now, the mute LED stays on when I mute the
> laptop microphone, unmute the headphone microphone, and set the
> headphone mic as default. Is it possible to fix this?

Can LED be controlled dynamically by writing to a sysfs file in
/sys/class/leds/*? e.g.

  % cat /sys/class/leds/platform::micmute/brightness
  1
  % echo 0 > /sys/class/leds/platform::micmute/brightness

If the direct write changes the actual LED status, it's not about the
sound driver problem, but possibly some plumbing in user-space via
UCM, etc.


thanks,

Takashi

  reply	other threads:[~2026-02-09 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 13:41 [PATCH] ALSA: hda/realtek: add quirk for Acer Nitro ANV15-51 Zhang Heng
2026-02-09 15:07 ` Takashi Iwai [this message]
2026-02-26  1:43   ` zhangheng
2026-02-26  6:33     ` 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=87bjhy0xd1.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=chris.chiu@canonical.com \
    --cc=kailang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sbinding@opensource.cirrus.com \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=zhangheng@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.