From: Danilo Krummrich <dakr@kernel.org>
To: Remo Senekowitsch <remo@buenzli.dev>
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 v6 4/9] rust: device: Enable printing fwnode name and path
Date: Sun, 25 May 2025 14:48:18 +0200 [thread overview]
Message-ID: <aDMRkq9oPzFJBBzy@pollux.localdomain> (raw)
In-Reply-To: <20250524192232.705860-5-remo@buenzli.dev>
On Sat, May 24, 2025 at 09:22:27PM +0200, Remo Senekowitsch wrote:
> + /// Returns an object that implements [`Display`](core::fmt::Display) for
> + /// printing the full path of a node.
> + pub fn display_path(&self) -> impl core::fmt::Display + '_ {
While testing the code I found the following buggy print statement:
"test-device@2/test-device@2/test-device@2/test-device@2: property 'test,u32-required-prop' is missing"
and I think the following changes fix this:
> + struct FwNodeDisplayPath<'a>(&'a FwNode);
> +
> + impl core::fmt::Display for FwNodeDisplayPath<'_> {
> + fn fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result {
> + // The logic here is the same as the one in lib/vsprintf.c
> + // (fwnode_full_name_string).
> +
> + // SAFETY: `self.0.as_raw()` is valid by its type invariant.
> + let num_parents = unsafe { bindings::fwnode_count_parents(self.0.as_raw()) };
> +
> + for depth in (0..=num_parents).rev() {
> + let fwnode = if depth == 0 {
> + self.0.as_raw()
self.0
> + } else {
> + // SAFETY: `self.0.as_raw()` is valid.
> + unsafe { bindings::fwnode_get_nth_parent(self.0.as_raw(), depth) }
let ptr = unsafe { bindings::fwnode_get_nth_parent(self.0.as_raw(), depth) };
FwNode::as_ref(ptr)
where FwNode::as_ref() is
unsafe fn as_ref<'a>(ptr: *mut bindings::fwnode_handle) -> &'a Self
> + };
> +
> + // SAFETY: `fwnode` is valid, it is either `self.0.as_raw()`
> + // or the return value of `bindings::fwnode_get_nth_parent`
> + // which returns a valid pointer to a `fwnode_handle` if the
> + // provided depth is within the valid range, which we know
> + // to be true.
> + let prefix = unsafe { bindings::fwnode_get_name_prefix(fwnode) };
> + if !prefix.is_null() {
> + // SAFETY: `fwnode_get_name_prefix` returns null or a
> + // valid C string.
> + let prefix = unsafe { CStr::from_char_ptr(prefix) };
> + write!(f, "{prefix}")?;
> + }
> + write!(f, "{}", self.0.display_name())?;
write!(f, "{}", fwnode.0.display_name())?;
Otherwise we always write the name of self, no matter the actual parent depth.
> +
> + if depth != 0 {
> + // SAFETY:
> + // - `fwnode` is valid, because `depth` is
> + // a valid depth of a parent of `self.0.as_raw()`.
> + // - `fwnode_get_nth_parent` increments the refcount and
> + // we are responsible to decrement it.
> + unsafe { bindings::fwnode_handle_put(fwnode) }
> + }
> + }
> +
> + Ok(())
> + }
> + }
> +
> + FwNodeDisplayPath(self)
> + }
next prev parent reply other threads:[~2025-05-25 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 19:22 [PATCH v6 0/9] More Rust bindings for device property reads Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 1/9] rust: device: Create FwNode abstraction for accessing device properties Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 2/9] rust: device: Enable accessing the FwNode of a Device Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 3/9] rust: device: Add property_present() to FwNode Remo Senekowitsch
2025-05-25 23:19 ` Charalampos Mitrodimas
2025-05-24 19:22 ` [PATCH v6 4/9] rust: device: Enable printing fwnode name and path Remo Senekowitsch
2025-05-25 12:48 ` Danilo Krummrich [this message]
2025-05-24 19:22 ` [PATCH v6 5/9] rust: device: Introduce PropertyGuard Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 6/9] rust: device: Implement accessors for firmware properties Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 7/9] rust: device: Add child accessor and iterator Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 8/9] rust: device: Add property_get_reference_args Remo Senekowitsch
2025-05-24 19:22 ` [PATCH v6 9/9] samples: rust: platform: Add property read examples Remo Senekowitsch
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=aDMRkq9oPzFJBBzy@pollux.localdomain \
--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 \
/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