linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/5] mfd/regulator: dt-bindings: max77686: Document gpio properties
Date: Tue, 20 Jan 2015 15:43:11 +0000	[thread overview]
Message-ID: <20150120154311.GE13701@x1> (raw)
In-Reply-To: <1421763703.8855.10.camel@AMDC1943>

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:
> > 
> > > Document usage of maxim,ena-gpios properties which turn on external/GPIO
> > > control over regulator.
> > > 
> > > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > > ---
> > >  Documentation/devicetree/bindings/mfd/max77686.txt | 14 ++++++++++++++
> > >  1 file changed, 14 insertions(+)
> > > 
> > > 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 counterparts as follow:
> > >  	-BUCKn	:	1-4.
> > >    Use standard regulator bindings for it ('regulator-off-in-suspend').
> > >  
> > > +  LDO20, LDO21, LDO22, BUCK8 and BUCK9 can be configured to GPIO enable
> > > +  control. To turn this feature on this property must be added to the regulator
> > > +  sub-node:
> > > +	- maxim,ena-gpios :	one GPIO specifier enable control (the gpio
> > > +				flags are actually ignored and always
> > > +				ACTIVE_HIGH is used)
> > 
> > How does this differ to the 'enable-gpio' property which has already
> > been defined?
> 
> Strictly speaking - no difference, just a GPIO specifier.
> 
> However the 'enable-gpio' property exists only for gpio-regulator. The
> regulator core does not support generic enable-gpio property and each
> driver implements it on its own.
> 
> 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:
> > >  
> > > @@ -65,4 +71,12 @@ Example:
> > >  				regulator-always-on;
> > >  				regulator-boot-on;
> > >  			};
> > > +
> > > +			buck9_reg {
> > > +				regulator-compatible = "BUCK9";
> > > +				regulator-name = "CAM_ISP_CORE_1.2V";
> > > +				regulator-min-microvolt = <1000000>;
> > > +				regulator-max-microvolt = <1200000>;
> > > +				maxim,ena-gpios = <&gpm0 3 GPIO_ACTIVE_HIGH>;
> > > +			};
> > >  	}
> > 
> 

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2015-01-20 15:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 11:48 [PATCH v5 0/5] regulator: Allow parsing custom DT properties with simplified DT parse Krzysztof Kozlowski
2015-01-05 11:48 ` [PATCH v5 1/5] regulator: Copy config passed during registration Krzysztof Kozlowski
2015-01-05 11:48 ` [PATCH v5 2/5] regulator: Allow parsing custom properties when using simplified DT parsing Krzysztof Kozlowski
2015-01-05 11:48 ` [PATCH v5 3/5] regulator: max77686: Add GPIO control Krzysztof Kozlowski
2015-01-05 11:48 ` [PATCH v5 4/5] mfd/regulator: dt-bindings: max77686: Document gpio properties Krzysztof Kozlowski
2015-01-20 13:41   ` Lee Jones
2015-01-20 14:21     ` Krzysztof Kozlowski
2015-01-20 15:43       ` Lee Jones [this message]
2015-01-05 11:48 ` [PATCH v5 5/5] ARM: dts: exynos4412-trats: Switch max77686 regulators to GPIO control Krzysztof Kozlowski
2015-01-09  8:39   ` Krzysztof Kozlowski
2015-01-08 20:16 ` [PATCH v5 0/5] regulator: Allow parsing custom DT properties with simplified DT parse 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=20150120154311.GE13701@x1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).