From: narkewoody@gmail.com (Woody Wu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How kernel handle interrupts
Date: Fri, 21 Dec 2012 23:34:51 +0800 [thread overview]
Message-ID: <20121221153451.GB5530@zuhnb712> (raw)
In-Reply-To: <CAK7N6vq07CHhhOJTgC=5H5f3Nsi_od=qGJjzu01iL1_3AvTWHg@mail.gmail.com>
On Thu, Dec 20, 2012 at 10:05:05AM -0800, anish singh wrote:
> On Dec 20, 2012 6:30 AM, "Woody Wu" <narkewoody@gmail.com> wrote:
> >
> > Hi, List
> >
> > Where is the Kernel code that handles external interrupts? I want to
> > have a look at it but haven't found out where it is.
> >
> > Actually, I have some basic questions about interrupt handling in Linux.
> > 1. After Kernel's ISR received an interrupt, I believe it will invoke a
> > handler defined in a device driver if any. But it should be the
> > device driver's responsibility or kernel ISR's responsibility to
> > clear (or acknowledge) the interrupt?
> If the interrupt in question is currently being handled then in
> the case of edge triggered interrupt we just mask the interrupt,set it
> pending and bail out.Once the interrupt handler completes then we check for
> pending interrupt and handle it.In level triggered we don't do that.
> Kerenel ISR -this is mixture of core kernel interrupt handling code + your
> device driver interrupt handler(if this is chip driver which is supposed to
> get one interrupt and is reponsible for calling other interrupt handlers
> based on the chip register status then you do explicit masking unmasking
> yourself).
> If you device driver is a interrupt controller driver then you register
> your driver with kernel interrupt handling code and need to write some
> callbacks such as .mask,.unmask and so on.This callbacks are called at
> appropiate places whenever the interrupt is raised.This interrupt is then
> passed to drivers who has requested for this interrupt by calling
> request_irq.
> >
> > 2. My device, an AX88796B network controller, asserting the interrupt
> > line in a level-triggered manner. Now I met problem with the device
> that
> > might caused by the CPU interrupt mode is not set as level-triggered by
> > edge trigger. My CPU is Samsung S3C2410, an ARM920T powered one. Does
> > anyone know usually where and how should I do this kind of setting?
> Just pass the parameter "level triggered" in request_irq in your device
> driver.
Hi Sign,
I searched the interrupt.h for the all the defined flags that I can pass
to the request_irq, but there is no a flag looks like "level triggered".
Would you tell me what you mean the parameter "level triggered"?
Thanks.
> >
> >
> > Thanks in advance.
> >
> > --
> > woody
> > I can't go back to yesterday - because I was a different person then.
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
woody
I can't go back to yesterday - because I was a different person then.
next prev parent reply other threads:[~2012-12-21 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 14:27 How kernel handle interrupts Woody Wu
2012-12-20 18:05 ` anish singh
2012-12-21 9:34 ` Woody Wu
2012-12-21 10:53 ` anish kumar
2012-12-21 12:43 ` Woody Wu
2012-12-21 15:34 ` Woody Wu [this message]
2012-12-21 21:33 ` How kernel handle interrupts[AX88796B network controller] anish kumar
2012-12-22 15:11 ` Woody Wu
2013-01-07 16:36 ` anish kumar
2013-08-05 3:01 ` Woody Wu
2012-12-24 14:10 ` Woody Wu
2012-12-24 16:07 ` Woody Wu
2013-01-07 16:22 ` anish kumar
2012-12-20 18:16 ` How kernel handle interrupts Shahbaz khan
2012-12-21 0:37 ` Woody Wu
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=20121221153451.GB5530@zuhnb712 \
--to=narkewoody@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).