linux/rust
Alice Ryhl 29e16fcd67 rust: irq: add &Device<Bound> argument to irq callbacks
When working with a bus device, many operations are only possible while
the device is still bound. The &Device<Bound> type represents a proof in
the type system that you are in a scope where the device is guaranteed
to still be bound. Since we deregister irq callbacks when unbinding a
device, if an irq callback is running, that implies that the device has
not yet been unbound.

To allow drivers to take advantage of that, add an additional argument
to irq callbacks.

Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com>
Link: https://lore.kernel.org/r/20250811-topics-tyr-request_irq2-v9-7-0485dcd9bcbf@collabora.com
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
2025-08-12 20:33:33 +02:00
..
bindings rust: irq: add support for non-threaded IRQs and handlers 2025-08-12 20:22:00 +02:00
helpers rust: pci: add irq accessors 2025-08-12 20:33:33 +02:00
kernel rust: irq: add &Device<Bound> argument to irq callbacks 2025-08-12 20:33:33 +02:00
macros Rust changes for v6.17 2025-08-03 13:49:10 -07:00
pin-init pin-init changes for v6.17 2025-07-13 23:05:14 +02:00
uapi rust: enable `clippy::ref_as_ptr` lint 2025-06-22 23:09:32 +02:00
.gitignore
.kunitconfig
Makefile Rust changes for v6.17 2025-08-03 13:49:10 -07:00
bindgen_parameters
build_error.rs
compiler_builtins.rs
exports.c
ffi.rs rust: use absolute paths in macros referencing core and kernel 2025-05-23 00:12:14 +02:00