Lines Matching refs:system
9 Sleep states are global low-power states of the entire system in which user
10 space code cannot be executed and the overall system activity is significantly
18 the Linux kernel can support up to four system sleep states, including
19 hibernation and up to three variants of system suspend. The sleep states that
27 This is a generic, pure software, light-weight variant of system suspend (also
32 states while the system is suspended.
34 The system is woken up from this state by in-band interrupts, so theoretically
40 deeper system suspend variants to provide reduced resume latency. It is always
50 operating state is lost (the system core logic retains power), so the system can
55 <s2idle>` too, nonboot CPUs are taken offline and all low-level system functions
60 The set of devices that can wake up the system from this state usually is
66 core system suspend subsystem. On ACPI-based systems this state is mapped to
67 the S1 system state defined by ACPI.
75 energy savings as everything in the system is put into a low-power state, except
90 platform firmware to resume the system from it. This may be the case on other
93 The set of devices that can wake up the system from S2RAM usually is reduced
99 is set and the support for it is registered by the platform with the core system
100 suspend subsystem. On ACPI-based systems it is mapped to the S3 system state
110 for system suspend. However, it requires some low-level code for resuming the
111 system to be present for the underlying CPU architecture.
113 Hibernation is significantly different from any of the system suspend variants.
114 It takes three system state changes to put it into hibernation and two system
117 First, when hibernation is triggered, the kernel stops all system activity and
119 the system goes into a state in which the snapshot image can be saved, the image
120 is written out and finally the system goes into the target low-power state in
124 Once the snapshot image has been written out, the system may either enter a
127 any system. However, entering a special low-power state may allow additional
128 means of system wakeup to be used (e.g. pressing a key on the keyboard or
133 the boot loader, depending on the system configuration, but anyway it causes
137 activity in the system is stopped and the restore kernel overwrites itself with
141 image kernel restores the system to the pre-hibernation state and allows user
146 for the given CPU architecture includes the low-level code for system resume.
158 to start a transition of the system into the sleep state represented by
167 If the kernel does not support any system sleep states, this file is
171 This file contains a list of strings representing supported system
181 Writing one of the listed strings into this file causes the system
187 If the kernel does not support system suspend, this file is not present.
195 Put the system into a special low-power state (e.g. ACPI S4) to
201 Power off the system.
204 Reboot the system (useful for diagnostics mostly).
207 Hybrid system suspend. Put the system into the suspend sleep
209 If the system is successfully woken up from that state, discard
211 to restore the previous state of the system.
214 Diagnostic operation. Load the image as though the system had
216 instance was a restore kernel and follow up with full system
229 According to the above, there are two ways to make the system go into the
233 :file:`/sys/power/state`. Likewise, there are two ways to make the system go
237 system go into the :ref:`suspend-to-RAM <s2ram>` state (write "deep" into