Am Freitag, 27. Januar 2012, 20:27:29 schrieb Bjørn Mork: > This works well if the device supports remote wakeup, but when it > doesn't then this ends up with a device that only rarely autosuspends. > It is of course expected that the device cannot autosuspend between the > open and close calls, as needs_remote_wakeup is 1 then. But after close > I would expect the device to autosuspend again. It does not. Until some > external trigger event happens (e.g. changing the autosuspend timeout). > > I wonder if the problem might be that the usbcore doesn't notice the > changed needs_remote_wakeup? I experimented with wrapping this change > between usb_autopm_get_interface and usb_autopm_put_interface and that > worked! I.e. > That exactly is the problem and you found the correct solution. You might want to read this: http://lwn.net/Articles/373550/ HTH Oliver -- 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
