From: Jozef Riha <jose1711@gmail.com>
To: Jiri Kosina <jikos@kernel.org>, Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] HID: betop: add support for SPEEDLINK TORID
Date: Wed, 18 Nov 2026 15:32:17 +0100 [thread overview]
Message-ID: <20261118143306.75858-1-jose1711@gmail.com> (raw)
The SPEEDLINK TORID wireless gamepad (11c0:9105) is a Betop based
device. Its output report has the same 4 byte layout as the other
devices handled by hid-betopff, with the motors in bytes 2 and 3.
Without the device ID the gamepad is bound to hid-generic and has no
force feedback. Add it to betop_devices[].
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Jozef Riha <jose1711@gmail.com>
---
v2:
- Fix From/Signed-off-by name mismatch
- Cc linux-input and LKML, v1 was sent to the HID maintainers only
drivers/hid/hid-betopff.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/hid/hid-betopff.c b/drivers/hid/hid-betopff.c
index f802046a688a..28ab0acce6ad 100644
--- a/drivers/hid/hid-betopff.c
+++ b/drivers/hid/hid-betopff.c
@@ -16,6 +16,9 @@
*
* 0x20bc:0x5500 "BTP2185 V2 BFM mode Joystick"
* - tested with BTP2171s.
+ *
+ * 0x11c0:0x9105 "SPEEDLINK TORID"
+ * - tested with Speedlink TORID wireless gamepad.
* Copyright (c) 2014 Huang Bo <huangbobupt@163.com>
*/
@@ -137,6 +140,7 @@ static int betop_probe(struct hid_device *hdev, const struct hid_device_id *id)
static const struct hid_device_id betop_devices[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_BETOP_2185BFM, 0x2208) },
{ HID_USB_DEVICE(USB_VENDOR_ID_BETOP_2185PC, 0x5506) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_BETOP_2185PC, 0x9105) },
{ HID_USB_DEVICE(USB_VENDOR_ID_BETOP_2185V2PC, 0x1850) },
{ HID_USB_DEVICE(USB_VENDOR_ID_BETOP_2185V2BFM, 0x5500) },
{ }
--
2.56.1
reply other threads:[~2026-11-18 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261118143306.75858-1-jose1711@gmail.com \
--to=jose1711@gmail.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).