From: narkewoody@gmail.com (Woody Wu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How kernel handle interrupts
Date: Fri, 21 Dec 2012 08:37:22 +0800 [thread overview]
Message-ID: <20121221003722.GA9702@zuhnb712> (raw)
In-Reply-To: <CAN3nT1RDSD4cweOrXEAh4T+u8SSoNqUVLGAosFGzZq4kcs_UHQ@mail.gmail.com>
On Thu, Dec 20, 2012 at 07:16:34PM +0100, Shahbaz khan wrote:
> Hi Woody,
>
> Check "do_IRQ()" in arch/x86/kernel/irq.c. It is responsible to handle
> device specific interrupts, while ipi and timer interrupts are dealt
> elsewhere.
>
Thanks. Maybe you also know what's the name of the same function for
ARM, which is actual arch I am working on.
> Hope this helps.
>
> BR,
> Shahbaz Khan
>
> On Thu, Dec 20, 2012 at 3:27 PM, 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?
> >
> > 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?
> >
> >
> > 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
> >
>
>
>
> --
> Shahbaz Khan
--
woody
I can't go back to yesterday - because I was a different person then.
prev parent reply other threads:[~2012-12-21 0:37 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
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 [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=20121221003722.GA9702@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).