for powerdomain to be ON
when using clockdomain force wakeup
While using clockdomain force wakeup method, not waiting for powerdomain
to be effectively ON may end up locking the clockdomain FSM until a
next wakeup event occurs.
One such issue was seen on OMAP4430, where L4_PER was periodically
getting stuck
Subject: [PATCH] [PATCH] OMAP: clockdomain: Wait for powerdomain to be ON
when using clockdomain force wakeup
While using clockdomain force wakeup method, not waiting for powerdomain
to be effectively ON may end up locking the clockdomain FSM until a
next wakeup event occurs.
One such issue was seen
(cc Tero)
Hi Santosh,
On Thu, 11 Aug 2011, Santosh wrote:
On Saturday 16 July 2011 01:18 PM, Santosh Shilimkar wrote:
On 7/15/2011 1:03 AM, Paul Walmsley wrote:
On Wed, 13 Jul 2011, Santosh Shilimkar wrote:
- return arch_clkdm-clkdm_wakeup(clkdm);
+ ret =
Paul,
On Saturday 16 July 2011 01:18 PM, Santosh Shilimkar wrote:
Hi Paul,
On 7/15/2011 1:03 AM, Paul Walmsley wrote:
cc'ing Patrick
Hi Rajendra, Santosh,
some comments here:
On Wed, 13 Jul 2011, Santosh Shilimkar wrote:
While using clockdomain force wakeup method, not waiting for
Hi Paul,
On 7/15/2011 1:03 AM, Paul Walmsley wrote:
cc'ing Patrick
Hi Rajendra, Santosh,
some comments here:
On Wed, 13 Jul 2011, Santosh Shilimkar wrote:
While using clockdomain force wakeup method, not waiting for powerdomain
to be effectively ON may end up locking the clockdomain FSM
cc'ing Patrick
Hi Rajendra, Santosh,
some comments here:
On Wed, 13 Jul 2011, Santosh Shilimkar wrote:
While using clockdomain force wakeup method, not waiting for powerdomain
to be effectively ON may end up locking the clockdomain FSM until a
next wakeup event occurs.
One such issue was
While using clockdomain force wakeup method, not waiting for powerdomain
to be effectively ON may end up locking the clockdomain FSM until a
next wakeup event occurs.
One such issue was seen on OMAP4430, where L4_PER was periodically
getting stuck in in-transition state when transitioning from
