Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

dt-bindings: imx-cpufreq-dt: Document opp-supported-hw usage

The interpretation of opp-supported-hw bits for imx-cpufreq-dt driver is
not very obvious so attempt to explain it.

There is no OF compat string associated.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

authored by

Leonard Crestez and committed by
Viresh Kumar
a02177a3 4d28ba1d

+37
+37
Documentation/devicetree/bindings/cpufreq/imx-cpufreq-dt.txt
··· 1 + i.MX CPUFreq-DT OPP bindings 2 + ================================ 3 + 4 + Certain i.MX SoCs support different OPPs depending on the "market segment" and 5 + "speed grading" value which are written in fuses. These bits are combined with 6 + the opp-supported-hw values for each OPP to check if the OPP is allowed. 7 + 8 + Required properties: 9 + -------------------- 10 + 11 + For each opp entry in 'operating-points-v2' table: 12 + - opp-supported-hw: Two bitmaps indicating: 13 + - Supported speed grade mask 14 + - Supported market segment mask 15 + 0: Consumer 16 + 1: Extended Consumer 17 + 2: Industrial 18 + 3: Automotive 19 + 20 + Example: 21 + -------- 22 + 23 + opp_table { 24 + compatible = "operating-points-v2"; 25 + opp-1000000000 { 26 + opp-hz = /bits/ 64 <1000000000>; 27 + /* grade >= 0, consumer only */ 28 + opp-supported-hw = <0xf>, <0x3>; 29 + }; 30 + 31 + opp-1300000000 { 32 + opp-hz = /bits/ 64 <1300000000>; 33 + opp-microvolt = <1000000>; 34 + /* grade >= 1, all segments */ 35 + opp-supported-hw = <0xe>, <0x7>; 36 + }; 37 + }