On Mon, Oct 10, 2011 at 11:10 AM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
On Wed, Oct 5, 2011 at 3:06 AM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Tarun,
On 10/4/2011 11:20 PM, Cousson, Benoit wrote:
Hi Tony,
Here is the series to fix the warning and remove the redundant
latency
On 10/10/2011 12:05 PM, DebBarma, Tarun Kanti wrote:
On Mon, Oct 10, 2011 at 11:10 AM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
On Wed, Oct 5, 2011 at 3:06 AM, Cousson, Benoitb-cous...@ti.com wrote:
Hi Tarun,
On 10/4/2011 11:20 PM, Cousson, Benoit wrote:
Hi Tony,
Here is the
On Wed, Oct 5, 2011 at 3:06 AM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Tarun,
On 10/4/2011 11:20 PM, Cousson, Benoit wrote:
Hi Tony,
Here is the series to fix the warning and remove the redundant
latency structure that be removed since the timer runtime PM
adaptation was just pulled.
* Benoit Cousson b-cous...@ti.com [111004 13:46]:
Hi Tony,
Here is the series to fix the warning and remove the redundant
latency structure that be removed since the timer runtime PM
adaptation was just pulled.
I was just able to test that on OMAP4.
Patches are based on Kevin's
Hi Tony,
Here is the series to fix the warning and remove the redundant
latency structure that be removed since the timer runtime PM
adaptation was just pulled.
I was just able to test that on OMAP4.
Patches are based on Kevin's for_3.2/omap_device-2 branch
and are available here:
Hi Tarun,
On 10/4/2011 11:20 PM, Cousson, Benoit wrote:
Hi Tony,
Here is the series to fix the warning and remove the redundant
latency structure that be removed since the timer runtime PM
adaptation was just pulled.
I was just able to test that on OMAP4.
It will be nice if you can test
