linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Christopher Obbard <chris.obbard@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	kernel@collabora.com, Rob Herring <robh@kernel.org>
Subject: [PATCHv4 1/7] dt-bindings: soc: rockchip: add initial rk3588 syscon compatibles
Date: Thu, 24 Nov 2022 15:49:22 +0100	[thread overview]
Message-ID: <20221124144928.35381-2-sebastian.reichel@collabora.com> (raw)
In-Reply-To: <20221124144928.35381-1-sebastian.reichel@collabora.com>

Add IOC and PHP GRF syscon compatibles for RK3588.

Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
---
 Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
index 2ed8cca79b59..e682b407a383 100644
--- a/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
+++ b/Documentation/devicetree/bindings/soc/rockchip/grf.yaml
@@ -20,6 +20,11 @@ properties:
               - rockchip,rk3568-pipe-grf
               - rockchip,rk3568-pipe-phy-grf
               - rockchip,rk3568-usb2phy-grf
+              - rockchip,rk3588-bigcore0-grf
+              - rockchip,rk3588-bigcore1-grf
+              - rockchip,rk3588-ioc
+              - rockchip,rk3588-php-grf
+              - rockchip,rk3588-sys-grf
               - rockchip,rk3588-pcie3-phy-grf
               - rockchip,rk3588-pcie3-pipe-grf
               - rockchip,rv1108-usbgrf
-- 
2.38.1


  reply	other threads:[~2022-11-24 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 14:49 [PATCHv4 0/7] Initial rk3588 DT Sebastian Reichel
2022-11-24 14:49 ` Sebastian Reichel [this message]
2022-11-24 14:49 ` [PATCHv4 2/7] arm64: dts: rockchip: Add rk3588 pinctrl data Sebastian Reichel
2022-11-24 14:49 ` [PATCHv4 3/7] arm64: dts: rockchip: Add base DT for rk3588 SoC Sebastian Reichel
2022-11-24 14:49 ` [PATCHv4 4/7] dt-bindings: arm: rockchip: add initial rk3588 boards Sebastian Reichel
2022-11-24 14:49 ` [PATCHv4 5/7] arm64: dts: rockchip: Add rk3588-evb1 board Sebastian Reichel
2022-11-28  6:56   ` Michael Riesch
2022-11-24 14:49 ` [PATCHv4 6/7] arm64: dts: rockchip: Add rock-5a board Sebastian Reichel
2022-11-28  6:52   ` Michael Riesch
2022-11-24 14:49 ` [PATCHv4 7/7] arm64: dts: rockchip: Add rock-5b board Sebastian Reichel
2022-11-28  6:54   ` Michael Riesch

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=20221124144928.35381-2-sebastian.reichel@collabora.com \
    --to=sebastian.reichel@collabora.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=chris.obbard@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@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).