From: Seyed Mohammad Mahdi Hosseini <i@smmh.dev>
To: "Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Corentin Chary <corentin.chary@gmail.com>,
"Luke D. Jones" <luke@ljones.dev>,
Denis Benato <denis.benato@linux.dev>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] platform/x86: asus-nb-wmi: Ignore unknown event 0xE5
Date: Fri, 16 Oct 2026 00:10:54 +0200 [thread overview]
Message-ID: <d3871d83ee3f5eea3900d8bc0da1de764a8fc2ec.1791672579.git.i@smmh.dev> (raw)
In-Reply-To: <cover.1791672579.git.i@smmh.dev>
On the ASUS TUF Gaming A15 FA507RF (BIOS FA507RF.306) the firmware sends
WMI event 0xE5 about every 10 seconds, for many hours at a time, while
the laptop is on AC power. Nobody presses a key when it arrives. The
keymap has no entry for it, so asus-wmi logs
asus_wmi: Unknown key code 0xe5
each time and reports MSC_SCAN 0xe5 with a KEY_UNKNOWN press and release
on the "Asus WMI hotkeys" input device. Desktop environments take that
as user activity: the session never goes idle and a locked screen wakes
up every 10 seconds.
Owners of other TUF models (F15 FX506HE, A17) report the same periodic
event, and that it stops when the charger is unplugged.
Ignore the event, as was done for the AC and charger notifications 0x79,
0x7B, and 0xCF.
Assisted-by: LLM
Signed-off-by: Seyed Mohammad Mahdi Hosseini <i@smmh.dev>
---
Notes:
Built against 7.2.8 and loaded on this machine in place of the stock
asus-nb-wmi. The 0xE5 episode had already ended when it was loaded, so
this entry has not yet been seen silencing the event; until then the
events were dropped by an input filter on the same device.
The research, the keymap entry, and this changelog were prepared with an
LLM coding assistant; the logs and observations are from my machine.
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..23dce220f974 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 notification while on AC */
{ 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.55.0
next prev parent reply other threads:[~2026-10-15 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 22:10 [PATCH 0/2] platform/x86: asus-nb-wmi: Ignore events 0xE5 and 0x4F Seyed Mohammad Mahdi Hosseini
2026-10-15 22:10 ` Seyed Mohammad Mahdi Hosseini [this message]
2026-10-15 22:10 ` [PATCH 2/2] platform/x86: asus-nb-wmi: Ignore Windows key lock event 0x4F Seyed Mohammad Mahdi Hosseini
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=d3871d83ee3f5eea3900d8bc0da1de764a8fc2ec.1791672579.git.i@smmh.dev \
--to=i@smmh.dev \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--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®