From: Rob Herring <robh@kernel.org>
To: Jacky Chou <jacky_chou@aspeedtech.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-aspeed@lists.ozlabs.org, linux-pci@vger.kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Andrew Jeffery" <andrew@aj.id.au>,
openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v5 2/8] dt-bindings: PCI: Add ASPEED PCIe RC support
Date: Mon, 17 Nov 2025 16:13:57 -0600 [thread overview]
Message-ID: <20251117221357.GA806266-robh@kernel.org> (raw)
In-Reply-To: <20251117-upstream_pcie_rc-v5-2-b4a198576acf@aspeedtech.com>
On Mon, Nov 17, 2025 at 08:37:49PM +0800, Jacky Chou wrote:
> ASPEED AST2600 provides one PCIe RC for Gen2 and AST2700 provides three
> PCIe RC for two Gen4 and one Gen2. All of these RCs have just one root
> port to connect to PCIe device. And also have Mem, I/O access, legacy
> interrupt and MSI.
>
> Signed-off-by: Jacky Chou <jacky_chou@aspeedtech.com>
> ---
> .../bindings/pci/aspeed,ast2600-pcie.yaml | 149 +++++++++++++++++++++
> 1 file changed, 149 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/aspeed,ast2600-pcie.yaml b/Documentation/devicetree/bindings/pci/aspeed,ast2600-pcie.yaml
> new file mode 100644
> index 000000000000..459b5c49657a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pci/aspeed,ast2600-pcie.yaml
> @@ -0,0 +1,149 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pci/aspeed,ast2600-pcie.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ASPEED PCIe Root Complex Controller
> +
> +maintainers:
> + - Jacky Chou <jacky_chou@aspeedtech.com>
> +
> +description:
> + The ASPEED PCIe Root Complex controller provides PCI Express Root Complex
> + functionality for ASPEED SoCs, such as the AST2600 and AST2700.
> + This controller enables connectivity to PCIe endpoint devices, supporting
> + memory and I/O windows, MSI and INTx interrupts, and integration with
> + the SoC's clock, reset, and pinctrl subsystems. On AST2600, the PCIe Root
> + Port device number is always 8.
> +
> +properties:
> + compatible:
> + enum:
> + - aspeed,ast2600-pcie
> + - aspeed,ast2700-pcie
> +
> + reg:
> + maxItems: 1
> +
> + ranges:
> + minItems: 2
> + maxItems: 2
> +
> + interrupts:
> + maxItems: 1
> + description: INTx and MSI interrupt
> +
> + resets:
> + items:
> + - description: PCIe controller reset
> +
> + reset-names:
> + items:
> + - const: h2x
> +
> + aspeed,ahbc:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Phandle to the ASPEED AHB Controller (AHBC) syscon node.
> + This reference is used by the PCIe controller to access
> + system-level configuration registers related to the AHB bus.
> + To enable AHB access for the PCIe controller.
> +
> + aspeed,pciecfg:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Phandle to the ASPEED PCIe configuration syscon node.
> + This reference allows the PCIe controller to access
> + SoC-specific PCIe configuration registers. There are the others
> + functions such PCIe RC and PCIe EP will use this common register
> + to configure the SoC interfaces.
> +
> + interrupt-controller: true
> +
> +allOf:
> + - $ref: /schemas/pci/pci-host-bridge.yaml#
> + - $ref: /schemas/interrupt-controller/msi-controller.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: aspeed,ast2600-pcie
> + then:
> + required:
> + - aspeed,ahbc
> + else:
> + properties:
> + aspeed,ahbc: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: aspeed,ast2700-pcie
> + then:
> + required:
> + - aspeed,pciecfg
> + else:
> + properties:
> + aspeed,pciecfg: false
> +
> +required:
> + - reg
> + - interrupts
> + - bus-range
> + - ranges
> + - resets
> + - reset-names
> + - msi-controller
> + - interrupt-controller
> + - interrupt-map-mask
> + - interrupt-map
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/ast2600-clock.h>
> +
> + pcie0: pcie@1e770000 {
> + compatible = "aspeed,ast2600-pcie";
> + device_type = "pci";
> + reg = <0x1e770000 0x100>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>;
> + bus-range = <0x00 0xff>;
> +
> + ranges = <0x01000000 0x0 0x00018000 0x00018000 0x0 0x00008000
> + 0x02000000 0x0 0x60000000 0x60000000 0x0 0x20000000>;
> +
> + resets = <&syscon ASPEED_RESET_H2X>;
> + reset-names = "h2x";
> +
> + #interrupt-cells = <1>;
> + msi-controller;
> +
> + aspeed,ahbc = <&ahbc>;
> +
> + interrupt-controller;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0 0 0 1 &pcie0 0>,
> + <0 0 0 2 &pcie0 1>,
> + <0 0 0 3 &pcie0 2>,
> + <0 0 0 4 &pcie0 3>;
> +
> + pcie@8,0 {
This node and the properties need to be in the schema along with a ref
to pci-pci-bridge.yaml.
> + reg = <0x804000 0 0 0 0>;
The address should not have the bus number as it is dynamic.
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + resets = <&syscon ASPEED_RESET_PCIE_RC_O>;
> + reset-names = "perst";
Not sure this name is correct. PERST is a signal on the connector going
downstream to the endpoint.
> + clocks = <&syscon ASPEED_CLK_GATE_BCLK>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_pcierc1_default>;
> + phys = <&pcie_phy1>;
> + ranges;
> + };
> + };
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-11-17 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:37 [PATCH v5 0/8] Add ASPEED PCIe Root Complex support Jacky Chou
2025-11-17 12:37 ` [PATCH v5 1/8] dt-bindings: phy: aspeed: Add ASPEED PCIe PHY Jacky Chou
2025-11-17 12:37 ` [PATCH v5 2/8] dt-bindings: PCI: Add ASPEED PCIe RC support Jacky Chou
2025-11-17 22:13 ` Rob Herring [this message]
2025-11-19 3:11 ` Jacky Chou
2025-11-17 12:37 ` [PATCH v5 3/8] dt-bindings: pinctrl: aspeed,ast2600-pinctrl: Add PCIe RC PERST# group Jacky Chou
2025-11-19 13:51 ` Linus Walleij
2025-11-17 12:37 ` [PATCH v5 4/8] ARM: dts: aspeed-g6: Add PCIe RC and PCIe PHY node Jacky Chou
2025-11-17 12:37 ` [PATCH v5 5/8] PHY: aspeed: Add ASPEED PCIe PHY driver Jacky Chou
2025-11-17 12:37 ` [PATCH v5 6/8] PCI: Add FMT, TYPE and CPL status definition for TLP header Jacky Chou
2025-11-17 17:28 ` Bjorn Helgaas
2025-11-19 2:27 ` Jacky Chou
2025-11-17 12:37 ` [PATCH v5 7/8] PCI: aspeed: Add ASPEED PCIe RC driver Jacky Chou
2025-11-17 12:37 ` [PATCH v5 8/8] MAINTAINERS: " Jacky Chou
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=20251117221357.GA806266-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=andrew@codeconstruct.com.au \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacky_chou@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).