Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1518681

Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple regulators per device

From Viresh Kumar <viresh.kumar@linaro.org>
Newsgroups linux.kernel
Subject Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple regulators per device
Date 2016-11-10 05:10 +0100
Message-ID <sBOQx-om-3@gated-at.bofh.it> (permalink)
References <swq2t-8jC-3@gated-at.bofh.it> <swq2u-8jC-33@gated-at.bofh.it> <sBCw2-el-23@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 09-11-16, 14:58, Mark Brown wrote:
> On Wed, Oct 26, 2016 at 12:02:56PM +0530, Viresh Kumar wrote:
> 
> > +  Entries for multiple regulators shall be provided in the same field separated
> > +  by angular brackets <>. The OPP binding doesn't provide any provisions to
> > +  relate the values to their power supplies or the order in which the supplies
> > +  need to be configured.
> 
> I don't understand how this works.  If we have an unordered list of
> values to set for regulators how will we make sense of them?

The platform driver is responsible to identify the order and pass it on to the
OPP core. And the platform driver needs to have that hard coded.

If we want to identify the entries for regulators just by parsing the DT then we
would need another field in the OPP table which I added earlier.

Something like this:

        cpu0_opp_table: opp_table0 {
                compatible = "operating-points-v2";
+               supply-names = "vcc0", "vcc1", "vcc2";
                opp-shared;
 
                opp00 {

Will that be acceptable ?

> > -			cpu-supply = <&cpu_supply0>, <&cpu_supply1>, <&cpu_supply2>;
> > +			vcc0-supply = <&cpu_supply0>;
> > +			vcc1-supply = <&cpu_supply1>;
> > +			vcc2-supply = <&cpu_supply2>;
> 
> This change doesn't seem to correspond to the documentation change.

This rectifies the incorrect binding previously added to the example, which I
realized to be incorrect only while attempting to code for it. And so it brings
the example on the same state as the documentation now.

-- 
viresh

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple  regulators per device Mark Brown <broonie@kernel.org> - 2016-11-09 16:00 +0100
  Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple  regulators per device Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-10 05:10 +0100
    Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple  regulators per device Mark Brown <broonie@kernel.org> - 2016-11-10 17:40 +0100
      Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple  regulators per device Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-10 19:10 +0100
        Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple  regulators per device Stephen Boyd <sboyd@codeaurora.org> - 2016-11-11 00:00 +0100
          Re: [PATCH V3 1/9] PM / OPP: Reword binding supporting multiple  regulators per device Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-11 04:20 +0100

csiph-web