Lines Matching full:wide

22 This writeup gives an overview of how drivers interact with system-wide
36 	Drivers can enter low-power states as part of entering system-wide
62 	states at run time may require special handling during system-wide power
75 to entering some system-wide low-power state (system sleep) ... and that
105 management while the remaining ones are used during system-wide power
214 system-wide power transitions.  In particular, the device can (and in the
216 system-wide transition to a sleep state even though its :c:member:`runtime_auto`
750 A system-wide power transition can be started while some devices are in low
757 desirable to leave a suspended device in that state during a system-wide power
763 If it is necessary to resume a device from runtime suspend during a system-wide
787 runtime suspend throughout those phases of the system-wide suspend (and
791 be valid in general.]  If the middle-layer system-wide PM callbacks are present
807 During system-wide resume from a sleep state it's easiest to put devices into
813 runtime suspend before the preceding system-wide suspend (or analogous)
819 after system-wide PM transitions to the working state.  Whether or not that is
850 during the preceding system-wide suspend transition and its
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
864 intervening ``->runtime_resume`` and system-wide suspend callbacks) and the
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"
880 functions for runtime PM and system-wide suspend/resume.]