[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110823095711.058d9cf4@lxorguk.ukuu.org.uk>
Date: Tue, 23 Aug 2011 09:57:11 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Paul Walmsley <paul@...an.com>
Cc: linux-serial@...r.kernel.org, Alan Cox <alan@...ux.intel.com>,
Pantelis Antoniou <pantelis.antoniou@...il.com>,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Felipe Balbi <balbi@...com>, torvalds@...ux-foundation.org,
mporter@...com, Kevin Hilman <khilman@...com>,
"Govindraj.R" <govindraj.raja@...com>
Subject: Re: [PATCH] tty: omap-serial: fix boot hang by converting to use a
threaded IRQ handler (was Re: [PATCH] irq: always set IRQF_ONESHOT if no
primary handler is specified)
On Mon, 22 Aug 2011 23:10:21 -0600 (MDT)
Paul Walmsley <paul@...an.com> wrote:
>
> Convert the omap-serial hardirq handler to a threaded IRQ handler. Without
> this patch, OMAP boards which use the on-board OMAP UARTs and the
> omap-serial driver will not boot to userspace after commit
> f3637a5f2e2eb391ff5757bc83fb5de8f9726464 ("irq: Always set IRQF_ONESHOT if
> no primary handler is specified"). Enabling CONFIG_DEBUG_SHIRQ reveals
> 'IRQ handler type mismatch' errors:
There are multiple other drivers reporting all these problems - the
faulty irq change should be reverted at this point not the drivers
fiddled with.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists