public inbox for linux-rtc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Dirk Behme" <dirk.behme@gmail.com>
Cc: "Ke Sun" <sunke@kylinos.cn>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	linux-rtc@vger.kernel.org, rust-for-linux@vger.kernel.org,
	"Alvin Sun" <sk.alvin.x@gmail.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Alexandre Courbot" <acourbot@nvidia.com>
Subject: Re: [RFC PATCH v1 4/4] rust: add PL031 RTC driver
Date: Wed, 07 Jan 2026 11:15:28 +0100	[thread overview]
Message-ID: <DFIA1F2LOTGS.X74JYB8BB0HE@kernel.org> (raw)
In-Reply-To: <48d23334-b167-48a5-a645-28276eb85b00@gmail.com>

On Sun Jan 4, 2026 at 10:02 AM CET, Dirk Behme wrote:

> Do we want a common register access style in Rust drivers and want to
> encourge using the register macro for that? Or do we take what we have
> at the moment (like here) and eventually convert later to the register
> macro? Or not? Opinions?

Yes, the idea is that drivers use the register!() macro for definitions (this
has been what I am looking for since proposing it in [1]).

Please also see [2] for some more rationale and design considerations.

Ideally, we land the patch series moving the register!() macro from nova-core
(which we used as a playground for development and to proof the concept) to
common infrastructure this cycle.

This way drivers targeting next cycle or later can start using it right away.

Should we not make it in this cycle, we can also consider a feature branch to
share with upcoming drivers, but let's see how it goes first.

> I know that it is not ready yet and still in development, but what's
> about the register!() macro [1] [2]?

As mentioned above, it's not that it is not ready. We are actively using it in
nova-core for quite a while now, but we now have to move it to common
infrastructure.

It probably would have been better to do the move first and then extract generic
bitfield code afterwards, but we should be on track now. :)

- Danilo

[1] https://docs.kernel.org/gpu/nova/core/todo.html#generic-register-abstraction-rega
[2] https://lore.kernel.org/all/DD15H63RK1KJ.1J584C1QC4L28@kernel.org/

  reply	other threads:[~2026-01-07 10:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04  6:06 [RFC PATCH v1 0/4] rust: Add RTC driver support Ke Sun
2026-01-04  6:06 ` [RFC PATCH v1 1/4] rust: add AMBA bus abstractions Ke Sun
2026-01-04 11:37   ` Miguel Ojeda
2026-01-04 12:37   ` Danilo Krummrich
2026-01-04  6:06 ` [RFC PATCH v1 2/4] rust: add device wakeup support Ke Sun
2026-01-04 13:31   ` Danilo Krummrich
2026-01-04  6:06 ` [RFC PATCH v1 3/4] rust: add RTC core abstractions and data structures Ke Sun
2026-01-04 13:00   ` Danilo Krummrich
2026-01-04  6:06 ` [RFC PATCH v1 4/4] rust: add PL031 RTC driver Ke Sun
2026-01-04  9:02   ` Dirk Behme
2026-01-07 10:15     ` Danilo Krummrich [this message]
2026-01-04 11:40   ` Miguel Ojeda
2026-01-04 13:10   ` Danilo Krummrich
2026-01-06  2:51     ` Ke Sun
2026-01-06 13:32       ` Danilo Krummrich
2026-01-06 14:44         ` Greg Kroah-Hartman
2026-01-06 15:04           ` Danilo Krummrich
2026-01-06 15:12             ` Greg Kroah-Hartman
2026-01-04 13:36 ` [RFC PATCH v1 0/4] rust: Add RTC driver support Danilo Krummrich
2026-01-04 14:11   ` Ke Sun
2026-01-06  7:41 ` Kari Argillander

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=DFIA1F2LOTGS.X74JYB8BB0HE@kernel.org \
    --to=dakr@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dirk.behme@gmail.com \
    --cc=gary@garyguo.net \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sk.alvin.x@gmail.com \
    --cc=sunke@kylinos.cn \
    --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