On 19.05.2016 14:23, Joao Pinto wrote:
Hi Felipe,
On 5/19/2016 11:32 AM, Felipe Balbi wrote:
Hi,
Note that we really did get a command timeout. Can you add a little
extra debugging to try and figure out why that command failed?
After instrumenting and capturing FPGA signals, the driver could go a bit
further... Could this be a FPGA timming issue?
..
xhci-hcd xhci-hcd.0.auto: Timeout while waiting for setup device command
usb 3-1: hub failed to enable device, error -62
xhci-hcd xhci-hcd.0.auto: Endpoint 0x0 ep reset callback called
xhci-hcd xhci-hcd.0.auto: xHCI dying or halted, can't queue_command
xhci-hcd xhci-hcd.0.auto: FIXME: allocate a command ring segment
usb usb3-port1: couldn't allocate usb_device
Joao
Does the patch from Chris Bainbridge help?
It's currently only Gregs tree in the usb-next branch.
It fixes a locking issue where hw can't handle several ports being in default state at
the same time, and setup device command timeout issue when both usb2 and usb3 devices
try to enumerate at the same time.
commit feb26ac31a2a5cb88d86680d9a94916a6343e9e6
usb: core: hub: hub_port_init lock controller instead of bus
-Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
