From: Magnus Damm <magnus.damm@gmail.com>
To: linux-pm@lists.linux-foundation.org
Cc: gregkh@suse.de
Subject: [PATCH 00/04] PM: Runtime PM v11 patches 20090731
Date: Fri, 31 Jul 2009 21:26:39 +0900 [thread overview]
Message-ID: <20090731122639.31004.95390.sendpatchset@rx1.opensource.se> (raw)
PM: Runtime PM v11 patches 20090731
[PATCH 01/04] PM: Runtime PM v11 - add dev_pm_ops helpers
[PATCH 02/04] PM: Runtime PM v11 - let bus-less devices succeed
[PATCH 03/04] PM: Runtime PM v11 - add debug printouts
[PATCH 04/04] PM: Runtime PM v11 - CONFIG_PM_SLEEP=n support
These patches contain architecture independent changes for
Runtime PM and are meant to be applied on top of:
"PM: Introduce core framework for run-time PM of I/O devices (rev. 11)"
by Rafael J. Wysocki.
Patch 01 + 03 are very straightforward and would be useful to have
upstream from the perspective of a Runtime PM bus developer.
Patch 02 + 04 try to address some problems I ran into while hacking
on the Runtime PM platform bus code for SuperH. There may be better
ways to solve those issues.
Please see each individual patch for more information. Thanks!
Signed-off-by: Magnus Damm <damm@igel.co.jp>
---
drivers/base/core.c | 3 ++
drivers/base/power/main.c | 3 --
drivers/base/power/runtime.c | 55 ++++++++++++++++++++++++++----------------
include/linux/pm_runtime.h | 19 ++++++++++++++
4 files changed, 57 insertions(+), 23 deletions(-)
next reply other threads:[~2009-07-31 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 12:26 Magnus Damm [this message]
2009-07-31 12:26 ` [PATCH 01/04] PM: Runtime PM v11 - add dev_pm_ops helpers Magnus Damm
2009-07-31 12:26 ` [PATCH 02/04] PM: Runtime PM v11 - let bus-less devices succeed Magnus Damm
2009-07-31 12:27 ` [PATCH 03/04] PM: Runtime PM v11 - add debug printouts Magnus Damm
2009-07-31 12:27 ` [PATCH 04/04] PM: Runtime PM v11 - CONFIG_PM_SLEEP=n support Magnus Damm
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=20090731122639.31004.95390.sendpatchset@rx1.opensource.se \
--to=magnus.damm@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-pm@lists.linux-foundation.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