|| ||"Rafael J. Wysocki" <email@example.com> |
|| ||Linux PM list <firstname.lastname@example.org> |
|| ||[PATCH 0/7] PM / QoS: Support for PM QoS device flags |
|| ||Mon, 08 Oct 2012 10:02:39 +0200|
|| ||ACPI Devel Mailing List <email@example.com>,
Alan Stern <firstname.lastname@example.org>,
Huang Ying <email@example.com>,
Sarah Sharp <firstname.lastname@example.org>,
Lan Tianyu <email@example.com>,
Aaron Lu <firstname.lastname@example.org>, Jean Pihet <email@example.com>,
Greg Kroah-Hartman <firstname.lastname@example.org>,
mark gross <email@example.com>,
|| ||Article, Thread
On Friday 28 of September 2012 23:51:10 Rafael J. Wysocki wrote:
> 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.
Time for a real submission, it seems. :-)
The changes since the previous iteration are addressed comments and a small
optimization in patch [5/7] (it won't resume the device if the setting is not
going to change in dev_pm_qos_update_flags()).
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/