From: Jagan Teki <jagan@amarulasolutions.com>
To: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jagan Teki <jagan@amarulasolutions.com>
Subject: [PATCH 1/7] dt-bindings: arm: rockchip: Add meaningful comments for Radxa CM3
Date: Tue, 17 Jan 2023 16:24:58 +0530 [thread overview]
Message-ID: <20230117105504.18296-1-jagan@amarulasolutions.com> (raw)
Radxa produced several versions of the RK356x-based Compute modules
called Radxa Compute Module 3(CM3) for consumer and industrial use
with a variety of form factors.
So, adding meaningful comments on dt-bindings would help to understand
more about specific module relevance.
This patch is trying to add comments on existing CM3 bindings and
expecting the subsequent modules are following similar comments while
adding dt-bindings to it.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index 98afd7c6b8e6..3d3c59624483 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -621,11 +621,11 @@ properties:
- const: pine64,soquartz
- const: rockchip,rk3566
- - description: Radxa Compute Module 3(CM3)
+ - description: Radxa Compute Module 3(CM3) SoM based boards
items:
- enum:
- - radxa,radxa-cm3-io
- - const: radxa,radxa-cm3
+ - radxa,radxa-cm3-io # Radxa Compute Module 3(CM3) IO Board
+ - const: radxa,radxa-cm3 # Radxa Compute Module 3(CM3)
- const: rockchip,rk3566
- description: Radxa CM3 Industrial
--
2.25.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:[~2023-01-17 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 10:54 Jagan Teki [this message]
2023-01-17 10:54 ` [PATCH 2/7] arm64: dts: rockchip: Add missing CM3i fallback compatible for Radxa E25 Jagan Teki
2023-01-17 10:55 ` [PATCH 3/7] dt-bindings: arm: rockchip: Fix description and compatible for Radxa CM3i Jagan Teki
2023-01-17 11:06 ` Krzysztof Kozlowski
2023-01-17 12:55 ` Jagan Teki
2023-01-17 20:32 ` Rob Herring
2023-01-17 10:55 ` [PATCH 4/7] arm64: dts: rockchip: Fix compatible and model " Jagan Teki
2023-01-17 11:07 ` Krzysztof Kozlowski
2023-01-17 12:52 ` Jagan Teki
2023-01-17 12:58 ` Krzysztof Kozlowski
2023-01-18 7:20 ` Jagan Teki
2023-01-17 10:55 ` [PATCH 5/7] arm64: dts: rockchip: Drop unneeded " Jagan Teki
2023-01-17 10:55 ` [PATCH 6/7] arm64: dts: rockchip: Update eMMC, SD aliases for Radxa SoM boards Jagan Teki
2023-01-17 10:55 ` [PATCH 7/7] arm64: dts: rockchip: Update eMMC, SD aliases for Radxa SBC boards Jagan Teki
2023-01-17 11:05 ` [PATCH 1/7] dt-bindings: arm: rockchip: Add meaningful comments for Radxa CM3 Krzysztof Kozlowski
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=20230117105504.18296-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).