From: James Ye <jye836@gmail.com>
To: jikos@kernel.org, bentiss@kernel.org, lee@kernel.org, pavel@kernel.org
Cc: linux-input@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, denis.benato@linux.dev,
James Ye <jye836@gmail.com>
Subject: [PATCH 2/6] HID: asus: check feature reports when determining is_vendor
Date: Sun, 3 May 2026 17:26:39 +1000 [thread overview]
Message-ID: <20260503072643.2774762-3-jye836@gmail.com> (raw)
In-Reply-To: <20260503072643.2774762-1-jye836@gmail.com>
ASUS T3304 Soft Keyboard has these reports on its touchpad interface,
which will be bound to hid_multitouch. To support a quirk allowing
hid_asus to configure the keyboard interface, feature reports should be
checked in addition to input reports, as is already the case in
asus_has_report_id.
Signed-off-by: James Ye <jye836@gmail.com>
---
drivers/hid/hid-asus.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/hid/hid-asus.c b/drivers/hid/hid-asus.c
index 3f5e96900b67..ef9d5eba4dc9 100644
--- a/drivers/hid/hid-asus.c
+++ b/drivers/hid/hid-asus.c
@@ -1282,10 +1282,12 @@ static int asus_probe(struct hid_device *hdev, const struct hid_device_id *id)
}
/* Check for vendor for RGB init and handle generic devices properly. */
- rep_enum = &hdev->report_enum[HID_INPUT_REPORT];
- list_for_each_entry(rep, &rep_enum->report_list, list) {
- if ((rep->application & HID_USAGE_PAGE) == HID_UP_ASUSVENDOR)
- is_vendor = true;
+ for (int t = HID_INPUT_REPORT; t <= HID_FEATURE_REPORT; t++) {
+ rep_enum = &hdev->report_enum[t];
+ list_for_each_entry(rep, &rep_enum->report_list, list) {
+ if ((rep->application & HID_USAGE_PAGE) == HID_UP_ASUSVENDOR)
+ is_vendor = true;
+ }
}
ret = hid_hw_start(hdev, HID_CONNECT_DEFAULT);
--
2.54.0
next prev parent reply other threads:[~2026-05-03 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 7:26 [PATCH 0/6] HID: asus: add support for T3304 keyboard James Ye
2026-05-03 7:26 ` [PATCH 1/6] HID: input: delete hid_battery on disconnect James Ye
2026-05-03 7:26 ` James Ye [this message]
2026-05-03 7:26 ` [PATCH 3/6] HID: asus: add support for T3304 detachable keyboard James Ye
2026-05-03 22:23 ` Denis Benato
2026-05-03 7:26 ` [PATCH 4/6] HID: multitouch: add support for ASUS T3304 media keys James Ye
2026-05-03 7:26 ` [PATCH 5/6] HID: asus: add microphone mute LED support for T3304 James Ye
2026-05-03 22:45 ` Denis Benato
2026-05-04 1:27 ` James Ye
2026-05-03 7:26 ` [PATCH 6/6] leds: led-class: mark classdev as unregistering early James Ye
2026-05-04 21:49 ` kernel test robot
2026-05-05 2:24 ` kernel test robot
2026-05-05 14:16 ` James Ye
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=20260503072643.2774762-3-jye836@gmail.com \
--to=jye836@gmail.com \
--cc=bentiss@kernel.org \
--cc=denis.benato@linux.dev \
--cc=jikos@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@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