Home
last modified time | relevance | path

Searched refs:OPP (Results 1 – 25 of 32) sorted by relevance

12

/kernel/linux/linux-5.10/Documentation/power/
Dopp.rst2 Operating Performance Points (OPP) Library
10 2. Initial OPP List Registration
11 3. OPP Search Functions
12 4. OPP Availability Control Functions
13 5. OPP Data Retrieval Functions
19 1.1 What is an Operating Performance Point (OPP)?
48 OPP library provides a set of helper functions to organize and query the OPP
50 is located in include/linux/pm_opp.h. OPP library can be enabled by enabling
51 CONFIG_PM_OPP from power management menuconfig menu. OPP library depends on
53 optionally boot at a certain OPP without needing cpufreq.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/opp/
Dopp.txt1 Generic OPP (Operating Performance Points) Bindings
10 This document contain multiple versions of OPP binding and only one of them
45 phandle to a OPP table in their DT node. The OPP core will use this phandle to
50 phandle is available, then the same OPP table will be used for all power domains
57 * OPP Table Node
66 - OPP nodes: One or more OPP nodes describing voltage-current-frequency
68 reference an OPP.
71 - opp-shared: Indicates that device nodes using this OPP Table Node's phandle
74 but they share OPP tables.
76 - status: Marks the OPP table enabled/disabled.
[all …]
Dti-omap5-opp-supply.txt1 Texas Instruments OMAP compatible OPP supply description
7 an OPP transitions.
11 to the vdd-supply and clk when making an OPP transition. By supplying two
12 regulators to the device that will undergo OPP transitions we can make use
13 of the multi regulator binding that is part of the OPP core described here [1]
25 "ti,omap-opp-supply" - basic OPP supply controlling VDD and VBB
34 volt: voltage in uV - reference voltage (OPP voltage)
36 - ti,absolute-max-voltage-uv: absolute maximum voltage for the OPP supply.
52 /* OMAP OPP Supply with Class0 registers */
Dqcom-opp.txt1 Qualcomm OPP bindings to describe OPP nodes
7 * OPP Table Node
13 * OPP Node
17 associated with this OPP node. Sometimes several corners/levels shares
Dqcom-nvmem-cpufreq.txt1 Qualcomm Technologies, Inc. NVMEM CPUFreq and OPP bindings
5 the CPU frequencies subset and voltage value of each OPP varies based on
11 to provide the OPP framework with required information (existing HW bitmap).
12 This is used to determine the voltage and frequency value for each OPP of
13 operating-points-v2 table when it is parsed by the OPP framework.
45 In every OPP node:
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Dpower_domain.txt54 - required-opps: This contains phandle to an OPP node in another device's OPP
56 OPP of a different device. It should not contain multiple phandles to the OPP
57 nodes in the same OPP table. This specifies the minimum required OPP of the
58 device(s), whose OPP's phandle is present in this property, for the
59 functioning of the current device at the current OPP (where this property is
63 - OPP table for domain provider that provides two domains.
/kernel/linux/linux-5.10/Documentation/driver-api/thermal/
Dcpu-idle-cooling.rst25 because of the OPP density, we can only choose an OPP with a power
27 losing performance. In other words, one OPP under-utilizes the CPU
28 with a power less than the requested power budget and the next OPP
29 exceeds the power budget. An intermediate OPP could have been used if
41 The Operating Performance Point (OPP) density has a great influence on
43 plethora of OPP density, and some have large power gap between OPPs,
47 At a specific OPP, we can assume that injecting idle cycle on all CPUs
52 relation with the OPP’s sustainable power and can be computed with a
55 Power(IdleCycle) = Coef x Power(OPP)
151 because we don’t want to change the OPP. We can group the
[all …]
/kernel/linux/linux-5.10/drivers/opp/
DKconfig8 is called Operating Performance Point or OPP. The actual definitions
9 of OPP varies over silicon within the same family of devices.
11 OPP layer organizes the data internally using device pointers
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/cpufreq/
Dti-cpufreq.txt1 TI CPUFreq and OPP bindings
7 provide the OPP framework with supported hardware information. This is
9 when it is parsed by the OPP framework.
30 1. Which revision of the SoC the OPP is supported by
31 2. Which eFuse bits indicate this OPP is available
34 matches, the OPP gets enabled.
Dimx-cpufreq-dt.txt1 i.MX CPUFreq-DT OPP bindings
6 the opp-supported-hw values for each OPP to check if the OPP is allowed.
Dnvidia,tegra20-cpufreq.txt21 matches, the OPP gets enabled.
Dcpufreq-st.txt5 from the SoC, then supplies the OPP framework with 'prop' and 'supported
/kernel/linux/linux-5.10/drivers/devfreq/
DKconfig26 When OPP is used with the devfreq device, it is recommended to
27 register devfreq's nb to the OPP's notifier head. If OPP is
28 used with the devfreq device, you may use OPP helper
75 devfreq device uses the OPP table to get the frequency/voltage.
91 and adjusts the operating frequencies and voltages with OPP support.
122 operating frequencies and voltages with OPP support.
132 frequencies and voltages with OPP support.
/kernel/linux/linux-5.10/Documentation/cpu-freq/
Dcore.rst17 3. CPUFreq Table Generation with Operating Performance Point (OPP)
83 3. CPUFreq Table Generation with Operating Performance Point (OPP)
85 For details about OPP, see Documentation/power/opp.rst
89 the OPP layer's internal information about the available frequencies
/kernel/linux/linux-5.10/Documentation/arm/omap/
Domap_pm.rst118 DSPBridge expresses target DSP performance levels in terms of OPP IDs.
137 Customizing OPP for platform
139 Defining CONFIG_PM should enable OPP layer for the silicon
140 and the registration of OPP table should take place automatically.
141 However, in special cases, the default OPP table may need to be
146 * Disable an unsupported OPP on the platform
/kernel/linux/linux-5.10/arch/arm/mach-davinci/
Dda850.c420 #define OPP(freq) \ macro
427 OPP(456),
428 OPP(408),
429 OPP(372),
430 OPP(300),
431 OPP(200),
432 OPP(96),
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gxl-s805x.dtsi13 /* The S805X Package doesn't seem to handle the 744MHz OPP correctly */
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/avs/
Dqcom,cpr.txt4 or other device. Each OPP of a device corresponds to a "corner" that has
48 Definition: A phandle to the OPP table containing the
/kernel/linux/linux-5.10/Documentation/scheduler/
Dsched-energy.rst161 The CPU capacity and power cost associated with each OPP is listed in
181 Current OPP: ===== Other OPP: - - - util_avg (100 each): ##
261 result in raising the OPP of the entire performance domain, and that will
265 which will keep running at a lower OPP. So, when considering the total energy
267 smaller than the cost of raising the OPP on the little CPUs for all the other
388 EAS tries to predict at which OPP will the CPUs be running in the close future
Dsched-capacity.rst25 physically able to attain the higher Operating Performance Points (OPP).
152 directly impacted by the current OPP the CPU is running at. Consider running a
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dam335x-osd335x-common.dtsi28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
Dam335x-boneblack.dts20 * to support 1GHz OPP so enable it for PG 2.0 on this board.
Dda850-lcdk.dts179 * can't enable more than one OPP by default, since the controller sometimes
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/msm/
Dgpu.txt24 - operating-points-v2: optional phandle to the OPP operating points
/kernel/linux/linux-5.10/arch/arm64/boot/dts/freescale/
Dimx8mq-phanbell.dts98 <&A53_0 0 1>; /* Exclude highest OPP */

12