From: "René Onier" <f3nr1l@me.com>
To: Benjamin Tissoires <bentiss@kernel.org>, Jiri Kosina <jikos@kernel.org>
Cc: "René Onier" <f3nr1l@me.com>,
"Ivan Gorinov" <linux-kernel@altimeter.info>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/4] HID: winwing: add URSA MINOR sticks
Date: Wed, 30 Sep 2026 15:55:59 -0400 [thread overview]
Message-ID: <ffd505a63cdd8ee5ea2c5c8c456f6691ffb23319.1790795726.git.f3nr1l@me.com> (raw)
In-Reply-To: <cover.1790795726.git.f3nr1l@me.com>
The URSA MINOR is a single-handed stick sold as a left/right pair, each
hand enumerating as its own USB device. It speaks the same vendor
protocol as the Orion 2 throttle, so reuse the LED code for it.
A stick exposes two controllers on the same endpoint, both named by the
vendor software: the base, J5_BASE, which answers on device 0x20, family
0xbb, and drives a single backlight, and the grip, JGRIP_F1_L or
JGRIP_F1_R, which carries the rumble motor. The a-a and a-g indicators of
the Orion 2 belong to an F/A-18 throttle panel and have no counterpart on
a stick, so give the sticks their own LED table.
The grips carry more than 32 buttons and so take the extended button
mapping as well. Their rumble motor is driven by a report the two-motor
throttle path does not send, and is added separately.
Signed-off-by: René Onier <f3nr1l@me.com>
---
drivers/hid/hid-winwing.c | 54 ++++++++++++++++++++++++++++++++++-----
1 file changed, 47 insertions(+), 7 deletions(-)
diff --git a/drivers/hid/hid-winwing.c b/drivers/hid/hid-winwing.c
index 9ec0d2cf53..a52e7efece 100644
--- a/drivers/hid/hid-winwing.c
+++ b/drivers/hid/hid-winwing.c
@@ -1,7 +1,7 @@
// SPDX-License-Identifier: GPL-2.0
/*
- * HID driver for WinWing Orion 2 throttle
+ * HID driver for WinWing Orion 2 throttle and URSA MINOR sticks
*
* Copyright (c) 2023 Ivan Gorinov
*/
@@ -35,6 +35,16 @@
#define ORION2_LIGHT_DEVICE 0x60
#define ORION2_LIGHT_FAMILY 0xbe
+/*
+ * Each URSA MINOR stick exposes two controllers on the same endpoint. The
+ * vendor software names them J5_BASE (0xbb20), the base, which carries the
+ * backlight, and JGRIP_F1_L and JGRIP_F1_R (0xbf09 and 0xbf0a), the grips,
+ * which carry the rumble motor. Each of these ids is the family byte followed
+ * by the device byte. The base answers on the same id on either hand.
+ */
+#define URSA_LIGHT_DEVICE 0x20
+#define URSA_LIGHT_FAMILY 0xbb
+
/* Rumble motors of the TGRIP-15 grips, one report each */
#define WINWING_STICK_FAMILY 0xbf
#define WINWING_RUMBLE_LEFT_DEVICE 0x01
@@ -42,6 +52,8 @@
/* Grip with a rumble motor and more than 32 buttons */
#define WINWING_GRIP15 BIT(0)
+/* URSA MINOR stick, one USB device per hand */
+#define WINWING_URSA_MINOR BIT(1)
struct winwing_led {
struct led_classdev cdev;
@@ -61,6 +73,17 @@ static const struct winwing_led_info orion2_led_info[] = {
{ 2, 1, "a-g" },
};
+/*
+ * The URSA MINOR sticks have a single monochrome backlight. The a-a and a-g
+ * indicators of the Orion 2 belong to an F/A-18 throttle panel and have no
+ * counterpart here.
+ */
+static const struct winwing_led_info ursa_led_info[] = {
+ { 0, 255, "backlight" },
+};
+
+#define WINWING_MAX_LEDS ARRAY_SIZE(orion2_led_info)
+
struct winwing_drv_data {
struct hid_device *hdev;
struct mutex lights_lock;
@@ -140,10 +163,17 @@ static int winwing_init_led(struct hid_device *hdev,
if (!data->report_lights)
return -ENOMEM;
- table = orion2_led_info;
- data->num_leds = ARRAY_SIZE(orion2_led_info);
- data->led_device = ORION2_LIGHT_DEVICE;
- data->led_family = ORION2_LIGHT_FAMILY;
+ if (data->quirks & WINWING_URSA_MINOR) {
+ table = ursa_led_info;
+ data->num_leds = ARRAY_SIZE(ursa_led_info);
+ data->led_device = URSA_LIGHT_DEVICE;
+ data->led_family = URSA_LIGHT_FAMILY;
+ } else {
+ table = orion2_led_info;
+ data->num_leds = ARRAY_SIZE(orion2_led_info);
+ data->led_device = ORION2_LIGHT_DEVICE;
+ data->led_family = ORION2_LIGHT_FAMILY;
+ }
for (i = 0; i < data->num_leds; i += 1) {
const struct winwing_led_info *info = &table[i];
@@ -368,7 +398,7 @@ static int winwing_probe(struct hid_device *hdev,
const struct hid_device_id *id)
{
struct winwing_drv_data *data;
- size_t data_size = struct_size(data, leds, 3);
+ size_t data_size = struct_size(data, leds, WINWING_MAX_LEDS);
int ret;
ret = hid_parse(hdev);
@@ -444,6 +474,16 @@ static const struct hid_device_id winwing_devices[] = {
.driver_data = 0 },
{ HID_USB_DEVICE(0x4098, 0xbe62), /* TGRIP-18 */
.driver_data = 0 },
+ /*
+ * The Fighter and Space variants are electrically identical and share
+ * these product ids; only the stick tilt accessory differs. The Civil
+ * variant, which has fewer buttons, is likely compatible, but its
+ * product ids have not been verified on hardware.
+ */
+ { HID_USB_DEVICE(0x4098, 0xbc2a), /* URSA MINOR R */
+ .driver_data = WINWING_GRIP15 | WINWING_URSA_MINOR },
+ { HID_USB_DEVICE(0x4098, 0xbc29), /* URSA MINOR L */
+ .driver_data = WINWING_GRIP15 | WINWING_URSA_MINOR },
{}
};
@@ -459,5 +499,5 @@ static struct hid_driver winwing_driver = {
};
module_hid_driver(winwing_driver);
-MODULE_DESCRIPTION("HID driver for WinWing Orion 2 throttle");
+MODULE_DESCRIPTION("HID driver for WinWing Orion 2 throttle and URSA MINOR sticks");
MODULE_LICENSE("GPL");
--
2.55.0
next prev parent reply other threads:[~2026-09-30 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 19:37 [PATCH 0/2] HID: winwing: two teardown fixes René Onier
2026-09-30 19:37 ` [PATCH 1/2] HID: winwing: fix use-after-free of the rumble work René Onier
2026-09-30 19:37 ` [PATCH 2/2] HID: winwing: initialize the lights_lock mutex René Onier
2026-09-30 19:55 ` [PATCH 0/4] HID: winwing: add WinWing URSA MINOR sticks René Onier
2026-09-30 19:55 ` [PATCH 1/4] HID: winwing: factor out vendor SET_LEDX report builder René Onier
2026-09-30 19:55 ` [PATCH 2/4] HID: winwing: make the LED set and lighting controller model-dependent René Onier
2026-09-30 19:55 ` René Onier [this message]
2026-09-30 19:56 ` [PATCH 4/4] HID: winwing: drive the URSA MINOR rumble motor René Onier
2026-09-30 19:58 ` [PATCH 0/2] HID: winwing: two teardown fixes René Onier
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=ffd505a63cdd8ee5ea2c5c8c456f6691ffb23319.1790795726.git.f3nr1l@me.com \
--to=f3nr1l@me.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@altimeter.info \
--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
all inboxes | Powered by JetHome®