Lines Matching +full:opp +full:- +full:v2 +full:- +full:base
1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic OPP (Operating Performance Points) Common Binding
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
29 Indicates that device nodes using this OPP Table Node's phandle switch
32 lines, but they share OPP tables.
36 '^opp-?[0-9]+$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
41 OPP. These are mandatory except for the case where the OPP table is
42 present only to indicate dependency between devices using the opp-shared
46 opp-hz:
48 Frequency in Hz, expressed as a 64-bit big-endian integer. This is a
50 property to uniquely identify the OPP nodes exists. Devices like power
53 opp-microvolt:
55 Voltage for the OPP
62 by angular brackets <>. The OPP binding doesn't provide any provisions to
75 opp-microamp:
82 Should only be set if opp-microvolt or opp-microvolt-<name> is set for
83 the OPP.
89 required. The OPP binding doesn't provide any provisions to relate the
96 opp-level:
101 opp-peak-kBps:
104 32-bit big-endian integers. Each element of the array represents the
110 opp-avg-kBps:
113 of 32-bit big-endian integers. Each element of the array represents the
116 meaningful in OPP tables where opp-peak-kBps is present.
120 clock-latency-ns:
123 switching to this OPP from any other OPP.
125 turbo-mode:
127 Marks the OPP to be used only for turbo modes. Turbo mode is available
133 opp-suspend:
135 Marks the OPP to be used during device suspend. If multiple OPPs in
136 the table have this, the OPP with highest opp-hz will be used.
139 opp-supported-hw:
142 from the larger set present in the OPP table, based on the current
146 a sub-group of hardware versions supported by the OPP. i.e. <sub-group
147 A>, <sub-group B>, etc. The OPP will be enabled if _any_ of these
148 sub-groups match the hardware's version.
150 Each sub-group is a platform defined array representing the hierarchy
155 opp-supported-hw = <X1 Y1 Z1>, <X2 Y2 Z2>, <X3 Y3 Z3>.
160 hardware's level version and a non-zero output for _all_ the levels in
161 a sub-group means the OPP is supported by hardware. A value of
162 0xFFFFFFFF for each level in the sub-group will enable the OPP for all
164 $ref: /schemas/types.yaml#/definitions/uint32-matrix
170 required-opps:
172 This contains phandle to an OPP node in another device's OPP table. It
173 may contain an array of phandles, where each phandle points to an OPP
175 OPP nodes in the same OPP table. This specifies the minimum required
176 OPP of the device(s), whose OPP's phandle is present in this property,
177 for the functioning of the current device at the current OPP (where
179 $ref: /schemas/types.yaml#/definitions/phandle-array
182 '^opp-microvolt-':
184 Named opp-microvolt property. This is exactly similar to the above
185 opp-microvolt property, but allows multiple voltage ranges to be
186 provided for the same OPP. At runtime, the platform can pick a <name>
187 and matching opp-microvolt-<name> property will be enabled for all
189 doesn't match with any opp-microvolt-<name> properties, then
190 opp-microvolt property shall be used, if present.
191 $ref: /schemas/types.yaml#/definitions/uint32-matrix
198 '^opp-microamp-':
200 Named opp-microamp property. Similar to opp-microvolt-<name> property,
202 $ref: /schemas/types.yaml#/definitions/uint32-array
207 opp-avg-kBps: [ opp-peak-kBps ]
210 - compatible