Lines Matching refs:and

1 System Suspend and Device Interrupts
7 Suspending and Resuming Device IRQs
12 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
17 trigger and if any devices have not been suspended properly yet, it is better to
22 of suspended devices and cause unpredictable behavior to ensue as a result.
23 Unfortunately, such problems are very difficult to debug and the introduction
24 of suspend_device_irqs(), along with the "noirq" phase of device suspend and
36 suspend-resume cycle, including the "noirq" phases of suspending and resuming
37 devices as well as during the time when nonboot CPUs are taken offline and
39 but also to IPIs and to some other special-purpose interrupts.
48 Note that the IRQF_NO_SUSPEND flag affects the entire IRQ and not just one
52 the IRQ's users.  For this reason, using IRQF_NO_SUSPEND and IRQF_SHARED at the
56 System Wakeup Interrupts, enable_irq_wake() and disable_irq_wake()
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
80 it will be disabled, marked as pending and "suspended" so that it will be
94 Interrupts and Suspend-to-Idle
98 system sleep state that works by idling all of the processors and waiting for
108 state interrupt delivery mechanisms and doesn't require the platform to use
112 IRQF_NO_SUSPEND and enable_irq_wake()
115 There are very few valid reasons to use both enable_irq_wake() and the
116 IRQF_NO_SUSPEND flag on the same IRQ, and it is never valid to use both for the
124 Second, both enable_irq_wake() and IRQF_NO_SUSPEND apply to entire IRQs and not
126 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally
129 In rare cases an IRQ can be shared between a wakeup device driver and an
133 ensure that the IRQ will function as a wakeup source, and must request the IRQ