From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Support Opensource <support.opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Eric Jeong <eric.jeong.opensource@diasemi.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] regulator: dt-bindings: dlg,slg51000: Convert to DT schema
Date: Wed, 26 Jul 2023 13:30:51 +0100 [thread overview]
Message-ID: <34edabd6-8dd1-42f8-8309-07dfbf157dff@sirena.org.uk> (raw)
In-Reply-To: <2df8d695-62aa-329f-f355-d6081d970ec2@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
On Wed, Jul 26, 2023 at 02:18:43PM +0200, Krzysztof Kozlowski wrote:
> On 26/07/2023 13:55, Mark Brown wrote:
> > Oh, you mean if the regulator is in use in the system rather than if
> > it's enabled!
> Enabled as "always-on" or "boot-on" could be encoded in the schema with
> multiple if::then:. But it is not enough, because regulators can be
> enabled on demand by drivers. So that's what I meant by "used".
Right, you said "enabled" in the changelog bit though.
> > I suspect that there's a requirement that either at least
> > one of the supplies be provided so that the chip I/O works, or there's
> > some other currently undocumented supply that is required for that
> > reason.
> I can add requirement of at least one supply. I don't think it changes
> much, but sure.
I wouldn't, I suspect it's the latter case and there's actually another
undocumented change.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-26 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:31 [PATCH v2] regulator: dt-bindings: dlg,slg51000: Convert to DT schema Krzysztof Kozlowski
2023-07-25 10:43 ` Mark Brown
2023-07-26 7:32 ` Krzysztof Kozlowski
2023-07-26 11:55 ` Mark Brown
2023-07-26 12:18 ` Krzysztof Kozlowski
2023-07-26 12:30 ` Mark Brown [this message]
2023-07-26 16:06 ` Krzysztof Kozlowski
2023-07-27 18:17 ` Mark Brown
2023-07-27 17:16 ` 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=34edabd6-8dd1-42f8-8309-07dfbf157dff@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eric.jeong.opensource@diasemi.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.com \
/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;
as well as URLs for NNTP newsgroup(s).