Lines Matching refs:sleep

56 	sleep power management case, they need to collaborate by implementing
63 to entering some system-wide low-power state (system sleep) ... and that
82 system sleep and runtime power management.
125 struct dev_pm_ops objects and it is suitable only for implementing system sleep
154 sleep state).  These fields are initialized by bus or device driver code using
190 device_may_wakeup() to decide what to do during a system sleep transition.
200 some systems it is impossible to trigger them from system sleep states.  In any
222 to a sleep state even though its runtime_auto flag is clear.
230 When the system goes into a sleep state, each device's driver is asked to
272 are used for freeze, standby, and memory sleep states ("suspend-to-RAM") and the
313 When the system goes into the freeze, standby or memory sleep state,
346 	that if a device has system-sleep callbacks but does not support runtime
383 system is in the sleep state.  For example, enable_irq_wake() might identify
394 When resuming from freeze, standby or memory sleep, the phases are:
471 sleep states, because it involves creating and saving a system image.
522 before putting the system into the freeze, standby or memory sleep state,
542 Resuming from hibernation is, again, more complicated than resuming from a sleep
578 functionality.  The operation is much like waking up from the memory sleep
649 active too, it'd only be the CPU and some peripherals that sleep).
652 can be fully active in certain sleep states, such as an LCD display that's
684 as "off", "sleep", "idle", "active", and so on.  Those states will in some
686 usually include hardware states that are also used in system sleep states.
689 power states due to runtime power management.  The system sleep PM callbacks
701 During system-wide resume from a sleep state it's easiest to put devices into