Lines Matching refs:suspend

26 	low-power states like "suspend" (also known as "suspend-to-RAM"), or
28 	"suspend-to-disk").
31 	by implementing various role-specific suspend and resume methods to
51 	transitions (suspend or hibernation).
57 	various role-specific suspend and resume methods, so that the hardware
94 	int (*suspend)(struct device *dev);
132 The core methods to suspend and resume devices reside in struct dev_pm_ops
231 suspend the device by putting it into a state compatible with the target
237 resume it by returning it to full power.  The suspend and resume operations
240 For simple drivers, suspend might quiesce the device using class code
253 walked in a bottom-up order to suspend devices.  A top-down order is
264 device to suspend) or has already suspended, as well as after all of the other
272 are used for freeze, standby, and memory sleep states ("suspend-to-RAM") and the
273 hibernation state ("suspend-to-disk").  Each phase involves executing callbacks
316 		prepare, suspend, suspend_late, suspend_noirq.
322 	time.)  Unlike the other suspend-related phases, during the prepare
332 	safely leave the device in runtime suspend (if runtime-suspended
334 	runtime suspend.  Namely, if the prepare callback returns a positive
337 	PM core will skip the suspend, suspend_late and	suspend_noirq suspend
344     2.	The suspend methods should quiesce the device to stop it from performing
349     3	For a number of devices it is convenient to split suspend into the
363 	an error during the suspend phase by fielding a shared interrupt
411 	undoing the actions of the suspend phase.
419 	the device may have been left in runtime suspend throughout the whole
420 	system suspend and resume (the suspend, suspend_late, suspend_noirq
421 	phases of system suspend and the resume_noirq, resume_early, resume
424 	back to the functional state after system suspend if necessary.  [For
443 suspend methods were called, for example by complete reinitialization.
446 the suspend was carried out, but that can't be guaranteed (in fact, it usually
520     10.	The poweroff phase is analogous to the suspend phase.
527 the same things as the suspend, suspend_late and suspend_noirq callbacks,
611 not NULL, the ->suspend() callback from the object pointed to by it will be
612 executed instead of its subsystem's (e.g. bus type's) ->suspend() callback and
626 Device Low Power (suspend) States
633 Some busses define rules about what different suspend states mean.  PCI
634 gives one example:  after the suspend sequence completes, a non-legacy