From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216824] Some laptop hotkeys don't work
Date: Wed, 21 Dec 2022 15:51:06 +0000 [thread overview]
Message-ID: <bug-216824-215701-rtdb4LHV9a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216824-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216824
--- Comment #14 from André Barata (andretiagob@protonmail.com) ---
(In reply to Hans de Goede from comment #13)
> Good to hear that the hotkeys work now.
>
> As for the mic/speaker mute LEDs, those are tricky. They can be either
> attached to the embedded-controller and then we would need support to
> register them under /sys/class/leds with their default triggers setup
> correctly, after which the kernel's HDA code shoould control them for us.
>
> Or they may be directly connected to some GPIOs on the HDA part of the main
> SoC or on the codec.
>
> And the Fn-lock LED typically just works automatically (controller by the
> EC) if you toggle the Fn-lock by pressing Fn + escape? Although sometimes
> it too needs to be controller in software.
>
> Figuring out the LEDs really requires someone with significant hw-enablement
> experience to actually have the laptop in their hands and then they will
> hopefully be able to figure things out.
>
> I have submitted the fixes for the hotkeys upstream here:
> https://github.com/systemd/systemd/pull/25824
Yeah if i FN + Escape tu led turns on :)
Well, what mattered was the hotkeys themselves and they are working now!
Thank you Hans!
--
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:[~2022-12-21 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 22:32 [Bug 216824] New: Some laptop hotkeys don't work bugzilla-daemon
2022-12-20 22:32 ` [Bug 216824] " bugzilla-daemon
2022-12-20 22:33 ` bugzilla-daemon
2022-12-20 22:33 ` bugzilla-daemon
2022-12-21 11:38 ` bugzilla-daemon
2022-12-21 11:38 ` bugzilla-daemon
2022-12-21 11:45 ` bugzilla-daemon
2022-12-21 12:12 ` bugzilla-daemon
2022-12-21 12:50 ` bugzilla-daemon
2022-12-21 13:00 ` bugzilla-daemon
2022-12-21 13:18 ` bugzilla-daemon
2022-12-21 13:18 ` bugzilla-daemon
2022-12-21 13:18 ` bugzilla-daemon
2022-12-21 15:33 ` bugzilla-daemon
2022-12-21 15:51 ` bugzilla-daemon [this message]
2023-03-22 13:58 ` bugzilla-daemon
2023-03-27 13:31 ` bugzilla-daemon
2023-03-27 13:43 ` bugzilla-daemon
2023-03-27 13:45 ` bugzilla-daemon
2023-03-27 14:05 ` bugzilla-daemon
2023-03-27 14:13 ` bugzilla-daemon
2023-03-27 14:36 ` bugzilla-daemon
2023-03-27 14:40 ` bugzilla-daemon
2023-03-27 14:41 ` bugzilla-daemon
2023-03-27 14:41 ` bugzilla-daemon
2023-03-27 14:50 ` 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-216824-215701-rtdb4LHV9a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox