On Thu, Feb 6, 2014 at 3:56 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Thursday 06 February 2014 14:24:03 Anup Patel wrote: >> > diff --git a/Documentation/devicetree/bindings/pci/linux,pci-virt.txt b/Documentation/devicetree/bindings/pci/linux,pci-virt.txt >> > new file mode 100644 >> > index 000000000000..54668a283498 >> > +- compatible : Must be "linux,pci-virt" >> > + >> > +- ranges : As described in IEEE Std 1275-1994, but must provide >> > + at least a definition of the Configuration Space plus >> > + one or both of IO and Memory Space. >> > + >> > +- #address-cells : Must be 3 >> > + >> > +- #size-cells : Must be 2 >> > + >> > +Configuration Space is assumed to be memory-mapped (as opposed to being >> >> It would be great to have a flag to specify whether Configuration Space is over >> ioports or memory mapped. >> > > I haven't seen config space access through ioport for a long > time on non-x86. Do you have reason to believe that we will need > that? I suggested it to make "pci-virt" useful for x86-world too. > > Arnd -- Anup -- 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
