From: Daniel Almeida <daniel.almeida@collabora.com>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, tmgross@umich.edu,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
Alice Ryhl <aliceryhl@google.com>
Subject: Re: [PATCH v2] rust: irq: add support for request_irq()
Date: Tue, 4 Mar 2025 13:48:30 -0300 [thread overview]
Message-ID: <BE595E8E-CB77-4E8B-B6EF-215CCAF5580A@collabora.com> (raw)
In-Reply-To: <87cyewhpxj.fsf@kernel.org>
Hi Andreas,
I will address your other comments later this week, as I’m off for a few days.
> On 4 Mar 2025, at 10:43, Andreas Hindborg <a.hindborg@kernel.org> wrote:
>
> "Daniel Almeida" <daniel.almeida@collabora.com> writes:
>
>> Add support for registering IRQ handlers in Rust.
>>
>> IRQ handlers are extensively used in drivers when some peripheral wants to
>> obtain the CPU attention. Registering a handler will make the system invoke the
>> passed-in function whenever the chosen IRQ line is triggered.
>>
>> Both regular and threaded IRQ handlers are supported through a Handler (or
>> ThreadedHandler) trait that is meant to be implemented by a type that:
>>
>> a) provides a function to be run by the system when the IRQ fires and,
>>
>> b) holds the shared data (i.e.: `T`) between process and IRQ contexts.
>>
>> The requirement that T is Sync derives from the fact that handlers might run
>> concurrently with other processes executing the same driver, creating the
>> potential for data races.
>>
>> Ideally, some interior mutability must be in place if T is to be mutated. This
>> should usually be done through the in-flight SpinLockIrq type.
>>
>> Co-developed-by: Alice Ryhl <aliceryhl@google.com>
>> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
>> Signed-off-by: Daniel Almeida <daniel.almeida@collabora.com>
>
> What is the base commit to apply this patch to? I am getting some
> compiler errors when trying it out:
>
> error[E0308]: mismatched types
> --> /home/aeh/src/linux-rust/linux/rust/kernel/irq/request.rs:240:21
> |
> 237 | bindings::request_irq(
> | --------------------- arguments to this function are incorrect
> ...
> 240 | flags.0,
> | ^^^^^^^ expected `usize`, found `u64`
> |
>
> [...]
This patch needs a rebase. I’ve been waiting for Lyude & Boqun
new SpinLockIrq series, which just came out last week.
I’ll work on a v3 soon.
next prev parent reply other threads:[~2025-03-04 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u-vC1KbeOK3Fd2PClzinb8LmqS_dntOW-pOSmZIFWotCZeTOg30xR_GYUc4oReAKZeuuu7ZaXWzfeTkpGMlr0A==@protonmail.internalid>
2025-01-22 16:39 ` Daniel Almeida
2025-01-23 7:17 ` Boqun Feng
2025-01-23 9:07 ` Alice Ryhl
2025-05-14 14:44 ` Daniel Almeida
2025-05-15 17:17 ` Christian Schrefl
2025-01-23 16:00 ` Christian Schrefl
2025-01-23 16:27 ` Daniel Almeida
2025-01-23 17:09 ` Christian Schrefl
2025-03-04 13:05 ` Andreas Hindborg
2025-02-10 8:41 ` Daniel Almeida
2025-02-10 16:41 ` Guangbo Cui
2025-03-04 13:11 ` Andreas Hindborg
2025-03-04 13:43 ` Andreas Hindborg
2025-03-04 16:48 ` Daniel Almeida [this message]
2025-03-17 14:58 ` Alice Ryhl
2025-05-09 13:58 ` Daniel Almeida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BE595E8E-CB77-4E8B-B6EF-215CCAF5580A@collabora.com \
--to=daniel.almeida@collabora.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®