mirror of
https://github.com/raspberrypi/linux.git
synced 2025-12-07 18:40:10 +00:00
746680ec66
Manipulating IRQ flags (i.e.: IRQF_*) will soon be necessary, specially to register IRQ handlers through bindings::request_irq(). Add a kernel::irq::Flags for that purpose. Reviewed-by: Alice Ryhl <aliceryhl@google.com> Tested-by: Joel Fernandes <joelagnelf@nvidia.com> Tested-by: Dirk Behme <dirk.behme@de.bosch.com> Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com> Link: https://lore.kernel.org/r/20250811-topics-tyr-request_irq2-v9-2-0485dcd9bcbf@collabora.com [ Use expect(dead_code) for into_inner(), fix broken intra-doc link and typo. - Danilo ] Signed-off-by: Danilo Krummrich <dakr@kernel.org>
17 lines
516 B
Rust
17 lines
516 B
Rust
// SPDX-License-Identifier: GPL-2.0
|
|
|
|
//! IRQ abstractions.
|
|
//!
|
|
//! An IRQ is an interrupt request from a device. It is used to get the CPU's
|
|
//! attention so it can service a hardware event in a timely manner.
|
|
//!
|
|
//! The current abstractions handle IRQ requests and handlers, i.e.: it allows
|
|
//! drivers to register a handler for a given IRQ line.
|
|
//!
|
|
//! C header: [`include/linux/device.h`](srctree/include/linux/interrupt.h)
|
|
|
|
/// Flags to be used when registering IRQ handlers.
|
|
mod flags;
|
|
|
|
pub use flags::Flags;
|