riscv: spacemit: initial support for OrangePi R2S
Subsystems (3)
PATCH v2 1/2 dt-bindings: riscv: spacemit: Add OrangePi R2S board
In reply to [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].
--- Documentation/devicetree/bindings/riscv/spacemit.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/riscv/spacemit.yaml +1 -0
@@ -24,6 +24,7 @@ properties: - milkv,jupiter - spacemit,musepi-pro - xunlong,orangepi-rv2 + - xunlong,orangepi-r2s - const: spacemit,k1 additionalProperties: true
PATCH v2 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].
The device tree is similar to the OrangePi RV2 device tree (k1-orangepi-rv2.dts).
This minimal device tree enables:
- booting into a serial console with UART.
- the two RGMII ethernet ports
supporting Gigabit Ethernet operation.
They have an external Motorcomm YT8531C PHY attached, the PHY uses GPIO for reset pin control. Their description was reused from the DTS from the OrangePi RV2 board.
- PDMA for the SpacemiT K1-based SoC.
- the 8 GB eMMC chip for storage.
It works fine with the same description as
on the BananaPi F3 board DTS.
--- 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
@@ -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
v2 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 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
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Re: [PATCH v2 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board
In reply to [email protected]Hi Michael,
Quoted 19 lines · On 10:11 Mon 10 Nov , [email protected] wrote:
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].
Signed-off-by Michael Opdenacker <[email protected]>--- Documentation/devicetree/bindings/riscv/spacemit.yaml | 1 + 1 file changed, 1 insertion(+)Documentation/devicetree/bindings/riscv/spacemit.yaml +0
-0
Documentation/devicetree/bindings/riscv/spacemit.yaml properties: · line 27
Quoted 4 lines
Documentation/devicetree/bindings/riscv/spacemit.yaml +1
-0@@ -24,6 +24,7 @@ properties: - milkv,jupiter - spacemit,musepi-pro - xunlong,orangepi-rv2 + - xunlong,orangepi-r2s
with Krzysztof's comment, you should put this new compatile before
xunlong,orangepi-rv2, see
https://lore.kernel.org/all/20251110-impressive-dalmatian-of-luck-4d1441@kuoka/
Quoted 3 lines
Documentation/devicetree/bindings/riscv/spacemit.yaml +0
-0- const: spacemit,k1 additionalProperties: true
Signature · 1 line
Yixun Lan (dlan)
Re: [PATCH v2 1/2] dt-bindings: riscv: spacemit: Add OrangePi R2S board
In reply to [email protected]Hi Michael,
Quoted 8 lines · On 10:11 Mon 10 Nov , [email protected] wrote:
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].
..
Quoted 1 line
drop this blank line, it's not necessary
Quoted 1 line
Signed-off-by Michael Opdenacker <[email protected]>
Signature · 1 line
Yixun Lan (dlan)
Re: [PATCH v2 2/2] riscv: dts: spacemit: Add OrangePi R2S board device tree
In reply to [email protected]Hi Michael,
Quoted 6 lines · On 10:11 Mon 10 Nov , [email protected] wrote:
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].
..
Quoted 2 lines
The device tree is similar to the OrangePi RV2 device tree (
k1-orangepi-rv2.dts).
Drop above, this info is useless, will even bring more confusion
Quoted 3 lines
This minimal device tree enables:
..
Quoted 1 line
- booting into a serial console with UART.
Enable UART0, to boot into a serial console
Quoted 6 lines
- the two RGMII ethernet ports
supporting Gigabit Ethernet operation.They have an external Motorcomm YT8531C PHY attached, the PHY uses GPIO for reset pin control.
..
Quoted 2 lines
Their description
was reused from the DTS from the OrangePi RV2 board.
As I commented in v1, please drop above which is not technical related, useless..
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.
(I'm no native english speaker, try to slightly rearrange above text)
Quoted 4 lines
- PDMA for the SpacemiT K1-based SoC.
- the 8 GB eMMC chip for storage.
..
Quoted 2 lines
It works fine with the same description as
on the BananaPi F3 board DTS.
ditto, useless & drop
Quoted 4 lines
ditto, no blank line
Quoted 12 lines
Signed-off-by Michael Opdenacker <[email protected]>--- 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.dtsarch/riscv/boot/dts/spacemit/Makefile +0
-0
arch/riscv/boot/dts/spacemit/Makefile dtb-$(CONFIG_ARCH_SPACEMIT) += k1-bananapi-f3.dtb · line 6
Quoted 4 lines
arch/riscv/boot/dts/spacemit/Makefile +1
-0@@ -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
ditto, please sort
Quoted 96 lines
arch/riscv/boot/dts/spacemit/k1-orangepi-r2s.dts new file +90
-0@@ -0,0 +1,90 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +/* + * Copyright (C) 2025 Michael Opdenacker <[email protected]> + */ + +/dts-v1/; + +#include "k1.dtsi" +#include "k1-pinctrl.dtsi" + +/ { + model = "OrangePi R2S"; + compatible = "xunlong,orangepi-r2s", "spacemit,k1"; + + aliases { + serial0 = &uart0; + ethernet0 = ð0; + ethernet1 = ð1; + }; + + chosen { + stdout-path = "serial0"; + }; +}; + +&emmc { + bus-width = <8>; + mmc-hs400-1_8v; + mmc-hs400-enhanced-strobe; + non-removable; + no-sd; + no-sdio; + status = "okay"; +}; + +ð0 { + phy-handle = <&rgmii0>; + phy-mode = "rgmii-id"; + pinctrl-names = "default"; + pinctrl-0 = <&gmac0_cfg>; + rx-internal-delay-ps = <0>; + tx-internal-delay-ps = <0>; + status = "okay"; + + mdio-bus { + #address-cells = <0x1>; + #size-cells = <0x0>; + + reset-gpios = <&gpio K1_GPIO(110) GPIO_ACTIVE_LOW>; + reset-delay-us = <10000>; + reset-post-delay-us = <100000>; + + rgmii0: phy@1 { + reg = <0x1>; + }; + }; +}; + +ð1 { + phy-handle = <&rgmii1>; + phy-mode = "rgmii-id"; + pinctrl-names = "default"; + pinctrl-0 = <&gmac1_cfg>; + rx-internal-delay-ps = <0>; + tx-internal-delay-ps = <250>; + status = "okay"; + + mdio-bus { + #address-cells = <0x1>; + #size-cells = <0x0>; + + reset-gpios = <&gpio K1_GPIO(115) GPIO_ACTIVE_LOW>; + reset-delay-us = <10000>; + reset-post-delay-us = <100000>; + + rgmii1: phy@1 { + reg = <0x1>; + }; + }; +}; + +&pdma { + status = "okay"; +}; + +&uart0 { + pinctrl-names = "default"; + pinctrl-0 = <&uart0_2_cfg>; + status = "okay"; +};
Signature · 1 line
Yixun Lan (dlan)