On Fri, 21 Sep 2012, Ming Lei wrote: > >> IMO, suppose it is a problem, we should try to use 0 to make it > >> working because 'lsusb' is just a tool which isn't involved into actual > >> hub function. > >> > >> I will try to study 'lsusb' to see if there is one problem and try to solve it. > > > > The problem isn't in lsusb. The problem is that the autosuspend > > timeout should not be too small. > > As I explained it in another email, there shouldn't be the problem since > the device will be resumed in open() when it is accessed via libusb and > be suspended in its close(), should there? The hub will also be resumed when a child is accessed via libusb, and suspended when the child is released. As a result, the hub gets suspended and resumed multiple times: once for itself and once for each descendant. If the autosuspend timeout is large enough then the hub will be suspended and resumed only once. 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
