On Fri, Feb 16, 2024 at 10:47:47AM +0100, Antonio Borneo wrote: > The mapping of EXTI interrupts to its parent interrupt controller > is both SoC and instance dependent. > The current implementation requires adding a new table to the > driver's code and a new compatible for each new EXTI instance. > > Add to the binding an interrupt nexus child node that will be > used on the new EXTI instances and can be optionally used on the > existing instances. > The property 'interrupt-map' in the nexus node maps each EXTI > interrupt to the parent interrupt. > Align #address-cells and #interrupt-cells between the EXTI node > and its nexus node. Looks like an abuse of interrupt-map. You avoid adding yourself to the abuser list by putting it in a child node. Clever. (See list in drivers/of/irq.c if you don't know what I'm talking about) I assume the EXTI has 0..N interrupts. Just define 'interrupts' with N entries with each entry mapping EXTI interrupt N to 'interrupts' entry N. Rob
