Lines Matching refs:wakeup

59 System wakeup interrupts generally need to be configured to wake up the system
65 during system sleep so as to trigger a system wakeup when needed.  For example,
67 handling system wakeup events.  Then, if a given interrupt line is supposed to
70 After wakeup, it generally is better to disable that input to prevent the
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
84 of the points where the suspend thread looks for pending wakeup events).
86 This way every interrupt from a wakeup interrupt source will either cause the
89 not executed for system wakeup IRQs.  They are only executed for IRQF_NO_SUSPEND
90 IRQs at that time, but those IRQs should not be configured for system wakeup
103 IRQ subsystem to trigger a system wakeup.
105 System wakeup interrupts, in turn, will trigger wakeup from suspend-to-idle in
107 is that the wakeup from suspend-to-idle is signaled using the usual working
121 directly at odds with the rules for handling system wakeup interrupts (interrupt
125 to individual interrupt handlers, so sharing an IRQ between a system wakeup
129 In rare cases an IRQ can be shared between a wakeup device driver and an
130 IRQF_NO_SUSPEND user. In order for this to be safe, the wakeup device driver
131 must be able to discern spurious IRQs from genuine wakeup events (signalling
133 ensure that the IRQ will function as a wakeup source, and must request the IRQ