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@dominikbrodowski.net, Ingo Molnar <mingo@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: [RFC V2 0/6] cpufreq: transition-latency cleanups
Date: Thu, 13 Jul 2017 11:10:51 +0530 [thread overview]
Message-ID: <cover.1499853492.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
Here is the V2 and sending it as RFC this time.
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 dropped as well.
Some code consolidation also done across governors.
Based of: pm/linux-next
Tested on: ARM64 Hikey board.
V1->V2:
- While we still get rid of the limitation of 10ms for using
ondemand/conservative, but we preserve the earlier behavior where the
transition latency set to CPUFREQ_ETERNAL would not allow use of
ondemand/conservative governors. Thanks to Dominik for his feedback on
that.
--
viresh
Viresh Kumar (6):
cpufreq: Replace "max_transition_latency" with "dynamic_switching"
cpufreq: schedutil: Set dynamic_switching to true
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 | 8 +++----
drivers/cpufreq/cpufreq_conservative.c | 6 ------
drivers/cpufreq/cpufreq_governor.c | 17 ++-------------
drivers/cpufreq/cpufreq_governor.h | 3 +--
drivers/cpufreq/cpufreq_ondemand.c | 12 -----------
include/linux/cpufreq.h | 36 ++++++++++++++++++++++++--------
kernel/sched/cpufreq_schedutil.c | 12 ++---------
9 files changed, 40 insertions(+), 72 deletions(-)
--
2.13.0.71.gd7076ec9c9cb
next reply other threads:[~2017-07-13 5:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 5:40 Viresh Kumar [this message]
2017-07-13 5:40 ` [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching" Viresh Kumar
2017-07-13 16:19 ` Rafael J. Wysocki
2017-07-14 7:01 ` Dominik Brodowski
2017-07-14 11:11 ` Rafael J. Wysocki
2017-07-14 22:06 ` Rafael J. Wysocki
2017-07-15 5:08 ` Dominik Brodowski
2017-07-15 12:26 ` Rafael J. Wysocki
2017-07-17 11:58 ` Viresh Kumar
2017-07-17 12:18 ` Rafael J. Wysocki
2017-07-13 5:40 ` [RFC V2 2/6] cpufreq: schedutil: Set dynamic_switching to true Viresh Kumar
2017-07-13 5:40 ` [RFC V2 3/6] cpufreq: governor: Drop min_sampling_rate Viresh Kumar
2017-07-13 5:40 ` [RFC V2 4/6] cpufreq: Use transition_delay_us for legacy governors as well Viresh Kumar
2017-07-13 16:31 ` Rafael J. Wysocki
2017-07-13 5:40 ` [RFC V2 5/6] cpufreq: Cap the default transition delay value to 10 ms Viresh Kumar
2017-07-13 5:40 ` [RFC V2 6/6] cpufreq: arm_big_little: Make ->get_transition_latency() mandatory 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.1499853492.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--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).