Skip to contentSkip to conversation

riscv: spacemit: initial support for OrangePi R2S

PATCH Superseded [email protected] 3 participants 10 messages Nov 10, 2025 – Nov 11, 2025

Subsystems (3)

v3 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

v3 cover riscv: spacemit: initial support for OrangePi R2S

From: Michael Opdenacker <[email protected]>

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]

Changes in V3
- DT bindings: insert new compatible string in alphanumeric order (feedback from Krzysztof Kozlowski)
- OrangePi R2S: remove useless description text in commit message (feedback from Yixun Lan)

Changes in V2
- Squash 3 commits for initial DTS, Ethernet & PDMA, and eMMC

==========
eMMC tests
==========

Read tests
----------

hdparm -t --direct /dev/mmcblk0

/dev/mmcblk0:
Timing O_DIRECT disk reads: 846 MB in 3.01 seconds = 281.52 MB/sec

Write tests
-----------

dd if=/dev/zero of=/dev/mmcblk0p2 bs=4M oflag=direct status=progress 7600078848 bytes (7.6 GB, 7.1 GiB) copied, 127 s, 59.8 MB/s
dd: error writing '/dev/mmcblk0p2': No space left on device 1825+0 records in
1824+0 records out
7650410496 bytes (7.7 GB, 7.1 GiB) copied, 127.866 s, 59.8 MB/s

==============
Ethernet tests
==============

Tests on eth0
-------------

root@orangepi-rv2-mainline:~# iperf3 -c 172.24.0.1
Connecting to host 172.24.0.1, port 5201
[ 5] local 172.24.0.2 port 51354 connected to 172.24.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 113 MBytes 947 Mbits/sec 0 395 KBytes
[ 5] 1.00-2.00 sec 113 MBytes 945 Mbits/sec 0 395 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 936 Mbits/sec 0 395 KBytes
[ 5] 3.00-4.00 sec 112 MBytes 942 Mbits/sec 0 395 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec 0 395 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 940 Mbits/sec 0 409 KBytes
[ 5] 6.00-7.00 sec 113 MBytes 948 Mbits/sec 0 409 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 940 Mbits/sec 0 409 KBytes
[ 5] 8.00-9.00 sec 112 MBytes 941 Mbits/sec 0 414 KBytes
[ 5] 9.00-10.03 sec 113 MBytes 919 Mbits/sec 0 414 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.03 sec 1.10 GBytes 940 Mbits/sec 0 sender
[ 5] 0.00-10.04 sec 1.10 GBytes 939 Mbits/sec receiver

iperf Done.

root@orangepi-rv2-mainline:~# iperf3 -s
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 172.24.0.1, port 38326
[ 5] local 172.24.0.2 port 5201 connected to 172.24.0.1 port 38332
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 112 MBytes 935 Mbits/sec
[ 5] 1.00-2.00 sec 112 MBytes 942 Mbits/sec
[ 5] 2.00-3.00 sec 112 MBytes 941 Mbits/sec
[ 5] 3.00-4.00 sec 112 MBytes 941 Mbits/sec
[ 5] 4.00-5.00 sec 112 MBytes 942 Mbits/sec
[ 5] 5.00-6.00 sec 112 MBytes 942 Mbits/sec
[ 5] 6.00-7.00 sec 112 MBytes 942 Mbits/sec
[ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec
[ 5] 8.00-9.00 sec 112 MBytes 941 Mbits/sec
[ 5] 9.00-10.00 sec 112 MBytes 943 Mbits/sec
[ 5] 10.00-10.01 sec 384 KBytes 725 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.01 sec 1.10 GBytes 941 Mbits/sec receiver

Tests on eth1
------------------

root@orangepi-rv2-mainline:~# iperf3 -c 172.24.0.1
Connecting to host 172.24.0.1, port 5201
[ 5] local 172.24.0.2 port 60564 connected to 172.24.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 113 MBytes 947 Mbits/sec 0 423 KBytes
[ 5] 1.00-2.00 sec 113 MBytes 945 Mbits/sec 0 423 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 943 Mbits/sec 0 423 KBytes
[ 5] 3.00-4.00 sec 112 MBytes 938 Mbits/sec 0 423 KBytes
[ 5] 4.00-5.00 sec 112 MBytes 944 Mbits/sec 0 423 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 936 Mbits/sec 0 423 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 943 Mbits/sec 0 423 KBytes
[ 5] 7.00-8.00 sec 112 MBytes 940 Mbits/sec 0 423 KBytes
[ 5] 8.00-9.00 sec 113 MBytes 951 Mbits/sec 0 639 KBytes
[ 5] 9.00-10.01 sec 112 MBytes 934 Mbits/sec 0 639 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.01 sec 1.10 GBytes 943 Mbits/sec 0 sender
[ 5] 0.00-10.02 sec 1.10 GBytes 940 Mbits/sec receiver

iperf Done.

root@orangepi-rv2-mainline:~# iperf3 -s 172.24.0.1
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 172.24.0.1, port 49628
[ 5] local 172.24.0.2 port 5201 connected to 172.24.0.1 port 49640
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 112 MBytes 934 Mbits/sec
[ 5] 1.00-2.00 sec 112 MBytes 942 Mbits/sec
[ 5] 2.00-3.00 sec 112 MBytes 942 Mbits/sec
[ 5] 3.00-4.00 sec 112 MBytes 942 Mbits/sec
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec
[ 5] 5.00-6.00 sec 112 MBytes 942 Mbits/sec
[ 5] 6.00-7.00 sec 112 MBytes 942 Mbits/sec
[ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec
[ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec
[ 5] 9.00-10.00 sec 112 MBytes 941 Mbits/sec
[ 5] 10.00-10.01 sec 640 KBytes 1.14 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.01 sec 1.10 GBytes 941 Mbits/sec receiver

Michael Opdenacker (2):
dt-bindings: riscv: spacemit: Add OrangePi R2S board
riscv: dts: spacemit: Add OrangePi R2S board device tree

 .../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
#1 lore raw

PATCH v3 1/2 dt-bindings: riscv: spacemit: Add OrangePi R2S board

From: Michael Opdenacker <[email protected]>

Document the compatible string 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].

---
 Documentation/devicetree/bindings/riscv/spacemit.yaml | 1 +
 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/riscv/spacemit.yaml +1 -0
index 52fe39296031..9c49482002f7 100644
@@ -23,6 +23,7 @@ properties:
               - bananapi,bpi-f3
               - milkv,jupiter
               - spacemit,musepi-pro
+              - xunlong,orangepi-r2s
               - xunlong,orangepi-rv2
           - const: spacemit,k1
 
#9 lore raw

PATCH v3 2/2 riscv: dts: spacemit: Add OrangePi R2S board device tree

In reply to [email protected]

From: Michael Opdenacker <[email protected]>

Add initial device tree support for the OrangePi RV2 board [1], which is marketed as using the Ky X1 SoC but has been confirmed to be identical to the SpacemiT K1 [2].

Enable UART0, to boot into a serial console

Two Gigabit Ethernet ports with RGMII interface standard support are enabled, each port is connected to an external Motorcomm YT8531C PHY chip which uses the GPIO for reset control.

Enable PDMA.

Enable 8 GB eMMC chip for storage.

---
 arch/riscv/boot/dts/spacemit/Makefile         |  1 +
 .../boot/dts/spacemit/k1-orangepi-r2s.dts     | 90 +++++++++++++++++++
 2 files changed, 91 insertions(+)
 create mode 100644 arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts
arch/riscv/boot/dts/spacemit/Makefile +1 -0
index 942ecb38bea0..96b3a13a3944 100644
@@ -3,3 +3,4 @@ dtb-$(CONFIG_ARCH_SPACEMIT) += k1-bananapi-f3.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k1-milkv-jupiter.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k1-musepi-pro.dtb
 dtb-$(CONFIG_ARCH_SPACEMIT) += k1-orangepi-rv2.dtb
+dtb-$(CONFIG_ARCH_SPACEMIT) += k1-orangepi-r2s.dtb
arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts new file +90 -0

90 lines not on this page · raw message

#2 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

In reply to [email protected]
Quoted 5 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…

From: Michael Opdenacker <[email protected]>

Document the compatible string 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].

Different SoC means different compatible. It is very, very unlikely that different vendor made same die, which would warrant same compatible. Identical does not mean the same die, so your explanation is not complete.

Best regards,
Krzysztof

#3 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

Hi Krzysztof,

Quoted 5 lines · Krzysztof Kozlowski
Quoted 4 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…

From: Michael Opdenacker <[email protected]>

Document the compatible string for the OrangePi R2S board [1], which is marketed as using the Ky X1 SoC but is in fact identical to

Maybe, just say it "same" to clarify the ambiguity?

Quoted 6 lines
Quoted 1 line

the SpacemiT K1 SoC [2].

Different SoC means different compatible. It is very, very unlikely that different vendor made same die, which would warrant same compatible. Identical does not mean the same die, so your explanation is not complete.

Unfortunately, it's true that Ky X1 is just a rebrand of SpacemiT K1 SoC.

I guess it's a marketing strategy although personally I don't know what's the motivation behind and even wish it never happens..

Signature · 1 line
Yixun Lan (dlan)
#4 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

Quoted 9 lines · Yixun Lan

Hi Krzysztof,

Quoted 5 lines · Krzysztof Kozlowski
Quoted 4 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…

From: Michael Opdenacker <[email protected]>

Document the compatible string for the OrangePi R2S board [1], which is marketed as using the Ky X1 SoC but is in fact identical to

Maybe, just say it "same" to clarify the ambiguity?

What is exactly "same"? Same die? Or same blocks/pieces? Whichever you choose please make it very explicit.

Best regards,
Krzysztof

#5 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

Greetings

Thanks one more time for the reviews!

Quoted 4 lines · Krzysztof Kozlowski
Quoted 3 lines · Yixun Lan

Hi Krzysztof,

On 08:43 Tue 11 Nov , Krzysztof Kozlowski wrote:

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…
Quoted 4 lines

From: Michael Opdenacker <[email protected]>

Document the compatible string for the OrangePi R2S board [1], which is marketed as using the Ky X1 SoC but is in fact identical to

Maybe, just say it "same" to clarify the ambiguity?

What is exactly "same"? Same die? Or same blocks/pieces? Whichever you choose please make it very explicit.

Maybe Troy Mitchell from Spacemit can shed light on this question.

Anyway, I could use the same wording as in this commit introducing "OrangePi RV2":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch?id=bab8dea259100a99e047fd11a48940b229d30031

"The board is described as using the Ky X1 SoC, which, based on available downstream sources and testing, appears to be identical or very closely related to the SpacemiT K1 SoC".

What do you think?

Cheers,
Michael

Signature · 4 lines
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/
#6 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

Quoted 24 lines · Michael Opdenacker

Greetings

Thanks one more time for the reviews!

Quoted 4 lines · Krzysztof Kozlowski
Quoted 3 lines · Yixun Lan

Hi Krzysztof,

On 08:43 Tue 11 Nov , Krzysztof Kozlowski wrote:

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…
Quoted 4 lines

From: Michael Opdenacker <[email protected]>

Document the compatible string for the OrangePi R2S board [1], which is marketed as using the Ky X1 SoC but is in fact identical to

Maybe, just say it "same" to clarify the ambiguity?

What is exactly "same"? Same die? Or same blocks/pieces? Whichever you choose please make it very explicit.

Maybe Troy Mitchell from Spacemit can shed light on this question.

Anyway, I could use the same wording as in this commit introducing "OrangePi RV2":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch?id=bab8dea259100a99e047fd11a48940b229d30031

Quoted 5 lines

"The board is described as using the Ky X1 SoC, which, based on available downstream sources and testing, appears to be identical or very closely related to the SpacemiT K1 SoC".

What do you think?

This clearly suggests they are not identical thus you should have also dedicated compatible. Let me then precise, I thought it is obvious, that except writing it more detailed in commit msg, you also need proper binding expressing this. If this is not the same die and they look compatible, then usually it means you need a compatible.

Best regards,
Krzysztof

#7 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

Hi Krzystof,

Quoted 28 lines · Krzysztof Kozlowski
Quoted 27 lines · Michael Opdenacker

Greetings

Thanks one more time for the reviews!

Quoted 4 lines · Krzysztof Kozlowski
Quoted 3 lines · Yixun Lan

Hi Krzysztof,

On 08:43 Tue 11 Nov , Krzysztof Kozlowski wrote:

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…
Quoted 4 lines

From: Michael Opdenacker <[email protected]>

Document the compatible string for the OrangePi R2S board [1], which is marketed as using the Ky X1 SoC but is in fact identical to

Maybe, just say it "same" to clarify the ambiguity?

What is exactly "same"? Same die? Or same blocks/pieces? Whichever you choose please make it very explicit.

Maybe Troy Mitchell from Spacemit can shed light on this question.

Anyway, I could use the same wording as in this commit introducing "OrangePi RV2":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch?id=bab8dea259100a99e047fd11a48940b229d30031

"The board is described as using the Ky X1 SoC, which, based on available downstream sources and testing, appears to be identical or very closely related to the SpacemiT K1 SoC".

Quoted 6 lines
Quoted 1 line

What do you think?

This clearly suggests they are not identical thus you should have also dedicated compatible. Let me then precise, I thought it is obvious, that except writing it more detailed in commit msg, you also need proper binding expressing this. If this is not the same die and they look compatible, then usually it means you need a compatible.

Note quite, the sentence I reused says "identical *or* very closely related".

Anyway, that's not up to me to decide, as what you suggest would mean to fix the DTS for OrangePi RV2 too.

I was just trying to share code for this board too in a very similar way to what was shared for OrangePi RV2, so that people can use the mainline kernel to collaborate and make support for this board better than the custom code produced by the board vendor...

Cheers
Michael.

Signature · 10 lines
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/


_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
#8 lore raw

Re: [PATCH v3 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board

In reply to Krzysztof Kozlowski

Hi All,

Quoted 21 lines · Krzysztof Kozlowski
Quoted 20 lines · Michael Opdenacker

Greetings

Thanks one more time for the reviews!

Quoted 4 lines · Krzysztof Kozlowski
Quoted 3 lines · Yixun Lan

Hi Krzysztof,

On 08:43 Tue 11 Nov , Krzysztof Kozlowski wrote:

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines · On Mon, Nov 10, 2025 at 10:06:48PM +0000, [email protected]…
Quoted 4 lines

From: Michael Opdenacker <[email protected]>

Document the compatible string for the OrangePi R2S board [1], which is marketed as using the Ky X1 SoC but is in fact identical to

Maybe, just say it "same" to clarify the ambiguity?

What is exactly "same"? Same die? Or same blocks/pieces? Whichever you choose please make it very explicit.

Maybe Troy Mitchell from Spacemit can shed light on this question.

Quoted 7 lines
Quoted 7 lines

Anyway, I could use the same wording as in this commit introducing "OrangePi RV2":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch?id=bab8dea259100a99e047fd11a48940b229d30031

"The board is described as using the Ky X1 SoC, which, based on available downstream sources and testing, appears to be identical or very closely related to the SpacemiT K1 SoC".

sorry for bringing confusion in previous series, we had no further discussion on this..

Quoted 9 lines
Quoted 2 lines

What do you think?

This clearly suggests they are not identical thus you should have also dedicated compatible. Let me then precise, I thought it is obvious, that except writing it more detailed in commit msg, you also need proper binding expressing this. If this is not the same die and they look compatible, then usually it means you need a compatible.

to be explicit, the Xy X1 has same die, same packaging as SpacemiT K1, so we should not introduce new compatible in the SoC level, but a new board compatible in patch [1/2] is ok to me

I hope this clarify this issue..

Signature · 1 line
Yixun Lan (dlan)