From: jay.xu@rock-chips.com (Jianqun Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] Documentation: devicetree: rockchip: Document rk3399-evb
Date: Tue, 26 Apr 2016 10:36:45 +0800 [thread overview]
Message-ID: <1461638206-20473-4-git-send-email-jay.xu@rock-chips.com> (raw)
In-Reply-To: <1461638206-20473-1-git-send-email-jay.xu@rock-chips.com>
Use "rockchip,rk3399-evb" compatible string for Rockchip RK3399
evaluation board.
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
---
changes in v3:
- modify title (Rob)
Documentation/devicetree/bindings/arm/rockchip.txt | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.txt b/Documentation/devicetree/bindings/arm/rockchip.txt
index 2549519..6491b56 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.txt
+++ b/Documentation/devicetree/bindings/arm/rockchip.txt
@@ -101,4 +101,8 @@ Rockchip platforms device tree bindings
- Rockchip RK3228 Evaluation board:
Required root node properties:
- - compatible = "rockchip,rk3228-evb", "rockchip,rk3228";
+ - compatible = "rockchip,rk3228-evb", "rockchip,rk3228";
+
+- Rockchip RK3399 evb:
+ Required root node properties:
+ - compatible = "rockchip,rk3399-evb", "rockchip,rk3399";
--
1.9.1
next prev parent reply other threads:[~2016-04-26 2:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 2:36 [PATCH v3 0/4] ARM64: dts: rockchip: add support for RK3399 Jianqun Xu
2016-04-26 2:36 ` [PATCH v3 1/4] Documentation: rockchip-dw-mshc: add description for rk3399 Jianqun Xu
2016-04-26 2:36 ` [PATCH v3 2/4] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs Jianqun Xu
2016-04-26 2:36 ` Jianqun Xu [this message]
2016-04-26 2:36 ` [PATCH 4/4] ARM64: dts: rockchip: add dts file for RK3399 evaluation board Jianqun Xu
2016-04-26 12:37 ` Heiko Stübner
2016-04-26 20:53 ` Doug Anderson
2016-04-27 0:57 ` jay.xu
2016-04-27 0:56 ` jay.xu
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=1461638206-20473-4-git-send-email-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.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