From: Mark Brown <broonie@kernel.org>
To: Daniel Okazaki <dtokazaki@google.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Zev Weiss <zev@bewilderbeest.net>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 0/2] userspace-consumer: adding is_shared flag
Date: Wed, 28 May 2025 19:16:04 +0100 [thread overview]
Message-ID: <a0bf24c6-58da-42e7-b686-03a893b38ecb@sirena.org.uk> (raw)
In-Reply-To: <20250528174426.3318110-1-dtokazaki@google.com>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Wed, May 28, 2025 at 05:44:23PM +0000, Daniel Okazaki wrote:
> Currently this userspace regulator driver requires exclusive control
> of the regulator to operate. This patch adds an optional flag to
> remove that constraint, and allow the regulator to be shared by other
> modules. This allows for userspace to share control over a regulator
> with kernel space.
What is the use case here? This is a debug tool intended mainly for
when you're developing a regulator driver and have something like a
development board with no consumers at all.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-28 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 17:44 Daniel Okazaki
2025-05-28 17:44 ` [PATCH v1 1/2] regulator: Add regulator-output is_shared property Daniel Okazaki
2025-05-28 17:44 ` [PATCH v1 2/2] regulator: userspace-consumer add shared supply functionality Daniel Okazaki
2025-05-28 18:16 ` Mark Brown [this message]
2025-05-28 18:32 ` [PATCH v1 0/2] userspace-consumer: adding is_shared flag Daniel Okazaki
2025-05-28 19:20 ` Mark Brown
2025-05-28 21:15 ` Daniel Okazaki
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=a0bf24c6-58da-42e7-b686-03a893b38ecb@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dtokazaki@google.com \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zev@bewilderbeest.net \
/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
all inboxes | Powered by JetHome®