| Message ID | 20181221085622.25573-2-rnayak@codeaurora.org (mailing list archive) |
|---|---|
| State | Superseded, archived |
| Headers | show |
| Series | Add power domain driver for corners on msm8996/sdm845 | expand |
On Fri, Dec 21, 2018 at 2:56 AM Rajendra Nayak <rnayak@codeaurora.org> wrote: > > On Qualcomm Technologies, Inc. platforms, an OPP node needs > to describe an additional level/corner value that is then communicated > to a remote microprocessor by the CPU, which then takes some > actions (like adjusting voltage values across various rails) > based on the value passed. > > Describe these bindings in the qcom-opp bindings document. > > Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org> > Reviewed-by: Stephen Boyd <swboyd@chromium.org> > Reviewed-by: Rob Herring <robh@kernel.org> And rescinded... [...] > +Required properties: > +- qcom,level: On Qualcomm platforms an OPP node can describe a positive value > +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. Now we have Mediatek adding mtk,level...[1] Create something common. Just 'opp-level' perhaps. Rob [1] https://lore.kernel.org/patchwork/patch/1028536/
On 1/4/2019 12:13 AM, Rob Herring wrote: > On Fri, Dec 21, 2018 at 2:56 AM Rajendra Nayak <rnayak@codeaurora.org> wrote: >> >> On Qualcomm Technologies, Inc. platforms, an OPP node needs >> to describe an additional level/corner value that is then communicated >> to a remote microprocessor by the CPU, which then takes some >> actions (like adjusting voltage values across various rails) >> based on the value passed. >> >> Describe these bindings in the qcom-opp bindings document. >> >> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org> >> Acked-by: Viresh Kumar <viresh.kumar@linaro.org> >> Reviewed-by: Stephen Boyd <swboyd@chromium.org> >> Reviewed-by: Rob Herring <robh@kernel.org> > > And rescinded... > > [...] > >> +Required properties: >> +- qcom,level: On Qualcomm platforms an OPP node can describe a positive value >> +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. > > Now we have Mediatek adding mtk,level...[1] > > Create something common. Just 'opp-level' perhaps. Sure Rob, I will resubmit with something more generic so it can be used across SoC vendors.
diff --git a/Documentation/devicetree/bindings/opp/qcom-opp.txt b/Documentation/devicetree/bindings/opp/qcom-opp.txt new file mode 100644 index 000000000000..b3850a5ed59a --- /dev/null +++ b/Documentation/devicetree/bindings/opp/qcom-opp.txt @@ -0,0 +1,28 @@ +Qualcomm OPP bindings to descibe OPP nodes with corner/level values + +OPP tables for devices on Qualcomm platforms require an additional +platform specific corner/level value to be specified. +This value is passed on to the RPM (Resource Power Manager) by +the CPU, which then takes the necessary actions to set a voltage +rail to an appropriate voltage based on the value passed. + +The bindings are based on top of the operating-points-v2 bindings +described in Documentation/devicetree/bindings/opp/opp.txt, +with the exception that all of the properties are now optional, +including the opp-hz property. + +Additional properties are described below. + +* OPP Table Node + +Required properties: +- compatible: Allow OPPs to express their compatibility. It should be: + "operating-points-v2-qcom-level" + +* OPP Node + +Required properties: +- qcom,level: On Qualcomm platforms an OPP node can describe a positive value +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.