All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ruzal Daminov <daminovruzal7@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] platform/x86: huawei-wmi: add modern Honor MagicBook hotkeys
Date: Tue, 18 Aug 2026 13:26:26 +0300 (EEST)	[thread overview]
Message-ID: <13b32041-0e33-367e-732a-1b8431c7628c@linux.intel.com> (raw)
In-Reply-To: <20260814171324.16727-1-daminovruzal7@gmail.com>

On Fri, 14 Aug 2026, Ruzal Daminov wrote:

> Honor MagicBook laptops (e.g. FMI-76 / X14 / X16 Plus series) use the
> ACPI WMI interface (GUID 0xA0) with modern function key scancodes.
> 
> Add the missing keycodes to huawei_wmi_keymap[]:
>  - 0x0287: Mic mute key (Fn+F7) -> KEY_MICMUTE
>  - 0x0288: Camera toggle (Fn+F8) -> KEY_CAMERA
>  - 0x028a: Honor Connect / Share (Fn+F10) -> KEY_CONFIG
>  - 0x028b: YOYO AI Assistant (Fn+F11) -> KEY_VOICECOMMAND
>  - 0x028e: Screenshot key (Fn+F12) -> KEY_PRINT
> 
> Tested on Honor MagicBook X14 Plus (FMI-76, AMD Ryzen 8845HS).
> 
> Signed-off-by: Ruzal Daminov <daminovruzal7@gmail.com>
> ---
>  drivers/platform/x86/huawei-wmi.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/platform/x86/huawei-wmi.c b/drivers/platform/x86/huawei-wmi.c
> index 93cca17fd..d5f77fb68 100644
> --- a/drivers/platform/x86/huawei-wmi.c
> +++ b/drivers/platform/x86/huawei-wmi.c
> @@ -72,6 +72,12 @@ struct huawei_wmi {
>  static struct huawei_wmi *huawei_wmi;
>  
>  static const struct key_entry huawei_wmi_keymap[] = {
> +	{ KE_KEY, 0x0287, { KEY_MICMUTE } },
> +	{ KE_KEY, 0x0288, { KEY_CAMERA } },              /* Fn+F8: Camera */
> +	{ KE_KEY, 0x028a, { KEY_CONFIG } },              /* Fn+F10: Honor Connect */
> +	{ KE_KEY, 0x028b, { KEY_VOICECOMMAND } },        /* Fn+F11: YOYO AI */
> +	{ KE_KEY, 0x028e, { KEY_PRINT } },               /* Fn+F12: Screenshot */
> +
>  	{ KE_KEY,    0x281, { KEY_BRIGHTNESSDOWN } },
>  	{ KE_KEY,    0x282, { KEY_BRIGHTNESSUP } },
>  	{ KE_KEY,    0x284, { KEY_MUTE } },

??? Multiple of those keys are already in the array ???

I suppose you'd have noticed it if you'd have not added the leading zeros 
and would have put those correctly in their place in the numerical order.

Please also keep the existing formatting.

-- 
 i.


  reply	other threads:[~2026-08-18 10:26 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 [this message]
2026-08-19  8:38 ` [PATCH v2] platform/x86: huawei-wmi: add camera toggle keycode Ruzal Daminov

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=13b32041-0e33-367e-732a-1b8431c7628c@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=daminovruzal7@gmail.com \
    --cc=hansg@kernel.org \
    --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 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.