From: Chukun Pan <amadeus@jmu.edu.cn>
To: maxime@cerno.tech
Cc: amadeus@jmu.edu.cn, devicetree@vger.kernel.org,
jernej.skrabec@siol.net, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
lkft-triage@lists.linaro.org, naresh.kamboju@linaro.org,
regressions@lists.linux.dev, robh+dt@kernel.org, wens@csie.org
Subject: [PATCH v2 2/2] dt-bindings: arm: Add NanoPi R1S H5
Date: Mon, 17 May 2021 00:35:23 +0800 [thread overview]
Message-ID: <20210516163523.9484-3-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <20210516163523.9484-1-amadeus@jmu.edu.cn>
Add the bindings for NanoPi R1S H5 board.
Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Acked-by: Rob Herring <robh@kernel.org>
---
Documentation/devicetree/bindings/arm/sunxi.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/sunxi.yaml b/Documentation/devicetree/bindings/arm/sunxi.yaml
index ec8108483b49..889128acf49a 100644
--- a/Documentation/devicetree/bindings/arm/sunxi.yaml
+++ b/Documentation/devicetree/bindings/arm/sunxi.yaml
@@ -275,6 +275,11 @@ properties:
- const: friendlyarm,nanopi-r1
- const: allwinner,sun8i-h3
+ - description: FriendlyARM NanoPi R1S H5
+ items:
+ - const: friendlyarm,nanopi-r1s-h5
+ - const: allwinner,sun50i-h5
+
- description: FriendlyARM ZeroPi
items:
- const: friendlyarm,zeropi
--
2.17.1
next prev parent reply other threads:[~2021-05-16 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 14:29 [PATCH 1/2] arm64: dts: allwinner: h5: Add NanoPi R1S H5 support Chukun Pan
2021-05-11 5:21 ` Naresh Kamboju
2021-05-11 8:18 ` Maxime Ripard
2021-05-16 16:35 ` [PATCH v2 0/2] Add support for NanoPi R1S H5 Chukun Pan
2021-05-16 16:35 ` [PATCH v2 1/2] arm64: dts: allwinner: h5: Add NanoPi R1S H5 support Chukun Pan
2021-05-16 16:35 ` Chukun Pan [this message]
2021-05-18 14:01 ` [PATCH v2 0/2] Add support for NanoPi R1S H5 Maxime Ripard
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=20210516163523.9484-3-amadeus@jmu.edu.cn \
--to=amadeus@jmu.edu.cn \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=lkft-triage@lists.linaro.org \
--cc=maxime@cerno.tech \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).