[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM5PR1001MB0994C60CB5B957CFE19E495D80510@AM5PR1001MB0994.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 16 Dec 2019 16:32:48 +0000
From: Adam Thomson <Adam.Thomson.Opensource@...semi.com>
To: Marco Felsch <m.felsch@...gutronix.de>,
Mark Brown <broonie@...nel.org>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Support Opensource <Support.Opensource@...semi.com>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"andrew@...id.au" <andrew@...id.au>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bgolaszewski@...libre.com" <bgolaszewski@...libre.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"joel@....id.au" <joel@....id.au>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH v3 3/6] dt-bindings: mfd: da9062: add regulator voltage
selection documentation
> -----Original Message-----
> From: Marco Felsch <m.felsch@...gutronix.de>
> Sent: 16 December 2019 08:55
> To: Mark Brown <broonie@...nel.org>
> Cc: devicetree@...r.kernel.org; Support Opensource
> <Support.Opensource@...semi.com>; linux-aspeed@...ts.ozlabs.org; linux-
> gpio@...r.kernel.org; andrew@...id.au; linus.walleij@...aro.org;
> lgirdwood@...il.com; linux-kernel@...r.kernel.org;
> bgolaszewski@...libre.com; robh+dt@...nel.org; joel@....id.au;
> kernel@...gutronix.de; Adam Thomson
> <Adam.Thomson.Opensource@...semi.com>; lee.jones@...aro.org; linux-arm-
> kernel@...ts.infradead.org
> Subject: Re: [PATCH v3 3/6] dt-bindings: mfd: da9062: add regulator voltage
> selection documentation
>
> On 19-12-12 16:51, Mark Brown wrote:
> > On Thu, Dec 12, 2019 at 05:21:53PM +0100, Marco Felsch wrote:
> >
> > > "... what's driving the input ..":
> > > Sorry I didn't get you here. What did you mean? The input is driven by
> > > the host. This can be any gpio line and in my case it is a gpio line
> > > driven by the soc-hw during a suspend operation.
> >
> > Something needs to say what that thing is, especially if it's runtime
> > controllable. In your case from the point of view of software there is
> > actually no enable control so we shouldn't be providing an enable
> > operation to the framework.
>
> The enabel control signal is always available, please check [1] table
> 63. There is a mux in front of the enable pin so:
>
> +-------------
> Seq. |\ | Regulator
> GPI1 | \ |
> GPI2 | | -- > Enable
> GPI3 | / |
> |/ .
> .
> .
>
> Adam please correct me if this is wrong.
>
> [1] https://www.dialog-
> semiconductor.com/sites/default/files/da9062_datasheet_3v6.pdf
>
> Regards,
> Marco
>
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@...ts.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Powered by blists - more mailing lists