1 Mar 2011 01:14
[PATCH] omap:mailbox: resolve hang issue
Armando Uribe <x0095078 <at> ti.com>
2011-03-01 00:14:23 GMT
2011-03-01 00:14:23 GMT
From: Hari Kanigeri <h-kanigeri2 <at> ti.com> omap4 interrupt disable bits is different. On rx kfifo full, the mbox rx interrupts wasn't getting disabled, and this is causing the rcm stress tests to hang. Signed-off-by: Hari Kanigeri <h-kanigeri2 <at> ti.com> Signed-off-by: Armando Uribe <x0095078 <at> ti.com> --- arch/arm/mach-omap2/mailbox.c | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-omap2/mailbox.c b/arch/arm/mach-omap2/mailbox.c index 3d05ac8..2bfe8c6 100644 --- a/arch/arm/mach-omap2/mailbox.c +++ b/arch/arm/mach-omap2/mailbox.c <at> <at> -207,7 +207,10 <at> <at> static void omap2_mbox_disable_irq(struct omap_mbox *mbox, struct omap_mbox2_priv *p = mbox->priv; u32 l, bit = (irq == IRQ_TX) ? p->notfull_bit : p->newmsg_bit; l = mbox_read_reg(p->irqdisable); - l &= ~bit; + if (cpu_is_omap44xx()) + l |= bit; + else + l &= ~bit; mbox_write_reg(l, p->irqdisable); } -- -- 1.7.0.4(Continue reading)
, you can
> kthread_ceate()+kthread_bind() in UP_PREPARE, just don't wake them yet.
I am OK doing the sched_setscheduler_nocheck() in UP_PREPARE, correct?
But yes, I can have the CPU_STARTING notifier wake up any kthreads that
the current CPU might have caused to be created.
RSS Feed