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>, devicetree@vger.kernel.org, Jianqun Xu <jay.xu@rock-chips.com>, Liang Chen <cl@rock-chips.com>, Brian Norris <briannorris@chromium.org>, linux-kernel@vger.kernel.org, Randy Li <ayaka@soulik.info>, Andy Yan <andy.yan@rock-chips.com>, Rob Herring <robh+dt@kernel.org>, Eddie Cai <eddie.cai.linux@gmail.com>, Mark Rutland <mark.rutland@arm.com>, linux-arm-kernel@lists.infradead.org, Xing Zheng <zhengxing@rock-chips.com> Subject: [PATCH v2 2/2] dt-bindings: document: add firefly-rk3399 board support Date: Wed, 5 Apr 2017 17:33:20 +0800 [thread overview] Message-ID: <1491384800-22412-2-git-send-email-kever.yang@rock-chips.com> (raw) In-Reply-To: <1491384800-22412-1-git-send-email-kever.yang@rock-chips.com> Use "firefly,firefly-rk3399" compatible string for firefly-rk3399 board. Signed-off-by: Kever Yang <kever.yang@rock-chips.com> --- Changes in v2: None Documentation/devicetree/bindings/arm/rockchip.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/rockchip.txt b/Documentation/devicetree/bindings/arm/rockchip.txt index 250fdf0..b5201f4 100644 --- a/Documentation/devicetree/bindings/arm/rockchip.txt +++ b/Documentation/devicetree/bindings/arm/rockchip.txt @@ -42,6 +42,10 @@ Rockchip platforms device tree bindings Required root node properties: - compatible = "firefly,firefly-rk3288-reload", "rockchip,rk3288"; +- Firefly Firefly-RK3399 board: + Required root node properties: + - compatible = "firefly,firefly-rk3399", "rockchip,rk3399"; + - ChipSPARK PopMetal-RK3288 board: Required root node properties: - compatible = "chipspark,popmetal-rk3288", "rockchip,rk3288"; -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: kever.yang@rock-chips.com (Kever Yang) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 2/2] dt-bindings: document: add firefly-rk3399 board support Date: Wed, 5 Apr 2017 17:33:20 +0800 [thread overview] Message-ID: <1491384800-22412-2-git-send-email-kever.yang@rock-chips.com> (raw) In-Reply-To: <1491384800-22412-1-git-send-email-kever.yang@rock-chips.com> Use "firefly,firefly-rk3399" compatible string for firefly-rk3399 board. Signed-off-by: Kever Yang <kever.yang@rock-chips.com> --- Changes in v2: None Documentation/devicetree/bindings/arm/rockchip.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/rockchip.txt b/Documentation/devicetree/bindings/arm/rockchip.txt index 250fdf0..b5201f4 100644 --- a/Documentation/devicetree/bindings/arm/rockchip.txt +++ b/Documentation/devicetree/bindings/arm/rockchip.txt @@ -42,6 +42,10 @@ Rockchip platforms device tree bindings Required root node properties: - compatible = "firefly,firefly-rk3288-reload", "rockchip,rk3288"; +- Firefly Firefly-RK3399 board: + Required root node properties: + - compatible = "firefly,firefly-rk3399", "rockchip,rk3399"; + - ChipSPARK PopMetal-RK3288 board: Required root node properties: - compatible = "chipspark,popmetal-rk3288", "rockchip,rk3288"; -- 1.9.1
next prev parent reply other threads:[~2017-04-05 9:34 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-05 9:33 [PATCH v2 1/2] arm64: dts: rk3399: add support for firefly-rk3399 board Kever Yang 2017-04-05 9:33 ` Kever Yang 2017-04-05 9:33 ` Kever Yang [this message] 2017-04-05 9:33 ` [PATCH v2 2/2] dt-bindings: document: add firefly-rk3399 board support Kever Yang 2017-04-10 16:25 ` Rob Herring 2017-04-10 16:25 ` Rob Herring 2017-04-10 16:25 ` Rob Herring 2017-04-12 13:30 ` Heiko Stuebner 2017-04-12 13:30 ` Heiko Stuebner 2017-04-12 13:30 ` Heiko Stuebner 2017-04-07 23:01 ` [PATCH v2 1/2] arm64: dts: rk3399: add support for firefly-rk3399 board Heiko Stuebner 2017-04-07 23:01 ` Heiko Stuebner 2017-04-07 23:01 ` Heiko Stuebner 2017-04-10 3:43 ` Kever Yang 2017-04-10 3:43 ` Kever Yang 2017-04-10 3:43 ` 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=1491384800-22412-2-git-send-email-kever.yang@rock-chips.com \ --to=kever.yang@rock-chips.com \ --cc=andy.yan@rock-chips.com \ --cc=ayaka@soulik.info \ --cc=briannorris@chromium.org \ --cc=cl@rock-chips.com \ --cc=devicetree@vger.kernel.org \ --cc=eddie.cai.linux@gmail.com \ --cc=heiko@sntech.de \ --cc=jay.xu@rock-chips.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.org \ --cc=zhengxing@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.