summaryrefslogtreecommitdiff
path: root/kernel/debug
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2026-11-13 15:29:01 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2026-11-15 19:28:39 +0100
commit52aedfca88cdc3c5676f65ce8ab01f87eac9e132 (patch)
tree6198e853f6e7fe5f366bdf2fa2887e2720e1a72c /kernel/debug
parent7aca8e31a8fbf2ceffb487cec67ae300b95fa8b1 (diff)
ACPI: CPPC: Drop compliance checks involving nominal performance
On a number of Intel platforms in the field, the nominal performance value in ACPI _CPC (which is an integer embedded in the _CPC package) is less than the guaranteed performance value, and it may even be less than the minimum nonlinear performance value or greater than the highest performance value (that all come from register reads). The new specification compliance checks involving those values added by commit 32299b29a887 ("ACPI: CPPC: Validate _CPC entry and control semantics") cause the CPPC library to refuse to work for some CPUs on the affected systems which in turn causes the intel_pstate driver to overestimate the maximum performance levels for those CPUs. One of the affected systems is Dell Pro 5 14 P514260. In this particular case, the fact that the specification is not exactly followed has no implications and the checks enforcing compliance are not really useful, so drop the checks in question from the CPPC library. If really necessary, they will need to be done elsewhere. Fixes: 32299b29a887 ("ACPI: CPPC: Validate _CPC entry and control semantics") Reviewed-by: Christian Loehle <christian.loehle@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Link: https://patch.msgid.link/6060382.DvuYhMxLoT@rafael.j.wysocki
Diffstat (limited to 'kernel/debug')
0 files changed, 0 insertions, 0 deletions