Jon Hunter jon-hun...@ti.com writes:
On Mon, 2009-06-22 at 18:44 -0500, Kevin Hilman wrote:
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
There are two scenarios where a race condition could result in a hang in
the
prcm_interrupt handler. These are:
Jon Hunter jon-hun...@ti.com writes:
Please find the update patch below.
Hi Jon,
What should this apply to? The patch you sent had some lines wrapped,
but even after unwrapping, it didn't apply to either the current PM
branch or pm-2.6.29.
Kevin
There are two scenarios where a race
On Mon, 2009-06-22 at 18:44 -0500, Kevin Hilman wrote:
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
There are two scenarios where a race condition could result in a hang in the
prcm_interrupt handler. These are:
IIRC, the RX51 tree has a workaround for some
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
There are two scenarios where a race condition could result in a hang in the
prcm_interrupt handler. These are:
IIRC, the RX51 tree has a workaround for some hangs seen in this
interrupt handler as well, so this has
From: Jon Hunter jon-hun...@ti.com
There are two scenarios where a race condition could result in a hang in the
prcm_interrupt handler. These are:
1). Waiting for PRM_IRQSTATUS_MPU register to clear.
Bit 0 of the PRM_IRQSTATUS_MPU register indicates that a wake-up event is
pending for the MPU.
