On Thursday 06 February 2014, Russell King - ARM Linux wrote: > On Thu, Feb 06, 2014 at 09:28:52AM +0100, Arnd Bergmann wrote: > > It certainly seems workable. OTOH if we just manage to do a > > helper that scans the OF ranges, allocates the I/O window, > > remaps it and calls the existing pci_add_resource_offset() > > helper, PCI host drivers don't need to worry about the > > io_offsets computation either and just need to pull out the > > correct window locations if they need to set up the hardware > > translation windows (which I'd hope we can often let the boot > > loader take care of). ... > So, whenever you enumerate a PCI bus, and read the resource information > out of the BARs, you must know how that address region specified in > the BAR as a bus address maps to the host address space. > None of that contradicts what I wrote. Please try to understand what I suggested, which is to have a common way to communicate that information from DT to the PCI core without involving the PCI host bridge driver. All the bus scanning is done in common code, which already knows how to factor in io_offset and mem_offset. The mem_offset can be trivially computed from the ranges property, and the io_offset is known by the time we call pci_ioremap_io() or rather a replacement such as the one I proposed that also contains an allocator. 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
