From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Legacy PCI interrupt support in PCIe host driver
Date: Thu, 16 Mar 2017 20:13:15 +0100 [thread overview]
Message-ID: <4e54c5f9-7cc1-cfab-592d-a87795147020@free.fr> (raw)
In-Reply-To: <alpine.DEB.2.20.1703161843420.3586@nanos>
On 16/03/2017 18:47, Thomas Gleixner wrote:
> On Thu, 16 Mar 2017, Mason wrote:
>> I guess if two interrupts fire at the same time, we'll just take two
>> separate exceptions?
>
> Wrong guess. That might work with level interrupts, 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.
When you say "That might work with level interrupts",
what is "that" ?
In my case,
interrupt-map = <0 0 0 1 &irq0 54 IRQ_TYPE_LEVEL_HIGH>;
interrupts = <54 IRQ_TYPE_LEVEL_HIGH>;
Both ISRs expect LEVEL_HIGH. In fact, doesn't request_irq
return an error if the triggers are different?
Regards.
next prev parent reply other threads:[~2017-03-16 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 15:40 Legacy PCI interrupt support in PCIe host driver Mason
2017-03-16 17:33 ` Mason
2017-03-16 17:47 ` Thomas Gleixner
2017-03-16 19:13 ` Mason [this message]
2017-03-16 19:36 ` Thomas Gleixner
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=4e54c5f9-7cc1-cfab-592d-a87795147020@free.fr \
--to=slash.tmp@free.fr \
--cc=linux-arm-kernel@lists.infradead.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