From: Ishaan Dandekar <ishaan.dandekar@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Cc: nikhilsolanke5@gmail.com, Ishaan Dandekar <ishaan.dandekar@gmail.com>
Subject: [PATCH v3] usb: quirks: Add ShanWan gamepad to quirk list
Date: Sun, 2 Aug 2026 17:31:29 +0530 [thread overview]
Message-ID: <20260802120128.38302-1-ishaan.dandekar@gmail.com> (raw)
The ShanWan Wireless Gamepad (dongle ID 2563:0575) crashes with a -71
EPROTO error during standard enumeration because it expects a 255-byte
initial configuration request. Add this device to the quirk list to
use the USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE flag.
Signed-off-by: Ishaan Dandekar <ishaan.dandekar@gmail.com>
---
Changes in v3:
- Sent as a standalone patch instead of a series.
- Dropped Nikhil Solanke's core patch from the submission to avoid duplication.
Note: This patch depends on Nikhil Solanke's updated patchset:
https://lore.kernel.org/linux-usb/20260728195158.65162-1-nikhilsolanke5@gmail.com/
Note: While these USB patches keep the device stable in X-Input mode, a
companion patch is submitted separately to the linux-input subsystem
(drivers/input/joystick/xpad.c) to ensure the device is routed correctly
and retains full haptic feedback and functionality.
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 87ee2d938..b1e7e6071 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -589,6 +589,9 @@ static const struct usb_device_id usb_quirk_list[] = {
{ USB_DEVICE(0x2386, 0x350e), .driver_info = USB_QUIRK_NO_LPM },
+ /* ShanWan Wireless Gamepad */
+ { USB_DEVICE(0x2563, 0x0575), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE },
+
/* UGREEN 35871 - BOS descriptor fetch hangs at SuperSpeed Plus */
{ USB_DEVICE(0x2b89, 0x5871), .driver_info = USB_QUIRK_NO_BOS },
--
2.34.1
reply other threads:[~2026-08-02 12:03 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=20260802120128.38302-1-ishaan.dandekar@gmail.com \
--to=ishaan.dandekar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=nikhilsolanke5@gmail.com \
/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