On Mon, Nov 05, 2018 at 05:17:45PM -0600, Rob Herring wrote: > On Mon, Oct 15, 2018 at 02:47:49PM +0200, Niklas Cassel wrote: > > Extend qcom-opp bindings with properties needed for Core Power Reduction > > (CPR). > > > > CPR is included in a great variety of Qualcomm SoC, e.g. msm8916 and > > msm8996, and was first introduced in msm8974. > > > > Signed-off-by: Niklas Cassel <niklas.cassel@xxxxxxxxxx> > > --- > > Hello Rob, Rajendra, > > > > Sorry for not replying sooner. > > Since Rob wanted the binding to be complete before merging, > > this is my proposal to extend the OPP binding with properties > > needed to support CPR (both for msm8916 and msm8996). > > I've discussed the proposal with Viresh, and this proposal > > seems better than what I previously suggested here: > > https://lore.kernel.org/lkml/20181005204424.GA29500@xxxxxxxxxxxx/ > > > > .../devicetree/bindings/opp/qcom-opp.txt | 19 +++++++++++++++++++ > > 1 file changed, 19 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/opp/qcom-opp.txt b/Documentation/devicetree/bindings/opp/qcom-opp.txt > > index db4d970c7ec7..3ab5dd84de86 100644 > > --- a/Documentation/devicetree/bindings/opp/qcom-opp.txt > > +++ b/Documentation/devicetree/bindings/opp/qcom-opp.txt > > @@ -23,3 +23,22 @@ Required properties: > > representing a corner/level that's communicated with a remote microprocessor > > (usually called the RPM) which then translates it into a certain voltage on > > a voltage rail. > > I've lost the context here. Please send this all together. Will do, as soon as I've gotten your feedback on this mail. > > > + > > +Optional properties: > > +- opp-hz: Frequency in Hz, expressed as a 64-bit big-endian integer. Even > > + though a power domain doesn't need a opp-hz, there can be devices in the > > + power domain that need to know the highest supported frequency for each > > + corner/level (e.g. CPR), in order to properly initialize the hardware. > > + > > +- qcom,fuse-level: A positive value representing the fuse corner/level > > + associated with this OPP node. Sometimes several corners/levels shares > > + a certain fuse corner/level. A fuse corner/level contains e.g. ref uV, > > + min uV, and max uV. > > + > > +- qcom,fuse-level-<name>: Named qcom,fuse-level property. This is exactly > > + similar to the above qcom,fuse-level property, but allows multiple > > + fuse corners/levels to be provided for the same OPP. At runtime, the > > + platform can pick a <name> and matching qcom,fuse-level-<name> property > > + will be enabled for all OPPs. If the platform doesn't pick a specific > > + <name> or the <name> doesn't match with any qcom,fuse-level-<name> > > + properties, then qcom,fuse-level property shall be used, if present. > > We've generally moved away from having variable property names (gpio and > regulators are the big exceptions) as they are harder to parse. > > I'm not clear why you'd need this. Just make qcom,fuse-level an array > and search each 'qcom,fuse-level' for the matching level number. This was my first thought as well, but then Viresh told me that the OPP framework already has logic for parsing and using this. If we call dev_pm_opp_set_prop_name(<name>) We will automatically use all the named-properties with that suffix (e.g.): opp-microvolt-<name> opp-microamp-<name> opp-fuse-corner-<name> if and only if they exist, otherwise the regular properties will be used: opp-microvolt opp-microamp opp-fuse-corner This also means that not all OPPs will need the named variants, e.g. if all the speedbins have the same fuse-corner: opp-fuse-corner-speedbin0 = <1>; opp-fuse-corner-speedbin1 = <1>; opp-fuse-corner-speedbin2 = <1>; this can simplified to: opp-fuse-corner = <1>; Another reason why I think that using named-properties might be good is because I recently found out that certain Qualcomm SoCs have several fuse revisions for each speedbin, e.g. msm8996 SG has 8 fuse revisions per speedbin: https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/arch/arm/boot/dts/qcom/msm8996pro.dtsi?h=msm-3.18#n62 https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/drivers/regulator/cpr3-hmss-regulator.c?h=msm-3.18#n88 Which means that some SoCs (in worst case) will actually need: opp-fuse-corner-speedbin0-rev0 = <x>; opp-fuse-corner-speedbin0-rev1 = <x>; opp-fuse-corner-speedbin0-rev2 = <x>; opp-fuse-corner-speedbin0-rev3 = <x>; opp-fuse-corner-speedbin0-rev4 = <x>; opp-fuse-corner-speedbin0-rev5 = <x>; opp-fuse-corner-speedbin0-rev6 = <x>; opp-fuse-corner-speedbin0-rev7 = <x>; opp-fuse-corner-speedbin1-rev0 = <x>; opp-fuse-corner-speedbin1-rev1 = <x>; opp-fuse-corner-speedbin1-rev2 = <x>; opp-fuse-corner-speedbin1-rev3 = <x>; opp-fuse-corner-speedbin1-rev4 = <x>; opp-fuse-corner-speedbin1-rev5 = <x>; opp-fuse-corner-speedbin1-rev6 = <x>; opp-fuse-corner-speedbin1-rev7 = <x>; opp-fuse-corner-speedbin2-rev0 = <x>; opp-fuse-corner-speedbin2-rev1 = <x>; opp-fuse-corner-speedbin2-rev2 = <x>; opp-fuse-corner-speedbin2-rev3 = <x>; opp-fuse-corner-speedbin2-rev4 = <x>; opp-fuse-corner-speedbin2-rev5 = <x>; opp-fuse-corner-speedbin2-rev6 = <x>; opp-fuse-corner-speedbin2-rev7 = <x>; For each OPP. Fortunately, it's not always this messy, some SoCs only have a single fuse revision. I think that having named-properties probably helps if more speedbins or fuse-revisions are added. I guess the alternative would be to do like downstream, where they have a bunch of arrays instead, but then we wouldn't be able to use the logic from the OPP framework. qcom,cpr-corner-fmax-map = /* Speed bin 0 */ <1 6 9 14 19>, //fuse rev0 <1 6 9 14 19>, //fuse rev1 <3 6 9 14 19>, //fuse rev2 <3 6 9 14 19>, //fuse rev3 <3 6 9 14 19>, //fuse rev4 <3 6 9 14 19>, //fuse rev5 <3 6 9 14 19>, //fuse rev6 <3 6 9 14 19>, //fuse rev7 /* Speed bin 1 */ <1 6 9 14 19>, //fuse rev0 <1 6 9 14 19>, //fuse rev1 <3 6 9 14 19>, //fuse rev2 <3 6 9 14 19>, //fuse rev3 <3 6 9 14 19>, //fuse rev4 <3 6 9 14 19>, //fuse rev5 <3 6 9 14 19>, //fuse rev6 <3 6 9 14 19>, //fuse rev7 /* Speed bin 2 */ <1 6 9 14 19>, //fuse rev0 <1 6 9 14 19>, //fuse rev1 <3 6 9 14 19>, //fuse rev2 <3 6 9 14 19>, //fuse rev3 <3 6 9 14 19>, //fuse rev4 <3 6 9 14 19>, //fuse rev5 <3 6 9 14 19>, //fuse rev6 <3 6 9 14 19>; //fuse rev7 Kind regards, Niklas
