Lines Matching refs:phases

146 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 various phases always run after tasks have been frozen and before they are
277 unfrozen.  Furthermore, the *_noirq phases run at a time when IRQ handlers have
280 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
314 the phases are:
322 	time.)  Unlike the other suspend-related phases, during the prepare
338 	phases as well as the resume_noirq, resume_early and resume phases of
350 	"quiesce device" and "save device state" phases, in which cases
367 At the end of these phases, drivers should have stopped all I/O transactions
387 When resuming from freeze, standby or memory sleep, the phases are:
421 	phases of system suspend and the resume_noirq, resume_early, resume
422 	phases of system resume may have been skipped for it).  In that case,
432 At the end of these phases, drivers should be as functional as they were before
465 Therefore there are more phases for hibernation, with a different set of
466 callbacks.  These phases always run after tasks have been frozen and memory has
472 system (poweroff).  The phases used to accomplish this are:
516 and the phases are similar.
530 during the freeze, freeze_late or freeze_noirq phases.
559 freeze, and freeze_noirq phases.  However the devices affected by these phases
565 thaw_noirq, thaw, and complete phases, and then continue running normally.  This
572 state, although it involves different phases:
587 state remembered from the freeze, freeze_late and freeze_noirq phases.  The