Message ID | 1589453659-27581-3-git-send-email-smasetty@codeaurora.org (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | Add support for GPU DDR BW scaling | expand |
On Thu, May 14, 2020 at 04:24:15PM +0530, Sharat Masetty wrote: > Subject: arm64: dts: qcom: sc7180: Add opp-peak-kBps to GPU opp nit: s/opp/OPPs/ > > Add opp-peak-kBps bindings to the GPU opp table, listing the peak > GPU -> DDR bandwidth requirement for each opp level. This will be > used to scale the DDR bandwidth along with the GPU frequency dynamically. > > Signed-off-by: Sharat Masetty <smasetty@codeaurora.org> > --- > arch/arm64/boot/dts/qcom/sc7180.dtsi | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi > index 0ce9921..89f7767 100644 > --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi > +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi > @@ -1392,36 +1392,43 @@ > opp-800000000 { > opp-hz = /bits/ 64 <800000000>; > opp-level = <RPMH_REGULATOR_LEVEL_TURBO>; > + opp-peak-kBps = <8532000>; > }; > > opp-650000000 { > opp-hz = /bits/ 64 <650000000>; > opp-level = <RPMH_REGULATOR_LEVEL_NOM_L1>; > + opp-peak-kBps = <7216000>; > }; > > opp-565000000 { > opp-hz = /bits/ 64 <565000000>; > opp-level = <RPMH_REGULATOR_LEVEL_NOM>; > + opp-peak-kBps = <5412000>; > }; > > opp-430000000 { > opp-hz = /bits/ 64 <430000000>; > opp-level = <RPMH_REGULATOR_LEVEL_SVS_L1>; > + opp-peak-kBps = <5412000>; I suppose it's intentional that the bandwidth is the same as for opp-565000000, just want to mention it for if it's a C&P error. > }; > > opp-355000000 { > opp-hz = /bits/ 64 <355000000>; > opp-level = <RPMH_REGULATOR_LEVEL_SVS>; > + opp-peak-kBps = <3072000>; > }; > > opp-267000000 { > opp-hz = /bits/ 64 <267000000>; > opp-level = <RPMH_REGULATOR_LEVEL_LOW_SVS>; > + opp-peak-kBps = <3072000>; > }; ditto > opp-180000000 { > opp-hz = /bits/ 64 <180000000>; > opp-level = <RPMH_REGULATOR_LEVEL_MIN_SVS>; > + opp-peak-kBps = <1804000>; > }; > }; > }; assuming the repeated bandwidths are indeed intentional: Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi index 0ce9921..89f7767 100644 --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi @@ -1392,36 +1392,43 @@ opp-800000000 { opp-hz = /bits/ 64 <800000000>; opp-level = <RPMH_REGULATOR_LEVEL_TURBO>; + opp-peak-kBps = <8532000>; }; opp-650000000 { opp-hz = /bits/ 64 <650000000>; opp-level = <RPMH_REGULATOR_LEVEL_NOM_L1>; + opp-peak-kBps = <7216000>; }; opp-565000000 { opp-hz = /bits/ 64 <565000000>; opp-level = <RPMH_REGULATOR_LEVEL_NOM>; + opp-peak-kBps = <5412000>; }; opp-430000000 { opp-hz = /bits/ 64 <430000000>; opp-level = <RPMH_REGULATOR_LEVEL_SVS_L1>; + opp-peak-kBps = <5412000>; }; opp-355000000 { opp-hz = /bits/ 64 <355000000>; opp-level = <RPMH_REGULATOR_LEVEL_SVS>; + opp-peak-kBps = <3072000>; }; opp-267000000 { opp-hz = /bits/ 64 <267000000>; opp-level = <RPMH_REGULATOR_LEVEL_LOW_SVS>; + opp-peak-kBps = <3072000>; }; opp-180000000 { opp-hz = /bits/ 64 <180000000>; opp-level = <RPMH_REGULATOR_LEVEL_MIN_SVS>; + opp-peak-kBps = <1804000>; }; }; };
Add opp-peak-kBps bindings to the GPU opp table, listing the peak GPU -> DDR bandwidth requirement for each opp level. This will be used to scale the DDR bandwidth along with the GPU frequency dynamically. Signed-off-by: Sharat Masetty <smasetty@codeaurora.org> --- arch/arm64/boot/dts/qcom/sc7180.dtsi | 7 +++++++ 1 file changed, 7 insertions(+) -- 2.7.4