Lines Matching refs:that

11 suspend after the "late" phase of suspending devices (that is, after all of the
15 The rationale for doing so is that after the "late" phase of device suspend
19 interrupt handlers for shared IRQs that device drivers implementing them were
28 of resuming devices (that is, before starting to execute ->resume_early
29 callbacks for devices).  The function doing that is resume_device_irqs().
35 There are interrupts that can legitimately trigger during the entire system
41 The IRQF_NO_SUSPEND flag is used to indicate that to the IRQ subsystem when
44 expected during the suspend-resume cycle, but does not guarantee that the
48 Note that the IRQF_NO_SUSPEND flag affects the entire IRQ and not just one
64 (such as an SoC) so that signals from a given line are routed in a different way
68 wake up the system from sleep sates, the corresponding input of that interrupt
70 After wakeup, it generally is better to disable that input to prevent the
76 turns that logic off.
80 it will be disabled, marked as pending and "suspended" so that it will be
83 progress to be aborted (that doesn't have to happen immediately, but at one
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
101 Of course, this means that all of the interrupts with the IRQF_NO_SUSPEND flag
102 set will bring CPUs out of idle while in that state, but they will not cause the
107 is that the wakeup from suspend-to-idle is signaled using the usual working
133 ensure that the IRQ will function as a wakeup source, and must request the IRQ
134 with IRQF_COND_SUSPEND to tell the core that it meets these requirements. If