On 02/18/2015 11:21 AM, Rafael J. Wysocki wrote:
On Wednesday, February 18, 2015 10:13:23 AM Preeti U Murthy wrote:
On 02/17/2015 11:23 PM, Rafael J. Wysocki wrote:
On Tuesday, February 17, 2015 01:29:10 PM Preeti U Murthy wrote:
Hi Rafael,
Hi,
Can you please pull this patch ?
Sorry,
it would be best if you
pulled it.
Thanks
--- PATCH -
[PATCH V4] cpuidle/powernv: Read target_residency value of idle states from DT
if available
From: Preeti U Murthy pre...@linux.vnet.ibm.com
The device tree now exposes the residency
On Wednesday, February 18, 2015 10:13:23 AM Preeti U Murthy wrote:
On 02/17/2015 11:23 PM, Rafael J. Wysocki wrote:
On Tuesday, February 17, 2015 01:29:10 PM Preeti U Murthy wrote:
Hi Rafael,
Hi,
Can you please pull this patch ?
Sorry, I wasn't sure whether or not the patch
On Tuesday, February 17, 2015 01:29:10 PM Preeti U Murthy wrote:
Hi Rafael,
Hi,
Can you please pull this patch ?
Sorry, I wasn't sure whether or not the patch was for me to take and then
I've been traveling lately. Applied now.
Another patch based on top of this is waiting to be pulled:
Hi Rafael,
Can you please pull this patch ?
Another patch based on top of this is waiting to be pulled:
[PATCH] driver/cpuidle-powernv: Avoid endianness conversions while parsing DT
Regards
Preeti U Murthy
On 02/03/2015 11:50 AM, Preeti U Murthy wrote:
The device tree now exposes the residency
The device tree now exposes the residency values for different idle states. Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
maintain
compatibility with the older firmware code which
On 02/02/2015 12:09 PM, Michael Ellerman wrote:
On Mon, 2015-02-02 at 10:40 +0530, Preeti U Murthy wrote:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are
The device tree now exposes the residency values for different idle states. Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
maintain
compatibility with the older firmware code which
On Mon, 2015-02-02 at 10:40 +0530, Preeti U Murthy wrote:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However
Preeti U Murthy pre...@linux.vnet.ibm.com writes:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
On Wed, 2015-28-01 at 02:13:06 UTC, Preeti U Murthy wrote:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However
Preeti U Murthy pre...@linux.vnet.ibm.com writes:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
On 01/28/2015 02:45 PM, Stewart Smith wrote:
Preeti U Murthy pre...@linux.vnet.ibm.com writes:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated
Preeti U Murthy pre...@linux.vnet.ibm.com writes:
On 01/28/2015 02:45 PM, Stewart Smith wrote:
Preeti U Murthy pre...@linux.vnet.ibm.com writes:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency
The device tree now exposes the residency values for different idle states. Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
maintain
compatibility with the older firmware code which
On 01/23/2015 10:29 AM, Michael Ellerman wrote:
On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
@@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
return nr_idle_states;
}
-idle_state_latency = of_get_property(power_mgt,
-
On Tue, 2015-01-27 at 09:32 +0530, Preeti U Murthy wrote:
On 01/23/2015 10:29 AM, Michael Ellerman wrote:
On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
@@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
for (i = 0; i dt_idle_states; i++) {
On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
@@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
return nr_idle_states;
}
- idle_state_latency = of_get_property(power_mgt,
- ibm,cpu-idle-state-latencies-ns, NULL);
-
On 01/20/2015 11:15 AM, Michael Ellerman wrote:
On Mon, 2015-19-01 at 11:32:51 UTC, Preeti U Murthy wrote:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT
On Mon, 2015-19-01 at 11:32:51 UTC, Preeti U Murthy wrote:
The device tree now exposes the residency values for different idle states.
Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However
The device tree now exposes the residency values for different idle states. Read
these values instead of calculating residency from the latency values. The
values
exposed in the DT are validated for optimal power efficiency. However to
maintain
compatibility with the older firmware code which
21 matches
Mail list logo
