diff options
| author | Mario Limonciello <mario.limonciello@amd.com> | 2024-12-09 19:52:34 +0100 |
|---|---|---|
| committer | Mario Limonciello <mario.limonciello@amd.com> | 2024-12-10 17:17:43 +0100 |
| commit | 50a062a7620051c09adacd6d140ebd56881a333b (patch) | |
| tree | 6ca86e714dfb62b5f98e46ffc62a76120541dc6a /Documentation | |
| parent | cpufreq/amd-pstate: Detect preferred core support before driver registration (diff) | |
| download | linux-50a062a7620051c09adacd6d140ebd56881a333b.tar.xz linux-50a062a7620051c09adacd6d140ebd56881a333b.zip | |
cpufreq/amd-pstate: Store the boost numerator as highest perf again
commit ad4caad58d91d ("cpufreq: amd-pstate: Merge
amd_pstate_highest_perf_set() into amd_get_boost_ratio_numerator()")
changed the semantics for highest perf and commit 18d9b52271213
("cpufreq/amd-pstate: Use nominal perf for limits when boost is disabled")
worked around those semantic changes.
This however is a confusing result and furthermore makes it awkward to
change frequency limits and boost due to the scaling differences. Restore
the boost numerator to highest perf again.
Suggested-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Fixes: ad4caad58d91 ("cpufreq: amd-pstate: Merge amd_pstate_highest_perf_set() into amd_get_boost_ratio_numerator()")
Link: https://lore.kernel.org/r/20241209185248.16301-2-mario.limonciello@amd.com
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/admin-guide/pm/amd-pstate.rst | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst index 210a808b74ec..412423c54f25 100644 --- a/Documentation/admin-guide/pm/amd-pstate.rst +++ b/Documentation/admin-guide/pm/amd-pstate.rst @@ -251,9 +251,7 @@ performance supported in `AMD CPPC Performance Capability <perf_cap_>`_). In some ASICs, the highest CPPC performance is not the one in the ``_CPC`` table, so we need to expose it to sysfs. If boost is not active, but still supported, this maximum frequency will be larger than the one in -``cpuinfo``. On systems that support preferred core, the driver will have -different values for some cores than others and this will reflect the values -advertised by the platform at bootup. +``cpuinfo``. This attribute is read-only. ``amd_pstate_lowest_nonlinear_freq`` |