From 4295424a6ecfebc683106cf9d2c68007f10620d7 Mon Sep 17 00:00:00 2001 From: Gavin Shan Date: Thu, 11 Aug 2016 14:55:14 +1000 Subject: core/pci: Print CRS retry times It's useful to know the CRS retry times before the PCI device is detected successfully. In PCI hot add case, it usually indicates time consumed for the adapter's firmware to be partially ready (responsive PCI config space). Signed-off-by: Gavin Shan Signed-off-by: Stewart Smith --- core/pci.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'core') diff --git a/core/pci.c b/core/pci.c index c9b5e16..30307c9 100644 --- a/core/pci.c +++ b/core/pci.c @@ -140,7 +140,7 @@ static struct pci_device *pci_scan_one(struct phb *phb, struct pci_device *paren uint16_t capreg; bool had_crs = false; - for (retries = 40; retries; retries--) { + for (retries = 0; retries < 40; retries++) { rc = pci_cfg_read32(phb, bdfn, 0, &vdid); if (rc) return NULL; @@ -156,7 +156,7 @@ static struct pci_device *pci_scan_one(struct phb *phb, struct pci_device *paren return NULL; } if (had_crs) - PCIDBG(phb, bdfn, "Probe success after CRS\n"); + PCIDBG(phb, bdfn, "Probe success after %d CRS\n", retries); /* Perform a dummy write to the device in order for it to * capture it's own bus number, so any subsequent error -- cgit v1.1