> > > > When the infrastructure is in place, it will automatically take care of > > > > suspending the device once all the interfaces are suspended. For now, > > > > however, that's your responsibility. > > > > I'd say it differently: For now don't try that at all. Because in addition > > to an autosuspend mechanism being missing, so is autoresume. > > That's not quite true. usbcore is aware of remote wakeup signals and will > automatically take care of resuming the device and all its interfaces. > Remember, though, that everything you do will be experimental and subject > to change once the runtime PM infrastructure is ready.
By "autoresume" I meant at the level of automatically resuming an interface (and hence potentially device) that's been "autosuspended" and which does not support remote wakeup. One example would be a usb-storage device; they rarely support remote wakeup. For something like a USB mouse, you're right that remote wakeup will normally suffice ... it wouldn't need autoresume. - Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
