From: Mark Brown <broonie@kernel.org>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Rob Herring <robh@kernel.org>,
Naresh Solanki <naresh.solanki@9elements.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v4 2/4] dt-bindings: regulator: add bindings for output-supply
Date: Thu, 21 Jul 2022 12:05:27 +0100 [thread overview]
Message-ID: <Ytky912vo1HmEWkd@sirena.org.uk> (raw)
In-Reply-To: <YtkPUOh5XiQyGLxw@hatter.bewilderbeest.net>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On Thu, Jul 21, 2022 at 01:33:20AM -0700, Zev Weiss wrote:
> A question for Mark though -- in one of my earliest stabs at this I floated
> the idea of using reg-userspace-consumer for it, but was told in no
> uncertain terms that that driver was for testing only and should under no
> circumstances ever be instantiated in a production system. Has the thinking
> on its usage changed in the last year or so such that this approach was
> deemed okay?
I was talked around after some discussion of the use case. It's still
not a great API but for at least some of these users it'll do. It's
important that it not appear directly in bindings though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-21 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 8:18 [PATCH v4 0/4] regulator: output-supply DT support Naresh Solanki
2022-07-07 8:18 ` [PATCH v4 1/4] dt-bindings: vendor-prefixes: add 9elements Naresh Solanki
2022-07-11 22:19 ` Rob Herring
2022-07-07 8:18 ` [PATCH v4 2/4] dt-bindings: regulator: add bindings for output-supply Naresh Solanki
2022-07-08 18:33 ` Mark Brown
2022-07-14 14:02 ` Rob Herring
2022-07-14 14:10 ` Rob Herring
2022-07-14 14:14 ` Mark Brown
2022-07-14 14:23 ` Rob Herring
2022-07-14 14:42 ` Mark Brown
2022-07-14 15:07 ` Rob Herring
2022-07-14 15:54 ` Mark Brown
2022-07-14 16:59 ` Rob Herring
2022-07-14 17:50 ` Mark Brown
2022-07-21 8:33 ` Zev Weiss
2022-07-21 11:05 ` Mark Brown [this message]
2022-07-07 8:18 ` [PATCH v4 3/4] regulator: output-supply: Add devicetree support Naresh Solanki
2022-07-07 8:18 ` [PATCH v4 4/4] regulator: output-supply: Add Notification support Naresh Solanki
2022-07-11 19:11 ` [PATCH v4 0/4] regulator: output-supply DT support Mark Brown
2022-07-14 14:17 ` Rob Herring
2022-07-14 18:24 ` Mark Brown
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=Ytky912vo1HmEWkd@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--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®