From: Jonas Karlman <jonas@kwiboo.se>
To: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Yao Zi <ziyao@disroot.org>, Chukun Pan <amadeus@jmu.edu.cn>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jonas Karlman <jonas@kwiboo.se>
Subject: [PATCH 0/3] arm64: dts: rockchip: Add Radxa E24C
Date: Sun, 27 Jul 2025 14:44:00 +0000 [thread overview]
Message-ID: <20250727144409.327740-1-jonas@kwiboo.se> (raw)
This series adds dt-bindings and initial device tree for the Radxa E24C.
The product page for E24C mentions that onboard eMMC is optional and the
model I have come with SPI flash instead of eMMC.
On RK3528 the eMMC and SPI flash is muxed so only one of them can work.
I have included both SPI flash and eMMC nodes in the device tree,
however the sdhci node has been marked with status=fail. Something that
possible could be enabled using a DTBO or FDT fixup by the bootloader.
This also leaves out describing the RTL8367RB-VB switch as support for
the switch requires dt-binding and/or driver changes to make it work,
something that will be handled in a separate follow-up series.
This board can be booted from SD-card using the U-Boot 2025.07
generic-rk3528 target or preferably using work-in-progress patches [1].
This series depends on following series for a clean apply:
- arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and NanoPi Zero2 [2]
- rockchip: Add power controller support for RK3528 [3]
- rockchip: Add USB 2.0 support for RK3528 [4]
A branch with all these (and some more) patches can be found at [5].
[1] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commits/rk3528
[2] https://lore.kernel.org/r/20250717103720.2853031-1-jonas@kwiboo.se
[3] https://lore.kernel.org/r/20250723085654.2273324-1-jonas@kwiboo.se
[4] https://lore.kernel.org/r/20250723122323.2344916-1-jonas@kwiboo.se
[5] https://github.com/Kwiboo/linux-rockchip/commits/next-20250722-rk3528/
Jonas Karlman (3):
arm64: dts: rockchip: Add SFC node for RK3528
dt-bindings: arm: rockchip: Add Radxa E24C
arm64: dts: rockchip: Add Radxa E24C
.../devicetree/bindings/arm/rockchip.yaml | 6 +-
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3528-radxa-e24c.dts | 519 ++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3528.dtsi | 12 +
4 files changed, 536 insertions(+), 2 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-radxa-e24c.dts
--
2.50.1
WARNING: multiple messages have this Message-ID (diff)
From: Jonas Karlman <jonas@kwiboo.se>
To: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Yao Zi <ziyao@disroot.org>, Chukun Pan <amadeus@jmu.edu.cn>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jonas Karlman <jonas@kwiboo.se>
Subject: [PATCH 0/3] arm64: dts: rockchip: Add Radxa E24C
Date: Sun, 27 Jul 2025 14:44:00 +0000 [thread overview]
Message-ID: <20250727144409.327740-1-jonas@kwiboo.se> (raw)
This series adds dt-bindings and initial device tree for the Radxa E24C.
The product page for E24C mentions that onboard eMMC is optional and the
model I have come with SPI flash instead of eMMC.
On RK3528 the eMMC and SPI flash is muxed so only one of them can work.
I have included both SPI flash and eMMC nodes in the device tree,
however the sdhci node has been marked with status=fail. Something that
possible could be enabled using a DTBO or FDT fixup by the bootloader.
This also leaves out describing the RTL8367RB-VB switch as support for
the switch requires dt-binding and/or driver changes to make it work,
something that will be handled in a separate follow-up series.
This board can be booted from SD-card using the U-Boot 2025.07
generic-rk3528 target or preferably using work-in-progress patches [1].
This series depends on following series for a clean apply:
- arm64: dts: rockchip: Add ROCK 2A/2F, Sige1 and NanoPi Zero2 [2]
- rockchip: Add power controller support for RK3528 [3]
- rockchip: Add USB 2.0 support for RK3528 [4]
A branch with all these (and some more) patches can be found at [5].
[1] https://source.denx.de/u-boot/contributors/kwiboo/u-boot/-/commits/rk3528
[2] https://lore.kernel.org/r/20250717103720.2853031-1-jonas@kwiboo.se
[3] https://lore.kernel.org/r/20250723085654.2273324-1-jonas@kwiboo.se
[4] https://lore.kernel.org/r/20250723122323.2344916-1-jonas@kwiboo.se
[5] https://github.com/Kwiboo/linux-rockchip/commits/next-20250722-rk3528/
Jonas Karlman (3):
arm64: dts: rockchip: Add SFC node for RK3528
dt-bindings: arm: rockchip: Add Radxa E24C
arm64: dts: rockchip: Add Radxa E24C
.../devicetree/bindings/arm/rockchip.yaml | 6 +-
arch/arm64/boot/dts/rockchip/Makefile | 1 +
.../boot/dts/rockchip/rk3528-radxa-e24c.dts | 519 ++++++++++++++++++
arch/arm64/boot/dts/rockchip/rk3528.dtsi | 12 +
4 files changed, 536 insertions(+), 2 deletions(-)
create mode 100644 arch/arm64/boot/dts/rockchip/rk3528-radxa-e24c.dts
--
2.50.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2025-07-27 15:15 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 14:44 Jonas Karlman [this message]
2025-07-27 14:44 ` [PATCH 0/3] arm64: dts: rockchip: Add Radxa E24C Jonas Karlman
2025-07-27 14:44 ` [PATCH 1/3] arm64: dts: rockchip: Add SFC node for RK3528 Jonas Karlman
2025-07-27 14:44 ` Jonas Karlman
2025-07-28 7:00 ` Chukun Pan
2025-07-28 7:00 ` Chukun Pan
2025-07-28 16:18 ` Jonas Karlman
2025-07-28 16:18 ` Jonas Karlman
2025-07-27 14:44 ` [PATCH 2/3] dt-bindings: arm: rockchip: Add Radxa E24C Jonas Karlman
2025-07-27 14:44 ` Jonas Karlman
2025-07-28 5:48 ` Krzysztof Kozlowski
2025-07-28 5:48 ` Krzysztof Kozlowski
2025-07-27 14:44 ` [PATCH 3/3] arm64: dts: " Jonas Karlman
2025-07-27 14:44 ` Jonas Karlman
2025-07-27 16:15 ` Andrew Lunn
2025-07-27 16:15 ` Andrew Lunn
2025-07-27 16:26 ` Jonas Karlman
2025-07-27 16:26 ` Jonas Karlman
2025-07-27 16:44 ` Andrew Lunn
2025-07-27 16:44 ` Andrew Lunn
2025-07-28 12:50 ` Chukun Pan
2025-07-28 12:50 ` Chukun Pan
2025-07-28 17:09 ` Jonas Karlman
2025-07-28 17:09 ` Jonas Karlman
2025-07-29 13:20 ` Chukun Pan
2025-07-29 13:20 ` Chukun Pan
2025-07-29 21:15 ` Jonas Karlman
2025-07-29 21:15 ` Jonas Karlman
2025-08-15 4:46 ` FUKAUMI Naoki
2025-08-15 4:46 ` FUKAUMI Naoki
2025-08-15 10:01 ` Chukun Pan
2025-08-15 10:01 ` Chukun Pan
2025-08-18 6:17 ` FUKAUMI Naoki
2025-08-18 6:17 ` FUKAUMI Naoki
2025-09-09 12:28 ` FUKAUMI Naoki
2025-09-09 12:28 ` FUKAUMI Naoki
2025-09-09 14:48 ` Jonas Karlman
2025-09-09 14:48 ` Jonas Karlman
2025-09-09 15:39 ` Heiko Stübner
2025-09-09 15:39 ` Heiko Stübner
2025-09-09 19:36 ` Jonas Karlman
2025-09-09 19:36 ` Jonas Karlman
2025-09-10 2:43 ` FUKAUMI Naoki
2025-09-10 2:43 ` FUKAUMI Naoki
2025-09-10 8:07 ` Heiko Stübner
2025-09-10 8:07 ` Heiko Stübner
2025-09-10 9:50 ` FUKAUMI Naoki
2025-09-10 9:50 ` FUKAUMI Naoki
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=20250727144409.327740-1-jonas@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=amadeus@jmu.edu.cn \
--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 \
--cc=ziyao@disroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.