From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Jones Subject: Re: [PATCH v5 4/5] mfd/regulator: dt-bindings: max77686: Document gpio properties Date: Tue, 20 Jan 2015 15:43:11 +0000 Message-ID: <20150120154311.GE13701@x1> References: <1420458525-22576-1-git-send-email-k.kozlowski@samsung.com> <1420458525-22576-5-git-send-email-k.kozlowski@samsung.com> <20150120134111.GI13701@x1> <1421763703.8855.10.camel@AMDC1943> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <1421763703.8855.10.camel@AMDC1943> Sender: linux-kernel-owner@vger.kernel.org To: Krzysztof Kozlowski Cc: Liam Girdwood , Mark Brown , linux-kernel@vger.kernel.org, Kukjin Kim , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, Kyungmin Park , Bartlomiej Zolnierkiewicz List-Id: devicetree@vger.kernel.org On Tue, 20 Jan 2015, Krzysztof Kozlowski wrote: > On wto, 2015-01-20 at 13:41 +0000, Lee Jones wrote: > > On Mon, 05 Jan 2015, Krzysztof Kozlowski wrote: > >=20 > > > Document usage of maxim,ena-gpios properties which turn on extern= al/GPIO > > > control over regulator. > > >=20 > > > Signed-off-by: Krzysztof Kozlowski > > > --- > > > Documentation/devicetree/bindings/mfd/max77686.txt | 14 ++++++++= ++++++ > > > 1 file changed, 14 insertions(+) > > >=20 > > > diff --git a/Documentation/devicetree/bindings/mfd/max77686.txt b= /Documentation/devicetree/bindings/mfd/max77686.txt > > > index 75fdfaf41831..e39f0bc1f55e 100644 > > > --- a/Documentation/devicetree/bindings/mfd/max77686.txt > > > +++ b/Documentation/devicetree/bindings/mfd/max77686.txt > > > @@ -39,6 +39,12 @@ to get matched with their hardware counterpart= s as follow: > > > -BUCKn : 1-4. > > > Use standard regulator bindings for it ('regulator-off-in-susp= end'). > > > =20 > > > + LDO20, LDO21, LDO22, BUCK8 and BUCK9 can be configured to GPIO= enable > > > + control. To turn this feature on this property must be added t= o the regulator > > > + sub-node: > > > + - maxim,ena-gpios : one GPIO specifier enable control (the gpio > > > + flags are actually ignored and always > > > + ACTIVE_HIGH is used) > >=20 > > How does this differ to the 'enable-gpio' property which has alread= y > > been defined? >=20 > Strictly speaking - no difference, just a GPIO specifier. >=20 > However the 'enable-gpio' property exists only for gpio-regulator. Th= e > regulator core does not support generic enable-gpio property and each > driver implements it on its own. >=20 > Anyway Mark Brown already applied this patch to his regulator tree. Well if he has no issue with it, then I guess I don't. > > > Example: > > > =20 > > > @@ -65,4 +71,12 @@ Example: > > > regulator-always-on; > > > regulator-boot-on; > > > }; > > > + > > > + buck9_reg { > > > + regulator-compatible =3D "BUCK9"; > > > + regulator-name =3D "CAM_ISP_CORE_1.2V"; > > > + regulator-min-microvolt =3D <1000000>; > > > + regulator-max-microvolt =3D <1200000>; > > > + maxim,ena-gpios =3D <&gpm0 3 GPIO_ACTIVE_HIGH>; > > > + }; > > > } > >=20 >=20 --=20 Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org =E2=94=82 Open source software for ARM SoCs =46ollow Linaro: Facebook | Twitter | Blog