From: Wolfgang Grandegger <wg@grandegger.com>
To: "Jorge Ramirez Ortiz, HCL Europe" <Jorge.Ramirez-Ortiz@hcl.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Edge interrupts on PCI drivers
Date: Tue, 17 Jul 2012 17:00:36 +0200 [thread overview]
Message-ID: <50057E14.3080904@grandegger.com> (raw)
In-Reply-To: <4F534D1A615F544D95E57BFD8460658301CBE3D1@GEO-HCLT-UKEVS1.GEO.CORP.HCL.IN>
On 07/17/2012 04:57 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Typical PCI devices have many sources of interrupts (some level, some edge triggered) normally all routed through PIN A.
AFAIC, PCI interrupts are *always* level sensitive.
> When writing an RTDM pci driver for one of these devices, how does the microkernel manage the edge interrupts?
>
> I am looking at some traces where the CPU seems to be interrupted continuously by an edge interrupt until the actual condition that causes it is cleared.
That's normal for level sensitive interrupt sources.
Wolfgang.
next prev parent reply other threads:[~2012-07-17 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 14:57 [Xenomai] Edge interrupts on PCI drivers Jorge Ramirez Ortiz, HCL Europe
2012-07-17 15:00 ` Wolfgang Grandegger [this message]
2012-07-17 15:02 ` Jan Kiszka
2012-07-17 15:16 ` Jorge Ramirez Ortiz, HCL Europe
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=50057E14.3080904@grandegger.com \
--to=wg@grandegger.com \
--cc=Jorge.Ramirez-Ortiz@hcl.com \
--cc=xenomai@xenomai.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 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.