Re: [PATCH v3 1/2] USB: check port changes before hub runtime suspend for some bug device

2012-09-27 Thread Alan Stern
On Thu, 27 Sep 2012, Ming Lei wrote: > The hub status endpoint has a long 'bInterval', which is 255ms > for FS/LS device and 256ms for HS device according to USB 2.0 spec, > so the device connection change may be reported later more than 255ms > via status pipe. > > The connection change in hub m

[PATCH v3 1/2] USB: check port changes before hub runtime suspend for some bug device

2012-09-27 Thread Ming Lei
The hub status endpoint has a long 'bInterval', which is 255ms for FS/LS device and 256ms for HS device according to USB 2.0 spec, so the device connection change may be reported later more than 255ms via status pipe. The connection change in hub may have been happened already on the downstream po