From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/6] cpufreq: Remove the redundant !setpolicy check
Date: Wed, 19 Jun 2019 17:05:37 +0530 [thread overview]
Message-ID: <b9bac95bcc36f5f70e910e4801be5d4f8fd32d0c.1560944014.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1560944014.git.viresh.kumar@linaro.org>
cpufreq_start_governor() is only called for !setpolicy case, checking it
again is not required.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
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 85ff958e01f1..54befd775bd6 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -2153,7 +2153,7 @@ static int cpufreq_start_governor(struct cpufreq_policy *policy)
pr_debug("%s: for CPU %u\n", __func__, policy->cpu);
- if (cpufreq_driver->get && !cpufreq_driver->setpolicy)
+ if (cpufreq_driver->get)
cpufreq_update_current_freq(policy);
if (policy->governor->start) {
--
2.21.0.rc0.269.g1a574e7a288b
next prev parent reply other threads:[~2019-06-19 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 11:35 [PATCH 0/6] cpufreq: cleanups Viresh Kumar
2019-06-19 11:35 ` Viresh Kumar [this message]
2019-06-19 11:35 ` [PATCH 2/6] cpufreq: Replace few CPUFREQ_CONST_LOOPS checks with has_target() Viresh Kumar
2019-06-19 12:20 ` Rafael J. Wysocki
2019-06-19 14:18 ` Viresh Kumar
2019-06-19 11:35 ` [PATCH 3/6] cpufreq: Remove the has_target() check from notifier handler Viresh Kumar
2019-06-19 12:25 ` Rafael J. Wysocki
2019-06-19 14:19 ` Viresh Kumar
2019-06-19 11:35 ` [PATCH 4/6] cpufreq: Use has_target() instead of !setpolicy Viresh Kumar
2019-06-19 12:28 ` Rafael J. Wysocki
2019-06-19 14:20 ` Viresh Kumar
2019-06-19 11:35 ` [PATCH 5/6] cpufreq: Reuse cpufreq_update_current_freq() in __cpufreq_get() Viresh Kumar
2019-06-19 11:35 ` [PATCH 6/6] cpufreq: Avoid calling cpufreq_verify_current_freq() from handle_update() 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=b9bac95bcc36f5f70e910e4801be5d4f8fd32d0c.1560944014.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@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;
as well as URLs for NNTP newsgroup(s).