[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <6A5766B8-EF9A-41EA-AE55-D29C5184A9DB@collabora.com>
Date: Mon, 16 Jun 2025 11:27:25 -0300
From: Daniel Almeida <daniel.almeida@...labora.com>
To: Mark Brown <broonie@...nel.org>
Cc: Alexandre Courbot <acourbot@...dia.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>,
Danilo Krummrich <dakr@...nel.org>,
Boris Brezillon <boris.brezillon@...labora.com>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v4] rust: regulator: add a bare minimum regulator
abstraction
Mark,
The current patch implements different strategies to handle regulators. By
‘dynamic regulator’ he means the one that implements the current C
behavior.
> I'm not sure what you mean by a "dynamic regulator" here but as
> previously outlined we currently take a very conservative approach and
> don't do things without being explicitly told to do so since getting
> things wrong can result in physical damage to the system.
>
> Please delete unneeded context from mails when replying. Doing this
> makes it much easier to find your reply in the message, helping ensure
> it won't be missed by people scrolling through the irrelevant quoted
> material.
Ok, no worries, this current version of the binding is already implemented as
you said, so we won’t have any problems there.
— Daniel
Powered by blists - more mailing lists