[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKr6ag8JOPjkyjyxJ6mf37h4pukGM5ZGkqru1+bqF+B+Q@mail.gmail.com>
Date: Wed, 17 Oct 2018 08:31:59 -0500
From: Rob Herring <robh@...nel.org>
To: Dmitry Osipenko <digetx@...il.com>
Cc: Mark Brown <broonie@...nel.org>,
Maciej Purski <m.purski@...sung.com>,
Thierry Reding <thierry.reding@...il.com>,
Jon Hunter <jonathanh@...dia.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Lucas Stach <l.stach@...gutronix.de>,
devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-tegra@...r.kernel.org,
linux-omap <linux-omap@...r.kernel.org>
Subject: Re: [PATCH v1 05/11] dt-bindings: regulator: Change
regulator-coupled-max-spread property
On Wed, Oct 17, 2018 at 8:27 AM Rob Herring <robh@...nel.org> wrote:
>
> On Fri, 5 Oct 2018 18:36:32 +0300, Dmitry Osipenko wrote:
> > Redefine binding for regulator-coupled-max-spread property in a way that
> > max-spread values are defined per regulator couple instead of defining
> > single max-spread for the whole group of coupled regulators.
> >
> > With that change the following regulators coupling configuration will be
> > possible:
> >
> > regA: regulatorA {
> > regulator-coupled-with = <®B ®C>;
> > regulator-coupled-max-spread = <100000 300000>;
> > };
> >
> > regB: regulatorB {
> > regulator-coupled-with = <®A ®C>;
> > regulator-coupled-max-spread = <100000 200000>;
> > };
> >
> > regC: regulatorC {
> > regulator-coupled-with = <®A ®B>;
> > regulator-coupled-max-spread = <300000 200000>;
> > };
> >
> > Signed-off-by: Dmitry Osipenko <digetx@...il.com>
> > ---
> > Documentation/devicetree/bindings/regulator/regulator.txt | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
>
> Reviewed-by: Rob Herring <robh@...nel.org>
Sent this by mistake. Disregard as I have questions.
Rob
Powered by blists - more mailing lists