On 11:43-20181227, Lokesh Vutla wrote: > With the system coprocessor managing the range allocation of the > inputs to Interrupt Aggregator, it is difficult to represent > the device IRQs from DT. > > The suggestion is to use MSI in such cases where devices wants > to allocate and group interrupts dynamically. > > Create a MSI domain bus layer that allocates and frees MSIs for > a device. > > APIs that are implemented are: > - inta_msi_create_irq_domain() that creates a MSI domain > - inta_msi_domain_alloc_group_irqs() that creates MSIs for the > specified device and source indexes. All these are expected to > be grouped by the parent interrupt controller to MSI domain. > - inta_msi_domain_free_group_irqs() frees the grouped irqs. > > Signed-off-by: Lokesh Vutla <[email protected]> > --- > > - May be the same functionaly can be included in platform msi. But I would > like to get a feedback on the approach. > > drivers/soc/ti/Kconfig | 6 + > drivers/soc/ti/Makefile | 1 + > drivers/soc/ti/k3_inta_msi.c | 193 +++++++++++++++++++++++++++++ > include/linux/irqdomain.h | 1 + > include/linux/msi.h | 6 + > include/linux/soc/ti/k3_inta_msi.h | 22 ++++ > 6 files changed, 229 insertions(+) > create mode 100644 drivers/soc/ti/k3_inta_msi.c > create mode 100644 include/linux/soc/ti/k3_inta_msi.h
Did we miss maintainer file? -- Regards, Nishanth Menon
