[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZHmbgaHHbsXuAg4GD_cWWSx33WQ71Sk11HySoeorfUbA@mail.gmail.com>
Date: Fri, 29 Nov 2019 09:33:04 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Marco Felsch <m.felsch@...gutronix.de>
Cc: Bartosz Golaszewski <bgolaszewski@...libre.com>,
Support Opensource <support.opensource@...semi.com>,
Lee Jones <lee.jones@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, stwiss.opensource@...semi.com,
Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sascha Hauer <kernel@...gutronix.de>
Subject: Re: [PATCH v2 4/5] dt-bindings: mfd: da9062: add regulator gpio
enable/disable documentation
On Wed, Nov 27, 2019 at 2:59 PM Marco Felsch <m.felsch@...gutronix.de> wrote:
> At the gpio-based regulator enable/disable documentation. This property
> can be applied to each subnode within the 'regulators' node so each
> regulator can be configured differently.
>
> Signed-off-by: Marco Felsch <m.felsch@...gutronix.de>
(...)
> + - dlg,ena-sense-gpios : The GPIO reference which should be used by the
> + regulator to enable/disable the output. If the signal is active the
> + regulator is on else it is off. Attention: Sharing the same gpio for other
> + purposes or across multiple regulators is possible but the gpio settings
> + must be the same. Also the gpio phandle must refer to the mfd root node
> + other gpios are not allowed and make no sense.
- Point out that this concerns references to the GPI general purpose
input on the DA9062 itself, and not just "any" GPIO. The last sentence
tries to say this but it should be stated more clearly.
- Clarify which "gpio settings" must be the same, e.g. polarity I guess.
Yours,
Linus Walleij
Powered by blists - more mailing lists