[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCS71sbQKn7zeosR@finisterre.sirena.org.uk>
Date: Wed, 14 May 2025 17:50:46 +0200
From: Mark Brown <broonie@...nel.org>
To: Benno Lossin <lossin@...nel.org>
Cc: Daniel Almeida <daniel.almeida@...labora.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 v3] rust: regulator: add a bare minimum regulator
abstraction
On Wed, May 14, 2025 at 05:38:40PM +0200, Benno Lossin wrote:
> On Wed May 14, 2025 at 4:40 PM CEST, Daniel Almeida wrote:
> > By the way, IIUC, regulator_disable() does not disable a regulator necessarily.
> > It just tells the system that you don't care about it being enabled anymore. It can
> > still remain on if there are other users.
> Hmm, so a `struct regulator` might already be enabled and calling
> `regulator_enable` doesn't do anything?
It takes a reference to the regulator. This may or may not result in a
change in an underlying physical regulator.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists