Hi Chris,
On 06/07/17 23:00, Chris Patterson wrote:
The purpose of tegra_interrupt_compat is to maintain a tegra-specific
whitelist of interrupt controllers we know how to route. Presumably,
there may be custom boards out there that may have additional
interrupt routing capabilities that this patch set would not support
as-is. I'm not sure of an appropriate way to maintain that logic and
merge them. However, I am certainly open to suggestion, if you have
any ideas.
Those custom boards would likely have a different machine compatible string
because the SOC would be different. So I think the tegra_interrupt_compat is
not necessary.
Sorry about the delayed response...
This check effectively filters out GPIO controllers. Any GPIO-sourced
interrupts route through the GPIO controller's interrupt, and need not
apply for map_irq_to_domain(). Devices requiring GPIO-based
interrupts would need to be passed through with the associated
controller (or maybe virtualize the GPIO routing?).
I am a bit confused. Could you give a concrete example based on tegra
platform?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
