mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lizhe <sensor1010@163.com>
To: vincent.guittot@linaro.org, ilpo.jarvinen@linux.intel.com,
	rafael@kernel.org, viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lizhe <sensor1010@163.com>
Subject: [PATCH] cpufreq/schedutil: When updating limitations, frequency modulation interval not become invalid.
Date: Sun,  4 Feb 2024 06:09:28 -0800	[thread overview]
Message-ID: <20240204140928.2865-1-sensor1010@163.com> (raw)

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@163.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


             reply	other threads:[~2024-02-04 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 14:09 Lizhe [this message]
2024-02-05  7:38 ` Viresh Kumar
     [not found]   ` <7654198e.15f6.18d78668d9b.Coremail.sensor1010@163.com>
2024-02-05  8:54     ` Viresh Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240204140928.2865-1-sensor1010@163.com \
    --to=sensor1010@163.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®