From: Danilo Krummrich <dakr@kernel.org>
To: gregkh@linuxfoundation.org, rafael@kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
airlied@gmail.com, acourbot@nvidia.com, jhubbard@nvidia.com
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
Danilo Krummrich <dakr@kernel.org>
Subject: [PATCH v2 0/4] Auxiliary bus Rust abstractions
Date: Thu, 13 Mar 2025 03:23:49 +0100 [thread overview]
Message-ID: <20250313022454.147118-1-dakr@kernel.org> (raw)
This series adds Rust abstractions for the auxiliary bus.
It implements the required abstractions to write auxiliary drivers and create
auxiliary device registrations. A driver sample illustrates how the
corresponding abstractions work.
The auxiliary abstractions are required for the Nova driver project, in order to
connect nova-core with the nova-drm driver.
This patch series depends on [1] (taken through the nova tree for v6.15) and
[2]; a branch containing the patches, including the dependency can be found in
[3].
[1] https://lore.kernel.org/rust-for-linux/20250306222336.23482-2-dakr@kernel.org/
[2] https://lore.kernel.org/lkml/20250313021550.133041-1-dakr@kernel.org/
[3] https://web.git.kernel.org/pub/scm/linux/kernel/git/dakr/linux.git/log/?h=rust/auxiliary
Changes in v2:
- implement bus device soundness improvements from [2]
Danilo Krummrich (4):
rust: types: add `Opaque::zeroed`
rust: auxiliary: add auxiliary device / driver abstractions
rust: auxiliary: add auxiliary registration
samples: rust: add Rust auxiliary driver sample
MAINTAINERS | 2 +
rust/bindings/bindings_helper.h | 1 +
rust/helpers/auxiliary.c | 23 ++
rust/helpers/helpers.c | 1 +
rust/kernel/auxiliary.rs | 345 ++++++++++++++++++++++++++
rust/kernel/lib.rs | 2 +
rust/kernel/types.rs | 8 +
samples/rust/Kconfig | 12 +
samples/rust/Makefile | 1 +
samples/rust/rust_driver_auxiliary.rs | 99 ++++++++
10 files changed, 494 insertions(+)
create mode 100644 rust/helpers/auxiliary.c
create mode 100644 rust/kernel/auxiliary.rs
create mode 100644 samples/rust/rust_driver_auxiliary.rs
base-commit: 31cc40e864273b384f4e640ba3f11add432b78e0
--
2.48.1
next reply other threads:[~2025-03-13 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 2:23 Danilo Krummrich [this message]
2025-03-13 2:23 ` [PATCH v2 1/4] rust: types: add `Opaque::zeroed` Danilo Krummrich
2025-03-13 2:23 ` [PATCH v2 2/4] rust: auxiliary: add auxiliary device / driver abstractions Danilo Krummrich
2025-03-13 2:23 ` [PATCH v2 3/4] rust: auxiliary: add auxiliary registration Danilo Krummrich
2025-03-17 20:42 ` Benoît du Garreau
2025-03-17 20:55 ` Danilo Krummrich
2025-03-18 18:36 ` Benno Lossin
2025-03-13 2:23 ` [PATCH v2 4/4] samples: rust: add Rust auxiliary driver sample Danilo Krummrich
2025-03-17 7:05 ` [PATCH v2 0/4] Auxiliary bus Rust abstractions Greg KH
2025-03-17 11:33 ` Danilo Krummrich
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=20250313022454.147118-1-dakr@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--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=gregkh@linuxfoundation.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).