All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Bogus External Interrupt
Date: Fri, 03 Mar 2006 10:13:03 -0500	[thread overview]
Message-ID: <44085CFF.2030200@smiths-aerospace.com> (raw)
In-Reply-To: <du7qbj$tft$1@sea.gmane.org>

do wrote:
> Hello,
> 
> I am trying to write simple program similar to examples/timer.c, which 
> uses interrupts from general purpose timers.
> 
> My board is based on mpc8260 and I am using U-boot 1.1.4.
> 
> When interrupt is generated from timer, there also appears message: 
> Bogus External Interrupt IRQ 0.
> 
> I don't know why bogus interrupt appears and how it is related to my 
> timer interrupt.This is also strange that the number of IRQ is 0. This 
> bogus interrupt appears only when timer is started. When I have 
> registered my timer interrupt handler with irq_install_handler, but not 
> started timer, everything was ok, and I was able to check with irqinfo 
> that my handler is registered.
> 
> I would be grateful for some suggestions what can be wrong.
> 
> Best regards!

Typically "IRQ 0" is an indication that there was no interrupt found 
when the ISR went to read the interrupt reason.  I can think of two 
reasons for this:
1) (Typical reason): an interrupt happened and was withdrawn (level 
sensitive interrupt: it went inactive) before the processor got to the ISR.

2) (Likely your problem): The ISR cleared the interrupt improperly so 
that the processor (re)latched the interrupt that was cleared.  When you 
exit the ISR, the processor has a pending interrupt so it re-enters the 
ISR, but doesn't find anything to do.  Typically this is caused by 
clearing the processor side of the interrupt and _then_ clearing the 
source.  You should clear the source _first_ and then the processor (or, 
for a multi-level interrupt, clear from the furthest out inward).

This should be a non-fatal error, but should be understood and fixed.

gvb

  reply	other threads:[~2006-03-03 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 22:07 [U-Boot-Users] Bogus External Interrupt do
2006-03-03 15:13 ` Jerry Van Baren [this message]
2006-03-07 20:26   ` [U-Boot-Users] " do

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=44085CFF.2030200@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.com \
    --cc=u-boot@lists.denx.de \
    /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.