[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191204134631.GT1998@sirena.org.uk>
Date: Wed, 4 Dec 2019 13:46:31 +0000
From: Mark Brown <broonie@...nel.org>
To: Marco Felsch <m.felsch@...gutronix.de>
Cc: support.opensource@...semi.com, lee.jones@...aro.org,
robh+dt@...nel.org, linus.walleij@...aro.org,
bgolaszewski@...libre.com, joel@....id.au, andrew@...id.au,
lgirdwood@...il.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-aspeed@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, kernel@...gutronix.de
Subject: Re: [PATCH v3 3/6] dt-bindings: mfd: da9062: add regulator voltage
selection documentation
On Fri, Nov 29, 2019 at 06:25:34PM +0100, Marco Felsch wrote:
> + Optional regulator device-specific properties:
> + - dlg,vsel-sense-gpios : A GPIO reference to a local general purpose input,
> + the datasheet calls it GPI. The regulator sense the input signal and select
> + the active or suspend voltage settings. If the signal is active the
> + active-settings are applied else the suspend-settings are applied.
> + Attention: Sharing the same GPI for other purposes or across multiple
> + regulators is possible but the polarity setting must equal.
I'm really confused by this. As far as I understand it it seems
to be doing pinmuxing on the chip using the GPIO bindings which
is itself a bit odd and I don't see anything here that configures
whatever sets the state of the pins. Don't we need another GPIO
to set the vsel-sense inputs on the PMIC?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists