From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@rjwysocki.net
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, tianyu.lan@intel.com, nm@ti.com,
jinchoi@broadcom.com, sebastian.capella@linaro.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V2 0/2] cpufreq: suspend governors during s2r/hibernation
Date: Fri, 22 Nov 2013 16:59:47 +0530 [thread overview]
Message-ID: <cover.1385118255.git.viresh.kumar@linaro.org> (raw)
This patchset adds cpufreq callbacks to dpm_{suspend|resume}_noirq() for
handling suspend/resume of cpufreq governors. This is required for early suspend
and late resume of governors.
There are multiple problems that are fixed by this patch:
- Nishanth Menon (TI) found an interesting problem on his platform, OMAP. His board
wasn't working well with suspend/resume as calls for removing non-boot CPUs
was turning out into a call to drivers ->target() which then tries to play
with regulators. But regulators and their I2C bus were already suspended and
this resulted in a failure. This is why we need a PM notifier here.
- Lan Tianyu (Intel) & Jinhyuk Choi (Broadcom) found another issue where
tunables configuration for clusters/sockets with non-boot CPUs was getting
lost after suspend/resume, as we were notifying governors with
CPUFREQ_GOV_POLICY_EXIT on removal of the last cpu for that policy and so
deallocating memory for tunables.
This was earlier sent here:
https://lkml.org/lkml/2013/11/15/107
V1->V2:
- Used direct callbacks from dpm_{suspend|resume}_noirq() for
suspending/resuming govenors instead of doing that with help of PM notifiers.
- Patch 2/2: Switching to the desirable frequency before suspending the
governors.
Viresh Kumar (2):
cpufreq: suspend governors on system suspend/hibernate
cpufreq: Change freq before suspending governors
drivers/base/power/main.c | 3 ++
drivers/cpufreq/cpufreq.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++
include/linux/cpufreq.h | 5 +++
3 files changed, 87 insertions(+)
--
1.7.12.rc2.18.g61b472e
next reply other threads:[~2013-11-22 11:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 11:29 Viresh Kumar [this message]
2013-11-22 11:29 ` [PATCH V2 1/2] cpufreq: suspend governors on system suspend/hibernate Viresh Kumar
2013-11-22 12:33 ` Rafael J. Wysocki
2013-11-22 12:48 ` Viresh Kumar
2013-11-25 21:30 ` Nishanth Menon
2013-11-25 21:30 ` Nishanth Menon
2013-11-26 2:16 ` Viresh Kumar
2013-11-26 19:39 ` Pavel Machek
2013-11-26 20:18 ` Rafael J. Wysocki
2013-11-27 2:56 ` Viresh Kumar
2013-11-27 14:26 ` Rafael J. Wysocki
2013-11-22 11:29 ` [PATCH V2 2/2] cpufreq: Change freq before suspending governors Viresh Kumar
2013-11-22 12:37 ` Rafael J. Wysocki
2013-11-22 12:52 ` Viresh Kumar
2013-11-22 13:25 ` Rafael J. Wysocki
2013-11-22 13:14 ` Viresh Kumar
2013-11-22 19:39 ` Stephen Warren
2013-11-24 21:32 ` Rafael J. Wysocki
2013-11-25 4:28 ` Viresh Kumar
2013-11-25 10:14 ` 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.1385118255.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=jinchoi@broadcom.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=sebastian.capella@linaro.org \
--cc=tianyu.lan@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.