cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode

[ Upstream commit 1cefe495cacba5fb0417da3a75a1a76e3546d176 ]

In the passive mode, intel_cpufreq_update_pstate() sets HWP_MIN_PERF in
accordance with the target frequency to ensure delivering adequate
performance, but it sets HWP_DESIRED_PERF to 0, so the processor has no
indication that the desired performance level is actually equal to the
floor one.  This may cause it to choose a performance point way above
the desired level.

Moreover, this is inconsistent with intel_cpufreq_adjust_perf() which
actually sets HWP_DESIRED_PERF in accordance with the target performance
value.

Address this by adjusting intel_cpufreq_update_pstate() to pass
target_pstate as both the minimum and the desired performance levels
to intel_cpufreq_hwp_update().

Fixes: a365ab6b9dfb ("cpufreq: intel_pstate: Implement the ->adjust_perf() callback")
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Shashank Balaji <shashank.mahadasyam@sony.com>
Link: https://patch.msgid.link/6173276.lOV4Wx5bFT@rjwysocki.net
Signed-off-by: Sasha Levin <sashal@kernel.org>

diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index 64587d31826725cd4059ab2933a93cd10f43f83f..60326ab5475f9dad59a224ac2737df3b3ca3dd92 100644 (file)
--- a/drivers/cpufreq/intel_pstate.c
+++ b/drivers/cpufreq/intel_pstate.c
@@ -3249,8 +3249,8 @@ static int intel_cpufreq_update_pstate(struct cpufreq_policy *policy,
                int max_pstate = policy->strict_target ?
                                        target_pstate : cpu->max_perf_ratio;
 
-               intel_cpufreq_hwp_update(cpu, target_pstate, max_pstate, 0,
-                                        fast_switch);
+               intel_cpufreq_hwp_update(cpu, target_pstate, max_pstate,
+                                        target_pstate, fast_switch);
        } else if (target_pstate != old_pstate) {
                intel_cpufreq_perf_ctl_update(cpu, target_pstate, fast_switch);
        }