Lines Matching refs:phases

136 they are called in phases for every device, respecting the parent-child
271 Suspending or resuming the system is done in several phases.  Different phases
276 callbacks.  The various phases always run after tasks have been frozen and
277 before they are unfrozen.  Furthermore, the ``*_noirq`` phases run at a time
281 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
318 the phases are: ``prepare``, ``suspend``, ``suspend_late``, ``suspend_noirq``.
325 	suspend-related phases, during the ``prepare`` phase the device
344 	``suspend_noirq`` phases as well as all of the corresponding phases of
387 	"quiesce device" and "save device state" phases, in which cases
404 At the end of these phases, drivers should have stopped all I/O transactions
425 When resuming from freeze, standby or memory sleep, the phases are:
451         For this reason, unlike the other resume-related phases, during the
461 	``suspend_noirq`` phases of system suspend and the ``resume_noirq``,
462 	``resume_early``, ``resume`` phases of system resume may have been
473 At the end of these phases, drivers should be as functional as they were before
509 more phases for hibernation, with a different set of callbacks.  These phases
515 the system ("power off").  The phases used to accomplish this are: ``prepare``,
560 and the phases are similar.
575 ``freeze_noirq`` phases.
606 ``prepare``, ``freeze``, and ``freeze_noirq`` phases.  However, the devices
607 affected by these phases are only those having drivers in the restore kernel;
612 ``thaw_noirq``, ``thaw_early``, ``thaw``, and ``complete`` phases, and then
620 the memory contents preserved), although it involves different phases:
635 ``freeze_late`` and ``freeze_noirq`` phases.  The device may even need to be