From: Rajagopal Venkat <rajagopal.venkat@linaro.org>
To: myungjoo.ham@samsung.com, rjw@sisk.pl,
Kevin Hilman <khilman@linaro.org>,
Alan Stern <stern@rowland.harvard.edu>
Cc: patches@linaro.org, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rajagopal Venkat <rajagopal.venkat@linaro.org>
Subject: [PATCH v2 0/2] Add devfreq runtime pm support
Date: Wed, 27 Mar 2013 19:22:52 +0530 [thread overview]
Message-ID: <1364392374-12236-1-git-send-email-rajagopal.venkat@linaro.org> (raw)
Patch to bind devfreq to runtime pm framework. Instead of explicitly
using devfreq_suspend_device() and devfreq_resume_device() apis for
devfreq core suspend/resume, let runtime-pm core handle it automatically.
Suspend device devfreq core load monitoring with pm_runtime_suspend() and
resume back on pm_runtime_resume().
Discussed at http://comments.gmane.org/gmane.linux.linaro.devel/13787
Changes from v1:
- improved change log and code comments
- added NULL check for devfreq runtime-pm callbacks
-----
Rajagopal Venkat (2):
PM / devfreq: Fix compiler warnings
PM / devfreq: tie suspend/resume to runtime-pm
drivers/base/power/runtime.c | 21 ++++++++++++-
drivers/devfreq/devfreq.c | 69 +++++++++++++++++++++++++++++++++++++++---
include/linux/devfreq.h | 30 ++++++------------
include/linux/pm.h | 2 ++
4 files changed, 97 insertions(+), 25 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-03-27 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 13:52 Rajagopal Venkat [this message]
2013-03-27 13:52 ` [PATCH v2 1/2] PM / devfreq: Fix compiler warnings Rajagopal Venkat
2013-03-28 6:03 ` MyungJoo Ham
2013-04-02 0:16 ` Rafael J. Wysocki
2013-03-27 13:52 ` [PATCH v2 2/2] PM / devfreq: tie suspend/resume to runtime-pm Rajagopal Venkat
2013-04-03 18:16 ` Kevin Hilman
2013-04-04 10:41 ` Rajagopal Venkat
2013-04-04 10:48 ` Rajagopal Venkat
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=1364392374-12236-1-git-send-email-rajagopal.venkat@linaro.org \
--to=rajagopal.venkat@linaro.org \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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).