From: John Hubbard <jhubbard@nvidia.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Gary Guo <gary@garyguo.net>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Yury Norov" <yury.norov@gmail.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>, "Edwin Peer" <epeer@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Steven Price" <steven.price@arm.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] rust: io: add `register!` macro
Date: Sun, 25 Jan 2026 20:33:35 -0800 [thread overview]
Message-ID: <dd9e0094-ee84-449e-90ec-a75c7d8479cf@nvidia.com> (raw)
In-Reply-To: <edac88ac-664a-4bdc-a702-b6f41d9cea41@nvidia.com>
On 1/25/26 8:31 PM, John Hubbard wrote:
> On 1/21/26 8:15 AM, Miguel Ojeda wrote:
>> On Wed, Jan 21, 2026 at 3:58 PM Gary Guo <gary@garyguo.net> wrote:
>>>
>>> Another top-level question I have is whether we should define multiple registers
>>> (perhaps all) in one macro invocation. That's the strategy of `tock-registers`
>>> crate which is widely used in embedded Rust.
>>
>> Yeah, I suggested a multi-register one for something similar in 2021
>> and even tackling extra automatic codegen there, like e.g. adjusting
>> the value as needed to get to the proper unit from a sensor.
>>
>> Not sure how useful the multi-register part in practice it would be,
>> but it would allow to relate several registers together if needed (is
>> that even common nowadays?). Or perhaps things like the
>
> For the NVIDIA GPU drivers, maybe not. Just a data point.
...although it depends on what you mean. We do have lots of registers
with a common base MMIO address. It's just that they are not all
invoked in one shot, is what I'm trying (struggling) to say.
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-01-26 4:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 7:23 [PATCH v2 0/5] rust: " Alexandre Courbot
2026-01-21 7:23 ` [PATCH v2 1/5] rust: enable the `generic_arg_infer` feature Alexandre Courbot
2026-01-21 11:48 ` Gary Guo
2026-01-21 7:23 ` [PATCH v2 2/5] rust: num: add `shr` and `shl` methods to `Bounded` Alexandre Courbot
2026-01-21 14:12 ` Gary Guo
2026-01-26 3:23 ` Alexandre Courbot
2026-01-26 3:28 ` Miguel Ojeda
2026-01-21 17:49 ` kernel test robot
2026-01-21 7:23 ` [PATCH v2 3/5] rust: num: add `as_bool` method to `Bounded<_, 1>` Alexandre Courbot
2026-01-21 14:13 ` Gary Guo
2026-01-21 7:23 ` [PATCH v2 4/5] rust: io: add `register!` macro Alexandre Courbot
2026-01-21 13:13 ` Alexandre Courbot
2026-01-21 14:15 ` Gary Guo
2026-01-26 3:23 ` Alexandre Courbot
2026-01-21 14:50 ` Gary Guo
2026-01-21 16:15 ` Miguel Ojeda
2026-01-26 4:31 ` John Hubbard
2026-01-26 4:33 ` John Hubbard [this message]
2026-01-26 3:24 ` Alexandre Courbot
2026-01-26 6:57 ` Alexandre Courbot
2026-01-26 7:45 ` Alexandre Courbot
2026-01-26 11:46 ` Alexandre Courbot
2026-01-21 21:39 ` kernel test robot
2026-01-21 7:23 ` [PATCH FOR REFERENCE v2 5/5] gpu: nova-core: use the kernel " Alexandre Courbot
2026-01-21 9:16 ` [PATCH v2 0/5] rust: add " Dirk Behme
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=dd9e0094-ee84-449e-90ec-a75c7d8479cf@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dirk.behme@de.bosch.com \
--cc=ecourtney@nvidia.com \
--cc=epeer@nvidia.com \
--cc=gary@garyguo.net \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
--cc=yury.norov@gmail.com \
/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
Powered by JetHome