RE: IRQ handler

[Nazim Khan <Nazimk@ishoni.com>]

Title: IRQ handler

I guess, when you have to share an irq number with other device, The ISR for your device

take care and check whether ther interrupt is for your device or not.

 

In your ISR, you have to probe your device and check if that has generated the interrupt.

If not then simply return from your ISR.

This should be the first thing you should do in your ISR.

 

According to my understanding, In case of shared IRQ Number.

All the ISRs, which are registered to one particular IRQ number, will

be executed on interrupt condition.

 

Hope this helps.

 

Nazim Khan

 

 -----Original Message-----
From: David Stroupe [mailto:dstroupe@keyed-upsoftware.com]
Sent: Tuesday, March 05, 2002 3:18 AM
To: kernelnewbies@nl.linux.org
Subject: IRQ handler

When I setup a handler for a device that is sharing a particular IRQ
will my handler be called for every occurance of that IRQ even if it is
for the other card?
I am seeing lots of interrupts that are not being caused by the
card/slot that I inserted the handler for but the dev_id matches the one
that I used when I created my handler.  I assumed(rashly) that the
dev_id would be associated with the hardware that was casuing the
interrupt and that I could use that to weed out the interrupts that do
not pertain to me.

Any suggestions and comments would be appreciated.

--
Best regards,
David Stroupe
Keyed-Up Software

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.kernelnewbies.org/