Re: [PATCH v5 13/17] PCI: rcar-gen4: Route Root Port AER to a virtual Root Port IRQ

[Wolfram Sang]

On Mon, Nov 09, 2026 at 11:41:52AM +0900, Koichiro Den wrote:
> On Wed, Oct 21, 2026 at 02:19:46AM +0200, Marek Vasut wrote:
> > On 10/20/26 5:10 AM, Koichiro Den wrote:
> > > On R-Car Gen4 SoCs, the APP block exposes the Root Port interrupt
> > > signals in PCIEINTSTS0 and routes them to platform IRQs: AER to
> > > intreq_pcim_lperr, and PME and bandwidth notifications to
> > > intreq_pcim_sub. On an R-Car S4 with GIC ITS, a link retrain set
> > > LnkSta.LBMS and latched PCIEINTSTS0[23] (cfg_bw_mgt_msi), but the Root
> > > Port's MSI never fired while endpoint MSIs worked fine. With iMSI-RX the
> > > Root Port MSI capabilities are already hidden, but its INTx maps to
> > > intreq_pcim_sub. Note that even before this driver took over the IRQ
> > > with rcar_gen4_pcie_msi_irq_handler, the port service was unable to
> > > request it, as the DWC core used that IRQ for its chained MSI handler.
> > > In either case, iMSI-RX or an external MSI controller, Root Port
> > > interrupts are not delivered to the port services.
> > > 
> > > Hide the Root Port MSI/MSI-X capabilities so the port services use
> > > INTx regardless of the MSI controller. Do this in the R-Car host setup,
> > > which also runs on reset and resume. Use a virtual IRQ to deliver
> > > notifications from separate platform IRQs to the standard handlers.
> > > Route AER from the optional "aer" interrupt. DTs without it remain
> > > supported, but Root Port AER stays unavailable.
> > > 
> > > The APP block may still receive MSI-form notifications because hiding
> > > the Root Port's MSI capabilities does not clear MSICAP0.MSIE. Handle
> > > these alongside the INTx-form level signals. Clear the MSI-form latch
> > > before the AER handler clears Root Error Status, so a late APP clear
> > > does not erase a new notification.
> > > 
> > > Check for reset requests before dispatch: on S4, DBI accesses from
> > > the port services can hang the host immediately after link down.
> > > 
> > > The next patch also feeds PME and bandwidth notifications from "msi"
> > > into this IRQ, so both parents may dispatch concurrently.
> > > handle_level_irq() calls irq_ack() before checking whether it can run
> > > the handlers. Keep the APP latches set while the IRQ is in progress or
> > > disabled, so the level parents can retry through the reset checks.
> > > This avoids losing notifications without a raw lock around port
> > > services that take regular spinlocks.
> > > 
> > > Signed-off-by: Koichiro Den <den@xxxxxxxxxxxxx>
> > > ---
> > > Changes since v4:
> > >    - Hide the Root Port MSI/MSI-X capabilities in host_setup() instead of
> > >      adding a no_rp_msi flag to the DWC core. (Shawn)
> > >      https://lore.kernel.org/r/bi3rvyqpdu4iq6pfyrqvx7eplyim6gmg2ijal67mpateobmtlq@gec7zewfm76r/
> > >      I did not carry Marek's Reviewed-by tag over due to the change.
> > 
> > Bjorn/Manivannan, can you please have a look at this patch and the MSI
> > handling, to be sure this is OK ?
> > 
> > (no further comments from me below this point)
> > 
> > Thank you !
> 
> Marek, thanks for the review.
> 
> Bjorn/Mani, just a gentle ping. Could one of you take a look? To summarize:
> 
> - v4 had 'no_rp_msi' flag to the DWC core. Shawn suggested keeping that in the
>   glue driver instead, which I found reasonable:
>   https://lore.kernel.org/r/20261015033103.3076869-14-den@xxxxxxxxxxxxx/
> - v5 hides them in rcar_gen4_pcie_host_setup(). (this patch)
> 
> If you'd rather I send v6 first, rebased on the pp->msi_irq_domain rename Shawn
> and Geert pointed out, please let me know. Otherwise I'll wait for your comments
> before respinning.

As maintainers are usually super-busy, is there another MSI expert we
could ask to offload work from them?

I'd also like to have this series in the next merge window. Thanks
everyone for all the work involved, so far!

Attachment: signature.asc
Description: PGP signature