]> git.karo-electronics.de Git - linux-beck.git/commit
OMAP: clockdomain: Wait for powerdomain to be ON when using clockdomain force wakeup
authorSantosh Shilimkar <santosh.shilimkar@ti.com>
Fri, 19 Aug 2011 22:59:39 +0000 (16:59 -0600)
committerPaul Walmsley <paul@pwsan.com>
Fri, 19 Aug 2011 22:59:39 +0000 (16:59 -0600)
commitb1cbdb00da2ac00eb67fe277e563ff1f5093b4ba
tree102865903e981befe15585b0b63ad14b482a160d
parentc956b753e706f24d18a026f8efa4df3b1919fcc9
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 on OMAP4430, where L4_PER was periodically
getting stuck in in-transition state when transitioning from from OSWR to ON.

This issue was reported and investigated by Patrick Titiano <p-titiano@ti.com>

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
Reported-by: Patrick Titiano <p-titiano@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
[paul@pwsan.com: updated to apply; added transition wait on clkdm_deny_idle();
 remove two superfluous pwrdm_wait_transition() calls]
Signed-off-by: Paul Walmsley <paul@pwsan.com>
arch/arm/mach-omap2/clockdomain.c
arch/arm/mach-omap2/pm.c