<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general">
    <title>gmane.linux.power-management.general</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27384"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27383"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27382"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27379"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27378"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27377"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27376"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27375"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27374"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27373"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27372"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27371"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27370"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27369"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27368"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27367"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27366"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27365"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27364"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/27363"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27384">
    <title>Re: [PATCH 0/2] bug fixes for coupled cpuidle</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27384</link>
    <description>&lt;pre&gt;
I confirm that these two fixes are needed to get couple idle
v4 series working.

Regards
Santosh

&lt;/pre&gt;</description>
    <dc:creator>Santosh Shilimkar</dc:creator>
    <dc:date>2012-05-21T06:44:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27383">
    <title>[PATCH][v2] ARM: davinci: cpuidle - remove ops</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27383</link>
    <description>&lt;pre&gt;This patch removes the ops usage because we have the index
passed as parameter to the idle function and we can determine
if we do WFI or memory retention.

The benefit of this cleanup is the removal of:
 * the ops
 * the statedata usage because we want to get rid of it in all the drivers
 * extra structure definition
 * extra functions definition
 * remove macro definition using BIT(0)

It also benefits the readability.

Signed-off-by: Daniel Lezcano &amp;lt;daniel.lezcano&amp;lt; at &amp;gt;linaro.org&amp;gt;
---
 arch/arm/mach-davinci/cpuidle.c |   81 +++++++++++++--------------------------
 1 files changed, 27 insertions(+), 54 deletions(-)

diff --git a/arch/arm/mach-davinci/cpuidle.c b/arch/arm/mach-davinci/cpuidle.c
index f0f179c..1b0782a 100644
--- a/arch/arm/mach-davinci/cpuidle.c
+++ b/arch/arm/mach-davinci/cpuidle.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -25,35 +25,46 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
 #define DAVINCI_CPUIDLE_MAX_STATES2
 
-struct davinci_ops {
-void (*enter) (u32 flags);
-void (*exit) (u32 flags);
-u32 flags;
-};
+static bool ddr2_pwdn;
+
+static void __iomem *ddr2_reg_bas&lt;/pre&gt;</description>
    <dc:creator>Daniel Lezcano</dc:creator>
    <dc:date>2012-05-20T22:07:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27382">
    <title>Re: [PATCH 2/2] ARM: DAVINCI: cpuidle - remove ops</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27382</link>
    <description>&lt;pre&gt;
Sure, I will resend a version without the initialization and the 
_raw_write variant.

Thanks
   -- Daniel


&lt;/pre&gt;</description>
    <dc:creator>Daniel Lezcano</dc:creator>
    <dc:date>2012-05-20T10:37:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27379">
    <title>Re: [PATCH 0/2] ARM: DAVINCI: cpuidle - cleanups</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27379</link>
    <description>&lt;pre&gt;
Hi,

maybe these patches did not raise attention.
Do you think they sound good ?

Thanks
&lt;/pre&gt;</description>
    <dc:creator>Daniel Lezcano</dc:creator>
    <dc:date>2012-05-19T09:26:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27378">
    <title>Re: [PATCHv3 0/4] coupled cpuidle state support</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27378</link>
    <description>&lt;pre&gt;Great !!
I will pull Len's tree and rebase OMAP patches against it.

Regards
Santosh
&lt;/pre&gt;</description>
    <dc:creator>Shilimkar, Santosh</dc:creator>
    <dc:date>2012-05-19T07:04:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27377">
    <title>Re: [PATCHv3 0/4] coupled cpuidle state support</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27377</link>
    <description>&lt;pre&gt;
Len silently picked up the last version.  I just posted two fixes to
it, hopefully he'll pick up those too.
&lt;/pre&gt;</description>
    <dc:creator>Colin Cross</dc:creator>
    <dc:date>2012-05-18T20:18:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27376">
    <title>Re: [PATCHv3 0/4] coupled cpuidle state support</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27376</link>
    <description>&lt;pre&gt;
That should be Len, but he's been silent recently.

How urgent is it?

Rafael
&lt;/pre&gt;</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2012-05-18T19:03:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27375">
    <title>[PATCH 0/2] bug fixes for coupled cpuidle</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27375</link>
    <description>&lt;pre&gt;The last modifications made to the coupled cpuidle patches introduced
two bugs that I missed during testing.  The online count was never
initialized, causing coupled idle to always wait and never enter the
ready loop.  That hid the second bug, the ready count could never be
decremented after exiting idle.

Len, these two patches could be squashed into patch 3 of the original
set.  If you do squash them, you could also add Rafael's tags to the
set (Reviewed-by on 1 and 2, acked-by on 3).  Or I can reupload the
whole stack as v5 if you prefer.
&lt;/pre&gt;</description>
    <dc:creator>Colin Cross</dc:creator>
    <dc:date>2012-05-18T18:05:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27374">
    <title>[PATCH 1/2] cpuidle: coupled: fix count of online cpus</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27374</link>
    <description>&lt;pre&gt;online_count was never incremented on boot, and was also counting
cpus that were not part of the coupled set.  Fix both issues by
introducting a new function that counts online coupled cpus, and
call it from register as well as the hotplug notifier.

Signed-off-by: Colin Cross &amp;lt;ccross&amp;lt; at &amp;gt;android.com&amp;gt;
---
 drivers/cpuidle/coupled.c |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/drivers/cpuidle/coupled.c b/drivers/cpuidle/coupled.c
index 3e65de1..b02810a 100644
--- a/drivers/cpuidle/coupled.c
+++ b/drivers/cpuidle/coupled.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -532,6 +532,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int cpuidle_enter_state_coupled(struct cpuidle_device *dev,
 return entered_state;
 }
 
+static void cpuidle_coupled_update_online_cpus(struct cpuidle_coupled *coupled)
+{
+cpumask_t cpus;
+cpumask_and(&amp;amp;cpus, cpu_online_mask, &amp;amp;coupled-&amp;gt;coupled_cpus);
+coupled-&amp;gt;online_count = cpumask_weight(&amp;amp;cpus);
+}
+
 /**
  * cpuidle_coupled_register_device - register a coupled cpuidle device
  * &amp;lt; at &amp;gt;dev: struct cpuidle_device for the current cpu
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; &lt;/pre&gt;</description>
    <dc:creator>Colin Cross</dc:creator>
    <dc:date>2012-05-18T18:05:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27373">
    <title>[PATCH 2/2] cpuidle: coupled: fix decrementing readycount</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27373</link>
    <description>&lt;pre&gt;cpuidle_coupled_set_not_ready sometimes refuses to decrement the
ready count in order to prevent a race condition.  This makes it
unsuitable for use when finished with idle.  Add a new function
cpuidle_coupled_set_done that decrements both the ready count and
waiting count, and call it after idle is complete.

Signed-off-by: Colin Cross &amp;lt;ccross&amp;lt; at &amp;gt;android.com&amp;gt;
---
 drivers/cpuidle/coupled.c |   18 ++++++++++++++++--
 1 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/drivers/cpuidle/coupled.c b/drivers/cpuidle/coupled.c
index b02810a..fc427fa 100644
--- a/drivers/cpuidle/coupled.c
+++ b/drivers/cpuidle/coupled.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -388,6 +388,21 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static void cpuidle_coupled_set_not_waiting(int cpu,
 }
 
 /**
+ * cpuidle_coupled_set_done - mark this cpu as leaving the ready loop
+ * &amp;lt; at &amp;gt;cpu: the current cpu
+ * &amp;lt; at &amp;gt;coupled: the struct coupled that contains the current cpu
+ *
+ * Marks this cpu as no longer in the ready and waiting loops.  Decrements
+ * the waiting count first to prevent another cpu looping back in an&lt;/pre&gt;</description>
    <dc:creator>Colin Cross</dc:creator>
    <dc:date>2012-05-18T18:05:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27372">
    <title>Re: [PATCHv3 0/4] coupled cpuidle state support</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27372</link>
    <description>&lt;pre&gt;
[...]


I haven't seen any response so far on who is lining up this
series for 3.5 ? Not sure if it made it to linux-next either.

Regards
santosh
&lt;/pre&gt;</description>
    <dc:creator>Santosh Shilimkar</dc:creator>
    <dc:date>2012-05-18T10:36:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27371">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27371</link>
    <description>&lt;pre&gt;:(

I received this:

Your message (attached below) was not delivered to:

 paulmck&amp;lt; at &amp;gt;vnet.ibm.com

because:

 Bad destination mailbox address

Final-recipient: rfc822;paulmck&amp;lt; at &amp;gt;vnet.ibm.com
Action: failed
Status: 5.1.1
Diagnostic-code: X-Xagent; Bad destination mailbox address

On Thu, May 17, 2012 at 4:47 PM, Sundar &amp;lt;sunder.svit&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Sundar</dc:creator>
    <dc:date>2012-05-17T11:30:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27370">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27370</link>
    <description>&lt;pre&gt;I put in a rough draft &amp;lt; at &amp;gt;
https://blueprints.launchpad.net/lpc/+spec/lpc2012-power-management-constraints

Cheers!

On Wed, May 16, 2012 at 5:43 AM, mark gross &amp;lt;markgross&amp;lt; at &amp;gt;thegnar.org&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Sundar</dc:creator>
    <dc:date>2012-05-17T11:17:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27369">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27369</link>
    <description>&lt;pre&gt;
Jean,

Do you already consider GPU drivers, backlight drivers and battery
charging for setting constraints (performance and thermal) ?

Between your, Eduardo's and Antti's proposals, a lot of ground is
being covered and I don't want to make a new proposal just for these
three. But we're keen on helping consolidate on generic interfaces to
deal with these three kinds of devices.

&lt;/pre&gt;</description>
    <dc:creator>Amit Kucheria</dc:creator>
    <dc:date>2012-05-15T12:58:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27368">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27368</link>
    <description>&lt;pre&gt;Hi Mark,

mark gross &amp;lt;markgross&amp;lt; at &amp;gt;thegnar.org&amp;gt; writes:


Thanks for organizing this.

I won't be at Plumbers this year (I'll be on vacation), but will
certainly participate by email as I have an interest in these topics.

I've added Jean Pihet to Cc as he is also working on QoS/constraints
related topics.

Kevin
&lt;/pre&gt;</description>
    <dc:creator>Kevin Hilman</dc:creator>
    <dc:date>2012-05-09T18:54:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27367">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27367</link>
    <description>&lt;pre&gt;Hi Mark,

mark gross &amp;lt;markgross&amp;lt; at &amp;gt;thegnar.org&amp;gt; writes:


Thanks for organizing this.

I won't be at Plumbers this year (I'll be on vacation), but will
certainly participate by email as I have an interest in these topics.

I've added Jean Pihet to Cc as he is also working on QoS/constraints
related topics.

Kevin
&lt;/pre&gt;</description>
    <dc:creator>Kevin Hilman</dc:creator>
    <dc:date>2012-05-09T18:35:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27366">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27366</link>
    <description>&lt;pre&gt;Valentin,
plumbers
critical mass
extending pm-
of
developers
long as
limiting
participate in
the
linux-
correspondence
me.  I know
think its a
cases.
Mark,

Please find a draft proposal on priority based PM-QoS Parameters,
https://blueprints.launchpad.net/lpc/+spec/lpc-2012-priority-based-pmqos-paramet
ers

Thanks,
&lt;/pre&gt;</description>
    <dc:creator>Mansoor, Illyas</dc:creator>
    <dc:date>2012-05-16T09:45:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27365">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27365</link>
    <description>&lt;pre&gt;
It will be great to have you there in any case.

It feels like we have enough content to come up with portable
requirements and maybe an ok design that can work for multiple SoC's.

--mark

&lt;/pre&gt;</description>
    <dc:creator>mark gross</dc:creator>
    <dc:date>2012-05-16T00:13:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27364">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27364</link>
    <description>&lt;pre&gt;
looks great to me!  you should toss it up on the plumbers site.

--mark


&lt;/pre&gt;</description>
    <dc:creator>mark gross</dc:creator>
    <dc:date>2012-05-16T00:09:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27363">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27363</link>
    <description>&lt;pre&gt;Hello,

I submitted a blueprint on launchpad as well, available here:
https://blueprints.launchpad.net/linux/+spec/lpc2012-cf-thermal-pm-constraint

On Tue, May 15, 2012 at 12:40 PM, Jean Pihet &amp;lt;jean.pihet&amp;lt; at &amp;gt;newoldbits.com&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Valentin, Eduardo</dc:creator>
    <dc:date>2012-05-15T11:00:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/27362">
    <title>Re: Plumbers: PM constraints micro-conf RFP</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/27362</link>
    <description>&lt;pre&gt;Hi!

Here is my proposal for the PM constraints micro-conf RFP, as e-mailed today:

Session title: A New Model for the System and Devices Latency

Name of microconference (if applicable): PM constraints micro-conf,
led by Mark Gross

Abstract:
 Due to the nature of the new SoC architectures the Power Management
needs a new model for the various system latencies. The talk presents:
  . the concepts of system, devices, wake-up and resume latencies,
  . the recent changes in the devices framework for the latency, why
and how to make it generic,
  . the link with the other PM QoS frameworks: thermal, cpuidle,
  . the recent changes in the ARM/OMAP platform code for the system latency,
  . the problems encountered while modelling and measuring the
various latencies,
  . a proposal on the model and on the way to implement it,
  . the planned changes in the device framework, the platform code
and the APIs.

 This talk is oriented towards Linux power management developers. The
goal is to agree on a framework impleme&lt;/pre&gt;</description>
    <dc:creator>Jean Pihet</dc:creator>
    <dc:date>2012-05-15T09:40:44</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.power-management.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.power-management.general</link>
  </textinput>
</rdf:RDF>

