Lines Matching refs:suspend
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
20 the target sleep state is referred to as *system suspend* too (in the majority
25 The kernel code flows associated with the suspend and resume transitions for
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
35 available. Apart from that, the suspend and resume code flows for these sleep
37 *platform-dependent suspend* states in what follows.
46 state to the :ref:`suspend-to-idle <s2idle>` sleep state:
48 1. Invoking system-wide suspend notifiers.
50 Kernel subsystems can register callbacks to be invoked when the suspend
68 The kernel threads that choose to be frozen during system suspend for
73 available in kernel space to synchronize themselves with system suspend and
79 Devices are suspended in four phases called *prepare*, *suspend*,
80 *late suspend* and *noirq suspend* (see :ref:`driverapi_pm_devices` for more
86 The runtime PM API is disabled for every device during the *late* suspend
88 invoked before the *noirq* suspend phase.
124 :ref:`suspend-to-idle <s2idle>` sleep state into the working state:
129 leaves the idle state entered in the last step of the preceding suspend
152 Tasks frozen in step 2 of the preceding `suspend <s2idle_suspend_>`_
159 This is analogous to step 1 of the `suspend <s2idle_suspend_>`_ transition
168 state to platform-dependent suspend state:
170 1. Invoking system-wide suspend notifiers.
172 This step is the same as step 1 of the suspend-to-idle suspend transition
177 This step is the same as step 2 of the suspend-to-idle suspend transition
182 This step is analogous to step 3 of the suspend-to-idle suspend transition
189 suspend-to-idle can reduce system power very effectively.
199 devices are suspended and is finalized by the platform suspend hooks later
204 On some platforms the suspend hooks mentioned above must run in a one-CPU
206 by any code running in parallel with the platform suspend hooks that may,
208 suspend transition).
230 to finalize the suspend transition as needed.
237 platform-dependent suspend state into the working state:
249 The suspend-time configuration of the core system components is restored and
254 The CPUs disabled in step 4 of the preceding suspend transition are taken
255 back online and their suspend-time configuration is restored.
259 This step is the same as step 2 of the suspend-to-idle suspend transition
264 This step is the same as step 3 of the suspend-to-idle suspend transition
269 This step is the same as step 4 of the suspend-to-idle suspend transition