Lines Matching full:system

2 System Suspend and Device Interrupts
12 Device interrupt request lines (IRQs) are generally disabled during system
29 Device IRQs are re-enabled during system resume, right before the "early" phase
37 There are interrupts that can legitimately trigger during the entire system
47 interrupt will wake the system from a suspended state -- for such cases it is
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
70 wake up the system from sleep states, the corresponding input of that interrupt
77 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
83 re-enabled by resume_device_irqs() during the subsequent system resume.  Also
84 the PM core is notified about the event which causes the system suspend in
89 system suspend currently in progress to be aborted or wake up the system if
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
100 system sleep state that works by idling all of the processors and waiting for
105 IRQ subsystem to trigger a system wakeup.
107 System wakeup interrupts, in turn, will trigger wakeup from suspend-to-idle in
108 analogy with what they do in the full system suspend case.  The only difference
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