From: Daire McNamara <daire.mcnamara@microchip.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-pci@vger.kernel.org,
"Conor Dooley" <conor.dooley@microchip.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/2] PCI: microchip: support using either instance 1 or 2
Date: Fri, 28 Jun 2024 10:04:36 +0100 [thread overview]
Message-ID: <Zn58pDsX5YZL/pTD@daire-X570> (raw)
In-Reply-To: <20240612-outfield-gummy-388a36d95100@spud>
With the proviso of fixing the axi_/apb_ nit
Acked-by: Daire McNamara <daire.mcnamara@microchip.com>
On Wed, Jun 12, 2024 at 11:57:54AM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@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@microchip.com>
> CC: Lorenzo Pieralisi <lpieralisi@kernel.org>
> CC: Krzysztof Wilczyński <kw@linux.com>
> CC: Rob Herring <robh@kernel.org>
> CC: Bjorn Helgaas <bhelgaas@google.com>
> CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
> CC: Conor Dooley <conor+dt@kernel.org>
> CC: linux-pci@vger.kernel.org
> CC: devicetree@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: linux-riscv@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
>
>
prev parent reply other threads:[~2024-06-28 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 10:57 [PATCH v2 0/2] PCI: microchip: support using either instance 1 or 2 Conor Dooley
2024-06-12 10:57 ` [PATCH v2 1/2] dt-bindings: PCI: microchip,pcie-host: fix reg properties Conor Dooley
2024-06-12 10:57 ` [PATCH v2 2/2] PCI: microchip: rework reg region handing to support using either instance 1 or 2 Conor Dooley
2024-06-28 9:02 ` Daire McNamara
2024-06-28 9:04 ` Daire McNamara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zn58pDsX5YZL/pTD@daire-X570 \
--to=daire.mcnamara@microchip.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox