From: Kent Borg <kentborg@borg.org>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Shared Interrupts Question (2.4)
Date: Fri, 9 May 2003 13:34:17 -0400 [thread overview]
Message-ID: <20030509133417.B26462@borg.org> (raw)
In-Reply-To: <20030508211426.GA1440@rover.farnsworth.org>; from dale@farnsworth.org on Thu, May 08, 2003 at 02:14:26PM -0700
On Thu, May 08, 2003 at 02:14:26PM -0700, Dale Farnsworth wrote:
> Create and register a board-specific interrupt driver. Assign it
> a range of irqs (non-conflicting with the main interrupt driver).
> When called with an irq outside its range, the board-specific driver
> routines forward the call to the main driver.
Cool, cool...
> The board-specific driver does a request_irq at init time for the
> one main irq it is multiplexing.
What does my handler on the main irq do? Perhaps nothing?
I am figuring I supply my own get_irq call, and it returns one of this
new interrupt range, or if none, calls the previous get_irq. If I
never let the main irq number come back, my handler on the main irq
never gets called, right? If so, why am calling request_irq in the
first place? To keep the system from puking on spurious interrupts?
(But if I answer the get_irq, and if I never answer the main irq
number, how would it know?)
Thanks,
-kb, the Kent who thinks he is getting close.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-09 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 20:08 Shared Interrupts Question (2.4) Kent Borg
2003-05-08 20:20 ` bhupinder sahran
2003-05-08 20:28 ` Kent Borg
2003-05-08 21:14 ` Dale Farnsworth
2003-05-09 17:34 ` Kent Borg [this message]
2003-05-10 2:00 ` Dale Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 21:48 Kent Borg
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=20030509133417.B26462@borg.org \
--to=kentborg@borg.org \
--cc=dale@farnsworth.org \
--cc=linuxppc-embedded@lists.linuxppc.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.