From: Kent Borg <kentborg@borg.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Why ack interrupt before calling handler?
Date: Fri, 6 Jun 2003 14:29:39 -0400 [thread overview]
Message-ID: <20030606142939.B15725@borg.org> (raw)
I am confused by something in ppc_irq_dispatch_handler(). It looks to
me that the interrupt is ack-ed before the handler is called. Maybe I
am misunderstanding, but doesn't the ack only reset the interrupt
controller? If so, the interrupting hardware could still be
presenting a level-triggered interrupt. Wouldn't it make more sense
to let the interrupt routine get service the hardware first, then
reset the interrupt controller?
Thanks,
-kb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-06-06 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 18:29 Kent Borg [this message]
2003-06-11 10:33 ` Why ack interrupt before calling handler? Kenneth Johansson
2003-06-11 11:28 ` Wolfgang Denk
2003-06-11 12:24 ` eric lescouet
2003-06-11 12:51 ` Kent Borg
2003-06-11 12:39 ` Kent Borg
2003-06-11 12:58 ` Kenneth Johansson
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=20030606142939.B15725@borg.org \
--to=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).