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

[Daniel Almeida]

> On 11 Aug 2025, at 09:33, Alice Ryhl <aliceryhl@xxxxxxxxxx> 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@xxxxxxxxxx>
> ---
> 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.
> 
> [1]: https://lore.kernel.org/all/20250810-topics-tyr-request_irq2-v8-0-8163f4c4c3a6@xxxxxxxxxxxxx/
> ---
> Changes in v2:
> - Rebase on v8 of [1] (and hence v6.17-rc1).
> 

Thanks, I’ll apply on top of the series as a convenience to the maintainers.

— Daniel