Lines Matching refs:suspend

42 the system, we speak of it as a "system suspend".  When a particular
44 call it a "dynamic suspend" (also known as a "runtime suspend" or
45 "selective suspend").  This document concentrates mostly on how
98 Dynamic suspends occur when the kernel decides to suspend an idle
120 agent outside the USB stack: system suspend/resume (triggered by
124 all dynamic suspend events are internal; external agents are not
152 		effect until the following suspend.)
168 		"suspend", meaning that the device should remain
242 support it very well.  You can suspend them all right, but when you
266 If a driver knows that its device has proper suspend/resume support,
293 	.suspend
300 	The suspend method is called to warn the driver that the
302 	negative error code, the suspend will be aborted.  Normally
315 	before the suspend).
320 waking up from hibernation, as many systems do not maintain suspend
333 USB drivers are bound to interfaces, so their suspend and resume
335 principle one might want to suspend some interfaces on a device (i.e.,
340 to suspend or resume some but not all of a device's interfaces.  The
387 	use a workqueue to do the resume or suspend part of their
458 long enough but not yet gotten around to calling the driver's suspend
459 method.  The suspend method must be responsible for synchronizing with
464 External suspend calls should never be allowed to fail in this way,
466 the PMSG_IS_AUTO() macro to the message argument to the suspend
476 suspend or resume method is called.  This implies that external
477 suspend/resume events are mutually exclusive with calls to probe,
481 If a driver wants to block all suspend/resume calls during some
495 Firstly, a device may already be autosuspended when a system suspend
504 suspend is underway.  The window for this is short, since system
508 cause the system suspend to abort.  If the remote wakeup doesn't
510 resume as soon as the system suspend is complete.  Or the remote
578 goes through during system suspend, i.e. the power session is lost.  Any
579 USB device or driver that misbehaves with system suspend will be
604 need to unbind the interface drivers before the usb_device will suspend.  An
648 1/ Port suspend is sequenced to guarantee that hi-speed ports are powered-off
651    the port to power-off until its highspeed peer has gone to its runtime suspend
662    device can suspend (autosuspend-delay) and resume (reset-resume latency).
668 		port may suspend/poweroff provided that
694 		expected to be safe to allow these ports to suspend
732 		power session loss (suspend / port-power event).  When