On Mon, Mar 11, 2013 at 10:58:05AM -0400, Alan Stern wrote: > On Mon, 11 Mar 2013, Alexander Shishkin wrote: > > > > For USB 3.0 host CV test, the host sends GET_DESCRIPTOR very quick > > > (<500us) > > > once it accept the status of SET_ADDRESS > > > > The USB 2.0 spec says the recovery period after the status phase of > > SetAddress is 2ms. That should be enough to process the transfer > > completion interrupt, shouldn't it? > > Why is USB 3 CV violating this and why should we care? I guess, if we > > Probably because the recovery period, being in the USB 2.0 spec, > applies to USB-2 devices -- whereas the USB-3 CV tries to test USB-3 > devices. Do they have the same recovery period? >
Alex & Alan, I checked the USB 3.0 spec, there is no requirement for recovery time. So, for this problem, it is USB3 CV suite's problem, When it detects 2.0 device, it should follow 2.0 recovery time. -- Best Regards, Peter Chen -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
