From: Danilo Krummrich <dakr@kernel.org>
To: Igor Korotin <igor.korotin@yahoo.com>
Cc: "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,
"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>, "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: Re: [PATCH v2 3/5] rust: driver: Add ACPI id table support to Adapter trait
Date: Fri, 6 Jun 2025 15:50:10 +0200 [thread overview]
Message-ID: <aELyEqg0GrkC8oZY@pollux> (raw)
In-Reply-To: <20250605162726.3659792-1-igor.korotin@yahoo.com>
On Thu, Jun 05, 2025 at 05:27:26PM +0100, Igor Korotin wrote:
> From: Igor Korotin <igor.korotin.linux@gmail.com>
>
> Extend the `Adapter` trait to support ACPI device identification.
>
> This mirrors the existing Open Firmware (OF) support (`of_id_table`) and
> enables Rust drivers to match and retrieve ACPI-specific device data
> when `CONFIG_ACPI` is enabled.
>
> To avoid breaking compilation, a stub implementation of `acpi_id_table()`
> is added to the Platform adapter; the full implementation will be provided
> in a subsequent patch.
> ---
> rust/bindings/bindings_helper.h | 1 +
> rust/kernel/driver.rs | 58 ++++++++++++++++++++++++++++++---
> rust/kernel/platform.rs | 5 +++
> 3 files changed, 60 insertions(+), 4 deletions(-)
>
> diff --git a/rust/bindings/bindings_helper.h b/rust/bindings/bindings_helper.h
> index e0bcd130b494..d974fc6c141f 100644
> --- a/rust/bindings/bindings_helper.h
> +++ b/rust/bindings/bindings_helper.h
> @@ -6,6 +6,7 @@
> * Sorted alphabetically.
> */
>
> +#include <linux/acpi.h>
> #include <kunit/test.h>
> #include <linux/blk-mq.h>
> #include <linux/blk_types.h>
> diff --git a/rust/kernel/driver.rs b/rust/kernel/driver.rs
> index ec9166cedfa7..d4098596188a 100644
> --- a/rust/kernel/driver.rs
> +++ b/rust/kernel/driver.rs
> @@ -6,7 +6,7 @@
> //! register using the [`Registration`] class.
>
> use crate::error::{Error, Result};
> -use crate::{device, of, str::CStr, try_pin_init, types::Opaque, ThisModule};
> +use crate::{device, of, acpi, str::CStr, try_pin_init, types::Opaque, ThisModule};
> use core::pin::Pin;
> use pin_init::{pin_data, pinned_drop, PinInit};
>
> @@ -141,6 +141,38 @@ pub trait Adapter {
> /// The type holding driver private data about each device id supported by the driver.
> type IdInfo: 'static;
>
> + /// The [`acpi::IdTable`] of the corresponding driver
> + fn acpi_id_table() -> Option<acpi::IdTable<Self::IdInfo>>;
> +
> + /// Returns the driver's private data from the matching entry in the [`acpi::IdTable`], if any.
> + ///
> + /// If this returns `None`, it means there is no match with an entry in the [`acpi::IdTable`].
> + #[cfg(CONFIG_ACPI)]
> + fn acpi_id_info(dev: &device::Device) -> Option<&'static Self::IdInfo> {
> + let table = Self::acpi_id_table()?;
> +
> + // SAFETY:
> + // - `table` has static lifetime, hence it's valid for read,
> + // - `dev` is guaranteed to be valid while it's alive, and so is `pdev.as_ref().as_raw()`.
> + let raw_id = unsafe { bindings::acpi_match_device(table.as_ptr(), dev.as_raw()) };
> +
> + if raw_id.is_null() {
> + None
> + } else {
> + // SAFETY: `DeviceId` is a `#[repr(transparent)` wrapper of `struct of_device_id` and
> + // does not add additional invariants, so it's safe to transmute.
> + let id = unsafe { &*raw_id.cast::<acpi::DeviceId>() };
> +
> + Some(table.info(<acpi::DeviceId as crate::device_id::RawDeviceId>::index(id)))
> + }
> + }
> +
> + #[cfg(not(CONFIG_ACPI))]
> + #[allow(missing_docs)]
> + fn acpi_id_info(_dev: &device::Device) -> Option<&'static Self::IdInfo> {
> + None
> + }
> +
> /// The [`of::IdTable`] of the corresponding driver.
> fn of_id_table() -> Option<of::IdTable<Self::IdInfo>>;
>
> @@ -178,9 +210,27 @@ fn of_id_info(_dev: &device::Device) -> Option<&'static Self::IdInfo> {
> /// If this returns `None`, it means that there is no match in any of the ID tables directly
> /// associated with a [`device::Device`].
> fn id_info(dev: &device::Device) -> Option<&'static Self::IdInfo> {
> - let id = Self::of_id_info(dev);
> - if id.is_some() {
> - return id;
> + // SAFETY: `id_info` is called from `Adapter::probe_callback` with a valid `dev` argument.
> + let fwnode = unsafe{ (*dev.as_raw()).fwnode};
There is an abstraction for FwNode on the list [1] that I plan to merge soon.
Generally, it would make sense to build on top of that.
However, I don't understand why we need this and the subsequent
is_acpi_device_node() and is_of_node() checks.
Instead, I think we can keep the existing code and just add the following.
let id = Self::acpi_id_info(dev);
if id.is_some() {
return id;
}
[1] https://lore.kernel.org/lkml/20250530192856.1177011-1-remo@buenzli.dev/
> +
> + // SAFETY: `bindings::is_acpi_device_node` checks `fwnode` before accessing `fwnode->ops`,
> + // and only compares it with the address of `acpi_device_fwnode_ops`.
> + if unsafe { bindings::is_acpi_device_node(fwnode) } {
As mentioned above, I think we don't need this check.
> + let id = Self::acpi_id_info(dev);
> +
> + if id.is_some() {
> + return id;
> + }
> + }
> +
> + // SAFETY: `bindings::is_of_node` checks `fwnode` before accessing `fwnode->ops`,
> + // and only compares it with the address of `of_fwnode_ops`.
> + if unsafe { bindings::is_of_node(fwnode) } {
Same here.
> + let id = Self::of_id_info(dev);
> +
> + if id.is_some() {
> + return id;
> + }
> }
>
> None
> diff --git a/rust/kernel/platform.rs b/rust/kernel/platform.rs
> index fd4a494f30e8..3cc9fe6ccfcf 100644
> --- a/rust/kernel/platform.rs
> +++ b/rust/kernel/platform.rs
> @@ -5,6 +5,7 @@
> //! C header: [`include/linux/platform_device.h`](srctree/include/linux/platform_device.h)
>
> use crate::{
> + acpi,
> bindings, device, driver,
> error::{to_result, Result},
> of,
> @@ -95,6 +96,10 @@ impl<T: Driver + 'static> driver::Adapter for Adapter<T> {
> fn of_id_table() -> Option<of::IdTable<Self::IdInfo>> {
> T::OF_ID_TABLE
> }
> +
> + fn acpi_id_table() -> Option<acpi::IdTable<Self::IdInfo>> {
> + None
> + }
> }
>
> /// Declares a kernel module that exposes a single platform driver.
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-06-06 13:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 16:19 [PATCH v2 0/5] rust: Add ACPI match table support for Rust drivers Igor Korotin
2025-06-05 16:23 ` [PATCH v2 1/5] rust: acpi: add `acpi::DeviceId` abstraction Igor Korotin
2025-06-06 1:17 ` kernel test robot
2025-06-05 16:24 ` [PATCH v2 2/5] rust: helpers: Add `is_of_node` helper function Igor Korotin
2025-06-05 16:27 ` [PATCH v2 3/5] rust: driver: Add ACPI id table support to Adapter trait Igor Korotin
2025-06-06 13:50 ` Danilo Krummrich [this message]
2025-06-06 14:26 ` Igor Korotin
2025-06-06 14:32 ` Danilo Krummrich
2025-06-06 14:58 ` Igor Korotin
2025-06-06 15:14 ` Danilo Krummrich
2025-06-06 15:29 ` Greg Kroah-Hartman
2025-06-06 15:38 ` Danilo Krummrich
2025-06-06 15:59 ` Igor Korotin
2025-06-05 16:51 ` Igor Korotin
2025-06-06 1:50 ` kernel test robot
2025-06-05 16:51 ` [PATCH v2 4/5] rust: platform: Add ACPI match table support to `Driver` trait Igor Korotin
2025-06-05 16:52 ` [PATCH v2 5/5] samples: rust: add ACPI match table example to platform driver Igor Korotin
2025-06-06 13:58 ` Danilo Krummrich
2025-06-06 13:26 ` [PATCH v2 0/5] rust: Add ACPI match table support for Rust drivers 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=aELyEqg0GrkC8oZY@pollux \
--to=dakr@kernel.org \
--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=devicetree@vger.kernel.org \
--cc=dingxiangfei2009@gmail.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=igor.korotin.linux@gmail.com \
--cc=igor.korotin@yahoo.com \
--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).