Re: [PATCH] rust: irq: add &Device<Bound> argument to irq callbacks

[Daniel Almeida <daniel.almeida@collabora.com>]

Hi Alice,

> On 21 Jul 2025, at 11:38, Alice Ryhl <aliceryhl@google.com> wrote:
> 
> 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>
> ---
> This patch is a follow-up to Daniel's irq series [1] that adds a
> &Device<Bound> argument to all irq callbacks. This allows you to use
> operations that are only safe on a bound device inside an irq callback.
> 
> The patch is otherwise based on top of driver-core-next.
> 
> [1]: https://lore.kernel.org/r/20250715-topics-tyr-request_irq2-v7-0-d469c0f37c07@collabora.com
> ---
> 

I tried to rebase this so we could send it together with v8 of the request_irq
series. However, is it me or this doesn't apply on v7?

> ---
> base-commit: d860d29e91be18de62b0f441edee7d00f6cb4972

Yeah, I couldn’t find this, sorry.

> change-id: 20250721-irq-bound-device-c9fdbfdd8cd9
> 
> Best regards,
> -- 
> Alice Ryhl <aliceryhl@google.com>
> 
> 


My apologies.

— Daniel