On Thursday 08 October 2015 17:11:32 Arnd Bergmann wrote: > > > --- a/Documentation/devicetree/bindings/pci/host-generic-pci.txt > > > +++ b/Documentation/devicetree/bindings/pci/host-generic-pci.txt > > > @@ -34,7 +34,11 @@ Properties of the host controller node: > > > - #size-cells : Must be 2. > > > > > > - reg : The Configuration Space base address and size, as accessed > > > - from the parent bus. > > > + from the parent bus. The base address corresponds to > > > + bus zero, even though the "bus-range" property may specify > > > + a different starting bus number. The driver must only map > > > + or access the portion of the Configuration Space that > > > + corresponds to the "bus-range" > > I thought we had reached an agreement that it is a bad idea to have a 'reg' > property that lists registers belonging to a different device. > > To further clarify: the argument was to make it mirror what ACPI does for PCI. However, this is unlike what all other devices do with DT, where you have non-overlapping register ranges (start, length) for each device. ACPI as far as I understand it does not give a range for a PCIe host, but instead provides a way to get the start address of the ECAM register area for the domain that the host is part of, and that needs to be the same address for each host in the domain. 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
