[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141008143439.GB4609@sirena.org.uk>
Date: Wed, 8 Oct 2014 15:34:39 +0100
From: Mark Brown <broonie@...nel.org>
To: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Cc: Doug Anderson <dianders@...omium.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
Olof Johansson <olof@...om.net>,
Chris Zhong <zyw@...k-chips.com>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Abhilash Kesavan <kesavan.abhilash@...il.com>,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 3/5] regulator: dt-bindings: Add regulator-initial-mode
support
On Wed, Oct 08, 2014 at 03:44:05PM +0200, Javier Martinez Canillas wrote:
> +- regulator-initial-mode: initial regulator operating mode. One of following:
> + <1>: REGULATOR_MODE_FAST - Regulator can handle fast changes.
> + <2>: REGULATOR_MODE_NORMAL - Normal regulator power supply mode.
> + <4>: REGULATOR_MODE_IDLE - Regulator runs in a more efficient mode.
> + <8>: REGULATOR_MODE_STANDBY - Regulator runs in the most efficient mode.
> + modes are defined in the dt-bindings/regulator/regulator.h header and can be
> + used in device tree sources files. If no mode is defined, then the OS will not
> + manage the operating mode and the HW default values will be used instead.
...and as previously and repeatedly discussed this still gives the user
no way of telling if or how these modes might correspond to what the
chip is capable of doing. This really needs addressing rather than
ignoring, for example by not trying to define the modes in generic
bindings.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists