[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191001174104.GD4786@sirena.co.uk>
Date: Tue, 1 Oct 2019 18:41:04 +0100
From: Mark Brown <broonie@...nel.org>
To: Douglas Anderson <dianders@...omium.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Marco Felsch <m.felsch@...gutronix.de>,
ckeepax@...nsource.cirrus.com, zhang.chunyan@...aro.org,
devicetree@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org, Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH] regulator: Document "regulator-boot-on" binding more
thoroughly
On Thu, Sep 26, 2019 at 12:41:18PM -0700, Douglas Anderson wrote:
> - description: bootloader/firmware enabled regulator
> + description: bootloader/firmware enabled regulator.
> + It's expected that this regulator was left on by the bootloader.
> + If the bootloader didn't leave it on then OS should turn it on
> + at boot but shouldn't prevent it from being turned off later.
This is good...
> + This property is intended to only be used for regulators where
> + Linux cannot read the state of the regulator at bootup.
...but we shouldn't say "Linux" here since the DT binding is for all
OSs, not just Linux. I'd say "software" instead. Really the
expectation is that things wouldn't support readback at all, though it's
possible there's some weird hardware out there that will support
readback some of the time I guess.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists