Intel I350 mini-PCIe card (igb) on Mirabox (mvebu / Armada 370)
Jason Gunthorpe
jgunthorpe at obsidianresearch.com
Tue Mar 25 18:24:04 EDT 2014
On Tue, Mar 25, 2014 at 10:03:29PM +0000, Neil Greatorex wrote:
> I then replaced it with mdelay(1000) out of interest, and it succeeded
> in detecting the card at boot. It then proceeded exactly as described
> by Willy in his later e-mail (it successfully registers an MSI-X
> interrupt for one port, and then proceeds to implode).
Seem to confirm not enough time after reset..
Try this (untested) debugging patch:
diff --git a/drivers/pci/host/pci-mvebu.c b/drivers/pci/host/pci-mvebu.c
index b8f2fc9..74e2e20 100644
--- a/drivers/pci/host/pci-mvebu.c
+++ b/drivers/pci/host/pci-mvebu.c
@@ -999,6 +999,34 @@ static int mvebu_pcie_probe(struct platform_device *pdev)
mvebu_pcie_set_local_dev_nr(port, 1);
+ /* Wait for the link to come up */
+ if (!mvebu_pcie_link_up(port)) {
+ unsigned int I;
+
+ dev_info(&pdev->dev, "Waiting for link up\n");
+ for (I = 0; I != 100; I++) {
+ udelay(100);
+ if (mvebu_pcie_link_up(port))
+ break;
+ }
+ dev_info(&pdev->dev, "Link is %u\n",
+ mvebu_pcie_link_up(port));
+ }
+
+ /* Turn on CRS Software Visibility */
+ mvebu_writel(port, mvebu_readl(port, PCIE_CTRL_OFF) | BIT(31),
+ PCIE_CTRL_OFF);
+
+ /* Read the vendor ID from the connected device */
+ mvebu_writel(port, PCIE_CONF_ADDR(1, 0, 0), PCIE_CONF_ADDR_OFF);
+ dev_info(&pdev->dev, "Vendor ID is %x\n",
+ mvebu_readl(port, PCIE_CONF_DATA_OFF));
+ msleep(1000);
+ mvebu_writel(port, PCIE_CONF_ADDR(1, 0, 0), PCIE_CONF_ADDR_OFF);
+ dev_info(&pdev->dev, "Try 2: Vendor ID is %x\n",
+ mvebu_readl(port, PCIE_CONF_DATA_OFF));
+
+
port->dn = child;
spin_lock_init(&port->conf_lock);
mvebu_sw_pci_bridge_init(port);
Also, are you using the "reset-gpios" DT property? If so, ensure the
delay is at least 100 ms.
There is still an oddball problem:
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6710 (rev 01) (prog-if 00 [Normal decode])
Bus: primary=00, secondary=01, subordinate=02, sec-latency=0
I think the subordinate bus should be 01 - not sure what is going on
there... Maybe related to the rescan problem..
Jason
More information about the linux-arm-kernel
mailing list