Lines Matching full:resume

42 	by implementing various role-specific suspend and resume methods to
69 	various role-specific suspend and resume methods, so that the hardware
119 The core methods to suspend and resume devices reside in
233 resume it by returning it to full power.  The suspend and resume operations
238 matching resume calls would then completely reinitialize the hardware
251 used to resume those devices.
331 	method must not update its state in case it is necessary to resume it
343 	the subsequent device resume for all of these devices.	In that case,
378 	Namely, they may resume the devices from runtime suspend by
381 	time (in case the drivers need to resume the devices from runtime
428 ``resume_noirq``, ``resume_early``, ``resume``, ``complete``.
445 	of the resume methods.  This generally involves undoing the actions of
448     3.	The ``->resume`` methods should bring the device back to its operating
453         For this reason, unlike the other resume-related phases, during the
457 	soon as the ``->resume`` callbacks occur; it's not necessary to wait
462 	whole system suspend and resume (its ``->suspend``, ``->suspend_late``,
464 	``->resume_early``, and ``->resume`` callbacks may have been
468 	resume request for the device for this purpose.]  To check if that is
481 the end of resume might not be the one which preceded suspension.
552     7.	The ``thaw`` phase is analogous to the ``resume`` phase discussed
631     3.	The ``restore`` phase is analogous to the ``resume`` phase.
635 The main difference from ``resume[_early|_noirq]`` is that
641 matter, so the ``->resume[_early|_noirq]`` and ``->restore[_early|_norq]``
688 another might require a hard shut down with re-initialization on resume.
763 If it is necessary to resume a device from runtime suspend during a system-wide
777 Some bus types and PM domains have a policy to resume all devices from runtime
807 During system-wide resume from a sleep state it's easiest to put devices into
818 "early" resume callbacks to be skipped if the device can be left in suspend
821 suspend-resume cycle and on the type of the system transition under way.
834 has a reason to prevent the driver's "noirq" and "early" resume callbacks from
835 being skipped during the subsequent system resume transition, it should
843 for the driver's "noirq" and "early" resume callbacks to be skipped.  Whether or
847 If that function returns ``true``, the driver's "noirq" and "early" resume
855 system-wide resume-type transitions.]
859 callbacks are skipped, its system-wide "noirq" and "early" resume callbacks, if
862 driver must be prepared to cope with the invocation of its system-wide resume
870 system-wide suspend-resume callbacks of the driver are present, for example.]
873 system-wide "noirq" and "early" resume callbacks may be skipped while its "late"
879 ``DPM_FLAG_MAY_SKIP_RESUME`` and uses the same pair of suspend/resume callback
880 functions for runtime PM and system-wide suspend/resume.]