mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
synced 2026-10-31 06:14:39 +01:00
Nikhil Solanke
152f174a13
Certain third-party USB game controllers exposing (or spoofing) an Xbox
360-compatible interface (VID:PID 045e:028e) fail to enumerate under Linux.
The device disconnects from the bus without responding to the initial
GET_DESCRIPTOR(CONFIGURATION) request, and the kernel logs 'unable to read
config index 0 descriptor/start: -71'.
The device then falls back to a secondary Android HID mode (with a
different VID:PID), losing XInput functionality including rumble support.
The failure reproduces across multiple machines, host controller types, and
kernel versions including current mainline and LTS. The device enumerates
correctly and remains in XInput mode under Windows. Notably, the device
enumerates correctly in Android mode when the same 9-byte request
is issued for that mode's configuration descriptor, confirming the firmware
bug is specific to the XInput mode.
usbmon traces from Linux and Wireshark/USBPcap traces from Windows are
identical up to the point of failure, with no visible protocol-level
difference explaining the divergence. The root cause was identified when
Michal Pecio discovered via a QEMU bus-level capture that Windows does not
use wLength=9 for the initial config descriptor request; it uses
wLength=255. Alan Stern subsequently confirmed this with a bus
analyzer on a different USB 2.0 device, and Michal verified the behavior
goes back to Windows 95 OSR2.1.
So, add a new quirk flag USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE which causes
usb_get_configuration() to issue a 255 byte sized configuration request
instead of USB_DT_CONFIG_SIZE (9) for the initial
GET_DESCRIPTOR(CONFIGURATION) request, mimicking long-standing Windows
behavior.
This patch intentionally does not add any new VID:PID entries using this
quirk. Some affected Xbox 360-compatible controllers spoof Microsoft's
VID:PID, while genuine Microsoft controllers already enumerate correctly
and do not require this quirk. Other affected clone devices use their own
VID:PID pairs and can be added individually as they are identified.
Suggested-by: Alan Stern <[email protected]>
Suggested-by: Michal Pecio <[email protected]>
Closes: https://lore.kernel.org/linux-usb/CAFgddh+JWdT4LLwMc5qjM8q_pBu-fRo2qADR5ovAKoGHWMQrRw@mail.gmail.com/
Fixes: 1da177e4c3 ("Linux-2.6.12-rc2")
Cc: stable <[email protected]>
Acked-by: Alan Stern <[email protected]>
Signed-off-by: Nikhil Solanke <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
88 lines
2.7 KiB
C
88 lines
2.7 KiB
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
/*
|
|
* This file holds the definitions of quirks found in USB devices.
|
|
* Only quirks that affect the whole device, not an interface,
|
|
* belong here.
|
|
*/
|
|
|
|
#ifndef __LINUX_USB_QUIRKS_H
|
|
#define __LINUX_USB_QUIRKS_H
|
|
|
|
/* string descriptors must not be fetched using a 255-byte read */
|
|
#define USB_QUIRK_STRING_FETCH_255 BIT(0)
|
|
|
|
/* device can't resume correctly so reset it instead */
|
|
#define USB_QUIRK_RESET_RESUME BIT(1)
|
|
|
|
/* device can't handle Set-Interface requests */
|
|
#define USB_QUIRK_NO_SET_INTF BIT(2)
|
|
|
|
/* device can't handle its Configuration or Interface strings */
|
|
#define USB_QUIRK_CONFIG_INTF_STRINGS BIT(3)
|
|
|
|
/* device can't be reset(e.g morph devices), don't use reset */
|
|
#define USB_QUIRK_RESET BIT(4)
|
|
|
|
/* device has more interface descriptions than the bNumInterfaces count,
|
|
and can't handle talking to these interfaces */
|
|
#define USB_QUIRK_HONOR_BNUMINTERFACES BIT(5)
|
|
|
|
/* device needs a pause during initialization, after we read the device
|
|
descriptor */
|
|
#define USB_QUIRK_DELAY_INIT BIT(6)
|
|
|
|
/*
|
|
* For high speed and super speed interrupt endpoints, the USB 2.0 and
|
|
* USB 3.0 spec require the interval in microframes
|
|
* (1 microframe = 125 microseconds) to be calculated as
|
|
* interval = 2 ^ (bInterval-1).
|
|
*
|
|
* Devices with this quirk report their bInterval as the result of this
|
|
* calculation instead of the exponent variable used in the calculation.
|
|
*/
|
|
#define USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL BIT(7)
|
|
|
|
/* device can't handle device_qualifier descriptor requests */
|
|
#define USB_QUIRK_DEVICE_QUALIFIER BIT(8)
|
|
|
|
/* device generates spurious wakeup, ignore remote wakeup capability */
|
|
#define USB_QUIRK_IGNORE_REMOTE_WAKEUP BIT(9)
|
|
|
|
/* device can't handle Link Power Management */
|
|
#define USB_QUIRK_NO_LPM BIT(10)
|
|
|
|
/*
|
|
* Device reports its bInterval as linear frames instead of the
|
|
* USB 2.0 calculation.
|
|
*/
|
|
#define USB_QUIRK_LINEAR_FRAME_INTR_BINTERVAL BIT(11)
|
|
|
|
/*
|
|
* Device needs to be disconnected before suspend to prevent spurious
|
|
* wakeup.
|
|
*/
|
|
#define USB_QUIRK_DISCONNECT_SUSPEND BIT(12)
|
|
|
|
/* Device needs a pause after every control message. */
|
|
#define USB_QUIRK_DELAY_CTRL_MSG BIT(13)
|
|
|
|
/* Hub needs extra delay after resetting its port. */
|
|
#define USB_QUIRK_HUB_SLOW_RESET BIT(14)
|
|
|
|
/* device has endpoints that should be ignored */
|
|
#define USB_QUIRK_ENDPOINT_IGNORE BIT(15)
|
|
|
|
/* short SET_ADDRESS request timeout */
|
|
#define USB_QUIRK_SHORT_SET_ADDRESS_REQ_TIMEOUT BIT(16)
|
|
|
|
/* skip BOS descriptor request */
|
|
#define USB_QUIRK_NO_BOS BIT(17)
|
|
|
|
/* Device claims zero configurations, forcing to 1 */
|
|
#define USB_QUIRK_FORCE_ONE_CONFIG BIT(18)
|
|
|
|
/* Use a 255 bytes config descriptor request mirroring windows behavior */
|
|
#define USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE BIT(19)
|
|
|
|
#endif /* __LINUX_USB_QUIRKS_H */
|