| /linux/Documentation/power/ |
| A D | opp.rst | 11 3. OPP Search Functions 48 OPP library provides a set of helper functions to organize and query the OPP 67 Note on OPP Availability 103 The OPP is defined using the frequency and voltage. Once added, the OPP 128 3. OPP Search Functions 131 frequency back to the corresponding OPP, OPP library provides handy functions 132 to search the OPP list that OPP library internally manages. These search 138 OPP. Otherwise the memory for the OPP will never get freed and result in 205 availability of a OPP within the OPP list. This allows SoC frameworks to have 250 information from the OPP structure is necessary. Once an OPP pointer is [all …]
|
| /linux/Documentation/devicetree/bindings/opp/ |
| A D | opp-v2-base.yaml | 7 title: Generic OPP (Operating Performance Points) Common Binding 29 Indicates that device nodes using this OPP Table Node's phandle switch 32 lines, but they share OPP tables. 41 OPP. These are mandatory except for the case where the OPP table is 55 Voltage for the OPP 83 the OPP. 116 meaningful in OPP tables where opp-peak-kBps is present. 123 switching to this OPP from any other OPP. 172 This contains phandle to an OPP node in another device's OPP table. It 175 OPP nodes in the same OPP table. This specifies the minimum required [all …]
|
| 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 */
|
| 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
|
| A D | allwinner,sun50i-h6-operating-points.yaml | 7 title: Allwinner H6 CPU OPP Device Tree Bindings 15 OPP varies based on the silicon variant in use. Allwinner Process 19 provide the OPP framework with required information.
|
| A D | opp-v1.yaml | 7 title: Generic OPP (Operating Performance Points) v1 Bindings 29 - description: Voltage for OPP in uV
|
| 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:
|
| /linux/Documentation/devicetree/bindings/power/ |
| 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.
|
| A D | qcom,rpmpd.yaml | 58 // Example 1 (rpmh power domain controller and OPP table): 114 // Example 2 (rpm power domain controller and OPP table): 152 // Example 3 (Client/Consumer device using OPP table):
|
| A D | power-domain.yaml | 46 Phandles to the OPP tables of power domains provided by a power domain 48 the power domains provided by the provider have identical OPP tables,
|
| /linux/Documentation/driver-api/thermal/ |
| 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 …]
|
| /linux/Documentation/translations/zh_CN/cpu-freq/ |
| A D | core.rst | 26 3. 含有Operating Performance Point (OPP)的CPUFreq表的生成 79 3. 含有Operating Performance Point (OPP)的CPUFreq表的生成 81 关于OPP的细节请参阅 Documentation/power/opp.rst 84 这个功能提供了一个随时可用的转换程序,用来将OPP层关于可用频率的内部信息翻译成一种容易提供给
|
| /linux/Documentation/translations/zh_TW/cpu-freq/ |
| A D | core.rst | 26 3. 含有Operating Performance Point (OPP)的CPUFreq表的生成 79 3. 含有Operating Performance Point (OPP)的CPUFreq表的生成 81 關於OPP的細節請參閱 Documentation/power/opp.rst 84 這個功能提供了一個隨時可用的轉換程序,用來將OPP層關於可用頻率的內部信息翻譯成一種容易提供給
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| 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.
|
| 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.
|
| A D | nvidia,tegra20-cpufreq.txt | 21 matches, the OPP gets enabled.
|
| /linux/drivers/opp/ |
| 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
|
| /linux/drivers/devfreq/ |
| 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. 121 operating frequencies and voltages with OPP support.
|
| /linux/Documentation/arm/omap/ |
| 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
|
| /linux/Documentation/cpu-freq/ |
| 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
|
| /linux/arch/arm/mach-davinci/ |
| 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),
|
| /linux/Documentation/translations/zh_CN/core-api/ |
| A D | assoc_array.rst | 180 ``index_key`` 参数应持有索引键信息,并在调用OPP表中的方法时传递给它们。 197 ``index_key`` 参数应持有索引键信息,并在调用OPP表中的方法时传递给它们。
|
| /linux/Documentation/devicetree/bindings/power/avs/ |
| 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
|
| /linux/arch/arm64/boot/dts/amlogic/ |
| A D | meson-gxl-s805x.dtsi | 13 /* The S805X Package doesn't seem to handle the 744MHz OPP correctly */
|
| /linux/Documentation/scheduler/ |
| 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 393 EAS tries to predict at which OPP will the CPUs be running in the close future
|