From: Danilo Krummrich <dakr@kernel.org>
To: Remo Senekowitsch <remo@buenzli.dev>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"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>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v8 3/9] rust: device: Move property_present() to FwNode
Date: Wed, 11 Jun 2025 14:08:31 +0200 [thread overview]
Message-ID: <aElxv3hRIc6Z_7jg@cassiopeiae> (raw)
In-Reply-To: <20250611102908.212514-4-remo@buenzli.dev>
(+Viresh, FYI)
On Wed, Jun 11, 2025 at 12:29:02PM +0200, Remo Senekowitsch wrote:
> The new FwNode abstraction will be used for accessing all device
> properties.
>
> It would be possible to duplicate the methods on the device itself, but
> since some of the methods on Device would have different type sigatures
> as the ones on FwNode, this would only lead to inconsistency and
> confusion. For this reason, property_present is removed from Device and
> existing users are updated.
>
> Signed-off-by: Remo Senekowitsch <remo@buenzli.dev>
> ---
> drivers/cpufreq/rcpufreq_dt.rs | 3 ++-
> rust/kernel/device.rs | 7 -------
> rust/kernel/device/property.rs | 7 +++++++
> 3 files changed, 9 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/cpufreq/rcpufreq_dt.rs b/drivers/cpufreq/rcpufreq_dt.rs
> index 94ed81644fe1c..4eb240dc9fdc8 100644
> --- a/drivers/cpufreq/rcpufreq_dt.rs
> +++ b/drivers/cpufreq/rcpufreq_dt.rs
> @@ -20,7 +20,8 @@
> /// Finds exact supply name from the OF node.
> fn find_supply_name_exact(dev: &Device, name: &str) -> Option<CString> {
> let prop_name = CString::try_from_fmt(fmt!("{}-supply", name)).ok()?;
> - dev.property_present(&prop_name)
> + dev.fwnode()?
> + .property_present(&prop_name)
> .then(|| CString::try_from_fmt(fmt!("{name}")).ok())
> .flatten()
> }
> diff --git a/rust/kernel/device.rs b/rust/kernel/device.rs
> index b69f03a7f8d30..241a395d529a1 100644
> --- a/rust/kernel/device.rs
> +++ b/rust/kernel/device.rs
> @@ -6,7 +6,6 @@
>
> use crate::{
> bindings,
> - str::CStr,
> types::{ARef, Opaque},
> };
> use core::{fmt, marker::PhantomData, ptr};
> @@ -219,12 +218,6 @@ pub fn fwnode(&self) -> Option<&property::FwNode> {
> // defined as a `#[repr(transparent)]` wrapper around `fwnode_handle`.
> Some(unsafe { &*fwnode_handle.cast() })
> }
> -
> - /// Checks if property is present or not.
> - pub fn property_present(&self, name: &CStr) -> bool {
> - // SAFETY: By the invariant of `CStr`, `name` is null-terminated.
> - unsafe { bindings::device_property_present(self.as_raw().cast_const(), name.as_char_ptr()) }
> - }
> }
>
> // SAFETY: `Device` is a transparent wrapper of a type that doesn't depend on `Device`'s generic
> diff --git a/rust/kernel/device/property.rs b/rust/kernel/device/property.rs
> index 03850b7bb8087..50c61aa056e6b 100644
> --- a/rust/kernel/device/property.rs
> +++ b/rust/kernel/device/property.rs
> @@ -8,6 +8,7 @@
>
> use crate::{
> bindings,
> + str::CStr,
> types::{ARef, Opaque},
> };
>
> @@ -55,6 +56,12 @@ unsafe fn from_raw(raw: *mut bindings::fwnode_handle) -> ARef<Self> {
> pub(crate) fn as_raw(&self) -> *mut bindings::fwnode_handle {
> self.0.get()
> }
> +
> + /// Checks if property is present or not.
> + pub fn property_present(&self, name: &CStr) -> bool {
> + // SAFETY: By the invariant of `CStr`, `name` is null-terminated.
> + unsafe { bindings::fwnode_property_present(self.as_raw().cast_const(), name.as_char_ptr()) }
> + }
> }
>
> // SAFETY: Instances of `FwNode` are always reference-counted.
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-06-11 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 10:28 [PATCH v8 0/9] More Rust bindings for device property reads Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 1/9] rust: device: Create FwNode abstraction for accessing device properties Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 2/9] rust: device: Enable accessing the FwNode of a Device Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 3/9] rust: device: Move property_present() to FwNode Remo Senekowitsch
2025-06-11 12:08 ` Danilo Krummrich [this message]
2025-06-12 3:13 ` Viresh Kumar
2025-06-11 10:29 ` [PATCH v8 4/9] rust: device: Enable printing fwnode name and path Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 5/9] rust: device: Introduce PropertyGuard Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 6/9] rust: device: Implement accessors for firmware properties Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 7/9] rust: device: Add child accessor and iterator Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 8/9] rust: device: Add property_get_reference_args Remo Senekowitsch
2025-06-11 10:29 ` [PATCH v8 9/9] samples: rust: platform: Add property read examples Remo Senekowitsch
2025-06-11 12:06 ` [PATCH v8 0/9] More Rust bindings for device property reads Danilo Krummrich
2025-06-12 23:31 ` Danilo Krummrich
2025-06-13 7:45 ` Remo Senekowitsch
2025-06-13 8:50 ` 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=aElxv3hRIc6Z_7jg@cassiopeiae \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=remo@buenzli.dev \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@google.com \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).