On Wednesday 13 February 2013, Jason Gunthorpe wrote: > > You seem to propose a global regs = <...> property under > > pcie-controller, but indexing using marvell,pcie-port cannot work. PCIe > > interfaces are identified by two values (port,lane), so we have 0.0, > > 0.1, 0.2, 0.3, 1.0, 1.1, 1.2, 1.3, 2.0 and 3.0 on MV78460. I really > > would like to avoid having bizarre computations to find which entry in > > this big regs = <...> array correspond to a given PCIe interface. > > Well, using the 'global' regs is an easy way to avoid the complexity with > address translation and 'assigned-addresses'. So some way to translate > between link # and regs index is necessary. How about using the PCI > device number? Device number 1 is regs entry 0, 2 is regs entry 1, etc. Or you could use the "reg-names" property. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
