Lines Matching full:system

15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
18 kernel puts the system into one of these states when requested by user space
19 and the system stays in it until a special signal is received from one of
21 user space code can run.  Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
27 components of the system, as needed, in the working state.  In consequence, if
28 this strategy is in use, the working state of the system usually does not
30 a metastate covering a range of different power states of the system in which
37 If all of the system components are active, the system as a whole is regarded as
39 draw (or maximum energy usage) of it.  If all of them are inactive, the system
41 state from the physical system configuration and power draw perspective, but
43 for the same system in a sleep state.  However, transitions from sleep states
45 typically the system can spend much more time in a sleep state than it can be
50 Namely, if the user indicates that the system will not be in use going forward,
51 for example by closing its lid (if the system is a laptop), it probably should
55 may come back to it at any time and then may want the system to be immediately