aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/tty
diff options
context:
space:
mode:
authorSantosh Shilimkar <santosh.shilimkar@ti.com>2011-07-13 03:26:28 +0000
committerNishanth Menon <nm@ti.com>2011-07-23 12:05:49 -0500
commit4520aa34e2dd7652ce1768841dd85a6c4eb5657c (patch)
tree1aa02dfb7f188a854cd71f430551696bccdf7438 /drivers/tty
parent0d236ab9283a7c4d06ecbdd4472e7084e98e47a8 (diff)
downloadkernel_samsung_tuna-4520aa34e2dd7652ce1768841dd85a6c4eb5657c.zip
kernel_samsung_tuna-4520aa34e2dd7652ce1768841dd85a6c4eb5657c.tar.gz
kernel_samsung_tuna-4520aa34e2dd7652ce1768841dd85a6c4eb5657c.tar.bz2
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> https://patchwork.kernel.org/patch/970142/ 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>
Diffstat (limited to 'drivers/tty')
0 files changed, 0 insertions, 0 deletions