From: Ruzal Daminov <daminovruzal7@gmail.com>
To: ilpo.jarvinen@linux.intel.com, hansg@kernel.org
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ruzal Daminov <daminovruzal7@gmail.com>
Subject: [PATCH v2] platform/x86: huawei-wmi: add camera toggle keycode
Date: Wed, 19 Aug 2026 11:38:36 +0300 [thread overview]
Message-ID: <20260819083836.1410-1-daminovruzal7@gmail.com> (raw)
In-Reply-To: <20260814171324.16727-1-daminovruzal7@gmail.com>
Honor MagicBook laptops emit WMI event code 0x288 when pressing the
camera e-shutter / privacy toggle key (Fn+F8 on Honor).
Add the missing 0x288 keycode to huawei_wmi_keymap[] in correct numerical
order and map it to KEY_CAMERA_ACCESS_TOGGLE.
Tested on Honor MagicBook X14 Plus (FMI-76, AMD Ryzen 8845HS).
Signed-off-by: Ruzal Daminov <daminovruzal7@gmail.com>
---
v2:
- Drop duplicate keys already present in the table.
- Remove leading zeros to match existing table style.
- Place 0x288 in correct numerical order.
- Map 0x288 to KEY_CAMERA_ACCESS_TOGGLE.
drivers/platform/x86/huawei-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/huawei-wmi.c b/drivers/platform/x86/huawei-wmi.c
index 93cca17fdf5868..b5463edc4053d4 100644
--- a/drivers/platform/x86/huawei-wmi.c
+++ b/drivers/platform/x86/huawei-wmi.c
@@ -78,6 +78,7 @@ static const struct key_entry huawei_wmi_keymap[] = {
{ KE_KEY, 0x285, { KEY_VOLUMEDOWN } },
{ KE_KEY, 0x286, { KEY_VOLUMEUP } },
{ KE_KEY, 0x287, { KEY_MICMUTE } },
+ { KE_KEY, 0x288, { KEY_CAMERA_ACCESS_TOGGLE } },
{ KE_KEY, 0x289, { KEY_WLAN } },
// Huawei |M| key
{ KE_KEY, 0x28a, { KEY_CONFIG } },
--
2.45.2
prev parent reply other threads:[~2026-08-19 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 17:13 [PATCH 2/2] platform/x86: huawei-wmi: add modern Honor MagicBook hotkeys Ruzal Daminov
2026-08-18 10:26 ` Ilpo Järvinen
2026-08-19 8:38 ` Ruzal Daminov [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=20260819083836.1410-1-daminovruzal7@gmail.com \
--to=daminovruzal7@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®