On Tue, 23 Oct 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 may have been happened already on the > downstream ports, but no status URB completes when it is killed > in hub_suspend(auto), so the connection change may be missed by some > buggy hub devices, which won't generate remote wakeup signal after > their remote wakeup is enabled and they are put into suspend state. > > The problem can be observed at least on the below Genesys Logic, Inc. > hub devices: > > 0x05e3,0x0606 > 0x05e3,0x0608
> + .idVendor = 0x05e3, Can you make this a symbolic constant (USB_VENDOR_GENESYS_LOGIC)? Or at least put a comment there? Alan Stern -- 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
