[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240204140928.2865-1-sensor1010@163.com>
Date: Sun, 4 Feb 2024 06:09:28 -0800
From: Lizhe <sensor1010@....com>
To: vincent.guittot@...aro.org,
ilpo.jarvinen@...ux.intel.com,
rafael@...nel.org,
viresh.kumar@...aro.org
Cc: linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Lizhe <sensor1010@....com>
Subject: [PATCH] cpufreq/schedutil: When updating limitations, frequency modulation interval not become invalid.
If the current frequency scaling policy is schedutil.
echo schedutil > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
This would result in an invalid frequency modulation interval.
In sugov_limit(), sg_policy->limits_changed is set to true.
Signed-off-by: Lizhe <sensor1010@....com>
---
drivers/cpufreq/cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 44db4f59c4cc..a0af38fcb7e2 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -2631,7 +2631,7 @@ static int cpufreq_set_policy(struct cpufreq_policy *policy,
if (new_gov == policy->governor) {
pr_debug("governor limits update\n");
- cpufreq_governor_limits(policy);
+ cpufreq_policy_apply_limits(policy);
return 0;
}
--
2.25.1
Powered by blists - more mailing lists