From mboxrd@z Thu Jan 1 00:00:00 1970 From: m-karicheri2@ti.com (Murali Karicheri) Date: Fri, 18 Jul 2014 16:15:53 -0400 Subject: [PATCH v6 4/5] PCI: add PCI controller for keystone PCIe h/w In-Reply-To: <5467203.eMVRoNeSx1@wuerfel> References: <1405696469-7172-1-git-send-email-m-karicheri2@ti.com> <1405696469-7172-5-git-send-email-m-karicheri2@ti.com> <5467203.eMVRoNeSx1@wuerfel> Message-ID: <53C98079.4080707@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 07/18/2014 03:50 PM, Arnd Bergmann wrote: > On Friday 18 July 2014 14:31:39 Rob Herring wrote: >>> + >>> + Example: >>> + pcie_msi_intc: msi-interrupt-controller { >>> + interrupt-controller; >>> + #interrupt-cells =<1>; >>> + interrupt-parent =<&gic>; >>> + interrupts =, >>> +, >>> +, >>> +, >>> +, >>> +, >>> +, >>> +; >>> + }; >>> + >>> +pcie_intc: Interrupt controller device node for Legacy irq chip >>> + interrupt-cells: should be set to 1 >>> + interrupt-parent: Parent interrupt controller phandle >>> + interrupts: GIC interrupt lines connected to PCI Legacy interrupt lines >>> + >>> + Example: >>> + pcie_intc: legacy-interrupt-controller { >>> + interrupt-controller; >>> + #interrupt-cells =<1>; >>> + interrupt-parent =<&gic>; >>> + interrupts =, >>> +, >>> +, >>> +; >>> + }; >> This seems wrong. Legacy interrupts should be described with >> interrupt-map and then PCI child devices have a standard interrupt >> specifier. >> >> I'm not sure about MSIs, but I would think they would have a standard >> format too. >> > IIRC, it's actually the correct way to do this here: the problem is that > the PCI IRQs are not directly connected to the GIC, but instead there is > a nested irqchip that has each PCI IRQ routed to it and that requires > an extra EOI for each interrupt. > > The interrupt-map in the PCI host points to this special irqchip rather > than to the GIC. Arnd, Thanks. I agree with Arnd and believe there is no issue here > Arnd > -- > To unsubscribe from this list: send the line "unsubscribe linux-pci" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html