Re: [PATCH v4 0/5] PCI: rcar-gen4: irqchip/gic-v3: Handle GIC ITS
From: Marek Vasut
Date: Thu Jul 09 2026 - 08:40:32 EST
On 7/9/26 2:19 PM, Manivannan Sadhasivam wrote:
On Tue, Jul 07, 2026 at 10:35:38PM +0200, Marek Vasut wrote:I do not believe there is.
Configure all R-Car Gen4 PCIe controller MSI registers fully, both in
case MSI are enabled and disabled.
Patch GIC ITS driver and add quirks for R-Car Gen4 GIC ITS, which is
configured to 32-bit address width for AXI or APB interface.
Switch R-Car V4H to use GIC ITS in its DT and describe the GIC ITS
implementation cacheable and shareable limitations.
Marek Vasut (5):
PCI: dwc: Determine whether iMSI is used before calling .init
PCI: rcar-gen4: Configure AXIINTC if iMSI-RX not used
irqchip/gic-v3: Refactor GIC600 limited to 32bit PA erratum handling
irqchip/gic-v3: Add Renesas R-Car Gen4 erratum workaround
Is there a functional dependency between irqchip and PCI patches? Since the
irqchip patches touch ARM64 Kconfig etc... I'm wondering if it still need to go
through PCI tree.
These two configure the PCIe controller hardware:
PCI: dwc: Determine whether iMSI is used before calling .init
PCI: rcar-gen4: Configure AXIINTC if iMSI-RX not used
These two fill in GIC ITS quirks:
irqchip/gic-v3: Refactor GIC600 limited to 32bit PA erratum handling
irqchip/gic-v3: Add Renesas R-Car Gen4 erratum workaround
This one does yes depend on the two and two patches above, and can only be applied once all four aforementioned patches land, otherwise things really yes will break:
arm64: dts: renesas: r8a779g0: Add GICv3 ITS and update PCIe nodes
Would you like me to split the series up , or can you and Marc (?) pick the relevant parts via matching trees ?