[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCnQo15SbhXZ9Fln@finisterre.sirena.org.uk>
Date: Sun, 18 May 2025 13:20:51 +0100
From: Mark Brown <broonie@...nel.org>
To: Alexandre Courbot <acourbot@...dia.com>
Cc: Benno Lossin <lossin@...nel.org>,
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 Sun, May 18, 2025 at 05:14:41PM +0900, Alexandre Courbot wrote:
> The initial proposal does such clamping by design, but I also suspect
> the C API behave like it does for good reasons (which I am not familiar
> enough to be aware of unfortunately).
It's so that if you have multiple logical users within the device (eg,
an interrupt handler and code for normal operation) they can work
independently of each other. You could also request the regulator
multiple times but that's often not idiomatic.
Originally we didn't actually refcount within the individual consumers
at all and only refcounted on the underlying regulator, the per consumer
reference count is mainly there for debugging purposes.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists