On 9/10/26 2:50 PM, [email protected] wrote:
On 8/9/26 03:32, Marek Vasut via U-Boot wrote:
Avoid repeated link attempts for these controllers. In case the
controller link is up, this is a noop since the probe() already
finished. In case the controller link is down, a repeated link
up attempt seems to require reset of both PCIe controllers, which
is not desired. It is also unlikely that a repeated link attempt
would bring the link up, as U-Boot does not support hotplug anyway.
Therefore, prevent repeated link attempts.

Signed-off-by: Marek Vasut <[email protected]>
---
Cc: Nobuhiro Iwamatsu <[email protected]>
Cc: Tom Rini <[email protected]>
Cc: [email protected]
---
  drivers/pci/pci-rcar-gen4.c | 15 +++++++++++++++
  1 file changed, 15 insertions(+)

diff --git a/drivers/pci/pci-rcar-gen4.c b/drivers/pci/pci-rcar-gen4.c
index 34561406641..044bceee6c7 100644
--- a/drivers/pci/pci-rcar-gen4.c
+++ b/drivers/pci/pci-rcar-gen4.c
@@ -112,6 +112,15 @@ struct rcar_gen4_pcie {
      size_t            firmware_size;
  };
+/**
+ * struct rcar_gen4_pcie_plat - Renesas R-Car Gen4 DW PCIe controller platform data
+ *
+ * @probed: Controller was started

This commit is not sufficient, please explain that only a single probe off
all compatible controllers on the system can only be done once due to complex
reset reasons.
That is already in the commit message, this here is only an abbreviated description of the field in platdata. Would you like to have lengthy descriptions for structure fields ?

Reply via email to