[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171220211817.mpkkj747blr4qkqm@rob-hp-laptop>
Date: Wed, 20 Dec 2017 15:18:17 -0600
From: Rob Herring <robh@...nel.org>
To: Sricharan R <sricharan@...eaurora.org>
Cc: Viresh Kumar <viresh.kumar@...aro.org>, mark.rutland@....com,
mturquette@...libre.com, sboyd@...eaurora.org,
linux@...linux.org.uk, andy.gross@...aro.org,
david.brown@...aro.org, rjw@...ysocki.net,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v5 15/15] devicetree: bindings: Document qcom,pvs
On Wed, Dec 20, 2017 at 11:55:33AM +0530, Sricharan R wrote:
> Hi Viresh,
>
> On 12/20/2017 8:56 AM, Viresh Kumar wrote:
> > On 19-12-17, 21:25, Sricharan R wrote:
> >> + cpu@0 {
> >> + compatible = "qcom,krait";
> >> + enable-method = "qcom,kpss-acc-v1";
> >> + device_type = "cpu";
> >> + reg = <0>;
> >> + qcom,acc = <&acc0>;
> >> + qcom,saw = <&saw0>;
> >> + clocks = <&kraitcc 0>;
> >> + clock-names = "cpu";
> >> + cpu-supply = <&smb208_s2a>;
> >> + operating-points-v2 = <&cpu_opp_table>;
> >> + };
> >> +
> >> + qcom,pvs {
> >> + qcom,pvs-format-a;
> >> + };
> >
> > Not sure what Rob is going to say on that :)
> >
>
> Yes. Would be good to know the best way.
Seems like this should be a property of an efuse node either implied by
the compatible or a separate property. What determines format A vs. B?
Rob
Powered by blists - more mailing lists