From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Aaron Lu <aaron.lu@intel.com>, Huang Ying <ying.huang@intel.com>,
LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>,
Lv Zheng <lv.zheng@intel.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: [PATCH 0/7] ACPI / PM: ACPI power management callback routines for subsystems
Date: Mon, 29 Oct 2012 10:06:32 +0100 [thread overview]
Message-ID: <1766582.8gdQKXoi0K@vostro.rjw.lan> (raw)
Hi All,
The following series of patches rearranges ACPI device power management
code and introduces universal PM callback routines that may be used by
bus types that don't support power management natively and/or by drivers
of devices with those bus types.
[1/7] Move routines for adding/removing device wakeup notifiers into a separate
file.
[2/7] Move device power state selection routine to the new device PM file.
[3/7] Move runtime remote wakeup setup routine to the new device PM file.
[4/7] Split device wakeup management routines, so that it is possible to
reduce the number of acpi_bus_get_device() calls.
[5/7] Provide low-lever device PM functions operationg on struct acpi_device
objects.
[6/7] Move device PM functions related to sleep states from sleep.c to the
new device PM file.
[7/7] Provide ACPI PM callback routines for subsystems.
The patches are on top of the current Linus' tree with the git branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-qos
merged. The resulting kernel has been run on my test-bed Toshiba Portege R500
and hasn't crashed it, but more testing is still needed, so please use it with
care.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next reply other threads:[~2012-10-29 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 9:06 Rafael J. Wysocki [this message]
2012-10-29 9:07 ` [PATCH 1/7] ACPI / PM: Move routines for adding/removing device wakeup notifiers Rafael J. Wysocki
2012-10-29 9:09 ` [PATCH 2/7] ACPI / PM: Move device power state selection routine to device_pm.c Rafael J. Wysocki
2012-11-06 4:56 ` Aaron Lu
2012-11-06 13:03 ` Rafael J. Wysocki
2012-10-29 9:10 ` [PATCH 3/7] ACPI / PM: Move runtime remote wakeup setup " Rafael J. Wysocki
2012-10-29 9:10 ` [PATCH 4/7] ACPI / PM: Split device wakeup management routines Rafael J. Wysocki
2012-10-29 9:11 ` [PATCH 5/7] ACPI / PM: Provide device PM functions operating on struct acpi_device Rafael J. Wysocki
2012-10-30 7:28 ` Aaron Lu
2012-10-30 15:20 ` Rafael J. Wysocki
2012-11-02 5:17 ` Aaron Lu
2012-11-02 11:19 ` Rafael J. Wysocki
2012-10-29 9:12 ` [PATCH 6/7] ACPI / PM: Move device PM functions related to sleep states Rafael J. Wysocki
2012-11-06 19:52 ` David Rientjes
2012-11-08 19:20 ` [patch] acpi, pm: fix build breakage David Rientjes
2012-11-08 21:15 ` Rafael J. Wysocki
2012-10-29 9:13 ` [PATCH 7/7] ACPI / PM: Provide ACPI PM callback routines for subsystems Rafael J. Wysocki
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=1766582.8gdQKXoi0K@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=aaron.lu@intel.com \
--cc=adrian.hunter@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox