Lines Matching +full:opp +full:- +full:specific
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 Properties
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
54 array of frequencies. The OPP binding doesn't provide any provisions
57 specific binding.
63 opp-microvolt:
65 Voltage for the OPP
72 by angular brackets <>. The OPP binding doesn't provide any provisions to
74 need to be configured and that is left for the implementation specific
85 opp-microamp:
88 system specific parameters (such as transients, process, aging,
92 Should only be set if opp-microvolt or opp-microvolt-<name> is set for
93 the OPP.
99 required. The OPP binding doesn't provide any provisions to relate the
101 to be configured and that is left for the implementation specific
106 opp-microwatt:
108 The power for the OPP in micro-Watts.
114 required. The OPP binding doesn't provide any provisions to relate the
116 to be configured and that is left for the implementation specific
121 opp-level:
126 opp-peak-kBps:
129 32-bit big-endian integers. Each element of the array represents the
135 opp-avg-kBps:
138 of 32-bit big-endian integers. Each element of the array represents the
141 meaningful in OPP tables where opp-peak-kBps is present.
145 clock-latency-ns:
148 switching to this OPP from any other OPP.
150 turbo-mode:
152 Marks the OPP to be used only for turbo modes. Turbo mode is available
158 opp-suspend:
160 Marks the OPP to be used during device suspend. If multiple OPPs in
161 the table have this, the OPP with highest opp-hz will be used.
164 opp-supported-hw:
167 from the larger set present in the OPP table, based on the current
171 a sub-group of hardware versions supported by the OPP. i.e. <sub-group
172 A>, <sub-group B>, etc. The OPP will be enabled if _any_ of these
173 sub-groups match the hardware's version.
175 Each sub-group is a platform defined array representing the hierarchy
180 opp-supported-hw = <X1 Y1 Z1>, <X2 Y2 Z2>, <X3 Y3 Z3>.
185 hardware's level version and a non-zero output for _all_ the levels in
186 a sub-group means the OPP is supported by hardware. A value of
187 0xFFFFFFFF for each level in the sub-group will enable the OPP for all
189 $ref: /schemas/types.yaml#/definitions/uint32-matrix
195 required-opps:
197 This contains phandle to an OPP node in another device's OPP table. It
198 may contain an array of phandles, where each phandle points to an OPP
200 OPP nodes in the same OPP table. This specifies the minimum required
201 OPP of the device(s), whose OPP's phandle is present in this property,
202 for the functioning of the current device at the current OPP (where
204 $ref: /schemas/types.yaml#/definitions/phandle-array
209 '^opp-microvolt-':
211 Named opp-microvolt property. This is exactly similar to the above
212 opp-microvolt property, but allows multiple voltage ranges to be
213 provided for the same OPP. At runtime, the platform can pick a <name>
214 and matching opp-microvolt-<name> property will be enabled for all
215 OPPs. If the platform doesn't pick a specific <name> or the <name>
216 doesn't match with any opp-microvolt-<name> properties, then
217 opp-microvolt property shall be used, if present.
218 $ref: /schemas/types.yaml#/definitions/uint32-matrix
225 '^opp-microamp-':
227 Named opp-microamp property. Similar to opp-microvolt-<name> property,
229 $ref: /schemas/types.yaml#/definitions/uint32-array
233 '^opp-microwatt-':
235 Named opp-microwatt property. Similar to opp-microamp-<name> property,
237 $ref: /schemas/types.yaml#/definitions/uint32-array
242 opp-avg-kBps: [ opp-peak-kBps ]
245 - compatible