From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V3 0/5] CPUFreq: governors: further cleanups
Date: Tue, 13 Oct 2015 13:39:00 +0530 [thread overview]
Message-ID: <cover.1444723240.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
Here is the third version based on the review comments you gave. I have
tried to resolve most of them, and it looks much better now. Thanks for
your comments.
As I am traveling this week, don't have access to hardware to retest the
series. But I am quite sure it should work just fine, as there weren't
lots of updates from how the final code looked earlier. Anyway, I have
pushed this for the build bot sometime back and it will let us know of
any obvious issues.
V2->V3:
- Few got merged already, and are dropped now
- Patches are reordered a bit to make them more sensible
- gov_queue_work() isn't modified at all with the mask of CPUs, as you
suggested earlier.
- Some minor commit/logs updated.
V1->V2:
- Dropped 2/10 from V1 as it wasn't required
- 3/10 saw some changes due to above patch being dropped
- 7/10 changed a bit as we check for pending work items by looking at
shared->policy, rather than calling delayed_work_pending. We wanted to
check if governor is operational or not and the new check is enough
for that.
Viresh Kumar (5):
cpufreq: ondemand: Drop unnecessary locks from update_sampling_rate()
cpufreq: ondemand: update sampling rate immediately
cpufreq: ondemand: queue work for policy->cpus together
cpufreq: governor: Quit work-handlers early if governor is stopped
cpufreq: Get rid of ->governor_enabled and its lock
drivers/cpufreq/cpufreq.c | 24 ------------------
drivers/cpufreq/cpufreq_governor.c | 33 +++++++++++++++++--------
drivers/cpufreq/cpufreq_ondemand.c | 50 ++++++++++++--------------------------
include/linux/cpufreq.h | 1 -
4 files changed, 39 insertions(+), 69 deletions(-)
--
2.4.0
next reply other threads:[~2015-10-13 8:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:09 Viresh Kumar [this message]
2015-10-13 8:09 ` [PATCH V3 1/5] cpufreq: ondemand: Drop unnecessary locks from update_sampling_rate() Viresh Kumar
2015-10-28 4:05 ` Rafael J. Wysocki
2015-10-28 4:44 ` Viresh Kumar
2015-10-28 5:54 ` Rafael J. Wysocki
2015-10-28 6:43 ` Viresh Kumar
2015-10-28 7:46 ` Rafael J. Wysocki
2015-10-28 8:56 ` Viresh Kumar
2015-10-13 8:09 ` [PATCH V3 2/5] cpufreq: ondemand: update sampling rate immediately Viresh Kumar
2015-10-28 6:28 ` Rafael J. Wysocki
2015-10-28 9:31 ` Viresh Kumar
2015-10-28 15:31 ` Rafael J. Wysocki
2015-10-28 15:28 ` Viresh Kumar
2015-10-28 16:13 ` Rafael J. Wysocki
2015-10-28 15:47 ` Viresh Kumar
2015-10-13 8:09 ` [PATCH V3 3/5] cpufreq: ondemand: queue work for policy->cpus together Viresh Kumar
2015-10-28 6:38 ` Rafael J. Wysocki
2015-10-28 6:46 ` Viresh Kumar
2015-10-28 7:33 ` Rafael J. Wysocki
2015-10-28 8:34 ` Viresh Kumar
2015-10-13 8:09 ` [PATCH V3 4/5] cpufreq: governor: Quit work-handlers early if governor is stopped Viresh Kumar
2015-10-28 7:10 ` Rafael J. Wysocki
2015-10-28 8:25 ` Viresh Kumar
2015-10-28 15:12 ` Rafael J. Wysocki
2015-10-28 14:46 ` Viresh Kumar
2015-10-13 8:09 ` [PATCH V3 5/5] cpufreq: Get rid of ->governor_enabled and its lock 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=cover.1444723240.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).