From: "Tian, Kevin" <kevin.tian@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: request_irq() and setup_irq()
Date: Fri, 22 Oct 2004 01:22:48 +0000 [thread overview]
Message-ID: <571ACEFD467F7749BC50E0A98C17CDD80528CF08@pdsmsx403> (raw)
In-Reply-To: <4177D1A4.1040009@hob.de>
>-----Original Message-----
>From: linux-ia64-owner@vger.kernel.org
[mailto:linux-ia64-owner@vger.kernel.org]
>On Behalf Of Christian Hildner
>Sent: Thursday, October 21, 2004 11:12 PM
>Hi,
>
>looking through the sources of 2.4.21 there come up one question. If a
>device wants to register its interrupt it may call request_irq() that
>then calls setup_irq(). Now since SA_PERCPU_IRQ is not set by the
device
>setup_irq() does not initialize desc->handler. Can that be fixed by
>adding SA_PERCPU_IRQ to irqflags in request_irq() or does that
introduce
>problems at another place?
>
>Christian
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.
Thanks,
Kevin
next prev parent reply other threads:[~2004-10-22 1:22 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 [this message]
2004-10-22 13:06 ` Christian Hildner
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=571ACEFD467F7749BC50E0A98C17CDD80528CF08@pdsmsx403 \
--to=kevin.tian@intel.com \
--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