On Thu, Sep 18, 2025 at 03:44:41PM +0200, Marek Vasut wrote: > On R-Car V4H, the PCIEC controller DBI read would generate an SError > in case the controller reset is released by writing SRSTCLR register > first, and immediately afterward reading some PCIEC controller DBI > register. The issue triggers in rcar_gen4_pcie_additional_common_init() > on dw_pcie_readl_dbi(dw, PCIE_PORT_LANE_SKEW), which on V4H is the first > read after reset_control_deassert(dw->core_rsts[DW_PCIE_PWR_RST].rstc). > > The reset controller which contains the SRSTCLR register and the PCIEC > controller which contains the DBI register share the same root access > bus, but the bus then splits into separate segments before reaching > each IP. Even if the SRSTCLR write access was posted on the bus before > the DBI read access, it seems the DBI read access may reach the PCIEC > controller before the SRSTCLR write completed, and trigger the SError. > > Mitigate the issue by adding a dummy SRSTCLR read, which assures the > SRSTCLR write completes fully and is latched into the reset controller, > before the PCIEC DBI read access can occur. > > Fixes: 0ab55cf18341 ("clk: renesas: cpg-mssr: Add support for R-Car V4H") > Signed-off-by: Marek Vasut Reviewed-by: Wolfram Sang