From: michael.opdenacker@rootcommit.com
To: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@gentoo.org>
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: [PATCH 0/4] riscv: spacemit: initial support for OrangePi R2S
Date: Sun, 9 Nov 2025 22:29:48 +0000 (UTC) [thread overview]
Message-ID: <20251109222858.3085488-1-michael.opdenacker@rootcommit.com> (raw)
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
This adds initial support for the OrangePi R2S board [1], which
is marketed as using the Ky X1 SoC but is in fact identical to
the SpacemiT K1 SoC [2].
What makes this board attractive is its 4 Ethernet ports
(2 x Gigagit RGMII with an external Motorcomm YT8531C PHY,
and 2 x 2.5 Gigabit Ethernet with RTL8125BG on an internal PCI Express bus),
its small form factor and its attractive pricing like other OrangePi boards.
What is supported:
- Serial console on serial UART
- 8 GB eMMC
- 2x Gigabit RGMII Ethernet ports
This patch series is based on Spacemit's Linux tree, "linux-for-next" branch [3]
Link: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-R2S.html [1]
Link: https://www.spacemit.com/en/key-stone-k1 [2]
Link: https://github.com/spacemit-com/linux/commits/k1/dt-for-next [3]
Michael Opdenacker (4):
dt-bindings: riscv: spacemit: Add OrangePi R2S board
riscv: dts: spacemit: Add OrangePi R2S board device tree
riscv: dts: spacemit: add Gigabit Ethernet and PDMA to OrangePi R2S
riscv: dts: spacemit: add eMMC to OrangePi R2S
.../devicetree/bindings/riscv/spacemit.yaml | 1 +
arch/riscv/boot/dts/spacemit/Makefile | 1 +
.../boot/dts/spacemit/k1-orangepi-r2s.dts | 90 +++++++++++++++++++
3 files changed, 92 insertions(+)
create mode 100644 arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: michael.opdenacker@rootcommit.com
To: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>, Yixun Lan <dlan@gentoo.org>
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: [PATCH 0/4] riscv: spacemit: initial support for OrangePi R2S
Date: Sun, 9 Nov 2025 22:29:48 +0000 (UTC) [thread overview]
Message-ID: <20251109222858.3085488-1-michael.opdenacker@rootcommit.com> (raw)
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
This adds initial support for the OrangePi R2S board [1], which
is marketed as using the Ky X1 SoC but is in fact identical to
the SpacemiT K1 SoC [2].
What makes this board attractive is its 4 Ethernet ports
(2 x Gigagit RGMII with an external Motorcomm YT8531C PHY,
and 2 x 2.5 Gigabit Ethernet with RTL8125BG on an internal PCI Express bus),
its small form factor and its attractive pricing like other OrangePi boards.
What is supported:
- Serial console on serial UART
- 8 GB eMMC
- 2x Gigabit RGMII Ethernet ports
This patch series is based on Spacemit's Linux tree, "linux-for-next" branch [3]
Link: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-R2S.html [1]
Link: https://www.spacemit.com/en/key-stone-k1 [2]
Link: https://github.com/spacemit-com/linux/commits/k1/dt-for-next [3]
Michael Opdenacker (4):
dt-bindings: riscv: spacemit: Add OrangePi R2S board
riscv: dts: spacemit: Add OrangePi R2S board device tree
riscv: dts: spacemit: add Gigabit Ethernet and PDMA to OrangePi R2S
riscv: dts: spacemit: add eMMC to OrangePi R2S
.../devicetree/bindings/riscv/spacemit.yaml | 1 +
arch/riscv/boot/dts/spacemit/Makefile | 1 +
.../boot/dts/spacemit/k1-orangepi-r2s.dts | 90 +++++++++++++++++++
3 files changed, 92 insertions(+)
create mode 100644 arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts
next reply other threads:[~2025-11-09 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 22:29 michael.opdenacker [this message]
2025-11-09 22:29 ` [PATCH 0/4] riscv: spacemit: initial support for OrangePi R2S michael.opdenacker
2025-11-09 22:29 ` [PATCH 1/4] dt-bindings: riscv: spacemit: Add OrangePi R2S board michael.opdenacker
2025-11-09 22:29 ` michael.opdenacker
2025-11-10 8:02 ` Krzysztof Kozlowski
2025-11-10 8:02 ` Krzysztof Kozlowski
2025-11-09 22:30 ` [PATCH 2/4] riscv: dts: spacemit: Add OrangePi R2S board device tree michael.opdenacker
2025-11-09 22:30 ` michael.opdenacker
2025-11-09 22:30 ` [PATCH 3/4] riscv: dts: spacemit: add Gigabit Ethernet and PDMA to OrangePi R2S michael.opdenacker
2025-11-09 22:30 ` michael.opdenacker
2025-11-10 0:52 ` Yixun Lan
2025-11-10 0:52 ` Yixun Lan
2025-11-10 8:04 ` Krzysztof Kozlowski
2025-11-10 8:04 ` Krzysztof Kozlowski
2025-11-09 22:30 ` [PATCH 4/4] riscv: dts: spacemit: add eMMC " michael.opdenacker
2025-11-09 22:30 ` michael.opdenacker
2025-11-10 8:03 ` Krzysztof Kozlowski
2025-11-10 8:03 ` 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=20251109222858.3085488-1-michael.opdenacker@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=dlan@gentoo.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=spacemit@lists.linux.dev \
/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.