Irq domain for legacy interrupts
Bharat Kumar Gogada
bharat.kumar.gogada at xilinx.com
Wed Oct 7 08:20:49 PDT 2015
Sorry for not being clear,in arch/arm64/kernel/pci.c, pcibios_add_device(struct pci_dev *dev) does the irq mapping so, at this point of time the registered .map will be invoked?
In arch/arm64/kernel/pci.c, pcibios_add_device(struct pci_dev *dev) does the irq mapping so, at this point of time the registered irq domain mapping will be invoked at this time ?
From: Arnd Bergmann [mailto:arnd at arndb.de]
Sent: Wednesday, October 07, 2015 8:33 PM
To: linux-arm-kernel at lists.infradead.org
Cc: Bharat Kumar Gogada
Subject: Re: Irq domain for legacy interrupts
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 ?
> 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.
More information about the linux-arm-kernel