From: Bjorn Helgaas <helgaas@kernel.org>
To: Randolph Lin <randolph@andestech.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
jingoohan1@gmail.com, mani@kernel.org, lpieralisi@kernel.org,
kwilczynski@kernel.org, robh@kernel.org, bhelgaas@google.com,
krzk+dt@kernel.org, conor+dt@kernel.org, alex@ghiti.fr,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com, ben717@andestech.com,
inochiama@gmail.com, thippeswamy.havalige@amd.com,
namcao@linutronix.de, shradha.t@samsung.com, pjw@kernel.org,
randolph.sklin@gmail.com, tim609@andestech.com
Subject: Re: [PATCH v8 4/5] PCI: andes: Add Andes QiLai SoC PCIe host driver support
Date: Tue, 21 Oct 2025 12:05:16 -0500 [thread overview]
Message-ID: <20251021170516.GA1193376@bhelgaas> (raw)
In-Reply-To: <20251014120349.656553-5-randolph@andestech.com>
On Tue, Oct 14, 2025 at 08:03:48PM +0800, Randolph Lin wrote:
> Add driver support for DesignWare based PCIe controller in Andes
> QiLai SoC. The driver only supports the Root Complex mode.
> + * Setup the Qilai PCIe IOCP (IO Coherence Port) Read/Write Behaviors to the
> + * Write-Back, Read and Write Allocate mode.
s/Setup/Set up/
s/Qilai/QiLai/
> + * The QiLai SoC PCIe controller's outbound iATU region supports
> + * a maximum size of SZ_4G - 1. To prevent programming failures,
> + * only consider bridge->windows with sizes within this limit.
> + *
> + * To ensure compatibility with most endpoint devices, at least
> + * one memory region must be mapped within the 32-bits address space.
> + */
> +static int qilai_pcie_host_fix_ob_iatu_count(struct dw_pcie_rp *pp)
> +{
> + struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
> + struct device *dev = pci->dev;
> + struct resource_entry *entry;
> + /* Reserved 1 ob iATU for config space */
> + int count = 1;
> + bool ranges_32bits = false;
> + u64 pci_addr;
> + u64 size;
> +
> + resource_list_for_each_entry(entry, &pp->bridge->windows) {
> + if (resource_type(entry->res) != IORESOURCE_MEM)
> + continue;
> +
> + size = resource_size(entry->res);
> + if (size < SZ_4G)
> + count++;
> +
> + pci_addr = entry->res->start - entry->offset;
> + if (pci_addr < SZ_4G)
> + ranges_32bits = true;
> + }
> +
> + if (!ranges_32bits) {
> + dev_err(dev, "Bridge window must contain 32-bits address\n");
> + return -EINVAL;
Is this really a PCI host controller driver probe failure? I assume
there are devices that only have 64-bit BARs and could work fine
without a 32-bit window?
If a device requires a 32-bit BAR, and the PCI core can't assign such
an address, and gracefully decline to enable a device where we
couldn't assign the BAR, I think that would be preferable and would
identify the specific device that doesn't work.
> + }
> +
> + pci->num_ob_windows = count;
> +
> + return 0;
> +}
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Randolph Lin <randolph@andestech.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
jingoohan1@gmail.com, mani@kernel.org, lpieralisi@kernel.org,
kwilczynski@kernel.org, robh@kernel.org, bhelgaas@google.com,
krzk+dt@kernel.org, conor+dt@kernel.org, alex@ghiti.fr,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com, ben717@andestech.com,
inochiama@gmail.com, thippeswamy.havalige@amd.com,
namcao@linutronix.de, shradha.t@samsung.com, pjw@kernel.org,
randolph.sklin@gmail.com, tim609@andestech.com
Subject: Re: [PATCH v8 4/5] PCI: andes: Add Andes QiLai SoC PCIe host driver support
Date: Tue, 21 Oct 2025 12:05:16 -0500 [thread overview]
Message-ID: <20251021170516.GA1193376@bhelgaas> (raw)
In-Reply-To: <20251014120349.656553-5-randolph@andestech.com>
On Tue, Oct 14, 2025 at 08:03:48PM +0800, Randolph Lin wrote:
> Add driver support for DesignWare based PCIe controller in Andes
> QiLai SoC. The driver only supports the Root Complex mode.
> + * Setup the Qilai PCIe IOCP (IO Coherence Port) Read/Write Behaviors to the
> + * Write-Back, Read and Write Allocate mode.
s/Setup/Set up/
s/Qilai/QiLai/
> + * The QiLai SoC PCIe controller's outbound iATU region supports
> + * a maximum size of SZ_4G - 1. To prevent programming failures,
> + * only consider bridge->windows with sizes within this limit.
> + *
> + * To ensure compatibility with most endpoint devices, at least
> + * one memory region must be mapped within the 32-bits address space.
> + */
> +static int qilai_pcie_host_fix_ob_iatu_count(struct dw_pcie_rp *pp)
> +{
> + struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
> + struct device *dev = pci->dev;
> + struct resource_entry *entry;
> + /* Reserved 1 ob iATU for config space */
> + int count = 1;
> + bool ranges_32bits = false;
> + u64 pci_addr;
> + u64 size;
> +
> + resource_list_for_each_entry(entry, &pp->bridge->windows) {
> + if (resource_type(entry->res) != IORESOURCE_MEM)
> + continue;
> +
> + size = resource_size(entry->res);
> + if (size < SZ_4G)
> + count++;
> +
> + pci_addr = entry->res->start - entry->offset;
> + if (pci_addr < SZ_4G)
> + ranges_32bits = true;
> + }
> +
> + if (!ranges_32bits) {
> + dev_err(dev, "Bridge window must contain 32-bits address\n");
> + return -EINVAL;
Is this really a PCI host controller driver probe failure? I assume
there are devices that only have 64-bit BARs and could work fine
without a 32-bit window?
If a device requires a 32-bit BAR, and the PCI core can't assign such
an address, and gracefully decline to enable a device where we
couldn't assign the BAR, I think that would be preferable and would
identify the specific device that doesn't work.
> + }
> +
> + pci->num_ob_windows = count;
> +
> + return 0;
> +}
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-10-21 17:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 12:03 [PATCH v8 0/5] Add support for Andes Qilai SoC PCIe controller Randolph Lin
2025-10-14 12:03 ` Randolph Lin
2025-10-14 12:03 ` [PATCH v8 1/5] PCI: dwc: Allow adjusting the number of ob/ib windows in glue driver Randolph Lin
2025-10-14 12:03 ` Randolph Lin
2025-10-14 12:03 ` [PATCH v8 2/5] dt-bindings: PCI: Add Andes QiLai PCIe support Randolph Lin
2025-10-14 12:03 ` Randolph Lin
2025-10-21 13:30 ` Rob Herring
2025-10-21 13:30 ` Rob Herring
2025-10-14 12:03 ` [PATCH v8 3/5] riscv: dts: andes: Add PCIe node into the QiLai SoC Randolph Lin
2025-10-14 12:03 ` Randolph Lin
2025-10-14 12:03 ` [PATCH v8 4/5] PCI: andes: Add Andes QiLai SoC PCIe host driver support Randolph Lin
2025-10-14 12:03 ` Randolph Lin
2025-10-21 17:05 ` Bjorn Helgaas [this message]
2025-10-21 17:05 ` Bjorn Helgaas
2025-10-23 12:07 ` Randolph Lin
2025-10-23 12:07 ` Randolph Lin
2025-10-14 12:03 ` [PATCH v8 5/5] MAINTAINERS: Add maintainers for Andes QiLai PCIe driver Randolph Lin
2025-10-14 12:03 ` Randolph Lin
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=20251021170516.GA1193376@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ben717@andestech.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=namcao@linutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=randolph.sklin@gmail.com \
--cc=randolph@andestech.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--cc=thippeswamy.havalige@amd.com \
--cc=tim609@andestech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.