[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_1OaYt22_GJRX0b@cassiopeiae>
Date: Mon, 14 Apr 2025 20:05:29 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Remo Senekowitsch <remo@...nzli.dev>
Cc: Rob Herring <robh@...nel.org>, Saravana Kannan <saravanak@...gle.com>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v2 2/5] rust: Add bindings for reading device properties
On Mon, Apr 14, 2025 at 07:44:36PM +0200, Danilo Krummrich wrote:
> On Mon, Apr 14, 2025 at 05:26:27PM +0200, Remo Senekowitsch wrote:
> > The device property API is a firmware agnostic API for reading
> > properties from firmware (DT/ACPI) devices nodes and swnodes.
> >
> > While the C API takes a pointer to a caller allocated variable/buffer,
> > the rust API is designed to return a value and can be used in struct
> > initialization. Rust generics are also utilized to support different
> > types of properties where appropriate.
> >
> > The PropertyGuard is a way to force users to specify whether a property
> > is supposed to be required or not. This allows us to move error
> > logging of missing required properties into core, preventing a lot of
> > boilerplate in drivers.
>
> The patch adds a lot of thing, i.e.
> * implement PropertyInt
I meant the Property trait and all its impls of course. :)
> * implement PropertyGuard
> * extend FwNode by a lot of functions
> * extend Device by some property functions
Powered by blists - more mailing lists