Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1602713
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Legacy PCI interrupt support in PCIe host driver |
| Date | 2017-03-16 18:50 +0100 |
| Message-ID | <tlHHc-1ID-21@gated-at.bofh.it> (permalink) |
| References | <tlFP4-pI-27@gated-at.bofh.it> <tlHxv-1ET-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 16 Mar 2017, Mason wrote: > About shared ISRs. Are they supposed to return IRQ_HANDLED > if and only if they handled something? Every interrupt handler is supposed to return IRQ_NONE if it did not handle it. That does not depend on shared or not. The handler does not know if it's on a shared interrupt line or not. IRQF_SHARED only tells, that the handler is capable of sharing the interrupt line with another device. > Will that stop the next ISR from being called? No. > I guess if two interrupts fire at the same time, we'll just take two > separate exceptions? Wrong guess. That might work with level interupts, but with other types nothing will raise another exception. Sharing interrupts on edge types is a stupid idea, but hardware folks insist on implementing stupid ideas. Thanks, tglx
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Legacy PCI interrupt support in PCIe host driver Mason <slash.tmp@free.fr> - 2017-03-16 16:50 +0100
Re: Legacy PCI interrupt support in PCIe host driver Mason <slash.tmp@free.fr> - 2017-03-16 18:40 +0100
Re: Legacy PCI interrupt support in PCIe host driver Thomas Gleixner <tglx@linutronix.de> - 2017-03-16 18:50 +0100
Re: Legacy PCI interrupt support in PCIe host driver Mason <slash.tmp@free.fr> - 2017-03-16 20:20 +0100
Re: Legacy PCI interrupt support in PCIe host driver Thomas Gleixner <tglx@linutronix.de> - 2017-03-16 20:40 +0100
csiph-web