Lines Matching refs:in

20 the target sleep state is referred to as *system suspend* too (in the majority
37 *platform-dependent suspend* states in what follows.
45 The following steps are taken in order to transition the system from the working
58     Tasks are frozen primarily in order to avoid unchecked hardware accesses
61     of the transition is in progress (which might have been problematic for
73     available in kernel space to synchronize themselves with system suspend and
79     Devices are suspended in four phases called *prepare*, *suspend*,
81     information on what exactly happens in each phase).
83     Every device is visited in each phase, but typically it is not physically
84     accessed in more than two of them.
92     would be triggered in the working state of the system (those actions are
109     That allows the CPUs to stay in the deep idle state relatively long in one
115     system wakeup, in which case the system resume transition is started.
123 The following steps are taken in order to transition the system from the
129     leaves the idle state entered in the last step of the preceding suspend
139     Devices are resumed in four phases called *noirq resume*, *early resume*,
141     information on what exactly happens in each phase).
143     Every device is visited in each phase, but typically it is not physically
144     accessed in more than two of them.
152     Tasks frozen in step 2 of the preceding `suspend <s2idle_suspend_>`_
167 The following steps are taken in order to transition the system from the working
187     when all CPUs in them are in sufficiently deep idle states and all I/O
192     controllers) need to be turned off in a platform-specific way (implemented
193     in the hooks provided by the platform driver) to achieve comparable power
196     That usually prevents in-band hardware interrupts from waking up the system,
197     which must be done in a special platform-dependent way.  Then, the
204     On some platforms the suspend hooks mentioned above must run in a one-CPU
205     configuration of the system (in particular, the hardware cannot be accessed
206     by any code running in parallel with the platform suspend hooks that may,
207     and often do, trap into the platform firmware in order to finalize the
211     to take all of the CPUs in the system, except for one (the boot CPU),
226     for the memory controller and RAM (in order to preserve the contents of the
236 The following steps are taken in order to transition the system from a
242     wakeup devices (which need not be an in-band hardware interrupt)  and
254     The CPUs disabled in step 4 of the preceding suspend transition are taken