diff options
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2018-10-18 12:26:11 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2018-10-18 12:26:11 +0200 |
| commit | d1551f7a5aed809bb1e912da9faf36927e739ca0 (patch) | |
| tree | 742c7c347173f501c401f74d731f513f9a5533dc /Documentation | |
| parent | Merge branch 'pm-cpuidle' (diff) | |
| parent | cpufreq: tegra186: don't pass GFP_DMA32 to dma_alloc_coherent() (diff) | |
| download | linux-d1551f7a5aed809bb1e912da9faf36927e739ca0.tar.xz linux-d1551f7a5aed809bb1e912da9faf36927e739ca0.zip | |
Merge branch 'pm-cpufreq'
* pm-cpufreq:
cpufreq: tegra186: don't pass GFP_DMA32 to dma_alloc_coherent()
cpufreq: conservative: Take limits changes into account properly
Documentation: intel_pstate: Add base_frequency information
cpufreq: intel_pstate: Add base_frequency attribute
ACPI / CPPC: Add support for guaranteed performance
cpufreq: imx6q: read OCOTP through nvmem for imx6ul/imx6ull
cpufreq: dt-platdev: allow RK3399 to have separate tunables per cluster
cpufreq / CPPC: Mark acpi_ids as used
cpufreq: dt: Add support for r8a7744
cpufreq: Convert to using %pOFn instead of device_node.name
cpufreq: remove unnecessary unlikely()
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/admin-guide/pm/intel_pstate.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/admin-guide/pm/intel_pstate.rst b/Documentation/admin-guide/pm/intel_pstate.rst index 8f1d3de449b5..ac6f5c597a56 100644 --- a/Documentation/admin-guide/pm/intel_pstate.rst +++ b/Documentation/admin-guide/pm/intel_pstate.rst @@ -465,6 +465,13 @@ Next, the following policy attributes have special meaning if policy for the time interval between the last two invocations of the driver's utilization update callback by the CPU scheduler for that CPU. +One more policy attribute is present if the `HWP feature is enabled in the +processor <Active Mode With HWP_>`_: + +``base_frequency`` + Shows the base frequency of the CPU. Any frequency above this will be + in the turbo frequency range. + The meaning of these attributes in the `passive mode <Passive Mode_>`_ is the same as for other scaling drivers. |