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>
Subject: [PATCH 0/6] cpufreq: transition-latency cleanups
Date: Thu, 29 Jun 2017 16:29:03 +0530 [thread overview]
Message-ID: <cover.1498733506.git.viresh.kumar@linaro.org> (raw)
Hi,
This series tries to cleanup the code around transition-latency and its
users. Some of the old legacy code, which may not make much sense now,
is being dropped as.
Some code consolidation also happens across governors.
Based of: pm/linux-next
Tested on: ARM64 Hikey board.
--
viresh
Viresh Kumar (6):
cpufreq: Don't check for max_transition_latency
cpufreq: Remove (now) unused code related to max_transition_latency
cpufreq: governor: Drop min_sampling_rate
cpufreq: Use transition_delay_us for legacy governors as well
cpufreq: Cap the default transition delay value to 10 ms
cpufreq: arm_big_little: Make ->get_transition_latency() mandatory
Documentation/admin-guide/pm/cpufreq.rst | 8 --------
drivers/cpufreq/arm_big_little.c | 10 ++++-----
drivers/cpufreq/cpufreq.c | 19 -----------------
drivers/cpufreq/cpufreq_conservative.c | 6 ------
drivers/cpufreq/cpufreq_governor.c | 17 ++--------------
drivers/cpufreq/cpufreq_governor.h | 2 --
drivers/cpufreq/cpufreq_ondemand.c | 12 -----------
drivers/cpufreq/cpufreq_performance.c | 6 ------
include/linux/cpufreq.h | 35 +++++++++++++++++++++++---------
kernel/sched/cpufreq_schedutil.c | 11 +---------
10 files changed, 32 insertions(+), 94 deletions(-)
--
2.13.0.71.gd7076ec9c9cb
next reply other threads:[~2017-06-29 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 10:59 Viresh Kumar [this message]
2017-06-29 10:59 ` [PATCH 1/6] cpufreq: Don't check for max_transition_latency Viresh Kumar
2017-06-29 10:59 ` [PATCH 2/6] cpufreq: Remove (now) unused code related to max_transition_latency Viresh Kumar
2017-06-29 10:59 ` [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate Viresh Kumar
2017-06-29 18:01 ` Dominik Brodowski
2017-06-30 3:34 ` Viresh Kumar
2017-06-30 4:53 ` Dominik Brodowski
2017-06-30 5:40 ` Viresh Kumar
2017-07-02 7:23 ` Dominik Brodowski
2017-06-29 10:59 ` [PATCH 4/6] cpufreq: Use transition_delay_us for legacy governors as well Viresh Kumar
2017-06-29 10:59 ` [PATCH 5/6] cpufreq: Cap the default transition delay value to 10 ms Viresh Kumar
2017-06-29 10:59 ` [PATCH 6/6] cpufreq: arm_big_little: Make ->get_transition_latency() mandatory Viresh Kumar
2017-06-29 20:36 ` [PATCH 0/6] cpufreq: transition-latency cleanups Rafael J. Wysocki
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.1498733506.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.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).