From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesse Barnes <jbarnes@virtuousgeek.org>,
"Moore, Robert" <robert.moore@intel.com>,
Len Brown <lenb@kernel.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Matthew Garrett <mjg@redhat.com>
Subject: [PATCH 0/8] PCI run-time PM support (rev. 4)
Date: Wed, 17 Feb 2010 23:35:47 +0100 [thread overview]
Message-ID: <201002172335.47703.rjw__17718.3812404566$1266446786$gmane$org@sisk.pl> (raw)
Hi,
The following (updated) series of patches provides basic run-time power
management support for PCI devices through ACPI and/or the native PCIe
PME.
Patches [1/8] and [3/8] are unchanged, the other patches have been modified to
address the reviewers' comments and/or to fix reported bugs.
[1/8] - Add function for checking PME status of devices
[2/8][Updated] - PCIe PME root port service driver
[3/8] - "Don't use MSIs for PME signaling" switch for PCIe
[4/8][New] - ACPI GPE refcounting, based on 3 patches from Matthew Garrett
[5/8][Updated] - ACPI, add fields for handling run-wake devices
[6/8][New] - ACPI, make it possible to use more than 1 notify handler per node
[7/8][Updated] - PCI / ACPI platform support for run-time power management
[8/8] - Runtime PM callbacks for the PCI bus type
Bob, Len, patches [4/8] and [6/8] are vitally important for this feature, but
they cannot be merged without your approval. Please let me know if you have
any objections to these patches.
Thanks,
Rafael
next reply other threads:[~2010-02-17 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 22:35 Rafael J. Wysocki [this message]
2010-02-17 22:35 [PATCH 0/8] PCI run-time PM support (rev. 4) 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='201002172335.47703.rjw__17718.3812404566$1266446786$gmane$org@sisk.pl' \
--to=rjw@sisk.pl \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg@redhat.com \
--cc=robert.moore@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.