Lines Matching refs:states

22 states:
25 	Drivers can enter low-power states as part of entering system-wide
26 	low-power states like "suspend" (also known as "suspend-to-RAM"), or
40 	system enter low-power states more often.
43 	Devices may also be put into low-power states while the system is
50 	states at run time may require special handling during system-wide power
60 There's not a lot to be said about those low-power states except that they are
62 have been put into low-power states (at runtime), the effect may be very similar
197 low-power states to trigger specific interrupts to signal conditions in which
200 some systems it is impossible to trigger them from system sleep states.  In any
272 are used for freeze, standby, and memory sleep states ("suspend-to-RAM") and the
444 some systems support multiple "run" states, and the mode in effect at
471 sleep states, because it involves creating and saving a system image.
605 cases it generally is not possible to put devices into low-power states
635 Device low-power states aren't standard.  One device might only handle
640 Some busses define rules about what different suspend states mean.  PCI
644 several PCI-standard device states, some of which are optional.
652 can be fully active in certain sleep states, such as an LCD display that's
683 often support a range of runtime power states, which might use names such
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