From: Tianling Shen <cnsztl@gmail.com>
To: "Rob Herring" <robh+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Jagan Teki" <jagan@amarulasolutions.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Johan Jonker" <jbx6244@gmail.com>, "Pavel Machek" <pavel@ucw.cz>,
"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
"David Bauer" <mail@david-bauer.net>,
"Jensen Huang" <jensenhuang@friendlyarm.com>,
"Marty Jones" <mj8263788@gmail.com>,
"Tianling Shen" <cnsztl@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 1/2] dt-bindings: Add doc for FriendlyARM NanoPi R4S
Date: Fri, 19 Mar 2021 13:16:26 +0800 [thread overview]
Message-ID: <20210319051627.814-1-cnsztl@gmail.com> (raw)
Add devicetree binding documentation for the FriendlyARM NanoPi R4S.
Changes in v6:
- Fixed format of LED nodes
Changes in v5:
- Dropped the empty PCIe node
- Dropped useless `/delete-property/`
- Renamed LED nodes
Changes in v4:
- Correctly dropped `display-subsystem` node
- Dropped meaningless `pwm-fan` node
- Dropped wrong `sdmmc` node
- Disabled `i2c4` and `uart0` as they don't exist in the design
- Format fixes
Changes in v3:
- Dropped non-existent node `display_subsystem`
Changes in v2:
- Disable display for NanoPi R4S (reference commit: 74532de460ec)
- Light "sys" LED on NanoPi R4S (reference commit: 833821eeab91)
Signed-off-by: Tianling Shen <cnsztl@gmail.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index c3036f95c7bc..4a6f772c1043 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -134,6 +134,7 @@ properties:
- friendlyarm,nanopi-m4
- friendlyarm,nanopi-m4b
- friendlyarm,nanopi-neo4
+ - friendlyarm,nanopi-r4s
- const: rockchip,rk3399
- description: GeekBuying GeekBox
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-19 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 5:16 Tianling Shen [this message]
2021-03-19 5:16 ` [PATCH v6 2/2] rockchip: rk3399: Add support for FriendlyARM NanoPi R4S Tianling Shen
2021-03-21 19:02 ` [PATCH v6 1/2] dt-bindings: Add doc " Heiko Stuebner
2021-03-22 10:03 ` Heiko Stuebner
2021-04-25 21:33 ` Pavel Machek
2021-04-26 10:39 ` Tianling Shen
2021-04-26 11:03 ` Pavel Machek
2021-04-26 11:14 ` Tianling Shen
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=20210319051627.814-1-cnsztl@gmail.com \
--to=cnsztl@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=heiko@sntech.de \
--cc=jacek.anaszewski@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=jbx6244@gmail.com \
--cc=jensenhuang@friendlyarm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mail@david-bauer.net \
--cc=mj8263788@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.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).