summaryrefslogtreecommitdiff
path: root/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
diff options
context:
space:
mode:
authorLuiz Augusto von Dentz <luiz.von.dentz@intel.com>2024-10-16 18:47:00 +0300
committerLuiz Augusto von Dentz <luiz.von.dentz@intel.com>2024-10-16 23:10:25 +0300
commit2c1dda2acc4192d826e84008d963b528e24d12bc (patch)
tree8676a8126360b520eb6831506b86dd25975dfe29 /arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi
parent64a90991ba8d4e32e3173ddd83d0b24167a5668c (diff)
downloadlinux-2c1dda2acc4192d826e84008d963b528e24d12bc.tar.xz
Bluetooth: btusb: Fix regression with fake CSR controllers 0a12:0001
Fake CSR controllers don't seem to handle short-transfer properly which cause command to time out: kernel: usb 1-1: new full-speed USB device number 19 using xhci_hcd kernel: usb 1-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 kernel: usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 kernel: usb 1-1: Product: BT DONGLE10 ... Bluetooth: hci1: Opcode 0x1004 failed: -110 kernel: Bluetooth: hci1: command 0x1004 tx timeout According to USB Spec 2.0 Section 5.7.3 Interrupt Transfer Packet Size Constraints a interrupt transfer is considered complete when the size is 0 (ZPL) or < wMaxPacketSize: 'When an interrupt transfer involves more data than can fit in one data payload of the currently established maximum size, all data payloads are required to be maximum-sized except for the last data payload, which will contain the remaining data. An interrupt transfer is complete when the endpoint does one of the following: • Has transferred exactly the amount of data expected • Transfers a packet with a payload size less than wMaxPacketSize or transfers a zero-length packet' Link: https://bugzilla.kernel.org/show_bug.cgi?id=219365 Fixes: 7b05933340f4 ("Bluetooth: btusb: Fix not handling ZPL/short-transfer") Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi')
0 files changed, 0 insertions, 0 deletions