From: Shuai Liu <847807867@qq.com>
To: spi-devel-general@vger.kernel.org, rust-for-linux@vger.kernel.org
Cc: broonie@kernel.org, ojeda@kernel.org, dakr@kernel.org,
linux-kernel@vger.kernel.org, Shuai Liu <847807867@qq.com>
Subject: [PATCH 0/3] Rust abstractions for the SPI driver subsystem
Date: Mon, 26 Oct 2026 14:15:09 +0800 [thread overview]
Message-ID: <tencent_58EE6FD2C02C00F2884D18B81C620B130508@qq.com> (raw)
The Rust abstractions for several buses are already present in the
kernel (PCI, platform, I2C, USB, serdev, ...), but the SPI driver
subsystem is still missing such abstractions. This series adds them,
along with a sample driver demonstrating their usage.
To my knowledge, nobody is currently working on Rust SPI abstractions;
if someone already has work in progress, please let me know and I will
happily drop or rebase this series.
The abstractions follow the same layout as the existing I2C and serdev
abstractions: a `Driver` trait for drivers to implement, an `Adapter`
for driver registration, and a `SpiDevice` wrapping `struct spi_device`.
This first installment provides synchronous `read`, `write` and
`write_then_read` operations; message-based transfers (`spi_message` /
`spi_transfer`) can be added on top in a follow-up series.
One deviation from the I2C abstractions: `spi_match_id()` is not
exported to modules, so device id matching by modalias uses the
exported `spi_get_device_id()` instead, falling back to the OF and ACPI
tables.
The series is based on the current mainline tree (7.4 merge window) and
has been build-tested with CONFIG_RUST=y, including the KUnit tests and
doctests for the new abstractions. I do not have access to real SPI
hardware to run-test this series, but the included sample driver can be
used for that purpose.
Signed-off-by: Shuai Liu <847807867@qq.com>
Shuai Liu (3):
rust: helpers: add SPI helpers
rust: spi: add SPI driver abstractions
samples: rust: add SPI driver sample
rust/bindings/bindings_helper.h | 1 +
rust/helpers/helpers.c | 1 +
rust/helpers/spi.c | 21 ++
rust/kernel/Kconfig.test | 11 +
rust/kernel/lib.rs | 1 +
rust/kernel/spi.rs | 529 ++++++++++++++++++++++++++++++++
samples/rust/Kconfig | 11 +
samples/rust/Makefile | 1 +
samples/rust/rust_driver_spi.rs | 66 ++++
9 files changed, 642 insertions(+)
create mode 100644 rust/helpers/spi.c
create mode 100644 rust/kernel/spi.rs
create mode 100644 samples/rust/rust_driver_spi.rs
--
2.43.0
next reply other threads:[~2026-10-26 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 6:15 Shuai Liu [this message]
2026-10-26 6:29 Shuai Liu
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=tencent_58EE6FD2C02C00F2884D18B81C620B130508@qq.com \
--to=847807867@qq.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=spi-devel-general@vger.kernel.org \
/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®