summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/cpufreq-dt.h
diff options
context:
space:
mode:
authorWyes Karny <wyes.karny@amd.com>2023-03-07 14:27:38 +0300
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2023-03-17 21:06:23 +0300
commit2dd6d0ebf74049256160a3d03dabbd92fe0b8599 (patch)
treeb4e11ac524326526e89b7f57cc0816611839a817 /drivers/cpufreq/cpufreq-dt.h
parent3e6e078057640751654bda9fd2278a944f61fa4a (diff)
downloadlinux-2dd6d0ebf74049256160a3d03dabbd92fe0b8599.tar.xz
cpufreq: amd-pstate: Add guided autonomous mode
From ACPI spec below 3 modes for CPPC can be defined: 1. Non autonomous: OS scaling governor specifies operating frequency/ performance level through `Desired Performance` register and platform follows that. 2. Guided autonomous: OS scaling governor specifies min and max frequencies/ performance levels through `Minimum Performance` and `Maximum Performance` register, and platform can autonomously select an operating frequency in this range. 3. Fully autonomous: OS only hints (via EPP) to platform for the required energy performance preference for the workload and platform autonomously scales the frequency. Currently (1) is supported by amd_pstate as passive mode, and (3) is implemented by EPP support. This change is to support (2). In guided autonomous mode the min_perf is based on the input from the scaling governor. For example, in case of schedutil this value depends on the current utilization. And max_perf is set to max capacity. To activate guided auto mode ``amd_pstate=guided`` command line parameter has to be passed in the kernel. Acked-by: Huang Rui <ray.huang@amd.com> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com> Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name> Signed-off-by: Wyes Karny <wyes.karny@amd.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/cpufreq-dt.h')
0 files changed, 0 insertions, 0 deletions