linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* Irq domain for legacy interrupts
@ 2015-10-07 14:53 bharat kumar gogada
  2015-10-07 15:02 ` Arnd Bergmann
  0 siblings, 1 reply; 4+ messages in thread
From: bharat kumar gogada @ 2015-10-07 14:53 UTC (permalink / raw)
  To: linux-arm-kernel

why do we need a irq domain for legacy interrupts ? 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 ?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Irq domain for legacy interrupts
  2015-10-07 14:53 Irq domain for legacy interrupts bharat kumar gogada
@ 2015-10-07 15:02 ` Arnd Bergmann
  2015-10-07 15:13   ` Bharat Kumar Gogada
  2015-10-07 15:20   ` Bharat Kumar Gogada
  0 siblings, 2 replies; 4+ messages in thread
From: Arnd Bergmann @ 2015-10-07 15:02 UTC (permalink / raw)
  To: linux-arm-kernel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Irq domain for legacy interrupts
  2015-10-07 15:02 ` Arnd Bergmann
@ 2015-10-07 15:13   ` Bharat Kumar Gogada
  2015-10-07 15:20   ` Bharat Kumar Gogada
  1 sibling, 0 replies; 4+ messages in thread
From: Bharat Kumar Gogada @ 2015-10-07 15:13 UTC (permalink / raw)
  To: linux-arm-kernel

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 ?

-----Original Message-----
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 ?

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Irq domain for legacy interrupts
  2015-10-07 15:02 ` Arnd Bergmann
  2015-10-07 15:13   ` Bharat Kumar Gogada
@ 2015-10-07 15:20   ` Bharat Kumar Gogada
  1 sibling, 0 replies; 4+ messages in thread
From: Bharat Kumar Gogada @ 2015-10-07 15:20 UTC (permalink / raw)
  To: linux-arm-kernel

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 ?

-----Original Message-----
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 ?

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-10-07 15:20 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-07 14:53 Irq domain for legacy interrupts bharat kumar gogada
2015-10-07 15:02 ` Arnd Bergmann
2015-10-07 15:13   ` Bharat Kumar Gogada
2015-10-07 15:20   ` Bharat Kumar Gogada

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).