HI all,
In our custom developed board, we are having issues with the USB SS1 port.
When we connect a gen2x1 device, it is identified correctly, but then there are a lot of hiccups operating it. Is it possible to limit this port (or even all the USB phys) to USB3 Gen1?
It was possible in 35.5,
Hi, lots of resets during high-stress communication
we have a script that stresses a large USB disk
[ 375.529297] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 376.596787] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 376.626263] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=6s
[ 376.626335] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 41 4d c0 00 00 00 02 00 00 00
[ 376.626361] I/O error, dev sda, sector 1095614464 op 0x1:(WRITE) flags 0x8800 phys_seg 4 prio class 2
[ 377.641294] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 378.707839] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 379.773296] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 380.828665] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 381.887783] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 382.956293] usb 2-2: reset SuperSpeed Plus Gen 2x1 USB device number 4 using tegra-xusb
[ 382.987500] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=6s
[ 382.987567] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 01 b1 08 88 00 00 00 02 00 00 00
[ 382.987596] I/O error, dev sda, sector 7265093632 op 0x1:(WRITE) flags 0x8800 phys_seg 4 prio class 2
and so on and so forth…
We are trying to limit the USB3 device in the device tree using maximum-speed = "super-speed"; in the device tree in the usb@3… devicedefinitions, but honestly I am not really sure it’s doing anything