Hello, > The current driver and binding for PolarFire SoC's PCI controller assume > that the root port instance in use is instance 1. The second reg > property constitutes the region encompassing both "control" and "bridge" > registers for both instances. In the driver, a fixed offset is applied to > find the base addresses for instance 1's "control" and "bridge" > registers. The BeagleV Fire uses root port instance 2, so something must > be done so that software can differentiate. This series splits the > second reg property in two, with dedicated "control" and "bridge" > entries so that either instance can be used. Applied to controller/microchip, thank you! [01/02] PCI: dt-bindings: PCI: microchip,pcie-host: Fix reg properties https://git.kernel.org/pci/pci/c/ae5ebdb405dd [02/02] PCI: microchip: Rework reg region handing to support using either instance 1 or 2 https://git.kernel.org/pci/pci/c/e071e6bd9940 Krzysztof