From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <ext-roger.quadros@nokia.com>
Cc: linux-omap@vger.kernel.org,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Subject: Re: [PATCH] ARM: OMAP3: Clean up spurious interrupt check logic
Date: Thu, 2 Apr 2009 09:25:29 -0700 [thread overview]
Message-ID: <20090402162529.GO32530@atomide.com> (raw)
In-Reply-To: <49D4C9B8.10806@nokia.com>
* Roger Quadros <ext-roger.quadros@nokia.com> [090402 07:21]:
> From: Roger Quadros <ext-roger.quadros@nokia.com>
> Date: Thu, 2 Apr 2009 16:41:00 +0300
> Subject: [PATCH] ARM: OMAP3: Clean up spurious interrupt check logic
>
> SPURIOUSIRQ is contained in bits 31:7 of INTC_SIR, so
> INTC_SIR must be right shifted by 7, not 6.
>
> No change in logic, only changes for better readability.
> Refer to register definition of INTCPS_SIR_IRQ in OMAP3 Manual.
Argh, that bug explains why I could not figure out the meaning
of the first spurious bit.. :)
I guess the spurious bit value is still on or off instead of
actually telling the previous spurious irq number though.
Tony
> Signed-off-by: Roger Quadros <ext-roger.quadros@nokia.com>
> ---
> arch/arm/mach-omap2/irq.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/irq.c b/arch/arm/mach-omap2/irq.c
> index 2842fe8..296ab86 100644
> --- a/arch/arm/mach-omap2/irq.c
> +++ b/arch/arm/mach-omap2/irq.c
> @@ -73,9 +73,9 @@ static int omap_check_spurious(unsigned int irq)
> u32 sir, spurious;
>
> sir = intc_bank_read_reg(&irq_banks[0], INTC_SIR);
> - spurious = sir >> 6;
> + spurious = sir >> 7;
>
> - if (spurious > 1) {
> + if (spurious) {
> printk(KERN_WARNING "Spurious irq %i: 0x%08x, please flush "
> "posted write for irq %i\n",
> irq, sir, previous_irq);
> --
> 1.5.6.5
>
>
next prev parent reply other threads:[~2009-04-02 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 14:20 [PATCH] ARM: OMAP3: Clean up spurious interrupt check logic Roger Quadros
2009-04-02 16:25 ` Tony Lindgren [this message]
2009-04-03 6:18 ` Roger Quadros
2009-04-03 23:49 ` [APPLIED] > " Tony Lindgren
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=20090402162529.GO32530@atomide.com \
--to=tony@atomide.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=ext-roger.quadros@nokia.com \
--cc=linux-omap@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox