Lines Matching +full:device +full:- +full:version
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#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
17 uses CPU as a device.
19 This describes the OPPs belonging to a device.
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
29 Indicates that device nodes using this OPP Table Node's phandle switch
36 '^opp(-?[0-9]+)*$':
39 One or more OPP nodes describing voltage-current-frequency combinations.
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
49 required property for all device nodes, unless another "required"
61 opp-microvolt:
83 opp-microamp:
85 The maximum current drawn by the device in microamperes considering
90 Should only be set if opp-microvolt or opp-microvolt-<name> is set for
104 opp-microwatt:
106 The power for the OPP in micro-Watts.
119 opp-level:
121 A value representing the performance level of the device.
124 opp-peak-kBps:
127 32-bit big-endian integers. Each element of the array represents the
133 opp-avg-kBps:
136 of 32-bit big-endian integers. Each element of the array represents the
139 meaningful in OPP tables where opp-peak-kBps is present.
143 clock-latency-ns:
148 turbo-mode:
151 on some platforms, where the device can run over its operating
152 frequency for a short duration of time limited by the device's power,
156 opp-suspend:
158 Marks the OPP to be used during device suspend. If multiple OPPs in
159 the table have this, the OPP with highest opp-hz will be used.
162 opp-supported-hw:
166 version of the hardware (already known to the operating system).
169 a sub-group of hardware versions supported by the OPP. i.e. <sub-group
170 A>, <sub-group B>, etc. The OPP will be enabled if _any_ of these
171 sub-groups match the hardware's version.
173 Each sub-group is a platform defined array representing the hierarchy
175 three hierarchical levels of version (X.Y.Z), this field shall look
178 opp-supported-hw = <X1 Y1 Z1>, <X2 Y2 Z2>, <X3 Y3 Z3>.
180 Each level (eg. X1) in version hierarchy is represented by a 32 bit
181 value, one bit per version and so there can be maximum 32 versions per
183 hardware's level version and a non-zero output for _all_ the levels in
184 a sub-group means the OPP is supported by hardware. A value of
185 0xFFFFFFFF for each level in the sub-group will enable the OPP for all
187 $ref: /schemas/types.yaml#/definitions/uint32-matrix
193 required-opps:
195 This contains phandle to an OPP node in another device's OPP table. It
197 of a different device. It should not contain multiple phandles to the
199 OPP of the device(s), whose OPP's phandle is present in this property,
200 for the functioning of the current device at the current OPP (where
202 $ref: /schemas/types.yaml#/definitions/phandle-array
207 '^opp-microvolt-':
209 Named opp-microvolt property. This is exactly similar to the above
210 opp-microvolt property, but allows multiple voltage ranges to be
212 and matching opp-microvolt-<name> property will be enabled for all
214 doesn't match with any opp-microvolt-<name> properties, then
215 opp-microvolt property shall be used, if present.
216 $ref: /schemas/types.yaml#/definitions/uint32-matrix
223 '^opp-microamp-':
225 Named opp-microamp property. Similar to opp-microvolt-<name> property,
227 $ref: /schemas/types.yaml#/definitions/uint32-array
231 '^opp-microwatt-':
233 Named opp-microwatt property. Similar to opp-microamp-<name> property,
235 $ref: /schemas/types.yaml#/definitions/uint32-array
240 opp-avg-kBps: [ opp-peak-kBps ]
243 - compatible