From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Huang Ying <ying.huang@intel.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Lan Tianyu <tianyu.lan@intel.com>, Aaron Lu <aaron.lu@intel.com>,
Jean Pihet <j-pihet@ti.com>,
linux-pci@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
mark gross <markgross@thegnar.org>
Subject: [RFD][PATCH 0/7] PM / QoS: Support for PM QoS device flags
Date: Fri, 28 Sep 2012 23:51:10 +0200 [thread overview]
Message-ID: <201209282351.10663.rjw@sisk.pl> (raw)
Hi All,
The following patch series extends the existing device PM QoS core code to
support PM QoS flags representing binary (on/off) requirements, such as
whether or not power may be removed entirely from the device or whether
or not remote wakeup (i.e. signalling of external events while suspended)
should work for it.
[1/7] Prepare PM QoS device structure for adding more constraint types.
[2/7] Introduce request and constraint data types for PM QoS flags.
[3/7] Prepare struct dev_pm_qos_request for representing more request types.
[4/7] Introduce device PM QoS flags support.
[5/7] Make it possible to expose PM QoS device flags to user space.
[6/7] PM / Domains: Check device PM QoS flags in pm_genpd_poweroff().
[7/7] PM / ACPI: Take device PM QoS flags into account.
The last two patches make the generic PM domains framework and ACPI / PCI,
respectively, take the PM QoS device flags introduced by patch [5/7] into
accont when making their decisions.
The changelogs describe the details, but if anything isn't clear, please let
me know.
Thanks,
Rafael
next reply other threads:[~2012-09-28 21:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 21:51 Rafael J. Wysocki [this message]
2012-09-28 21:52 ` [RFD][PATCH 1/7] PM / QoS: Prepare device structure for adding more constraint types Rafael J. Wysocki
2012-09-28 21:52 ` [RFD][PATCH 2/7] PM / QoS: Introduce request and constraint data types for PM QoS flags Rafael J. Wysocki
2012-09-29 6:02 ` Lan Tianyu
2012-09-29 21:36 ` Rafael J. Wysocki
2012-09-28 21:53 ` [RFD][PATCH 3/7] PM / QoS: Prepare struct dev_pm_qos_request for more request types Rafael J. Wysocki
2012-09-28 21:54 ` [RFD][PATCH 4/7] PM / QoS: Introduce device PM QoS flags support Rafael J. Wysocki
2012-09-28 21:55 ` [RFD][PATCH 5/7] PM / QoS: Make it possible to expose PM QoS device flags to user space Rafael J. Wysocki
2012-10-30 8:53 ` Aaron Lu
2012-10-30 15:29 ` Rafael J. Wysocki
2012-09-28 21:56 ` [RFD][PATCH 6/7] PM / Domains: Check device PM QoS flags in pm_genpd_poweroff() Rafael J. Wysocki
2012-09-28 21:56 ` [RFD][PATCH 7/7] PM / ACPI: Take device PM QoS flags into account Rafael J. Wysocki
2012-09-29 3:16 ` Huang Ying
2012-09-29 21:39 ` Rafael J. Wysocki
2012-11-12 21:07 ` Bjorn Helgaas
2012-11-12 23:42 ` Rafael J. Wysocki
2012-10-01 16:17 ` [RFD][PATCH 0/7] PM / QoS: Support for PM QoS device flags Pihet-XID, Jean
2012-10-02 2:17 ` Rafael J. Wysocki
2012-10-08 8:02 ` [PATCH " Rafael J. Wysocki
2012-10-08 8:04 ` [PATCH 1/7] PM / QoS: Prepare device structure for adding more constraint types Rafael J. Wysocki
2012-10-10 3:15 ` mark gross
2012-10-10 23:12 ` Rafael J. Wysocki
2012-10-08 8:05 ` [PATCH 2/7] PM / QoS: Introduce request and constraint data types for PM QoS flags Rafael J. Wysocki
2012-10-10 3:21 ` mark gross
2012-10-08 8:06 ` [PATCH 3/7] PM / QoS: Prepare struct dev_pm_qos_request for more request types Rafael J. Wysocki
2012-10-10 3:37 ` mark gross
2012-10-08 8:07 ` [PATCH 4/7] PM / QoS: Introduce PM QoS device flags support Rafael J. Wysocki
2012-10-10 3:37 ` mark gross
2012-10-08 8:07 ` [PATCH 5/7] PM / QoS: Make it possible to expose PM QoS device flags to user space Rafael J. Wysocki
2012-10-10 3:33 ` mark gross
2012-10-08 8:08 ` [PATCH 6/7] PM / Domains: Check device PM QoS flags in pm_genpd_poweroff() Rafael J. Wysocki
2012-10-10 3:35 ` mark gross
2012-10-08 8:09 ` [PATCH 7/7] PM / ACPI: Take device PM QoS flags into account Rafael J. Wysocki
2012-10-09 2:46 ` Huang Ying
2012-10-10 3:36 ` mark gross
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=201209282351.10663.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=aaron.lu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-pihet@ti.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=markgross@thegnar.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tianyu.lan@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;
as well as URLs for NNTP newsgroup(s).