diff options
| author | Gautham R. Shenoy <[email protected]> | 2025-01-13 04:41:07 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2025-01-14 20:10:07 +0000 |
| commit | 0834667545962ef1c5e8684ed32b45d9c574acd3 (patch) | |
| tree | c510d2b0b118a363e86396d6a0f374f457bebaed /tools/testing/selftests/net/lib/py/utils.py | |
| parent | Merge tag 'amd-pstate-v6.14-2025-01-07' of ssh://gitolite.kernel.org/pub/scm/... (diff) | |
| download | kernel-0834667545962ef1c5e8684ed32b45d9c574acd3.tar.gz kernel-0834667545962ef1c5e8684ed32b45d9c574acd3.zip | |
cpufreq: ACPI: Fix max-frequency computation
Commit 3c55e94c0ade ("cpufreq: ACPI: Extend frequency tables to cover
boost frequencies") introduced an assumption in acpi_cpufreq_cpu_init()
that the first entry in the P-state table was the nominal frequency.
This assumption is incorrect. The frequency corresponding to the P0
P-State need not be the same as the nominal frequency advertised via
CPPC.
Since the driver is using the CPPC.highest_perf and CPPC.nominal_perf
to compute the boost-ratio, it makes sense to use CPPC.nominal_freq to
compute the max-frequency. CPPC.nominal_freq is advertised on
platforms supporting CPPC revisions 3 or higher.
Hence, fallback to using the first entry in the P-State table only on
platforms that do not advertise CPPC.nominal_freq.
Fixes: 3c55e94c0ade ("cpufreq: ACPI: Extend frequency tables to cover boost frequencies")
Tested-by: Dhananjay Ugwekar <[email protected]>
Signed-off-by: Gautham R. Shenoy <[email protected]>
Reviewed-by: Mario Limonciello <[email protected]>
Link: https://patch.msgid.link/[email protected]
[ rjw: Retain reverse X-mas tree ordering of local variable declarations ]
[ rjw: Subject and changelog edits ]
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions