Hi Kevin,
On Fri, 8 Jan 2010, Kevin Hilman wrote:
First, this patch adds new worst-case latency values to the
omap_device_pm_latency struct. Here the worst-case measured latencies
for the activate and deactivate hooks are stored.
In addition, add an option to auto-adjust the latency
Hi,
this patch is queued up here locally for 2.6.34, but wanted to post it to
lakml in case there are any further comments.
- Paul
From: Kevin Hilman khil...@deeprootsystems.com
First, this patch adds new worst-case latency values to the
omap_device_pm_latency struct. Here the worst-case
Nishanth Menon menon.nisha...@gmail.com writes:
Kevin Hilman said the following on 01/08/2010 05:26 PM:
First, this patch adds new worst-case latency values to the
omap_device_pm_latency struct. Here the worst-case measured latencies
for the activate and deactivate hooks are stored.
In
Kevin Hilman had written, on 01/11/2010 06:50 PM, the following:
Nishanth Menon menon.nisha...@gmail.com writes:
Kevin Hilman said the following on 01/08/2010 05:26 PM:
First, this patch adds new worst-case latency values to the
omap_device_pm_latency struct. Here the worst-case measured
Nishanth Menon n...@ti.com writes:
[...]
nitpick: I think you need {} for the else part too now a days..
you mean as a CodingStyle issue, or a compiler issue?
do you have a reference for this requirement?
do you mean if the 'if' part has {}, the else part should too, even if
it's a
Kevin Hilman said the following on 01/08/2010 05:26 PM:
First, this patch adds new worst-case latency values to the
omap_device_pm_latency struct. Here the worst-case measured latencies
for the activate and deactivate hooks are stored.
In addition, add an option to auto-adjust the latency
First, this patch adds new worst-case latency values to the
omap_device_pm_latency struct. Here the worst-case measured latencies
for the activate and deactivate hooks are stored.
In addition, add an option to auto-adjust the latency values used for
device activate/deactivate.
By setting a new
