linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: Andy Fleming <afleming@freescale.com>
Cc: Sylvain Munaut <tnt@246tnt.com>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: IRQ Level / Edge
Date: Sat, 3 Jul 2004 18:42:16 +0200	[thread overview]
Message-ID: <20040703164216.GA22998@pegasos> (raw)
In-Reply-To: <DE336CD5-CC79-11D8-BA44-000393C30512@freescale.com>


On Fri, Jul 02, 2004 at 05:47:59PM -0500, Andy Fleming wrote:
>
> Level sensitive Interrupts will continue to fire until the interrupt is
> cleared.  Essentially, the hardware device causing the interrupt will
> bring the interrupt line up (or down, depending on the polarity), and
> keep it at that level until the condition disappears.  By setting the
> IRQ controller to consider that interrupt level-sensitive, the
> controller knows that the interrupt is still firing, and if you unmask
> the interrupt while the signal is high, it will fire again.
>
> Edge sensitive means that the interrupt only fires on a transition (low
> to high for positive, high to low for negative).  Thus you don't have
> to worry about clearing the interrupt before unmasking it.
>
> I'm not sure if that's clear, but to summarize: Level and edge are
> descriptions of how the interrupt is detected (by the "level" of the
> interrupt, or by a transition *to* that level).  As for where to find
> out which it is, the manual for the device should specify whether the
> interrupt signal is level or edge sensitive.

Err, i suppose the interesting bit is not how the board designer will
know wheter the interrupt is edge or level, but how the kernel running
on the board is able to detect it ?

Friendly,

Sven Luther

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

  reply	other threads:[~2004-07-03 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 21:39 IRQ Level / Edge Sylvain Munaut
2004-07-02 22:47 ` Andy Fleming
2004-07-03 16:42   ` Sven Luther [this message]
2004-07-04 17:31     ` Sylvain Munaut
2004-07-04 17:58       ` Gary Thomas
2004-07-04 18:05       ` Sven Luther

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=20040703164216.GA22998@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=afleming@freescale.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tnt@246tnt.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 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).