Lines Matching full:wakeup

58 System Wakeup Interrupts, enable_irq_wake() and disable_irq_wake()
61 System wakeup interrupts generally need to be configured to wake up the system
67 during system sleep so as to trigger a system wakeup when needed.  For example,
69 handling system wakeup events.  Then, if a given interrupt line is supposed to
72 After wakeup, it generally is better to disable that input to prevent the
77 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
86 of the points where the suspend thread looks for pending wakeup events).
88 This way every interrupt from a wakeup interrupt source will either cause the
91 not executed for system wakeup IRQs.  They are only executed for IRQF_NO_SUSPEND
92 IRQs at that time, but those IRQs should not be configured for system wakeup
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
123 directly at odds with the rules for handling system wakeup interrupts (interrupt
127 to individual interrupt handlers, so sharing an IRQ between a system wakeup
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
133 must be able to discern spurious IRQs from genuine wakeup events (signalling
135 ensure that the IRQ will function as a wakeup source, and must request the IRQ