Lines Matching full:system

5 System Suspend Code Flows
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
19 For those sleep states, the transition from the working state of the system into
20 the target sleep state is referred to as *system suspend* too (in the majority
21 of cases, whether this means a transition or a sleep state of the system should
23 working state is referred to as *system resume*.
26 different sleep states of the system are quite similar, but there are some
45 The following steps are taken in order to transition the system from the working
48  1. Invoking system-wide suspend notifiers.
53     That allows them to prepare for the change of the system state and to clean
65     put into uninterruptible sleep until the end of the subsequent system resume
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
92     would be triggered in the working state of the system (those actions are
93     deferred till the subsequent system resume transition as described
96     IRQs associated with system wakeup devices are "armed" so that the resume
97     transition of the system is started when one of them signals an event.
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
134     If the interrupt that has woken up the CPU was armed for system wakeup,
135     the system resume transition begins.
157  4. Invoking system-wide resume notifiers.
167 The following steps are taken in order to transition the system from the working
170  1. Invoking system-wide suspend notifiers.
183     described `above <s2idle_suspend_>`_, but the arming of IRQs for system
189     suspend-to-idle can reduce system power very effectively.
196     That usually prevents in-band hardware interrupts from waking up the system,
198     configuration of system wakeup sources usually starts when system wakeup
205     configuration of the system (in particular, the hardware cannot be accessed
211     to take all of the CPUs in the system, except for one (the boot CPU),
218  5. Suspending core system components.
220     This prepares the core system components for (possibly) losing power going
225     This is expected to remove power from all of the system components except
227     latter) and some devices designated for system wakeup.
236 The following steps are taken in order to transition the system from a
239  1. Platform-specific system wakeup.
241     The platform is woken up by a signal from one of the designated system
247  2. Resuming core system components.
249     The suspend-time configuration of the core system components is restored and
267  6. Invoking system-wide resume notifiers.