|| ||"Rafael J. Wysocki" <firstname.lastname@example.org> |
|| ||Linux PM mailing list <email@example.com> |
|| ||[PATCH 0/3] PM: Runtime PM and device PM QoS refinements |
|| ||Sat, 24 Sep 2011 23:23:03 +0200|
|| ||LKML <firstname.lastname@example.org>,
"Linux-sh list" <email@example.com>,
Magnus Damm <firstname.lastname@example.org>,
Kevin Hilman <email@example.com>, firstname.lastname@example.org,
Ming Lei <email@example.com>|
|| ||Article, Thread
On Wednesday, August 31, 2011, Rafael J. Wysocki wrote:
> This patchset illustrates how device PM QoS may be used along with
> PM domains in my view.
> Actually, it consists of two parts. Namely, patches [1-3/5] seem to be
> suitable for 3.2, unless somebody hates them, but patches [4-5/5] are
> total RFC. They haven't been tested, only compiled, so the use of them
> is not encouraged (they may kill your dog or make your cat go wild, or
> do something equally nasty, so beware). Their purpose is to illustrate
> an idea that I'd like to discuss at the PM miniconference during the
> [1/5] - Split device PM domain data into a "base" and additional fields
> (one need_restore field at the moment, but the subsequent patches
> add more fields).
> [2/5] - Make runtime PM always release power.lock if power.irq_safe is set.
> [3/5] - Add function for reading device PM QoS values safely.
> [4/5] - Add governor function for stopping devices.
> [5/5] - Add generic PM domain power off governor function.
I have updated patches [1-3] after receiving some feedback and the result
follows. These patches are regarded as 3.2 material, if no one has
[1/3] - Split device PM domain data into a "base" and additional fields
(one need_restore field at the moment).
[2/3] - Make runtime PM always release power.lock if power.irq_safe is set.
[3/3] - Add function for reading device PM QoS values safely.
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/