From: Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com>
To: ilpo.jarvinen@linux.intel.com
Cc: ayaanmirza788@gmail.com, josh@joshuagrisham.com,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: samsung-galaxybook: Handle ACPI hotkey notifications
Date: Tue, 24 Mar 2026 13:36:14 +0000 [thread overview]
Message-ID: <acKSyeHQT4GS8pp2@gb5> (raw)
In-Reply-To: <20260318054242.24747-1-ayaanmirzabaig85@gmail.com>
On Wed, Mar 18, 2026 at 05:42:42AM +0000, Ayaan Mirza Baig wrote:
> On Samsung Galaxy Book 5 (SAM0430), the keyboard backlight, microphone
> mute, and camera block hotkeys do not generate i8042 scancodes.
> Instead they arrive as ACPI notifications 0x7d, 0x63, and 0x6f
> respectively, all of which previously fell through to the deafult
> "unknown" warning in galaxybook_acpi_notify().
Hi Ilpo,
Just following up on this patch - I wanted to check if you had any
feedback on v2 or if there's anything I should revise further.
Happy to send a v3 if needed.
Thanks,
Ayaan
prev parent reply other threads:[~2026-03-24 8:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 19:33 [PATCH] platform/x86: samsung-galaxybook: Handle ACPI hotkey notifications Ayaan Mirza Baig
2026-03-17 12:36 ` Ilpo Järvinen
2026-03-18 5:42 ` [PATCH v2] " Ayaan Mirza Baig
2026-03-24 13:19 ` Ilpo Järvinen
2026-03-26 3:15 ` [PATCH v3] " Ayaan Mirza Baig
2026-04-03 13:04 ` Joshua Grisham
2026-04-03 15:56 ` [PATCH v4] " Joshua Grisham
2026-04-03 16:06 ` Joshua Grisham
2026-04-07 6:39 ` Ilpo Järvinen
2026-04-18 0:46 ` [PATCH v5 1/2] platform/x86: samsung-galaxybook: Refactor camera lens cover input device Ayaan Mirza Baig
2026-04-18 0:46 ` [PATCH v5 2/2] platform/x86: samsung-galaxybook: Handle ACPI hotkey notifications Ayaan Mirza Baig
2026-05-07 14:25 ` [PATCH v5 1/2] platform/x86: samsung-galaxybook: Refactor camera lens cover input device Ilpo Järvinen
2026-03-24 13:36 ` Ayaan Mirza Baig [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=acKSyeHQT4GS8pp2@gb5 \
--to=ayaanmirzabaig85@gmail.com \
--cc=ayaanmirza788@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=josh@joshuagrisham.com \
--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