On Thu, Oct 30, 2014 at 05:45:41PM +0000, Jason Gunthorpe wrote: > On Thu, Oct 30, 2014 at 05:39:15PM +0000, Liviu Dudau wrote: > > > But of_pci_get_host_bridge_resources() does not request the resources, it only > > creates them out of the DT ranges. If/when the driver decides the list of > > resources is correct and it can work with it can also request them and use > > whatever domain number allocation strategy it wants (auto-incrementing or DT > > based). So I don't think the global sequencing is broken here. > > So how does mvebu now allocate a unique domain number per mvebu_pcie? > > Which hw_pci callback should do that? It is done through core code in pci_create_root_bus(), that in turn calls pci_bus_assign_domain_nr() which is implemented now in pcibios for arm, it is all in patch 2. What Liviu is saying is correct, it all depends on *when* the resource naming should be applied. For code relying on pcibios the setup hw_pci hook() is likely to be the place where resources are requested and the domain is not set-up yet there with the generic PCI domains approach, hence I can't attach a domain number to the resource names in question. Lorenzo -- 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
