Lines Matching refs:phases

142 they are called in phases for every device, respecting the parent-child
277 Suspending or resuming the system is done in several phases.  Different phases
282 callbacks.  The various phases always run after tasks have been frozen and
283 before they are unfrozen.  Furthermore, the ``*_noirq`` phases run at a time
287 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
324 the phases are: ``prepare``, ``suspend``, ``suspend_late``, ``suspend_noirq``.
331 	suspend-related phases, during the ``prepare`` phase the device
350 	``suspend_noirq`` phases as well as all of the corresponding phases of
393 	"quiesce device" and "save device state" phases, in which cases
410 At the end of these phases, drivers should have stopped all I/O transactions
431 When resuming from freeze, standby or memory sleep, the phases are:
457         For this reason, unlike the other resume-related phases, during the
467 	``suspend_noirq`` phases of system suspend and the ``resume_noirq``,
468 	``resume_early``, ``resume`` phases of system resume may have been
479 At the end of these phases, drivers should be as functional as they were before
515 more phases for hibernation, with a different set of callbacks.  These phases
521 the system ("power off").  The phases used to accomplish this are: ``prepare``,
566 and the phases are similar.
581 ``freeze_noirq`` phases.
612 ``prepare``, ``freeze``, and ``freeze_noirq`` phases.  However, the devices
613 affected by these phases are only those having drivers in the restore kernel;
618 ``thaw_noirq``, ``thaw_early``, ``thaw``, and ``complete`` phases, and then
626 the memory contents preserved), although it involves different phases:
641 ``freeze_late`` and ``freeze_noirq`` phases.  The device may even need to be