Lines Matching refs:wide
30 This writeup gives an overview of how drivers interact with system-wide
44 Drivers can enter low-power states as part of entering system-wide
70 states at run time may require special handling during system-wide power
83 to entering some system-wide low-power state (system sleep) ... and that
113 management while the remaining ones are used during system-wide power
222 system-wide power transitions. In particular, the device can (and in the
224 system-wide transition to a sleep state even though its :c:member:`runtime_auto`
752 A system-wide power transition can be started while some devices are in low
759 desirable to leave a suspended device in that state during a system-wide power
765 If it is necessary to resume a device from runtime suspend during a system-wide
783 runtime suspend at the beginning of the ``suspend_late`` phase of system-wide
786 after that point until the system-wide transition is over (the PM core itself
787 does that for devices whose "noirq", "late" and "early" system-wide PM callbacks
788 are executed directly by it). If that happens, the driver's system-wide resume
789 callbacks, if present, may still be invoked during the subsequent system-wide
792 cope with the invocation of its system-wide resume callbacks back-to-back with
797 During system-wide resume from a sleep state it's easiest to put devices into
805 runtime suspend before the preceding system-wide suspend (or analogous)
809 skipping their system-wide resume callbacks for this reason. Whether or not the
819 during the "noirq" phase of the preceding system-wide suspend (or analogous)
827 directly by the PM core, all of the system-wide resume callbacks are skipped if