From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Lauri Leukkunen <lauri.leukkunen@nokia.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: ack spurious IRQs in get_irqnr_and_base
Date: Fri, 17 Oct 2008 14:19:12 -0700 [thread overview]
Message-ID: <20081017211911.GU15820@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0810170226530.729@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [081017 01:30]:
> Hi Lauri,
>
> I think we should merge your patch along with the SO patch also, so in the
> event of a spurious interrupt, it won't wedge the whole system. One
> question though:
>
> On Wed, 15 Oct 2008, Lauri Leukkunen wrote:
>
> > This prevents spurious interrupts from repeating unacked and
> > thus locking the system, while still allowing the spurious
> > bad irq error message to be show on console.
> >
> > Signed-off-by: Lauri Leukkunen <lauri.leukkunen@nokia.com>
> > ---
> > arch/arm/plat-omap/include/mach/entry-macro.S | 21 ++++++++++++++++++++-
> > 1 files changed, 20 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/arm/plat-omap/include/mach/entry-macro.S b/arch/arm/plat-omap/include/mach/entry-macro.S
> > index a8fca9d..c88a4cb 100644
> > --- a/arch/arm/plat-omap/include/mach/entry-macro.S
> > +++ b/arch/arm/plat-omap/include/mach/entry-macro.S
> > @@ -87,7 +87,26 @@
> > ldr \irqnr, [\base, #0xd8] /* IRQ pending reg 3 */
> > cmp \irqnr, #0x0
> > 2222:
> > - ldrne \irqnr, [\base, #INTCPS_SIR_IRQ_OFFSET]
> > +#if defined(CONFIG_ARCH_OMAP34XX)
> > + mov \tmp, \irqnr
> > +#endif
> > + ldrne \irqnr, [\base, #INTCPS_SIR_IRQ_OFFSET]
> > +#if defined(CONFIG_ARCH_OMAP34XX)
> > + mov \irqstat, \irqnr
> > + bic \irqstat, \irqstat, #0x7f /* check for spurious flag */
>
> According to Table 10-14 in the TRM, the spurious flag field is 25 bits
> wide, but the patch only checks for 7 bits. This should probably be
> extended?
That's OK, as the bic clears the non-spurious bits, so pushing.
Tony
>
> > + cmp \irqstat, #0x0
> > + beq 2223f
> > + mov \irqstat, #0x1 /* Ack the spurious irq, this lets it
> > + * generate a bad irq error message,
> > + * but prevents infinitely repeating
> > + * irq.
> > + */
> > + str \irqstat, [\base, #0x48] /* INTC_CONTROL register */
> > +2223:
> > + cmp \tmp, #0x0 /* set conditional back to what it was
> > + * before spurious test
> > + */
> > +#endif
> >
> > .endm
> >
>
> - Paul
prev parent reply other threads:[~2008-10-17 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 11:51 [PATCH] OMAP3: ack spurious IRQs in get_irqnr_and_base Lauri Leukkunen
2008-10-17 8:30 ` Paul Walmsley
2008-10-17 21:17 ` Paul Walmsley
2008-10-17 21:19 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081017211911.GU15820@atomide.com \
--to=tony@atomide.com \
--cc=lauri.leukkunen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.