usb: quirks: add WINDOWS_CONFIG_REQ_SIZE for Razer BlackShark V3
PATCH 1/1 usb: quirks: add WINDOWS_CONFIG_REQ_SIZE for Razer BlackShark V3
The Razer BlackShark V3 and V3 Pro wireless dongles fingerprint the USB host by its configuration-descriptor read pattern during enumeration. Unless they see a single full-length (wLength=255) request like Windows sends, they refuse to bring up the wireless telemetry relay and battery, charging and EQ state all read back as zero.
USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE already implements exactly this behaviour, so just register it for the four BlackShark V3 PIDs:
0x0576 V3 Pro (wired USB-C) 0x0577 V3 Pro (2.4GHz dongle) 0x0579 V3 (wired USB-C) 0x057a V3 (2.4GHz dongle)
Both the dongle and the wired transport enumerate the same firmware and need the quirk. Verified on 0x057a and 0x0577: with the quirk the vendor channel answers and battery/charging/EQ read correctly; without it every vendor GET returns zero.
--- drivers/usb/core/quirks.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/usb/core/quirks.c +5 -0
@@ -502,6 +502,11 @@ static const struct usb_device_id usb_quirk_list[] = { USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL },/* Razer - Razer Kiyo Pro Webcam */ { USB_DEVICE(0x1532, 0x0e05), .driver_info = USB_QUIRK_NO_LPM }, + /* Razer BlackShark V3 / V3 Pro - unlock wireless telemetry relay */ + { USB_DEVICE(0x1532, 0x0576), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE }, + { USB_DEVICE(0x1532, 0x0577), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE }, + { USB_DEVICE(0x1532, 0x0579), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE }, + { USB_DEVICE(0x1532, 0x057a), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE }, /* Lenovo ThinkPad OneLink+ Dock twin hub controllers (VIA Labs VL812) */ { USB_DEVICE(0x17ef, 0x1018), .driver_info = USB_QUIRK_RESET_RESUME },
Signature · 1 line
2.55.0