mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 0/2] arm64: dts: rockchip: Add DFRobot UNIHIKER M10 V1.2 support
Date: Sat, 19 Sep 2026 13:41:29 +0000	[thread overview]
Message-ID: <20260919134125.59419-1-founder@crepuse.com> (raw)

Add initial mainline support for the DFRobot UNIHIKER M10 V1.2. Only
revision 1.2 is claimed because later board revisions have not been
electrically verified.

The board device tree enables a conservative core subset for a usable
mainline system: CPU regulation, eMMC, SD, RTL8723DS SDIO Wi-Fi, UART0,
USB host and peripheral operation, GPIO keys, and the watchdog.
Bluetooth, audio, display, touch, IMU, SARADC, and GD32 support are
intentionally deferred.

Runtime validation used normal U-Boot boot from the eMMC boot partition,
not kexec. Four candidate boots reached userspace. Testing covered eMMC
and SD card I/O, RTL8723DS SDIO Wi-Fi including network traffic, USB
gadget operation, USB host controller enumeration, watchdog and GPIO-key
probe, and an empty deferred-probe list.

SD hot removal and reinsertion, physical USB-host devices, physical
button events, and an independent UART0 adapter remain untested.

`dt_binding_check` and the full `dtbs_check` pass with zero errors or
warnings.

Mizuno Miotsuki (2):
  dt-bindings: arm: rockchip: Add DFRobot UNIHIKER M10 V1.2
  arm64: dts: rockchip: Add DFRobot UNIHIKER M10 V1.2

 Documentation/devicetree/bindings/arm/rockchip.yaml |   5 +
 arch/arm64/boot/dts/rockchip/Makefile                |   1 +
 .../dts/rockchip/rk3308-unihiker-m10-v1.2.dts        | 248 +++++++++++++++++++
 3 files changed, 254 insertions(+)
 create mode 100644 arch/arm64/boot/dts/rockchip/rk3308-unihiker-m10-v1.2.dts

-- 
2.55.0

             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 Mizuno Miotsuki [this message]
2026-09-19 13:41 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add DFRobot UNIHIKER M10 V1.2 Mizuno Miotsuki
2026-09-19 13:41 ` [PATCH 2/2] arm64: dts: " 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-1-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®