lkml.org 
[lkml]   [2011]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 0/3] PM: Runtime PM and device PM QoS refinements
Date
Hi,

On Wednesday, August 31, 2011, Rafael J. Wysocki wrote:
> Hi,
>
> 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
> LPC.
>
> [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
objections.

[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.

Thanks,
Rafael



\
 
 \ /
  Last update: 2011-09-24 23:27    [from the cache]
©2003-2011 Jasper Spaans