From: "Mark Pearson" <mpearson-lenovo@squebb.ca>
To: "Navon John Lukose" <navonjohnlukose@gmail.com>,
"Ike Panhc" <ikepanhc@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Derek J . Clark" <derekjohn.clark@gmail.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: ideapad-laptop: Add Yoga Pro 7 14IAH10 Mode key
Date: Fri, 18 Sep 2026 17:41:15 -0400 [thread overview]
Message-ID: <3c345c9f-ca1b-4f77-9641-cb026704c6c1@app.fastmail.com> (raw)
In-Reply-To: <20260914134216.1295740-1-navonjohnlukose@gmail.com>
On Mon, Sep 14, 2026, at 9:42 AM, Navon John Lukose wrote:
> The F9 "Mode" key emits WMI fn-key event 0x46, which the keymap does not
> cover, so it reaches userspace as KEY_UNKNOWN and cannot be remapped from
> there. Under Windows it opens a performance profile chooser. The Fn+Q
> button already cycles platform_profile through
> ideapad_check_special_buttons(), so map 0x46 to KEY_PROG4 as a
> user-assignable key rather than cycling the profile a second way.
>
> Signed-off-by: Navon John Lukose <navonjohnlukose@gmail.com>
> ---
> v2: reword the entry comment and explain why 0x46 is not routed through
> platform_profile_cycle() (Hans).
>
> https://lore.kernel.org/platform-driver-x86/2eab84cb-6d2f-4ec3-9869-e2aa9c1d75da@kernel.org/
>
> Lenovo Yoga Pro 7 14IAH10 (83KF), BIOS QGCN35WW.
>
> Measured with dyndbg on ideapad-laptop.c and a kprobe on
> platform_profile_cycle():
>
> Mode key (plain F9), 2 presses:
> WMI fn-key event: 0x46, twice
> no platform_profile change
>
> Fn+Q, 2 presses:
> platform_profile_cycle() twice, called from ideapad_acpi_notify()
> no WMI fn-key event
>
> drivers/platform/x86/lenovo/ideapad-laptop.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/platform/x86/lenovo/ideapad-laptop.c
> b/drivers/platform/x86/lenovo/ideapad-laptop.c
> index 8213524..35c13d9 100644
> --- a/drivers/platform/x86/lenovo/ideapad-laptop.c
> +++ b/drivers/platform/x86/lenovo/ideapad-laptop.c
> @@ -1360,6 +1360,8 @@ static const struct key_entry ideapad_keymap[] = {
> { KE_KEY, 0x45 | IDEAPAD_WMI_KEY, { KEY_PROG3 } },
> /* Performance toggle also Fn+Q, handled inside ideapad_wmi_notify()
> */
> { KE_KEY, 0x3d | IDEAPAD_WMI_KEY, { KEY_PROG4 } },
> + /* Mode, opens a profile chooser; the Fn+Q button cycles the profile
> */
> + { KE_KEY, 0x46 | IDEAPAD_WMI_KEY, { KEY_PROG4 } },
Just a note that on Thinkpad we handle the mode key also as a profile cycler so it's a shame these are different.
I personally would have added 0x46 to the code in ideapad_wmi_notify too so either mode key or FN+Q could be used. The mode key is a much more obvious way of cycling through profiles in my opinion.
In theory you could maybe use KEY_PERFORMANCE there so they're 'different'. ProfileD should handle that (don't think tuneD does yet).
Mark
prev parent reply other threads:[~2026-09-18 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:42 Navon John Lukose
2026-09-14 14:32 ` Hans de Goede
2026-09-15 11:32 ` Ilpo Järvinen
2026-09-18 21:41 ` Mark Pearson [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=3c345c9f-ca1b-4f77-9641-cb026704c6c1@app.fastmail.com \
--to=mpearson-lenovo@squebb.ca \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=ikepanhc@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=navonjohnlukose@gmail.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
all inboxes | Powered by JetHome®