From: Andy Yan <andy.yan@rock-chips.com>
To: heiko@sntech.de
Cc: kever.yang@rock-chips.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: [PATCH v2 1/4] dt-bindings: Add doc about rk3308 General Register Files
Date: Mon, 21 Oct 2019 16:45:55 +0800 [thread overview]
Message-ID: <20191021084555.28356-1-andy.yan@rock-chips.com> (raw)
In-Reply-To: <20191021084437.28279-1-andy.yan@rock-chips.com>
RK3308 GRF is divided into four sections: GRF, SGRF,
DETECTGRF, COREGRF. This patch add documentation for
it.
Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
---
Changes in v2: None
.../devicetree/bindings/soc/rockchip/grf.txt | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.txt b/Documentation/devicetree/bindings/soc/rockchip/grf.txt
index d7debec26ba4..61d89749918a 100644
--- a/Documentation/devicetree/bindings/soc/rockchip/grf.txt
+++ b/Documentation/devicetree/bindings/soc/rockchip/grf.txt
@@ -10,6 +10,12 @@ From RK3368 SoCs, the GRF is divided into two sections,
On RK3328 SoCs, the GRF adds a section for USB2PHYGRF,
+ON RK3308 SoC, the GRF is divided into four sections:
+- GRF, used for general non-secure system,
+- SGRF, used for general secure system,
+- DETECTGRF, used for audio codec system,
+- COREGRF, used for pvtm,
+
Required Properties:
- compatible: GRF should be one of the following:
@@ -19,10 +25,15 @@ Required Properties:
- "rockchip,rk3188-grf", "syscon": for rk3188
- "rockchip,rk3228-grf", "syscon": for rk3228
- "rockchip,rk3288-grf", "syscon": for rk3288
+ - "rockchip,rk3308-grf", "syscon": for rk3308
- "rockchip,rk3328-grf", "syscon": for rk3328
- "rockchip,rk3368-grf", "syscon": for rk3368
- "rockchip,rk3399-grf", "syscon": for rk3399
- "rockchip,rv1108-grf", "syscon": for rv1108
+- compatible: DETECTGRF should be one of the following:
+ - "rockchip,rk3308-detect-grf", "syscon": for rk3308
+- compatilbe: COREGRF should be one of the following:
+ - "rockchip,rk3308-core-grf", "syscon": for rk3308
- compatible: PMUGRF should be one of the following:
- "rockchip,px30-pmugrf", "syscon": for px30
- "rockchip,rk3368-pmugrf", "syscon": for rk3368
--
2.17.1
next prev parent reply other threads:[~2019-10-21 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 8:44 [PATCH v2 0/4] Add basic dts support for RK3308 Andy Yan
2019-10-21 8:45 ` Andy Yan [this message]
2019-10-25 21:32 ` [PATCH v2 1/4] dt-bindings: Add doc about rk3308 General Register Files Rob Herring
2019-10-27 17:45 ` Heiko Stuebner
2019-10-21 8:46 ` [PATCH v2 2/4] arm64: dts: rockchip: Add core dts for RK3308 SOC Andy Yan
2019-10-27 17:45 ` Heiko Stuebner
2019-10-21 8:46 ` [PATCH v2 3/4] dt-bindings: Add doc for rk3308-evb Andy Yan
2019-10-25 21:33 ` Rob Herring
2019-10-27 17:44 ` Heiko Stuebner
2019-10-21 8:46 ` [PATCH v2 4/4] arm64: dts: rockchip: Add basic dts for RK3308 EVB Andy Yan
2019-10-27 17:55 ` Heiko Stuebner
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=20191021084555.28356-1-andy.yan@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®