[PATCH v2 0/2] PCI: microchip: support using either instance 1 or 2

[Conor Dooley]

From: Conor Dooley <conor.dooley at microchip.com>

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.

Cheers,
Conor.

v2:
- try the new reg format before the old one to avoid warnings in the
  new case
- reword $subject for 2/2

CC: Daire McNamara <daire.mcnamara at microchip.com>
CC: Lorenzo Pieralisi <lpieralisi at kernel.org>
CC: Krzysztof Wilczyński <kw at linux.com>
CC: Rob Herring <robh at kernel.org>
CC: Bjorn Helgaas <bhelgaas at google.com>
CC: Krzysztof Kozlowski <krzk+dt at kernel.org>
CC: Conor Dooley <conor+dt at kernel.org>
CC: linux-pci at vger.kernel.org
CC: devicetree at vger.kernel.org
CC: linux-kernel at vger.kernel.org
CC: linux-riscv at lists.infradead.org

Conor Dooley (2):
  dt-bindings: PCI: microchip,pcie-host: fix reg properties
  PCI: microchip: rework reg region handing to support using either
    instance 1 or 2

 .../bindings/pci/microchip,pcie-host.yaml     |  10 +-
 drivers/pci/controller/pcie-microchip-host.c  | 155 +++++++++---------
 2 files changed, 79 insertions(+), 86 deletions(-)

-- 
2.43.0