| /OK3568_Linux_fs/kernel/Documentation/power/ |
| H A D | opp.rst | 2 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 …]
|
| /OK3568_Linux_fs/u-boot/arch/arm/mach-omap2/omap5/ |
| H A D | Kconfig | 60 menu "Voltage Domain OPP selections" 66 Select the Operating Performance Point(OPP) for the MPU voltage 70 bool "OPP NOM" 72 This config option enables Normal OPP for MPU. This is the safest 80 Select the Operating Performance Point(OPP) for the DSPEVE voltage 84 bool "OPP NOM" 86 This config option enables Normal OPP for DSPEVE. This is the safest 90 bool "OPP OD" 92 This config option enables Over drive OPP for DSPEVE. 95 bool "OPP HIGH" [all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/power/ |
| H A D | mali-opp.txt | 22 * ARM Mali Midgard OPP 24 * OPP Table Node 33 - OPP nodes: One or more OPP nodes describing voltage-current-frequency 35 reference an OPP. 37 * OPP Node 53 then all shader cores will be used for this OPP. 55 - opp-core-count: Number of cores to use for this OPP. If this is present then 60 used for this OPP. 77 provided for the same OPP. At runtime, the platform can pick a <name> and 88 Should only be set if opp-microvolt is set for the OPP. [all …]
|
| H A D | power_domain.txt | 54 - 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.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/opp/ |
| H A D | opp.txt | 1 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 …]
|
| H A D | ti-omap5-opp-supply.txt | 1 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 */
|
| H A D | qcom-opp.txt | 1 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
|
| H A D | qcom-nvmem-cpufreq.txt | 1 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:
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/thermal/ |
| H A D | cpu-idle-cooling.rst | 25 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/cpufreq/ |
| H A D | ti-cpufreq.txt | 1 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.
|
| H A D | imx-cpufreq-dt.txt | 1 i.MX CPUFreq-DT OPP bindings 6 the opp-supported-hw values for each OPP to check if the OPP is allowed.
|
| H A D | cpufreq-rockchip.txt | 5 and get frequency count from pvtm, then supplies the OPP framework 7 property of OPPS when it is parsed by the OPP framework. This is based 21 opp-microvolt-L<number> roperty in OPP node. 29 opp-microvolt-L<number> roperty in OPP node.
|
| H A D | nvidia,tegra20-cpufreq.txt | 21 matches, the OPP gets enabled.
|
| H A D | cpufreq-st.txt | 5 from the SoC, then supplies the OPP framework with 'prop' and 'supported
|
| /OK3568_Linux_fs/kernel/drivers/devfreq/ |
| H A D | Kconfig | 26 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.
|
| /OK3568_Linux_fs/kernel/drivers/opp/ |
| H A D | Kconfig | 8 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
|
| /OK3568_Linux_fs/kernel/Documentation/arm/omap/ |
| H A D | omap_pm.rst | 118 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
|
| /OK3568_Linux_fs/kernel/Documentation/cpu-freq/ |
| H A D | core.rst | 17 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
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-davinci/ |
| H A D | da850.c | 420 #define OPP(freq) \ macro 427 OPP(456), 428 OPP(408), 429 OPP(372), 430 OPP(300), 431 OPP(200), 432 OPP(96),
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/power/avs/ |
| H A D | qcom,cpr.txt | 4 or other device. Each OPP of a device corresponds to a "corner" that has 48 Definition: A phandle to the OPP table containing the
|
| /OK3568_Linux_fs/kernel/arch/arm64/boot/dts/amlogic/ |
| H A D | meson-gxl-s805x.dtsi | 13 /* The S805X Package doesn't seem to handle the 744MHz OPP correctly */
|
| /OK3568_Linux_fs/kernel/Documentation/scheduler/ |
| H A D | sched-energy.rst | 161 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
|
| /OK3568_Linux_fs/kernel/arch/arm/boot/dts/ |
| H A D | am335x-osd335x-common.dtsi | 28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
|
| H A D | am335x-boneblack.dts | 20 * to support 1GHz OPP so enable it for PG 2.0 on this board.
|
| /OK3568_Linux_fs/kernel/drivers/soc/rockchip/ |
| H A D | Kconfig | 97 tristate "Rockchip OPP select support" 100 Say y here to enable rockchip OPP support.
|