From: Igor Korotin <igor.korotin.linux@gmail.com>
To: Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, devicetree@vger.kernel.org
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Hung" <alex.hung@amd.com>,
"Tamir Duberstein" <tamird@gmail.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Xiangfei Ding" <dingxiangfei2009@gmail.com>,
"Igor Korotin" <igor.korotin.linux@gmail.com>
Subject: [PATCH v1 0/5] rust: Add ACPI match table support for Rust drivers
Date: Wed, 4 Jun 2025 13:29:39 +0100 [thread overview]
Message-ID: <20250604122945.3445776-1-igor.korotin.linux@gmail.com> (raw)
This patch series introduces support for ACPI match tables in Rust
drivers.
Currently, Rust abstractions support only Open Firmware (OF) device
matching. This series extends the driver model to support ACPI-based
matching, enabling Rust drivers to bind to ACPI-described devices.
Changes include:
- A new `acpi::DeviceId` abstraction for working with
`struct acpi_device_id`.
- A helper function `is_of_node()` for determining fwnode types.
- Updates to the core `Adapter` trait and `platform::Driver` to support
optional ACPI ID tables.
- A sample implementation in the Rust platform driver, demonstrating
multi-bus matching.
This is especially useful for writing drivers that work across platforms
using both OF and ACPI.
Tested using QEMU with a custom SSDT that creates an ACPI device matching
the sample Rust platform driver.
Igor Korotin (5):
rust: acpi: add `acpi::DeviceId` abstraction
rust: helpers: Add `is_of_node` helper function
rust: driver: Add ACPI id table support to Adapter trait
rust: platform: Add ACPI match table support to `Driver` trait
samples: rust: add ACPI match table example to platform driver
MAINTAINERS | 2 +
rust/bindings/bindings_helper.h | 1 +
rust/helpers/helpers.c | 1 +
rust/helpers/of.c | 6 +++
rust/kernel/acpi.rs | 62 ++++++++++++++++++++++++++++
rust/kernel/driver.rs | 58 ++++++++++++++++++++++++--
rust/kernel/lib.rs | 1 +
rust/kernel/platform.rs | 17 +++++++-
samples/rust/rust_driver_platform.rs | 41 +++++++++++++++++-
9 files changed, 183 insertions(+), 6 deletions(-)
create mode 100644 rust/helpers/of.c
create mode 100644 rust/kernel/acpi.rs
--
2.43.0
next reply other threads:[~2025-06-04 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 12:29 Igor Korotin [this message]
2025-06-04 12:29 ` [PATCH v1 1/5] rust: acpi: add `acpi::DeviceId` abstraction Igor Korotin
2025-06-04 12:29 ` [PATCH v1 2/5] rust: helpers: Add `is_of_node` helper function Igor Korotin
2025-06-04 12:29 ` [PATCH v1 4/5] rust: platform: Add ACPI match table support to `Driver` trait Igor Korotin
2025-06-04 21:34 ` [PATCH v1 0/5] rust: Add ACPI match table support for Rust drivers Danilo Krummrich
2025-06-05 13:57 ` Igor Korotin
2025-06-05 14:34 ` 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=20250604122945.3445776-1-igor.korotin.linux@gmail.com \
--to=igor.korotin.linux@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=alex.hung@amd.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dingxiangfei2009@gmail.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@google.com \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=wedsonaf@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;
as well as URLs for NNTP newsgroup(s).