Lines Matching +full:wake +full:- +full:device

2 System Suspend and Device Interrupts
9 Suspending and Resuming Device IRQs
10 -----------------------------------
12 Device interrupt request lines (IRQs) are generally disabled during system
14 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
17 The rationale for doing so is that after the "late" phase of device suspend
21 interrupt handlers for shared IRQs that device drivers implementing them were
26 of suspend_device_irqs(), along with the "noirq" phase of device suspend and
29 Device IRQs are re-enabled during system resume, right before the "early" phase
30 of resuming devices (that is, before starting to execute ->resume_early
35 ------------------------
38 suspend-resume cycle, including the "noirq" phases of suspending and resuming
41 but also to IPIs and to some other special-purpose interrupts.
44 requesting a special-purpose interrupt.  It causes suspend_device_irqs() to
46 expected during the suspend-resume cycle, but does not guarantee that the
47 interrupt will wake the system from a suspended state -- for such cases it is
59 ------------------------------------------------------------------
61 System wakeup interrupts generally need to be configured to wake up the system
70 wake up the system from sleep states, the corresponding input of that interrupt
75 The IRQ subsystem provides two helper functions to be used by device drivers for
83 re-enabled by resume_device_irqs() during the subsequent system resume.  Also
89 system suspend currently in progress to be aborted or wake up the system if
96 Interrupts and Suspend-to-Idle
97 ------------------------------
99 Suspend-to-idle (also known as the "freeze" sleep state) is a relatively new
107 System wakeup interrupts, in turn, will trigger wakeup from suspend-to-idle in
109 is that the wakeup from suspend-to-idle is signaled using the usual working
115 -------------------------------------
119 same device.
131 In rare cases an IRQ can be shared between a wakeup device driver and an
132 IRQF_NO_SUSPEND user. In order for this to be safe, the wakeup device driver