From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Irq domain for legacy interrupts
Date: Wed, 07 Oct 2015 17:02:38 +0200 [thread overview]
Message-ID: <41520723.9CcSmQjLSU@wuerfel> (raw)
In-Reply-To: <loom.20151007T164737-541@post.gmane.org>
On Wednesday 07 October 2015 14:53:03 bharat kumar gogada wrote:
> why do we need a irq domain for legacy interrupts ?
You need an irq domain if you want to refer to the interrupts from
DT, otherwise you have no way to describe them.
> Do we need any specific
> parameter in device tree other that interrupt-map, interrupt-map-mask, for
> handling with irq domain ?
no.
> when will the .map method in struct irq_domain_ops get invoked for legacy
> interrupts ?
when the interrupt gets mapped ;-)
This should happen whenever the first PCIe device starts using non-MSI
interrupts.
Arnd
next prev parent reply other threads:[~2015-10-07 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 14:53 Irq domain for legacy interrupts bharat kumar gogada
2015-10-07 15:02 ` Arnd Bergmann [this message]
2015-10-07 15:13 ` Bharat Kumar Gogada
2015-10-07 15:20 ` Bharat Kumar Gogada
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=41520723.9CcSmQjLSU@wuerfel \
--to=arnd@arndb.de \
--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