[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aO2tkGSUTYssSaVf@pie>
Date: Tue, 14 Oct 2025 01:55:28 +0000
From: Yao Zi <ziyao@...root.org>
To: Alex Elder <elder@...cstar.com>, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, bhelgaas@...gle.com, lpieralisi@...nel.org,
kwilczynski@...nel.org, mani@...nel.org, vkoul@...nel.org,
kishon@...nel.org
Cc: dlan@...too.org, guodong@...cstar.com, pjw@...nel.org,
palmer@...belt.com, aou@...s.berkeley.edu, alex@...ti.fr,
p.zabel@...gutronix.de, christian.bruel@...s.st.com,
shradha.t@...sung.com, krishna.chundru@....qualcomm.com,
qiang.yu@....qualcomm.com, namcao@...utronix.de,
thippeswamy.havalige@....com, inochiama@...il.com,
devicetree@...r.kernel.org, linux-pci@...r.kernel.org,
linux-phy@...ts.infradead.org, spacemit@...ts.linux.dev,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/7] dt-bindings: pci: spacemit: introduce PCIe host
controller
On Mon, Oct 13, 2025 at 10:35:20AM -0500, Alex Elder wrote:
> Add the Device Tree binding for the PCIe root complex found on the
> SpacemiT K1 SoC. This device is derived from the Synopsys Designware
> PCIe IP. It supports up to three PCIe ports operating at PCIe gen 2
> link speeds (5 GT/sec). One of the ports uses a combo PHY, which is
> typically used to support a USB 3 port.
>
> Signed-off-by: Alex Elder <elder@...cstar.com>
> ---
> v2: - Renamed the binding, using "host controller"
> - Added '>' to the description, and reworded it a bit
> - Added reference to /schemas/pci/snps,dw-pcie.yaml
> - Fixed and renamed the compatible string
> - Renamed the PMU property, and fixed its description
> - Consistently omit the period at the end of descriptions
> - Renamed the "global" clock to be "phy"
> - Use interrupts rather than interrupts-extended, and name the
> one interrupt "msi" to make clear its purpose
> - Added a vpcie3v3-supply property
> - Dropped the max-link-speed property
> - Changed additionalProperties to unevaluatedProperties
> - Dropped the label and status property from the example
>
> .../bindings/pci/spacemit,k1-pcie-host.yaml | 156 ++++++++++++++++++
> 1 file changed, 156 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pci/spacemit,k1-pcie-host.yaml
>
> diff --git a/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-host.yaml b/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-host.yaml
> new file mode 100644
> index 0000000000000..87745d49c53a1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-host.yaml
> @@ -0,0 +1,156 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pci/spacemit,k1-pcie-host.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SpacemiT K1 PCI Express Host Controller
> +
> +maintainers:
> + - Alex Elder <elder@...cstar.com>
> +
> +description: >
> + The SpacemiT K1 SoC PCIe host controller is based on the Synopsys
> + DesignWare PCIe IP. The controller uses the DesignWare built-in
> + MSI interrupt controller, and supports 256 MSIs.
> +
> +allOf:
> + - $ref: /schemas/pci/snps,dw-pcie.yaml#
> +
> +properties:
...
> + num-viewport:
> + const: 8
This property has been deprecated for a long time, and the driver now
detects viewports at runtime since commit 281f1f99cf3a (PCI: dwc: Detect
number of iATU windows, 2020-11-05), IOW, it makes no effect with the
current mainline DWC PCIe driver. Is it really necessary?
Best regards,
Yao Zi
Powered by blists - more mailing lists