261 	 * as read-only but this mvebu controller has it as read-write and must  in mvebu_pcie_setup_hw()
279 	 * Note that this mvebu PCI Bridge does not have compliant Type 1  in mvebu_pcie_setup_hw()
286 	 * different things: they are aliased into internal mvebu registers  in mvebu_pcie_setup_hw()
291 	 * access to configuration space via internal mvebu registers or  in mvebu_pcie_setup_hw()
294 	 * also via standard mvebu way for accessing PCI config space.  in mvebu_pcie_setup_hw()
587 		 * secondary bus number which is mvebu local bus number.  in mvebu_pci_bridge_emul_base_conf_read()
923 	 * Older mvebu hardware provides PCIe Capability structure only in  in mvebu_pci_bridge_emul_init()
934 	 * Set physical slot number to port+1 as mvebu ports are indexed from  in mvebu_pci_bridge_emul_init()
936 	 * as Root Port which is not mvebu case.  in mvebu_pci_bridge_emul_init()
1046 	.name = "mvebu-INTx",
1121 	/* Interrupt support on mvebu emulated bridges is not implemented yet */  in mvebu_pcie_map_irq()
1553 		 * PCIe topology exported by mvebu hw is quite complicated. In  in mvebu_pcie_probe()
1572 		 * This means that pci-mvebu.c driver provides "virtual" bus 0  in mvebu_pcie_probe()
1580 		 * configured on the bridge itself. But because mvebu PCI Bridge  in mvebu_pcie_probe()
1585 		 * There are two options how mvebu determinate type of config  in mvebu_pcie_probe()
1599 		 * register 0x1a2c) then mvebu hw determinate type of config  in mvebu_pcie_probe()
1716 		.name = "mvebu-pcie",