linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
To: Kent Borg <kentborg@borg.org>
Cc: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Why ack interrupt before calling handler?
Date: 11 Jun 2003 14:58:32 +0200	[thread overview]
Message-ID: <1055336312.26152.104.camel@spawn> (raw)
In-Reply-To: <20030611083953.A26856@borg.org>


On Wed, 2003-06-11 at 14:39, Kent Borg wrote:
> On Wed, Jun 11, 2003 at 12:33:42PM +0200, Kenneth Johansson wrote:

> Finally the interrupt end gets called, which acks and enables the
> interrupt.  This ack actually does something for me.
>

Hopefully this ack only happens if the interrupt is level triggered
otherwise you have a problem.

> I am thinking that the general purpose PPC code does the early
> ack for edge-triggered circumstances.  For latched level-triggered
> cases there is no harm in the extra early ack.

Thats right.

--
Kenneth Johansson
Ericsson AB                       Tel: +46 8 719 70 20
Tellusborgsvägen  90              Fax: +46 8 719 29 45
126 25 Stockholm                  ken@switchboard.ericsson.se


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-06-11 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 18:29 Why ack interrupt before calling handler? Kent Borg
2003-06-11 10:33 ` 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 [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=1055336312.26152.104.camel@spawn \
    --to=kenneth.johansson@etx.ericsson.se \
    --cc=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).