Lines Matching full:state

35 working state), such that the processors can spend time in their deepest idle
38 The system is woken up from this state by in-band interrupts, so theoretically
39 any devices that can cause interrupts to be generated in the working state can
42 This state can be used on platforms without support for :ref:`standby <standby>`
52 This state, if supported, offers moderate, but real, energy savings, while
53 providing a relatively straightforward transition back to the working state.  No
54 operating state is lost (the system core logic retains power), so the system can
60 are suspended during transitions into this state.  For this reason, it should
62 the resume latency will generally be greater than for that state.
64 The set of devices that can wake up the system from this state usually is
68 This state is supported if the :c:macro:`CONFIG_SUSPEND` kernel configuration
70 core system suspend subsystem.  On ACPI-based systems this state is mapped to
71 the S1 system state defined by ACPI.
78 This state (also referred to as STR or S2RAM), if supported, offers significant
79 energy savings as everything in the system is put into a low-power state, except
88 The state of devices and CPUs is saved and held in memory.  All devices are
91 back to the "on" state.
104 suspend subsystem.  On ACPI-based systems it is mapped to the S3 system state
112 This state (also referred to as Suspend-to-Disk or STD) offers the greatest
118 It takes three system state changes to put it into hibernation and two system
119 state changes to resume it.
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
129 special low-power state (like ACPI S4), or it may simply power down itself.
131 any system.  However, entering a special low-power state may allow additional
145 image kernel restores the system to the pre-hibernation state and allows user
162 ``state``
165 	to start a transition of the system into the sleep state represented by
180 	associated with the "mem" string in the ``state`` file described above.
190 	in the ``state`` file.  The string representing the suspend variant
191 	currently associated with the "mem" string in the ``state`` file is
204 		Put the system into a special low-power state (e.g. ACPI S4) to
222 		state selected through the ``mem_sleep`` file described above.
223 		If the system is successfully woken up from that state, discard
225 		to restore the previous state of the system.
241 	to :file:`/sys/power/state`.
275 :ref:`suspend-to-idle <s2idle>` state.  The first one is to write "freeze"
276 directly to :file:`/sys/power/state`.  The second one is to write "s2idle" to
278 :file:`/sys/power/state`.  Likewise, there are two ways to make the system go
279 into the :ref:`standby <standby>` state (the strings to write to the control
281 state is supported by the platform.  However, there is only one way to make the
282 system go into the :ref:`suspend-to-RAM <s2ram>` state (write "deep" into
283 :file:`/sys/power/mem_sleep` and "mem" into :file:`/sys/power/state`).