diff options
| author | Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com> | 2026-04-18 00:46:14 +0000 |
|---|---|---|
| committer | Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> | 2026-05-07 14:36:20 +0300 |
| commit | 90dc96c61be35a1f81b56dfc5dcb80d50debbf89 (patch) | |
| tree | 82e5df59ddc6074acf2a7852f4359309e6f0a9fe /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | 72d52bac023b376b73277804b24315ea2a49ad1e (diff) | |
| download | linux-90dc96c61be35a1f81b56dfc5dcb80d50debbf89.tar.gz linux-90dc96c61be35a1f81b56dfc5dcb80d50debbf89.zip | |
platform/x86: samsung-galaxybook: Handle ACPI hotkey notifications
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, 0x6e, and 0x6f
respectively, all of which previously fell through to the default
"unknown" warning in galaxybook_acpi_notify().
Add handling for these three events:
- 0x7d (Fn+F9, keyboard backlight): schedule the existing
kbd_backlight_hotkey_work which cycles brightness.
- 0x6e (Fn+F10, microphone mute): emit KEY_MICMUTE via the driver's
input device.
- 0x6f (Fn+F11, camera block): if block_recording is active use the
existing block_recording_hotkey_work; otherwise emit a toggle of
SW_CAMERA_LENS_COVER via the driver's input device on models where
the block_recording ACPI feature is not supported.
Tested on Samsung Galaxy Book 5 (SAM0430) and Samsung Galaxy Book2 Pro
(SAM0429).
Signed-off-by: Ayaan Mirza Baig <ayaanmirzabaig85@gmail.com>
Co-developed-by: Joshua Grisham <josh@joshuagrisham.com>
Signed-off-by: Joshua Grisham <josh@joshuagrisham.com>
Link: https://patch.msgid.link/20260418004613.93981-3-ayaanmirzabaig85@gmail.com
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions