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>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Frank Wang <frank.wang@rock-chips.com>,
Detlev Casanova <detlev.casanova@collabora.com>,
Yao Zi <ziyao@disroot.org>,
linux-kernel@vger.kernel.org,
Shresth Prasad <shresthprasad7@gmail.com>,
Andy Yan <andy.yan@rock-chips.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Subject: [PATCH v4 4/7] dt-bindings: soc: rockchip: Add rk3562 syscon compatibles
Date: Tue, 15 Apr 2025 13:18:52 +0800 [thread overview]
Message-ID: <20250415051855.59740-5-kever.yang@rock-chips.com> (raw)
In-Reply-To: <20250415051855.59740-1-kever.yang@rock-chips.com>
Add all syscon compatibles for rk3562.
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: None
Changes in v2: None
Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
index 2f61c1b95fea..8cbf5b6772dd 100644
--- a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
+++ b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
@@ -18,6 +18,12 @@ properties:
- rockchip,rk3528-ioc-grf
- rockchip,rk3528-vo-grf
- rockchip,rk3528-vpu-grf
+ - rockchip,rk3562-ioc-grf
+ - rockchip,rk3562-peri-grf
+ - rockchip,rk3562-pipephy-grf
+ - rockchip,rk3562-pmu-grf
+ - rockchip,rk3562-sys-grf
+ - rockchip,rk3562-usbphy-grf
- rockchip,rk3566-pipe-grf
- rockchip,rk3568-pcie3-phy-grf
- rockchip,rk3568-pipe-grf
@@ -82,6 +88,7 @@ properties:
- rockchip,rk3368-pmugrf
- rockchip,rk3399-grf
- rockchip,rk3399-pmugrf
+ - rockchip,rk3562-pmu-grf
- rockchip,rk3568-grf
- rockchip,rk3568-pmugrf
- rockchip,rk3576-ioc-grf
--
2.25.1
next prev parent reply other threads:[~2025-04-15 5:39 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 ` [PATCH v4 1/7] dt-bindings: PCI: dwc: rockchip: Add rk3562 support Kever Yang
2025-04-19 9:53 ` 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 ` Kever Yang [this message]
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-5-kever.yang@rock-chips.com \
--to=kever.yang@rock-chips.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=frank.wang@rock-chips.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shresthprasad7@gmail.com \
--cc=ziyao@disroot.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