6f18ce8026
Add snapshot of device tree bindings from keystone common kernel, branch
"android-mainline-keystone-qcom-release" at c4c12103f9c0 ("Snap for 9228065
from e32903b9a63bb558df8b803b076619c53c16baad to
android-mainline-keystone-qcom-release").
Change-Id: I7682079615cbd9f29340a5c1f2a1d84ec441a1f1
Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
38 lines
927 B
Plaintext
38 lines
927 B
Plaintext
i.MX CPUFreq-DT OPP bindings
|
|
================================
|
|
|
|
Certain i.MX SoCs support different OPPs depending on the "market segment" and
|
|
"speed grading" value which are written in fuses. These bits are combined with
|
|
the opp-supported-hw values for each OPP to check if the OPP is allowed.
|
|
|
|
Required properties:
|
|
--------------------
|
|
|
|
For each opp entry in 'operating-points-v2' table:
|
|
- opp-supported-hw: Two bitmaps indicating:
|
|
- Supported speed grade mask
|
|
- Supported market segment mask
|
|
0: Consumer
|
|
1: Extended Consumer
|
|
2: Industrial
|
|
3: Automotive
|
|
|
|
Example:
|
|
--------
|
|
|
|
opp_table {
|
|
compatible = "operating-points-v2";
|
|
opp-1000000000 {
|
|
opp-hz = /bits/ 64 <1000000000>;
|
|
/* grade >= 0, consumer only */
|
|
opp-supported-hw = <0xf>, <0x3>;
|
|
};
|
|
|
|
opp-1300000000 {
|
|
opp-hz = /bits/ 64 <1300000000>;
|
|
opp-microvolt = <1000000>;
|
|
/* grade >= 1, all segments */
|
|
opp-supported-hw = <0xe>, <0x7>;
|
|
};
|
|
}
|