Lines Matching +full:trigger +full:- +full:source

10 -----------------------------------
14 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
19 trigger and if any devices have not been suspended properly yet, it is better to
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 ------------------------
37 There are interrupts that can legitimately trigger during the entire system
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 ------------------------------------------------------------------
67 during system sleep so as to trigger a system wakeup when needed.  For example,
83 re-enabled by resume_device_irqs() during the subsequent system resume.  Also
88 This way every interrupt from a wakeup interrupt source will either cause the
96 Interrupts and Suspend-to-Idle
97 ------------------------------
99 Suspend-to-idle (also known as the "freeze" sleep state) is a relatively new
105 IRQ subsystem to trigger a system wakeup.
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 -------------------------------------
128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally
135 ensure that the IRQ will function as a wakeup source, and must request the IRQ