Lines Matching refs:system

10 Device interrupt request lines (IRQs) are generally disabled during system
27 Device IRQs are re-enabled during system resume, right before the "early" phase
35 There are interrupts that can legitimately trigger during the entire system
45 interrupt will wake the system from a suspended state -- for such cases it is
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
68 wake up the system from sleep sates, the corresponding input of that interrupt
75 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
81 re-enabled by resume_device_irqs() during the subsequent system resume.  Also
82 the PM core is notified about the event which causes the system suspend in
87 system suspend currently in progress to be aborted or wake up the system if
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
98 system sleep state that works by idling all of the processors and waiting for
103 IRQ subsystem to trigger a system wakeup.
106 analogy with what they do in the full system suspend case.  The only difference
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