From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Mark Brown <broonie@kernel.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 18:06:24 +0200 [thread overview]
Message-ID: <52c60fe9-fff0-29a7-1e7a-12ebd207ca58@linaro.org> (raw)
In-Reply-To: <34edabd6-8dd1-42f8-8309-07dfbf157dff@sirena.org.uk>
On 26/07/2023 14:30, Mark Brown wrote:
> 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.
Regulator can be enabled in different ways, including by drivers. The
text in description was accurate.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-26 16:06 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
2023-07-26 16:06 ` Krzysztof Kozlowski [this message]
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=52c60fe9-fff0-29a7-1e7a-12ebd207ca58@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=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=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).