From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: request_irq() and setup_irq()
Date: Fri, 22 Oct 2004 13:06:41 +0000 [thread overview]
Message-ID: <417905E1.4070404@hob.de> (raw)
In-Reply-To: <4177D1A4.1040009@hob.de>
Tian, Kevin schrieb:
>
>ACPI can provide MADT table for lsapic and iosapic info in local system.
From that table, linux will configure interrupt controller info for each
>interrupt line when bootup. You can look at iosapic_init(), which
>constructs per-line info related to iosapic. Say, by trigger mode of
>specific line, register_intr() will decide whether irq_type_iosapic_edge
>or irq_type_iosapic_level should be used.
>
Kevin,
thanks for your good pointers. Indeed iosapic_init() and register_intr()
are the choice since they install a handler as needed. But before I had
to walk through the hell of acpi.
Thanks a lot
Christian
prev parent reply other threads:[~2004-10-22 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 15:11 request_irq() and setup_irq() Christian Hildner
2004-10-21 15:38 ` Matthew Wilcox
2004-10-21 16:53 ` Grant Grundler
2004-10-22 1:22 ` Tian, Kevin
2004-10-22 13:06 ` Christian Hildner [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=417905E1.4070404@hob.de \
--to=christian.hildner@hob.de \
--cc=linux-ia64@vger.kernel.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