rust: Add ACPI match table support for Rust drivers
Subsystems (4)
v5 cover rust: Add ACPI match table support for Rust drivers
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.
- 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 (6):
rust: acpi: add acpi::DeviceId abstraction
rust: driver: Consolidate Adapter::of_id_info methods using #[cfg]
rust: driver: Add ACPI id table support to Adapter trait
rust: platform: Add ACPI match table support to Driver trait
rust: cpufreq: Remove unnecessary of dependency in cpufreq example
samples: rust: add ACPI match table example to platform driver
Changelog
---------
v5:
- Got rid of unnecessary consolidation of Adapter::acpi_id_info methods.
Instead, firstly made consolidation of Adapter::of_id_info, then Adapter::acpi_id_info is added using the same pattern.
- Set Adapter::OF_ID_TABLE and Adapter::ACPI_ID_TABLE as None by
default.
- Removed Adapter::OF_ID_TABLE/Adapter::ACPI_ID_TABLE initialization
example due to irrelevance.
- Removed extra of dependency and Adapter::OF_ID_TABLE initialization
in cpufreq driver.
- Link to v4: https://lore.kernel.org/rust-for-linux/[email protected]/
v4:
- Fixed code example for trait Adapter in platform.rs
- Fixed driver implementation example in rust_driver_platform.rs and moved
it to trait Adapter in platform.rs per Danilo Krummrich's suggestion.
- Consolidated Adapter::of_id_info and Adapter::acpi_id_info methods using
#[cfg] per Benno Lossin's suggestion.
- Link to v3: https://lore.kernel.org/rust-for-linux/[email protected]/
v3:
- Removed fwnode type check in Adapter::id_info per Greg's and Danilo's
comments
- Removed is_of_node rust helper, due to unnecessity.
- Fixed example code in rust_driver_platform.rs per Danilo's comment
- Added an instruction of testing ACPI using QEMU with a custom SSDT
- Fixed minor code formatting issues.
- Link to v2: https://lore.kernel.org/rust-for-linux/[email protected]/
v2:
- Removed misleading comment in acpi::DeviceID implementation.
- Removed unnecessary casting in acpi::DeviceID::new.
- Moved pub mod acpi to correct alphabetical position in rust/kernel/lib.rs.
- Link to v1: https://lore.kernel.org/rust-for-linux/[email protected]/
MAINTAINERS | 1 + rust/bindings/bindings_helper.h | 1 + rust/kernel/acpi.rs | 61 +++++++++++++++++++++ rust/kernel/cpufreq.rs | 3 +- rust/kernel/driver.rs | 81 +++++++++++++++++++++------- rust/kernel/lib.rs | 1 + rust/kernel/platform.rs | 29 ++++++++-- samples/rust/rust_driver_platform.rs | 71 +++++++++++++++++++++++- 8 files changed, 222 insertions(+), 26 deletions(-) create mode 100644 rust/kernel/acpi.rs
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
Signature · 1 line
2.43.0
PATCH v5 1/6 rust: acpi: add `acpi::DeviceId` abstraction
acpi::DeviceId is an abstraction around struct acpi_device_id.
This is used by subsequent patches, in particular the i2c driver abstractions, to create ACPI device ID tables.
--- MAINTAINERS | 1 + rust/kernel/acpi.rs | 61 +++++++++++++++++++++++++++++++++++++++++++++ rust/kernel/lib.rs | 1 + 3 files changed, 63 insertions(+) create mode 100644 rust/kernel/acpi.rs
MAINTAINERS +1 -0
@@ -302,6 +302,7 @@ F: include/linux/acpi.h F: include/linux/fwnode.h F: include/linux/fw_table.h F: lib/fw_table.c +F: rust/kernel/acpi.rs F: tools/power/acpi/ ACPI APEI
rust/kernel/acpi.rs new file +61 -0
61 lines not on this page · raw message
rust/kernel/lib.rs +1 -0
@@ -51,6 +51,7 @@pub use ffi; +pub mod acpi;pub mod alloc;#[cfg( CONFIG_AUXILIARY_BUS )] pub mod auxiliary;
Signature · 1 line
2.43.0
PATCH v5 2/6 rust: driver: Consolidate `Adapter::of_id_info` methods using `#[cfg]`
In reply to Igor KorotinRefactor the of_id_info methods in the Adapter trait to reduce duplication. Previously, the method had two versions selected via #[cfg(...)] and #[cfg(not(...))]. This change merges them into a single method by using #[cfg] blocks within the method body.
--- rust/kernel/driver.rs | 40 +++++++++++++++++++++------------------- 1 file changed, 21 insertions(+), 19 deletions(-)
rust/kernel/driver.rs +21 -19
@@ -147,30 +147,32 @@ pub trait Adapter {/// Returns the driver's private data from the matching entry in the [`of::IdTable`], if any. /// /// If this returns `None`, it means there is no match with an entry in the [`of::IdTable`]. -#[cfg( CONFIG_OF )] fn of_id_info (dev: &device::Device ) ->Option <&'staticSelf ::IdInfo > { -let table =Self ::of_id_table ()?; +#[cfg(not( CONFIG_OF ))] + { +let _ = dev; +return None ; + } -// 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::of_match_device (table.as_ptr (), dev.as_raw ()) }; +#[cfg( CONFIG_OF )] + { +let table =Self ::of_id_table ()?; -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 ::<of::DeviceId >() }; +// 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::of_match_device (table.as_ptr (), dev.as_raw ()) }; -Some (table.info (<of::DeviceId as crate ::device_id::RawDeviceId >::index (id))) - } - } +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 ::<of::DeviceId >() }; -#[cfg(not( CONFIG_OF ))] -#[allow(missing_docs)] -fn of_id_info (_dev: &device::Device ) ->Option <&'staticSelf ::IdInfo > { -None +Some (table.info (<of::DeviceId as crate ::device_id::RawDeviceId >::index (id))) + } + } }/// Returns the driver's private data from the matching entry of any of the ID tables, if any.
Signature · 1 line
2.43.0
PATCH v5 3/6 rust: driver: Add ACPI id table support to Adapter trait
In reply to Igor KorotinExtend 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 | 41 ++++++++++++++++++++++++++++++++- rust/kernel/platform.rs | 6 ++++- 3 files changed, 46 insertions(+), 2 deletions(-)
rust/bindings/bindings_helper.h +1 -0
@@ -28,6 +28,7 @@*/ #include <linux/hrtimer_types.h> +#include <linux/acpi.h> #include <drm/drm_device.h> #include <drm/drm_drv.h> #include <drm/drm_file.h>
rust/kernel/driver.rs +40 -1
59 lines not on this page · raw message
rust/kernel/platform.rs +5 -1
@@ -5,7 +5,7 @@//! C header: [`include/linux/platform_device.h`](srctree/include/linux/platform_device.h) use crate ::{ - bindings, container_of, device, driver, + acpi, bindings, container_of, device, driver, error::{to_result,Result }, of, prelude::*,
@@ -94,6 +94,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.
Signature · 1 line
2.43.0
PATCH v5 4/6 rust: platform: Add ACPI match table support to `Driver` trait
In reply to Igor KorotinExtend the platform::Driver trait to support ACPI device matching by adding the ACPI_ID_TABLE constant.
This allows Rust platform drivers to define ACPI match tables alongside their existing OF match tables. These changes mirror the existing OF support and allow Rust platform drivers to match devices based on ACPI identifiers.
In addition, set OF_ID_TABLE to None by default to match the behavior of ACPI_ID_TABLE and to avoid requiring drivers that do not use OF matching to import unnecessary dependencies or define dummy values.
--- rust/kernel/platform.rs | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-)
rust/kernel/platform.rs +22 -3
@@ -37,12 +37,18 @@ unsafe fn register( None => core::ptr::null(), }; +let acpi_table =match T ::ACPI_ID_TABLE { +Some (table) => table.as_ptr (), +None => core::ptr::null (), + }; +// SAFETY: It's safe to set the fields of `struct platform_driver` on initialization. unsafe { (*pdrv.get ()).driver.name = name.as_char_ptr (); (*pdrv.get ()).probe =Some (Self ::probe_callback); (*pdrv.get ()).remove =Some (Self ::remove_callback); (*pdrv.get ()).driver.of_match_table = of_table; + (*pdrv.get ()).driver.acpi_match_table = acpi_table; }// SAFETY: `pdrv` is guaranteed to be a valid `RegType`.
@@ -96,7 +102,7 @@ fn of_id_table() -> Option<of::IdTable<Self::IdInfo>> { }fn acpi_id_table () ->Option <acpi::IdTable <Self ::IdInfo >> { -None +T ::ACPI_ID_TABLE } }
@@ -127,7 +133,7 @@ macro_rules! module_platform_driver {/// # Example /// ///``` -/// # use kernel::{bindings, c_str, device::Core, of, platform}; +/// # use kernel::{acpi, bindings, c_str, device::Core, of, platform}; /// /// struct MyDriver; ///
@@ -140,9 +146,19 @@ macro_rules! module_platform_driver {/// ] /// ); /// +/// kernel::acpi_device_table!( +/// ACPI_TABLE, +/// MODULE_ACPI_TABLE, +/// <MyDriver as platform::Driver>::IdInfo, +/// [ +/// (acpi::DeviceId::new(c_str!("TEST4321")), ()) +/// ] +/// ); +/// /// impl platform::Driver for MyDriver { /// type IdInfo = (); /// const OF_ID_TABLE: Option<of::IdTable<Self::IdInfo>> = Some(&OF_TABLE); +/// const ACPI_ID_TABLE: Option<acpi::IdTable<Self::IdInfo>> = Some(&ACPI_TABLE); /// /// fn probe( /// _pdev: &platform::Device<Core>,
@@ -162,7 +178,10 @@ pub trait Driver: Send {type IdInfo : 'static;/// The table of OF device ids supported by the driver. -const OF_ID_TABLE :Option <of::IdTable <Self ::IdInfo >>; +const OF_ID_TABLE :Option <of::IdTable <Self ::IdInfo >> =None ; + +/// The table of ACPI device ids supported by the driver. +const ACPI_ID_TABLE :Option <acpi::IdTable <Self ::IdInfo >> =None ;/// Platform driver probe. ///
Signature · 1 line
2.43.0
Danilo Krummrich
maintainerRe: [PATCH v5 4/6] rust: platform: Add ACPI match table support to `Driver` trait
rust/kernel/platform.rs pub trait Driver: Send { · line 181
Quoted 6 lines · Igor Korotin
rust/kernel/platform.rs +1
-1@@ -162,7 +178,10 @@ pub trait Driver: Send {type IdInfo : 'static;/// The table of OF device ids supported by the driver. -const OF_ID_TABLE :Option <of::IdTable <Self ::IdInfo >>; +const OF_ID_TABLE :Option <of::IdTable <Self ::IdInfo >> =None ;
This change is fine, but it should be a separate patch.
PATCH v5 5/6 rust: cpufreq: Remove unnecessary `of` dependency in cpufreq example
In reply to Igor KorotinDrop the explicit use of and OF_ID_TABLE = None assignment in the cpufreq driver registration example.
Since Adapter::OF_ID_TABLE now defaults to None, drivers that do not require OpenFirmware matching no longer need to import of or define the constant explicitly.
--- rust/kernel/cpufreq.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
rust/kernel/cpufreq.rs +1 -2
@@ -842,7 +842,7 @@ fn register_em(_policy: &mut Policy) {/// c_str, /// device::{Core, Device}, /// macros::vtable, -/// of, platform, +/// platform, /// sync::Arc, /// }; /// struct SampleDevice;
@@ -887,7 +887,6 @@ fn register_em(_policy: &mut Policy) {/// /// impl platform::Driver for SampleDriver { /// type IdInfo = (); -/// const OF_ID_TABLE: Option<of::IdTable<Self::IdInfo>> = None; /// /// fn probe( /// pdev: &platform::Device<Core>,
Signature · 1 line
2.43.0
Danilo Krummrich
maintainerRe: [PATCH v5 5/6] rust: cpufreq: Remove unnecessary `of` dependency in cpufreq example
Quoted 6 lines · Igor Korotin
Drop the explicit
use ofandOF_ID_TABLE = Noneassignment in the cpufreq driver registration example.Since
Adapter::OF_ID_TABLEnow defaults toNone, drivers that do not require OpenFirmware matching no longer need to importofor define the constant explicitly.
This is slightly outside of the scope of this patch series and given that it doesn't add immediate value it's usually better to wait with such patches until the prerequisite is in Linus' tree.
However, if Viresh is fine with the patch and with taking it through the driver-core tree and does not expect any conflicts, I'm fine picking it up.
PATCH v5 6/6 samples: rust: add ACPI match table example to platform driver
In reply to Igor KorotinExtend the Rust sample platform driver to probe using device/driver name matching, OF ID table matching, or ACPI ID table matching.
--- samples/rust/rust_driver_platform.rs | 71 +++++++++++++++++++++++++++- 1 file changed, 70 insertions(+), 1 deletion(-)
samples/rust/rust_driver_platform.rs +70 -1
@@ -2,7 +2,7 @@//! Rust Platform driver sample. -use kernel::{c_str, device::Core , of, platform, prelude::*, types::ARef }; +use kernel::{acpi, c_str, device::Core , of, platform, prelude::*, types::ARef };struct SampleDriver { pdev:ARef <platform::Device >,
@@ -17,9 +17,78 @@ struct SampleDriver { [(of::DeviceId ::new (c_str! ("test,rust-device" )),Info (42 ))] ); +// ACPI match table test +// +// This demonstrates how to test an ACPI-based Rust platform driver using QEMU +// with a custom SSDT. +// +// Steps: +// +// 1. **Create an SSDT source file** (`ssdt.dsl`) with the following content: +// +// ```asl +// DefinitionBlock ("", "SSDT", 2, "TEST", "VIRTACPI", 0x00000001) +// { +// Scope (\_SB) +// { +// Device (T432) +// { +// Name (_HID, "TEST4321") // ACPI hardware ID to match +// Name (_UID, 1) +// Name (_STA, 0x0F) // Device present, enabled +// Name (_CRS, ResourceTemplate () +// { +// Memory32Fixed (ReadWrite, 0xFED00000, 0x1000) +// }) +// } +// } +// } +// ``` +// +// 2. **Compile the table**: +// +// ```sh +// iasl -tc ssdt.dsl +// ``` +// +// This generates `ssdt.aml` +// +// 3. **Run QEMU** with the compiled AML file: +// +// ```sh +// qemu-system-x86_64 -m 512M \ +// -enable-kvm \ +// -kernel path/to/bzImage \ +// -append "root=/dev/sda console=ttyS0" \ +// -hda rootfs.img \ +// -serial stdio \ +// -acpitable file=ssdt.aml +// ``` +// +// Requirements: +// - The `rust_driver_platform` must be present either: +// - built directly into the kernel (`bzImage`), or +// - available as a `.ko` file and loadable from `rootfs.img` +// +// 4. **Verify it worked** by checking `dmesg`: +// +// ``` +// rust_driver_platform TEST4321:00: Probed with info: '0'. +// ``` +// +// This demonstrates ACPI table matching using a custom ID in QEMU with a minimal SSDT + +kernel::acpi_device_table!( +ACPI_TABLE , +MODULE_ACPI_TABLE , + <SampleDriver as platform::Driver >::IdInfo , + [(acpi::DeviceId ::new (c_str! ("TEST4321" )),Info (0 ))] +); +impl platform::Driver for SampleDriver {type IdInfo =Info ;const OF_ID_TABLE :Option <of::IdTable <Self ::IdInfo >> =Some (&OF_TABLE ); +const ACPI_ID_TABLE :Option <acpi::IdTable <Self ::IdInfo >> =Some (&ACPI_TABLE );fn probe ( pdev: &platform::Device<Core>,
Signature · 1 line
2.43.0