[PATCH v4 1/2] dt: cpufreq: st: Provide bindings for ST's CPUFreq implementation
From: viresh.kumar@linaro.org (Viresh Kumar)
Date: 2015-07-28 02:23:15
Also in:
linux-devicetree, linux-pm, lkml
On 27-07-15, 16:20, Lee Jones wrote:
quoted hunk ↗ jump to hunk
Cc: devicetree at vger.kernel.org Signed-off-by: Lee Jones <redacted> --- Changelog: - Using OPP-v2 - Moved (and linked) a bunch of documentation to ../power/ .../devicetree/bindings/cpufreq/cpufreq-st.txt | 40 ++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-st.txtdiff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt b/Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt new file mode 100644 index 0000000..79add9d --- /dev/null +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-st.txt@@ -0,0 +1,40 @@ +Binding for ST's CPUFreq driver +=============================== + +Frequency Scaling only +---------------------- + +Located in CPU's node: + +- operating-points : [See: ../power/opp.txt] + +Example [safe] +-------------- + +cpus { + cpu at 0 { + /* kHz uV */ + operating-points = <1500000 0 + 1200000 0 + 800000 0 + 500000 0>; + }; +}; + +Dynamic Voltage and Frequency Scaling (DVFS) +-------------------------------------------- + +Located in CPU's node: + +- operating-points-v2-sti : [See ../power/opp-st.txt] + +Example [unsafe] +---------------- + +cpus { + cpu at 0 { + operating-points-v2 = <[OPP list phandle]>; + }; +}; + +For an example of an OPP list, see ../power/opp-st.txt.
I don't think you need this file/patch at all.. It is almost blank and doesn't define a binding. And so there is no need to specify this at all. Just an OPP binding file is enough. -- viresh