Lines Matching refs:phases

134 they are called in phases for every device, respecting the parent-child
269 Suspending or resuming the system is done in several phases.  Different phases
274 callbacks.  The various phases always run after tasks have been frozen and
275 before they are unfrozen.  Furthermore, the ``*_noirq`` phases run at a time
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
316 the phases are: ``prepare``, ``suspend``, ``suspend_late``, ``suspend_noirq``.
323 	suspend-related phases, during the ``prepare`` phase the device
342 	``suspend_noirq`` phases as well as all of the corresponding phases of
389 	"quiesce device" and "save device state" phases, in which cases
406 At the end of these phases, drivers should have stopped all I/O transactions
427 When resuming from freeze, standby or memory sleep, the phases are:
453         For this reason, unlike the other resume-related phases, during the
475 At the end of these phases, drivers should be as functional as they were before
511 more phases for hibernation, with a different set of callbacks.  These phases
517 the system ("power off").  The phases used to accomplish this are: ``prepare``,
562 and the phases are similar.
577 ``freeze_noirq`` phases.  Also, on many machines the firmware will power-down
610 ``prepare``, ``freeze``, and ``freeze_noirq`` phases.  However, the devices
611 affected by these phases are only those having drivers in the restore kernel;
616 ``thaw_noirq``, ``thaw_early``, ``thaw``, and ``complete`` phases, and then
624 the memory contents preserved), although it involves different phases:
639 ``freeze_late`` and ``freeze_noirq`` phases.  The device may even need to be
787 runtime suspend throughout those phases of the system-wide suspend (and