From: Ahmed Yaseen <yaseen@ghoul.dev>
To: Jiri Kosina <jikos@kernel.org>, Benjamin Tissoires <bentiss@kernel.org>
Cc: "Denis Benato" <denis.benato@linux.dev>,
"Antheas Kapenekakis" <lkml@antheas.dev>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Kerim Kabirov" <the.privat33r+linux@pm.me>,
GameBurrow <gameburrow@pm.me>,
regressions@lists.linux.dev, linux-usb@vger.kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ahmed Yaseen" <yaseen@ghoul.dev>
Subject: [PATCH v2 0/1] HID: usbhid: skip interrupt IN polling for devices with no input reports
Date: Fri, 28 Aug 2026 10:42:10 +0000 [thread overview]
Message-ID: <20260828104159.62399-1-yaseen@ghoul.dev> (raw)
On some ASUS ROG N-Key keyboards, a second input-less interface is
exposed for RGB control. Polling this interface causes keypress reports
on the first keyboard interface to be dropped: a lost key-down drops a
letter, a lost key-up leaves the key stuck. Any hidraw reader opening
the node is enough to trigger it, including SDL/Steam Input or a plain
cat.
This patch skips the poll if no input reports exist for an interface. A
device with no input reports has no benefit from being polled, so
instead of adding a new quirk, I have opted to skip it entirely.
Devices other than the ASUS ones are unaffected. HID core already
discards whatever arrives on the interrupt IN endpoint of an interface
that declares no input reports: hid_get_report() matches nothing, so
neither ->raw_event() nor hidraw and hiddev are ever reached.
The affected machines are 2024-2025 Strix SCAR 16/18 (G635L/G835L) and
G16/G18 (G615L/G815L) laptops, and the bug is widely reported across
distributions, so I would appreciate this being considered for the
current cycle. Reports:
https://discuss.cachyos.org/t/keyboard-input-issues-on-asus-rog-strix-16-2025-with-cachyos-during-gaming/30823
https://github.com/ublue-os/bazzite/issues/4590
v1: https://lore.kernel.org/all/20260605113952.38435-1-yaseen@ghoul.dev
Changes since v1:
- Added a short comment above the condition in usbhid_open() explaining
the reason for skipping there.
- Added Cc: stable@vger.kernel.org; v1 was not marked for backport. The
bug reaches every tree carrying 4ac74ea68f64, i.e. v7.0 onwards.
- Added Link: tags for two of the downstream bug reports.
- No functional change: the hunk is byte-identical to v1 apart from the
new comment, so the Tested-by and Reviewed-by tags carry over.
Since v1, this patch has been adopted by three downstream kernels, with
no regressions reported by any user since:
- OGC kernel: from v7.1.3-ogc5 (2026-07-21) onwards
- Nobara kernel: from 7.1.4 onwards
- G14 kernel: from 7.1.4 onwards
Ahmed Yaseen (1):
HID: usbhid: skip interrupt IN polling for devices with no input
reports
drivers/hid/usbhid/hid-core.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
base-commit: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f
--
2.55.0
next reply other threads:[~2026-08-28 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 10:42 Ahmed Yaseen [this message]
2026-08-28 10:42 ` [PATCH v2] " Ahmed Yaseen
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=20260828104159.62399-1-yaseen@ghoul.dev \
--to=yaseen@ghoul.dev \
--cc=bentiss@kernel.org \
--cc=denis.benato@linux.dev \
--cc=dmitry.torokhov@gmail.com \
--cc=gameburrow@pm.me \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=regressions@lists.linux.dev \
--cc=stern@rowland.harvard.edu \
--cc=the.privat33r+linux@pm.me \
/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®