2012/10/12 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > On Fri, 12 Oct 2012, Elric Fu wrote: > >> > What is error -145 on your platform? Is it -ETIMEDOUT? >> >> Yes. -145 means -ETIMEOUT. >> >> > >> >> usb core send a get configuration descriptor request, but the control transfer >> >> will be timeout again. >> >> >> >> I used the usb analyzer to capture the trace and found host just sent one >> >> get-device-qualifier-descriptor control transfer and the device return a >> >> STALL. But at the second time, actually, the host even didn't send the setup >> >> packet. I don't know why. >> > >> > Since the transfer uses aplit transactions, the host doesn't send any >> > SETUP packets at all. The intervening hub sends them. Maybe there's >> > something wrong with the hub. >> > >> > Can you use your analyzer to capture the traffic between the computer >> > and the hub, rather than between the hub and the device? >> >> Yes. I have already capture the traffic between the host and the hub.Same >> situation would happened. I can't found any packets belong to the second >> get-device-qualifier-descriptor control transfer. > > Are you certain? There should be at least a StartSplit packet. > > Of course, if there are no packets that would explain why you get a > ETIMEDOUT error. Yes, I am. I don't know why. > >> >> My opinion is the split transactions to the device which has a 0x0200 bcdUSB >> >> but is actually a full speed device have some issues. I would >> >> appreciate any ideas. >> > >> > What happens if you use both the device and the same hub with a regular >> > PC? >> >> If I use the same device and the same hub with a regular pc, everything is >> normal. The issue just occurred on Atheros ar9331 platform. > > Maybe there's a bug in the platform's EHCI hardware. Anyway. I appreciate that. After doing a couple of tests and debugs, it seems that I can't modify the driver to fix it. > > Alan Stern > -- 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
