From: Kever Yang <kever.yang@rock-chips.com>
To: heiko@sntech.de
Cc: linux-rockchip@lists.infradead.org,
"Kever Yang" <kever.yang@rock-chips.com>,
"Rob Herring" <robh@kernel.org>, "Simon Xue" <xxm@rock-chips.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, "Krzysztof Wilczyński" <kw@linux.com>,
linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
devicetree@vger.kernel.org,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/7] dt-bindings: PCI: dwc: rockchip: Add rk3562 support
Date: Tue, 15 Apr 2025 13:18:49 +0800 [thread overview]
Message-ID: <20250415051855.59740-2-kever.yang@rock-chips.com> (raw)
In-Reply-To: <20250415051855.59740-1-kever.yang@rock-chips.com>
rk3562 is using the same dwc controller as rk3576.
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
---
Changes in v4:
- Collect ack tag;
Changes in v3:
- Rebase the change base on rk3576 pcie patches
Changes in v2: None
.../devicetree/bindings/pci/rockchip-dw-pcie.yaml | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml b/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml
index 4764a0173ae4..6c6d828ce964 100644
--- a/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml
+++ b/Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml
@@ -22,6 +22,7 @@ properties:
- const: rockchip,rk3568-pcie
- items:
- enum:
+ - rockchip,rk3562-pcie
- rockchip,rk3576-pcie
- rockchip,rk3588-pcie
- const: rockchip,rk3568-pcie
@@ -76,7 +77,9 @@ allOf:
properties:
compatible:
contains:
- const: rockchip,rk3576-pcie
+ enum:
+ - rockchip,rk3562-pcie
+ - rockchip,rk3576-pcie
then:
required:
- msi-map
@@ -85,7 +88,9 @@ allOf:
properties:
compatible:
contains:
- const: rockchip,rk3576-pcie
+ enum:
+ - rockchip,rk3562-pcie
+ - rockchip,rk3576-pcie
then:
properties:
interrupts:
--
2.25.1
next prev parent reply other threads:[~2025-04-15 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 5:18 [PATCH v4 0/7] rockchip: Add rk3562 SoC and evb support Kever Yang
2025-04-15 5:18 ` Kever Yang [this message]
2025-04-19 9:53 ` [PATCH v4 1/7] dt-bindings: PCI: dwc: rockchip: Add rk3562 support Manivannan Sadhasivam
2025-04-15 5:18 ` [PATCH v4 3/7] dt-bindings: rockchip: pmu: Add rk3562 compatible Kever Yang
2025-04-15 5:18 ` [PATCH v4 4/7] dt-bindings: soc: rockchip: Add rk3562 syscon compatibles Kever Yang
2025-04-15 5:18 ` [PATCH v4 5/7] dt-bindings: arm: rockchip: Add rk3562 evb2 board Kever Yang
2025-04-15 5:18 ` [PATCH v4 6/7] arm64: dts: rockchip: add core dtsi for RK3562 Soc Kever Yang
2025-05-01 13:28 ` Heiko Stübner
2025-04-15 5:18 ` [PATCH v4 7/7] arm64: dts: rockchip: Add RK3562 evb2 devicetree Kever Yang
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=20250415051855.59740-2-kever.yang@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=xxm@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox