From: Alex Elder <elder@riscstar.com>
To: Rob Herring <robh@kernel.org>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, bhelgaas@google.com,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
dlan@gentoo.org, guodong@riscstar.com,
devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
spacemit@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/7] dt-bindings: pci: spacemit: introduce PCIe host controller
Date: Thu, 30 Oct 2025 20:37:16 -0500 [thread overview]
Message-ID: <9e60f7ed-7afc-4151-a301-4a0832b9105f@riscstar.com> (raw)
In-Reply-To: <20251031005718.GA539812-robh@kernel.org>
On 10/30/25 7:58 PM, Rob Herring wrote:
> On Thu, Oct 30, 2025 at 05:02:54PM -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@riscstar.com>
>> ---
>> .../bindings/pci/spacemit,k1-pcie-host.yaml | 157 ++++++++++++++++++
>> 1 file changed, 157 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..58239a155ecc0
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pci/spacemit,k1-pcie-host.yaml
>> @@ -0,0 +1,157 @@
>> +# 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@riscstar.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.
>
> Wrap lines at 80.
OK.
>> +
>> +allOf:
>> + - $ref: /schemas/pci/snps,dw-pcie.yaml#
>> +
>> +properties:
>> + compatible:
>> + const: spacemit,k1-pcie
>> +
>> + 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
>> +
>> + reset-names:
>> + items:
>> + - const: dbi
>> + - const: mstr
>> + - const: slv
>> +
>> + interrupts:
>> + items:
>> + - description: Interrupt used for MSIs
>> +
>> + interrupt-names:
>> + const: msi
>> +
>> + spacemit,apmu:
>> + $ref: /schemas/types.yaml#/definitions/phandle-array
>> + description:
>> + A phandle that refers to the APMU system controller, whose
>> + regmap is used in managing resets and link state, along with
>> + and offset of its reset control register.
>> + items:
>> + - items:
>> + - description: phandle to APMU system controller
>> + - description: register offset
>> +
>> +patternProperties:
>> + '^pcie?@':
>
> It's always PCIe, so drop the '?'.
I'll fix that.
> With that,
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Thanks for the review.
-Alex
next prev parent reply other threads:[~2025-10-31 1:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 22:02 [PATCH v4 0/7] Introduce SpacemiT K1 PCIe phy and host controller Alex Elder
2025-10-30 22:02 ` [PATCH v4 1/7] dt-bindings: phy: spacemit: add SpacemiT PCIe/combo PHY Alex Elder
2025-10-30 22:02 ` [PATCH v4 2/7] dt-bindings: phy: spacemit: introduce PCIe PHY Alex Elder
2025-10-30 22:02 ` [PATCH v4 3/7] dt-bindings: pci: spacemit: introduce PCIe host controller Alex Elder
2025-10-31 0:58 ` Rob Herring
2025-10-31 1:37 ` Alex Elder [this message]
2025-10-30 22:02 ` [PATCH v4 4/7] phy: spacemit: introduce PCIe/combo PHY Alex Elder
2025-11-02 21:52 ` kernel test robot
2025-11-02 22:25 ` kernel test robot
2025-10-30 22:02 ` [PATCH v4 5/7] PCI: spacemit: introduce SpacemiT PCIe host driver Alex Elder
2025-10-30 23:08 ` Bjorn Helgaas
2025-10-31 1:16 ` Alex Elder
2025-10-31 22:31 ` Aurelien Jarno
2025-11-03 16:51 ` Alex Elder
2025-10-30 22:02 ` [PATCH v4 6/7] riscv: dts: spacemit: add a PCIe regulator Alex Elder
2025-10-30 22:02 ` [PATCH v4 7/7] 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=9e60f7ed-7afc-4151-a301-4a0832b9105f@riscstar.com \
--to=elder@riscstar.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=guodong@riscstar.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=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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).