[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1rT96QzwIn5pIVn@sirena.org.uk>
Date: Thu, 27 Oct 2022 19:54:47 +0100
From: Mark Brown <broonie@...nel.org>
To: Zev Weiss <zev@...ilderbeest.net>
Cc: Rob Herring <robh@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Naresh Solanki <naresh.solanki@...ements.com>,
Patrick Rudolph <patrick.rudolph@...ements.com>,
Laxman Dewangan <ldewangan@...dia.com>,
openbmc@...ts.ozlabs.org
Subject: Re: [PATCH 2/3] dt-bindings: regulator: Add regulator-output binding
On Thu, Sep 29, 2022 at 02:27:19PM -0700, Zev Weiss wrote:
> On Thu, Sep 29, 2022 at 02:07:14PM PDT, Rob Herring wrote:
> never as any sort of default/automatic action. The two obvious things to
> guard against there seem to be automatic enablement during initialization
> and automatic disablement on de-init (shutdown, unbind, etc.). The former I
> think can be avoided by simply not setting regulator-boot-on, so I added
> this as a corresponding property to avoid the latter.
> I'm definitely open to suggestions for a better approach though.
regulator-boot-on mainly exists for handover of state from the
bootloader where we can't read back the state of the hardware rather
than as a control for boot purposes.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists