From: Alex Elder <elder@riscstar.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
bhelgaas@google.com, vkoul@kernel.org, kishon@kernel.org
Cc: dlan@gentoo.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, p.zabel@pengutronix.de,
tglx@linutronix.de, johan+linaro@kernel.org,
thippeswamy.havalige@amd.com, namcao@linutronix.de,
mayank.rana@oss.qualcomm.com, shradha.t@samsung.com,
inochiama@gmail.com, quic_schintav@quicinc.com,
fan.ni@samsung.com, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org, linux-pci@vger.kernel.org,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/6] dt-bindings: phy: spacemit: introduce PCIe root complex
Date: Wed, 13 Aug 2025 13:46:57 -0500 [thread overview]
Message-ID: <20250813184701.2444372-4-elder@riscstar.com> (raw)
In-Reply-To: <20250813184701.2444372-1-elder@riscstar.com>
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@riscstar.com>
---
.../bindings/pci/spacemit,k1-pcie-rc.yaml | 141 ++++++++++++++++++
1 file changed, 141 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/spacemit,k1-pcie-rc.yaml
diff --git a/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-rc.yaml b/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-rc.yaml
new file mode 100644
index 0000000000000..6bcca2f91a6fd
--- /dev/null
+++ b/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-rc.yaml
@@ -0,0 +1,141 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/pci/spacemit,k1-pcie-rc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: SpacemiT K1 PCI Express Root Complex
+
+maintainers:
+ - Alex Elder <elder@riscstar.com>
+
+description:
+ The SpacemiT K1 SoC PCIe root complex controller is based on the
+ Synopsys DesignWare PCIe IP.
+
+properties:
+ compatible:
+ const: spacemit,k1-pcie-rc.yaml
+
+ reg:
+ items:
+ - description: DesignWare PCIe registers
+ - description: ATU address space
+ - description: PCIe configuration space
+ - description: Link control registers
+
+ reg-names:
+ items:
+ - const: dbi
+ - const: atu
+ - const: config
+ - const: link
+
+ clocks:
+ items:
+ - description: DWC PCIe Data Bus Interface (DBI) clock
+ - description: DWC PCIe application AXI-bus Master interface clock
+ - description: DWC PCIe application AXI-bus Slave interface clock.
+
+ clock-names:
+ items:
+ - const: dbi
+ - const: mstr
+ - const: slv
+
+ resets:
+ items:
+ - description: DWC PCIe Data Bus Interface (DBI) reset
+ - description: DWC PCIe application AXI-bus Master interface reset
+ - description: DWC PCIe application AXI-bus Slave interface reset.
+ - description: Global reset; must be deasserted for PHY to function
+
+ reset-names:
+ items:
+ - const: dbi
+ - const: mstr
+ - const: slv
+ - const: global
+
+ interrupts-extended:
+ maxItems: 1
+
+ spacemit,syscon-pmu:
+ description:
+ PHandle that refers to the APMU system controller, whose
+ regmap is used in managing resets and link state.
+ $ref: /schemas/types.yaml#/definitions/phandle
+
+ device_type:
+ const: pci
+
+ max-link-speed:
+ const: 2
+
+ num-viewport:
+ const: 8
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - clock-names
+ - resets
+ - reset-names
+ - spacemit,syscon-pmu
+ - "#address-cells"
+ - "#size-cells"
+ - device_type
+ - max-link-speed
+ - bus-range
+ - num-viewport
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/clock/spacemit,k1-syscon.h>
+ pcie0: pcie@ca000000 {
+ compatible = "spacemit,k1-pcie-rc";
+ reg = <0x0 0xca000000 0x0 0x00001000>,
+ <0x0 0xca300000 0x0 0x0001ff24>,
+ <0x0 0x8f000000 0x0 0x00002000>,
+ <0x0 0xc0b20000 0x0 0x00001000>;
+ reg-names = "dbi",
+ "atu",
+ "config",
+ "link";
+
+ ranges = <0x01000000 0x8f002000 0x0 0x8f002000 0x0 0x100000>,
+ <0x02000000 0x80000000 0x0 0x80000000 0x0 0x0f000000>;
+
+ clocks = <&syscon_apmu CLK_PCIE0_DBI>,
+ <&syscon_apmu CLK_PCIE0_MASTER>,
+ <&syscon_apmu CLK_PCIE0_SLAVE>;
+ clock-names = "dbi",
+ "mstr",
+ "slv";
+
+ resets = <&syscon_apmu RESET_PCIE0_DBI>,
+ <&syscon_apmu RESET_PCIE0_MASTER>,
+ <&syscon_apmu RESET_PCIE0_SLAVE>,
+ <&syscon_apmu RESET_PCIE0_GLOBAL>;
+ reset-names = "dbi",
+ "mstr",
+ "slv",
+ "global";
+
+ interrupts-extended = <&plic 141>;
+
+ spacemit,syscon-pmu = <&syscon_apmu 0x03cc>;
+
+ #address-cells = <3>;
+ #size-cells = <2>;
+
+ device_type = "pci";
+ max-link-speed = <2>;
+ bus-range = <0x00 0xff>;
+ num-viewport = <8>;
+
+ status = "disabled";
+ };
--
2.48.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-08-13 22:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 18:46 [PATCH 0/6] Introduce SpacemiT K1 PCIe phy and host controller Alex Elder
2025-08-13 18:46 ` [PATCH 1/6] dt-bindings: phy: spacemit: add SpacemiT PCIe/combo PHY Alex Elder
2025-08-14 2:52 ` Yao Zi
2025-08-14 12:30 ` Alex Elder
2025-08-14 6:11 ` Krzysztof Kozlowski
2025-08-14 11:59 ` Alex Elder
2025-08-14 20:51 ` Rob Herring
2025-08-14 21:48 ` Alex Elder
2025-08-13 18:46 ` [PATCH 2/6] dt-bindings: phy: spacemit: introduce PCIe PHY Alex Elder
2025-08-14 6:17 ` Krzysztof Kozlowski
2025-08-13 18:46 ` Alex Elder [this message]
2025-08-13 20:49 ` [PATCH 3/6] dt-bindings: phy: spacemit: introduce PCIe root complex Rob Herring (Arm)
2025-08-13 21:21 ` Alex Elder
2025-09-15 8:14 ` Manivannan Sadhasivam
2025-09-19 20:14 ` Alex Elder
2025-09-20 5:55 ` Manivannan Sadhasivam
2025-10-01 2:40 ` Alex Elder
2025-08-13 18:46 ` [PATCH 4/6] phy: spacemit: introduce PCIe/combo PHY Alex Elder
2025-08-13 23:42 ` Inochi Amaoto
2025-08-14 12:15 ` Alex Elder
2025-08-14 22:49 ` Inochi Amaoto
2025-08-14 23:57 ` Yixun Lan
2025-08-13 18:46 ` [PATCH 5/6] PCI: spacemit: introduce SpacemiT PCIe host driver Alex Elder
2025-08-13 21:22 ` Bjorn Helgaas
2025-08-13 21:27 ` Alex Elder
2025-09-19 18:06 ` Alex Elder
2025-09-15 8:09 ` Manivannan Sadhasivam
2025-09-19 22:10 ` Alex Elder
2025-09-20 5:33 ` Manivannan Sadhasivam
2025-10-01 2:40 ` Alex Elder
2025-08-13 18:47 ` [PATCH 6/6] riscv: dts: spacemit: PCIe and PHY-related updates Alex Elder
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=20250813184701.2444372-4-elder@riscstar.com \
--to=elder@riscstar.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=fan.ni@samsung.com \
--cc=inochiama@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mayank.rana@oss.qualcomm.com \
--cc=namcao@linutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=quic_schintav@quicinc.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--cc=spacemit@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=thippeswamy.havalige@amd.com \
--cc=vkoul@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