From: Evgeny Volferts <eugene.wolferz@gmail.com>
To: corentin.chary@gmail.com, luke@ljones.dev,
denis.benato@linux.dev, hansg@kernel.org,
ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, i@smmh.dev,
eugene.wolferz@gmail.com
Subject: [PATCH v2] platform/x86: asus-nb-wmi: Ignore spurious 0xe5 events
Date: Mon, 9 Nov 2026 11:16:44 +0300 [thread overview]
Message-ID: <20261109081644.2790549-1-eugene.wolferz@gmail.com> (raw)
In-Reply-To: <20261015163029.107250-1-eugene.wolferz@gmail.com>
Some ASUS laptops periodically emit WMI event 0xe5, which is not
associated with a supported key or action.
On the ROG Zephyrus G16 GU605MY, this event occurs approximately
every 12 seconds and is reported as KEY_UNKNOWN. When the session
is locked, it repeatedly wakes both the internal display and an
external monitor connected through a Thunderbolt dock.
Ignore event 0xe5 globally to prevent these spurious input events.
The same event has also been observed on other ASUS laptop models.
Signed-off-by: Evgeny Volferts <eugene.wolferz@gmail.com>
---
Changes in v2:
- Replace the GU605MY-specific DMI quirk with a global KE_IGNORE
entry for event 0xE5, following review feedback.
- Remove the DMI quirk and associated key filter logic.
A similar global fix was independently submitted by
Seyed Mohammad Mahdi Hosseini:
https://lore.kernel.org/r/d3871d83ee3f5eea3900d8bc0da1de764a8fc2ec.1791672579.git.i@smmh.dev
drivers/platform/x86/asus-nb-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/asus-nb-wmi.c b/drivers/platform/x86/asus-nb-wmi.c
index aeb461b1644d..6e784a4909a0 100644
--- a/drivers/platform/x86/asus-nb-wmi.c
+++ b/drivers/platform/x86/asus-nb-wmi.c
@@ -662,6 +662,7 @@ static const struct key_entry asus_nb_wmi_keymap[] = {
{ KE_KEY, 0xCB, { KEY_F14 } }, /* Fn+noise-cancel */
{ KE_IGNORE, 0xC6, }, /* Ambient Light Sensor notification */
{ KE_IGNORE, 0xCF, }, /* AC mode */
+ { KE_IGNORE, 0xE5, }, /* Periodic EC notification */
{ KE_KEY, 0xFA, { KEY_PROG2 } }, /* Lid flip action */
{ KE_KEY, 0xBD, { KEY_PROG2 } }, /* Lid flip action on ROG xflow laptops */
{ KE_KEY, ASUS_WMI_KEY_ARMOURY, { KEY_PROG3 } },
--
2.56.0
prev parent reply other threads:[~2026-11-09 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 16:30 [PATCH] platform/x86: asus-nb-wmi: Ignore spurious 0xe5 events on GU605MY Evgeny Volferts
2026-10-19 22:12 ` Denis Benato
2026-10-19 22:28 ` Евгений Вольферц
2026-10-30 0:47 ` Seyed Mohammad Mahdi Hosseini
2026-10-20 11:11 ` Ilpo Järvinen
2026-10-20 11:27 ` Denis Benato
2026-11-09 8:16 ` Evgeny Volferts [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=20261109081644.2790549-1-eugene.wolferz@gmail.com \
--to=eugene.wolferz@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=i@smmh.dev \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--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®