Lines Matching full:system
5 System Sleep States
13 Sleep states are global low-power states of the entire system in which user
14 space code cannot be executed and the overall system activity is significantly
22 the Linux kernel can support up to four system sleep states, including
23 hibernation and up to three variants of system suspend. The sleep states that
31 This is a generic, pure software, light-weight variant of system suspend (also
36 states while the system is suspended.
38 The system is woken up from this state by in-band interrupts, so theoretically
44 deeper system suspend variants to provide reduced resume latency. It is always
54 operating state is lost (the system core logic retains power), so the system can
59 <s2idle>` too, nonboot CPUs are taken offline and all low-level system functions
64 The set of devices that can wake up the system from this state usually is
70 core system suspend subsystem. On ACPI-based systems this state is mapped to
71 the S1 system state defined by ACPI.
79 energy savings as everything in the system is put into a low-power state, except
94 platform firmware to resume the system from it. This may be the case on other
97 The set of devices that can wake up the system from S2RAM usually is reduced
103 is set and the support for it is registered by the platform with the core system
104 suspend subsystem. On ACPI-based systems it is mapped to the S3 system state
114 for system suspend. However, it requires some low-level code for resuming the
115 system to be present for the underlying CPU architecture.
117 Hibernation is significantly different from any of the system suspend variants.
118 It takes three system state changes to put it into hibernation and two system
121 First, when hibernation is triggered, the kernel stops all system activity and
123 the system goes into a state in which the snapshot image can be saved, the image
124 is written out and finally the system goes into the target low-power state in
128 Once the snapshot image has been written out, the system may either enter a
131 any system. However, entering a special low-power state may allow additional
132 means of system wakeup to be used (e.g. pressing a key on the keyboard or
137 the boot loader, depending on the system configuration, but anyway it causes
141 activity in the system is stopped and the restore kernel overwrites itself with
145 image kernel restores the system to the pre-hibernation state and allows user
150 for the given CPU architecture includes the low-level code for system resume.
153 Basic ``sysfs`` Interfaces for System Suspend and Hibernation
157 interface for system sleep regardless of the underlying system architecture or
165 to start a transition of the system into the sleep state represented by
174 If the kernel does not support any system sleep states, this file is
178 This file contains a list of strings representing supported system
188 Writing one of the listed strings into this file causes the system
194 If the kernel does not support system suspend, this file is not present.
204 Put the system into a special low-power state (e.g. ACPI S4) to
210 mechanism to put the system to sleep after creating a
215 Power off the system.
218 Reboot the system (useful for diagnostics mostly).
221 Hybrid system suspend. Put the system into the suspend sleep
223 If the system is successfully woken up from that state, discard
225 to restore the previous state of the system.
227 It is available if system suspend is supported.
230 Diagnostic operation. Load the image as though the system had
232 instance was a restore kernel and follow up with full system
263 during system suspend or resume (which is more common) more effectively.
267 information), so it will survive a system crash if one occurs right
274 According to the above, there are two ways to make the system go into the
278 :file:`/sys/power/state`. Likewise, there are two ways to make the system go
282 system go into the :ref:`suspend-to-RAM <s2ram>` state (write "deep" into