On Wed, Mar 13, 2019 at 10:19 PM Lina Iyer <ilina@xxxxxxxxxxxxxx> wrote: > +Mapping the interrupt specifiers in the device tree can be done using the > +"irqdomain-map" property. The property contains interrupt specifier at the > +current interrupt controller followed by the interrupt specifier at the mapped > +interrupt controller. > + > + irqdomain-map = <incoming-interrupt-specifier mapped-interrupt-specifier> > + > +The optional properties "irqdomain-map-mask" and "irqdomain-map-pass-thru" may > +be provided to help interpret the valid bits of the incoming and mapped > +interrupt specifiers respectively. > + > + Example: > + irqdomain-map = <22 0 &intc 36 0>, <24 0 &intc 37 0>; > + irqdomain-map-mask = <0xff 0>; > + irqdomain-map-pass-thru = <0 0xff>; This is looking a bit familiar to the existing interrupt-map that is used for PCI interrupts and Swizzling back to a set of PCI host interrupts. I tried to document interrupt-map here: https://elinux.org/Device_Tree_Usage#Advanced_Interrupt_Mapping interrupt-map is a bit convoluted, so I don't know if it would be subject to reuse for this. I suspect that interrupt-map, despite the name, is for PCI only. Yours, Linus Walleij