From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222044] hp-wmi: Mute and mic-mute LEDs not supported on HP Laptop 15-fc0xxx (board 8DC9)
Date: Fri, 09 Oct 2026 17:55:53 +0000 [thread overview]
Message-ID: <bug-222044-215701-UHOmPiIfvU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222044-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222044
--- Comment #8 from Piyush (neonblade018@proton.me) ---
Hi Zhang,
I built and tested kernel 7.2.9 with those two chaining lines added to
ALC236_FIXUP_HP_DMIC:
.chained = true,
.chain_id = ALC236_FIXUP_HP_MUTE_LED_MICMUTE_GPIO
It works perfectly!
Both LEDs registered under `/sys/class/leds/` as `hda::mute` and `hda::micmute`
with native kernel triggers `[audio-mute]` and `[audio-micmute]`. Both the
speaker mute LED and the mic-mute LED now toggle instantly in hardware on audio
state changes without needing any userland workarounds.
The internal digital microphone is also fully detected and functional via
ALSA/PipeWire.
You can consider this tested and verified working on my hardware. Thanks a lot
for the fix!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-10-09 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 15:05 [Bug 222044] New: hp-wmi: Mute and mic-mute LEDs not supported on HP Laptop 15-fc0xxx (board 8DC9) bugzilla-daemon
2026-09-24 18:42 ` [Bug 222044] " bugzilla-daemon
2026-09-25 2:06 ` bugzilla-daemon
2026-10-06 9:50 ` bugzilla-daemon
2026-10-06 10:27 ` bugzilla-daemon
2026-10-07 6:44 ` bugzilla-daemon
2026-10-07 7:12 ` bugzilla-daemon
2026-10-07 7:12 ` bugzilla-daemon
2026-10-07 7:12 ` bugzilla-daemon
2026-10-09 1:46 ` bugzilla-daemon
2026-10-09 17:55 ` bugzilla-daemon [this message]
2026-10-09 17:59 ` bugzilla-daemon
2026-10-09 18:01 ` bugzilla-daemon
2026-10-10 10:14 ` bugzilla-daemon
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=bug-222044-215701-UHOmPiIfvU@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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.