Expand description

Container for interrupt flags.

Constants

If the IRQ is shared with a NO_SUSPEND user, execute this interrupt handler after suspending interrupts. For system wakeup devices users need to implement wakeup detection in their interrupt handlers.
Resume IRQ early during syscore instead of at device resume time.
Force enable it on resume even if NO_SUSPEND is set.
Interrupt is used for polling (only the interrupt that is registered first in a shared interrupt is considered for performance reasons).
Flag to exclude this interrupt from irq balancing.
Don’t enable IRQ or NMI automatically when users request it. Users will enable it explicitly by enable_irq or enable_nmi later.
Exclude from runnaway detection for IPI and similar handlers, depends on PERCPU.
Do not disable this IRQ during suspend. Does not guarantee that this interrupt will wake the system from a suspended state.
Interrupt cannot be threaded.
Interrupt is not reenabled after the hardirq handler finished. Used by threaded interrupts which need to keep the irq line disabled until the threaded handler has been run.
Interrupt is per cpu.
Set by callers when they expect sharing mismatches to occur.
Allow sharing the irq among several devices.
Flag to mark this interrupt as timer interrupt.
The interrupt is triggered when the signal goes from high to low.
The interrupt is triggered while the signal is held high.
The interrupt is triggered while the signal is held low.
Use the interrupt line as already configured.
The interrupt is triggered when the signal goes from low to high.
This documentation is an old archive. Please see https://rust.docs.kernel.org instead.