On Tue, 22 May 2007, Alan Stern wrote: > > > > - adapt to hibernate > > > > > > What adaptations are needed? > > > > Do I need to kill remote wakeup? > > No. It should be handled at a higher level. (Right now we don't > really handle it properly; this is partly the fault of the PM core.)
This isn't is bad as it may sound. Our handling of remote wakeup isn't truly _bad_ -- it just doesn't quite match the USB spec. There's no danger of a remote wakeup request accidentally activating a device in the middle of snapshotting, or even in the middle of preparing for the snapshot, since khubd will already be frozen. The USB spec puts pretty stringent limitations on how long a host is allowed to ignore a remote wakeup request. In fact, the limit is 1 ms (TURSM; see 7.1.7.7). If a device does send a wakeup request during snapshotting, we will almost certainly violate that limit. The correct approach is to disable remote wakeup before starting the snapshot, but we don't currently do this. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
