From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: daire.mcnamara@microchip.com
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
conor.dooley@microchip.com, lpieralisi@kernel.org, kw@linux.com,
robh@kernel.org, bhelgaas@google.com,
LKML <linux-kernel@vger.kernel.org>,
linux-riscv@lists.infradead.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v3 1/3] PCI: microchip: Fix outbound address translation tables
Date: Fri, 14 Jun 2024 16:17:53 +0300 (EEST) [thread overview]
Message-ID: <77415307-f80c-a34b-b84f-a0febe6f2641@linux.intel.com> (raw)
In-Reply-To: <20240612112213.2734748-2-daire.mcnamara@microchip.com>
On Wed, 12 Jun 2024, daire.mcnamara@microchip.com wrote:
> From: Daire McNamara <daire.mcnamara@microchip.com>
>
> On Microchip PolarFire SoC (MPFS) the PCIe Root Port can be behind one of
> three general-purpose Fabric Interface Controller (FIC) buses that
> encapsulate an AXI-M interface. That FIC is responsible for managing
> the translations of the upper 32-bits of the AXI-M address. On MPFS,
> the Root Port driver needs to take account of that outbound address
> translation done by the parent FIC bus before setting up its own
> outbound address translation tables. In all cases on MPFS,
> the remaining outbound address translation tables are 32-bit only.
>
> Limit the outbound address translation tables to 32-bit only.
>
> Fixes: 6f15a9c9f941 ("PCI: microchip: Add Microchip Polarfire PCIe controller driver")
>
> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
Don't leave spaces between tag lines.
> ---
> drivers/pci/controller/pcie-microchip-host.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pci/controller/pcie-microchip-host.c b/drivers/pci/controller/pcie-microchip-host.c
> index 137fb8570ba2..853adce24492 100644
> --- a/drivers/pci/controller/pcie-microchip-host.c
> +++ b/drivers/pci/controller/pcie-microchip-host.c
> @@ -933,7 +933,7 @@ static int mc_pcie_init_irq_domains(struct mc_pcie *port)
>
> static void mc_pcie_setup_window(void __iomem *bridge_base_addr, u32 index,
> phys_addr_t axi_addr, phys_addr_t pci_addr,
> - size_t size)
> + u64 size)
I don't see how this is related to what is described by the commit
message.
If there's need for this change it should be justified properly and
it looks to me that resource_size_t would be more appropriate here given
the callers use resource_size() to determine this parameter?
> {
> u32 atr_sz = ilog2(size) - 1;
> u32 val;
> @@ -983,7 +983,8 @@ static int mc_pcie_setup_windows(struct platform_device *pdev,
> if (resource_type(entry->res) == IORESOURCE_MEM) {
> pci_addr = entry->res->start - entry->offset;
> mc_pcie_setup_window(bridge_base_addr, index,
> - entry->res->start, pci_addr,
> + entry->res->start & 0xffffffff,
> + pci_addr,
> resource_size(entry->res));
> index++;
> }
> @@ -1117,9 +1118,8 @@ static int mc_platform_init(struct pci_config_window *cfg)
> int ret;
>
> /* Configure address translation table 0 for PCIe config space */
> - mc_pcie_setup_window(bridge_base_addr, 0, cfg->res.start,
> - cfg->res.start,
> - resource_size(&cfg->res));
> + mc_pcie_setup_window(bridge_base_addr, 0, cfg->res.start & 0xffffffff,
> + 0, resource_size(&cfg->res));
Given your commit message, it would be more obvious to the code reader if
the literal is replaced with something like RP_OUTBOUND_TRANS_TBL_MASK
(that is GENMASK(31, 0)). Feel free to come up better name if I didn't
understand all the details right based on your commit message.
--
i.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-06-14 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 11:22 [PATCH v3 0/3] Fix address translations on MPFS PCIe controller daire.mcnamara
2024-06-12 11:22 ` [PATCH v3 1/3] PCI: microchip: Fix outbound address translation tables daire.mcnamara
2024-06-14 13:17 ` Ilpo Järvinen [this message]
2024-06-12 11:22 ` [PATCH v3 2/3] PCI: microchip: Fix inbound " daire.mcnamara
2024-06-14 13:29 ` Ilpo Järvinen
2024-06-19 13:48 ` Daire McNamara
2024-06-12 11:22 ` [PATCH v3 3/3] dt-bindings: PCI: microchip,pcie-host: allow dma-noncoherent daire.mcnamara
2024-06-13 7:26 ` Krzysztof Kozlowski
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=77415307-f80c-a34b-b84f-a0febe6f2641@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--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