On Fri, Nov 28, 2014 at 12:54:27PM +0100, Krzysztof Kozlowski wrote:
> On pią, 2014-11-28 at 11:21 +, Mark Brown wrote:
> > On Fri, Nov 28, 2014 at 10:09:44AM +0100, Krzysztof Kozlowski wrote:
> > > I understand your concerns here however I didn't want to overengineer
> > > this. Is the same G
On pią, 2014-11-28 at 11:21 +, Mark Brown wrote:
> On Fri, Nov 28, 2014 at 10:09:44AM +0100, Krzysztof Kozlowski wrote:
>
> > I understand your concerns here however I didn't want to overengineer
> > this. Is the same GPIO (on more complex PMICs) used in different
> > contexts? Like enable con
On Fri, Nov 28, 2014 at 10:09:44AM +0100, Krzysztof Kozlowski wrote:
> I understand your concerns here however I didn't want to overengineer
> this. Is the same GPIO (on more complex PMICs) used in different
> contexts? Like enable control and something more in the same time?
Yes, and it's often
On czw, 2014-11-27 at 18:30 +, Mark Brown wrote:
> On Thu, Nov 27, 2014 at 12:20:48PM +0100, Krzysztof Kozlowski wrote:
>
> > +- ena-gpios: GPIO to use for enable control. Actual implementation depends
> > + on regulator driver. The bindings documentation for given driver
> > describes
> > +
On Thu, Nov 27, 2014 at 12:20:48PM +0100, Krzysztof Kozlowski wrote:
> +- ena-gpios: GPIO to use for enable control. Actual implementation depends
> + on regulator driver. The bindings documentation for given driver describes
> + which regulator actually supports it.
> +- ena-gpio-open-drain: GP
Document new properties for regulators (ena-gpios and
ena-gpio-open-drain) for enabling control over GPIO.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/regulator/regulator.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/re
