The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Charalampos Mitrodimas <charmitro@posteo.net>
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>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"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 3/9] rust: device: Add property_present() to FwNode
Date: Sun, 25 May 2025 23:19:54 +0000	[thread overview]
Message-ID: <874ix8num4.fsf@posteo.net> (raw)
In-Reply-To: <20250524192232.705860-4-remo@buenzli.dev>


Remo Senekowitsch <remo@buenzli.dev> writes:

> The new FwNode abstraction will be used for accessing all device
> properties, so it must have the property_present method.
>
> It's 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.
> So, in the future, property_perent will be removed from Device. However,

Hi Remo!

Spotted a typo, property_present.

--
C. Mitrodimas

> there's a user about to be merged, so the method is left to make merging
> easier.
>
> Signed-off-by: Remo Senekowitsch <remo@buenzli.dev>
> ---
>  rust/kernel/device/property.rs | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/rust/kernel/device/property.rs b/rust/kernel/device/property.rs
> index ca525ed0e8e8f..71a0605b8ecad 100644
> --- a/rust/kernel/device/property.rs
> +++ b/rust/kernel/device/property.rs
> @@ -6,7 +6,7 @@
>  
>  use core::ptr;
>  
> -use crate::{bindings, types::Opaque};
> +use crate::{bindings, str::CStr, types::Opaque};
>  
>  /// A reference-counted fwnode_handle.
>  ///
> @@ -31,6 +31,12 @@ impl FwNode {
>      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.


  reply	other threads:[~2025-05-25 23:22 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 [this message]
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
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=874ix8num4.fsf@posteo.net \
    --to=charmitro@posteo.net \
    --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=dakr@kernel.org \
    --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