From: Andrew Davis <afd@ti.com>
To: "Igor Korotin" <igor.korotin@linux.dev>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Andrew Davis" <afd@ti.com>
Subject: [RFC PATCH v2] rust: i2c: Remove use of bindings::i2c_match_id
Date: Wed, 11 Nov 2026 17:10:53 -0600 [thread overview]
Message-ID: <20261111231053.529616-1-afd@ti.com> (raw)
In-Reply-To: <20261111205204.481923-1-afd@ti.com>
The C function i2c_match_id() is slated for removal, remove use of this
from Rust I2C by switching to bindings::i2c_get_match_data().
Signed-off-by: Andrew Davis <afd@ti.com>
---
Well Sashiko suggested I take the easy way and just re-use a different C
function instead of trying to open-code the loop in Rust. The C function
implements the same lookup as i2c_id_info did so we can drop that out and
its i2c_id_table helper. Still would like some help on checking if this
is actually correct though..
Thanks,
Andrew
rust/kernel/i2c.rs | 39 +++++++--------------------------------
1 file changed, 7 insertions(+), 32 deletions(-)
diff --git a/rust/kernel/i2c.rs b/rust/kernel/i2c.rs
index b4ff25c830fc0..37d914fcb3662 100644
--- a/rust/kernel/i2c.rs
+++ b/rust/kernel/i2c.rs
@@ -148,10 +148,13 @@ extern "C" fn probe_callback(idev: *mut bindings::i2c_client) -> kernel::ffi::c_
// INVARIANT: `idev` is valid for the duration of `probe_callback()`.
let idev = unsafe { &*idev.cast::<I2cClient<device::CoreInternal<'_>>>() };
- let info = Self::i2c_id_info(idev).or_else(|| {
- // SAFETY: `idev` matched data is of type `Self::IdInfo`.
- unsafe { <Self as driver::Adapter>::id_info(idev.as_ref()) }
- });
+ // SAFETY: `idev` is a valid `struct i2c_client` bound to this driver, so
+ // `i2c_get_match_data()` may read `idev.dev.driver`.
+ let raw_info = unsafe { bindings::i2c_get_match_data(idev.as_raw()) };
+
+ // SAFETY: Non-NULL match data is either the OF/ACPI entry data or the `driver_data` of an
+ // I2C id entry. Both are built from `&'static Self::IdInfo` by this driver's tables.
+ let info = unsafe { raw_info.cast::<T::IdInfo>().as_ref() };
from_result(|| {
let data = T::probe(idev, info);
@@ -184,34 +187,6 @@ extern "C" fn shutdown_callback(idev: *mut bindings::i2c_client) {
T::shutdown(idev, data);
}
-
- /// The [`i2c::IdTable`] of the corresponding driver.
- fn i2c_id_table() -> Option<IdTable<<Self as driver::Adapter>::IdInfo>> {
- T::I2C_ID_TABLE
- }
-
- /// Returns the driver's private data from the matching entry in the [`i2c::IdTable`], if any.
- ///
- /// If this returns `None`, it means there is no match with an entry in the [`i2c::IdTable`].
- fn i2c_id_info(dev: &I2cClient) -> Option<&'static <Self as driver::Adapter>::IdInfo> {
- let table = Self::i2c_id_table()?;
-
- // SAFETY:
- // - `table` has static lifetime, hence it's valid for reads
- // - `dev` is guaranteed to be valid while it's alive, and so is `dev.as_raw()`.
- let raw_id = unsafe { bindings::i2c_match_id(table.as_ptr(), dev.as_raw()) };
-
- if raw_id.is_null() {
- return None;
- }
-
- // SAFETY: `DeviceId` is a `#[repr(transparent)` wrapper of `struct i2c_device_id` and
- // does not add additional invariants, so it's safe to transmute.
- let id = unsafe { &*raw_id.cast::<DeviceId>() };
-
- // SAFETY: `id` comes from `table` which is of type `IdArray<_, Self::IdInfo>`.
- Some(unsafe { id.info_unchecked::<T::IdInfo>() })
- }
}
impl<T: Driver> driver::Adapter for Adapter<T> {
--
2.43.0
prev parent reply other threads:[~2026-11-11 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:52 [RFC PATCH] " Andrew Davis
2026-11-11 23:10 ` Andrew Davis [this message]
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=20261111231053.529616-1-afd@ti.com \
--to=afd@ti.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=igor.korotin@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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®