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>,
Sudeep Holla <sudeep.holla@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] cpufreq: Allow light-weight tear down on CPU offline
Date: Mon, 11 Feb 2019 14:11:34 +0530 [thread overview]
Message-ID: <cover.1549874368.git.viresh.kumar@linaro.org> (raw)
The cpufreq core doesn't remove the cpufreq policy anymore on CPU
offline operation, rather that happens when the CPU device gets
unregistered from the kernel. This allows faster recovery when the CPU
comes back online. This is also very useful during system wide
suspend/resume where we offline all non-boot CPUs during suspend and
then bring them back on resume.
This patcset takes the same idea a step ahead to allow drivers to do
light weight tear-down during CPU offline operation and updates the
cpufreq-dt driver to implement the new helper.
Viresh Kumar (2):
cpufreq: Allow light-weight tear down on CPU offline operation
cpufreq: dt: Implement light_weight_exit() callback
drivers/cpufreq/cpufreq-dt.c | 19 +++++++++++++++++++
drivers/cpufreq/cpufreq.c | 16 +++++++++++-----
include/linux/cpufreq.h | 1 +
3 files changed, 31 insertions(+), 5 deletions(-)
--
2.20.1.321.g9e740568ce00
next reply other threads:[~2019-02-11 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 8:41 Viresh Kumar [this message]
2019-02-11 8:41 ` [PATCH 1/2] cpufreq: Allow light-weight tear down on CPU offline operation Viresh Kumar
2019-02-11 10:51 ` Rafael J. Wysocki
2019-02-11 10:56 ` Rafael J. Wysocki
2019-02-11 8:41 ` [PATCH 2/2] cpufreq: dt: Implement light_weight_exit() callback 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.1549874368.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--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).