Hi, Vincent Pelletier <plr.vincent@xxxxxxxxx> writes: >> > What happens when you run your test with dummy-hcd? >> >> this is a good idea too. > > Tested (on the edison, as it was the most convenient place to build > that module and debian kernel on host does not have it), the whole > test suite passes there. This said, dummy_hcd allocates endpoints on > very different addresses: > > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x86 EP 6 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > > Back the dwc3 I tried pushing the IN descriptor first (IN, OUT, IN > instead of OUT, IN, IN). ep1in is still silent, so it looks like in the > event of IN+OUT endpoint address (4 LSb), OUT wins and IN looses > whatever the initialisation order. this looks very similar to problem I'm debugging with ADB on Joule. I see no errors on Joule (dwc3) side and xHCI fails transfers with "USB Transaction Error" (hence my asking for xHCI traces). -- balbi -- 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
