From: Armin Wolf <W_Armin@gmx.de>
To: matan@svgalib.org
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, helian.caumeil@clever.cloud
Subject: Re: [PATCH] platform/x86: lg-laptop: Fix input of super key
Date: Tue, 17 Nov 2026 23:32:23 +0100 [thread overview]
Message-ID: <26f1d116-479b-414a-856e-290e4775274c@gmx.de> (raw)
In-Reply-To: <20261103180750.228116-1-W_Armin@gmx.de>
Am 03.11.26 um 19:07 schrieb Armin Wolf:
> From: Helian Caumeil <helian.caumeil@clever.cloud>
>
> Some devices emit special event codes when the super key is pressed.
> Mapping those events onto KEY_UNKNOWN by the sparse keymap seems to
> confuse userspace, causing duplicated super key input events.
>
> Prevent this by ignoring those event codes.
Any updates on this? More users have reported the same issue.
Thanks,
Armin Wolf
> Signed-off-by: Helian Caumeil <helian.caumeil@clever.cloud>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=222161
> Co-developed-by: Armin Wolf <W_Armin@gmx.de>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> ---
> drivers/platform/x86/lg-laptop.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/platform/x86/lg-laptop.c b/drivers/platform/x86/lg-laptop.c
> index 36ad1e269443..49e3029d4b95 100644
> --- a/drivers/platform/x86/lg-laptop.c
> +++ b/drivers/platform/x86/lg-laptop.c
> @@ -138,6 +138,10 @@ static const struct key_entry wmi_keymap[] = {
> { KE_IGNORE, 0x30010001, { KEY_UNKNOWN }},
> /* Change fan mode */
> { KE_KEY, 0x30010051, { KEY_PERFORMANCE }},
> + /* Super key pressed */
> + { KE_IGNORE, 0x30020000, { KEY_LEFTMETA }},
> + /* Super key released */
> + { KE_IGNORE, 0x30020001, { KEY_LEFTMETA }},
> /* Disable camera */
> { KE_KEY, 0x40020000, { KEY_CAMERA_ACCESS_TOGGLE }},
> /* Mute microphone */
prev parent reply other threads:[~2026-11-17 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 18:07 Armin Wolf
2026-11-17 22:32 ` Armin Wolf [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=26f1d116-479b-414a-856e-290e4775274c@gmx.de \
--to=w_armin@gmx.de \
--cc=hansg@kernel.org \
--cc=helian.caumeil@clever.cloud \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matan@svgalib.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®