On Thursday 30 October 2014 11:45:41 Jason Gunthorpe wrote:

On Thu, Oct 30, 2014 at 05:39:15PM +0000, Liviu Dudau wrote:

quoted

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?

I believe the answer to that is that the mvebu PCIe driver currently only
supports one domain, and it will have the unique number '0', which is the
default.

Which hw_pci callback should do that?

I think the purpose Lorenzo's patches (more to come) is to obsolete all
of the hw_pci callbacks for modern drivers.

	Arnd