From: Mizuno Miotsuki <founder@crepuse.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] dt-bindings: arm: rockchip: Add DFRobot UNIHIKER M10 V1.2
Date: Sat, 19 Sep 2026 13:41:31 +0000 [thread overview]
Message-ID: <20260919134125.59419-2-founder@crepuse.com> (raw)
In-Reply-To: <20260919134125.59419-1-founder@crepuse.com>
Add a board compatible for revision 1.2 of the DFRobot UNIHIKER M10.
Other PCB revisions are intentionally not covered.
Signed-off-by: Mizuno Miotsuki <founder@crepuse.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index a799bb843f74..65c4b2cf248f 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -175,6 +175,11 @@ properties:
- const: coolpi,pi-4b
- const: rockchip,rk3588s
+ - description: DFRobot UNIHIKER M10 V1.2
+ items:
+ - const: dfrobot,unihiker-m10-v1.2
+ - const: rockchip,rk3308
+
- description: Alientek CLRV1126F SoM based boards
items:
- enum:
--
2.55.0
next prev parent reply other threads:[~2026-09-19 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 13:41 [PATCH 0/2] arm64: dts: rockchip: Add DFRobot UNIHIKER M10 V1.2 support Mizuno Miotsuki
2026-09-19 13:41 ` Mizuno Miotsuki [this message]
2026-09-19 13:41 ` [PATCH 2/2] arm64: dts: rockchip: Add DFRobot UNIHIKER M10 V1.2 Mizuno Miotsuki
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=20260919134125.59419-2-founder@crepuse.com \
--to=founder@crepuse.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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
all inboxes | Powered by JetHome®