[RFC PATCH v1 0/4] Add upstream board Xunlong Orange Pi RV

[RFC PATCH v1 0/4] Add upstream board Xunlong Orange Pi RV

[E Shattow]

Xunlong Orange Pi RV patches are now queued up for the next merge window
to Linux v6.19, so let's introduce support for this board.

Note: The content of EEPROM is not known to be unique on this board, and
in this RFC there is a placeholder value of "XOPIRV".

E Shattow (4):
  riscv: dts: starfive: Add Orange Pi RV from upstream Linux for-next
  board: starfive: visionfive2: Add Orange Pi RV selection by product_id
  riscv: dts: Add placeholder files for pending upstream Orange Pi RV
  configs: starfive: Add Orange Pi RV to visionfive2

 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi | 76 +++++++++++++++++++
 board/starfive/visionfive2/spl.c              |  3 +
 .../visionfive2/starfive_visionfive2.c        |  2 +
 configs/starfive_visionfive2_defconfig        |  2 +-
 .../src/riscv/starfive/jh7110-orangepi-rv.dts |  0
 5 files changed, 82 insertions(+), 1 deletion(-)
 create mode 100644 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
 create mode 100644 dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts


base-commit: c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9
-- 
2.50.0

[RFC PATCH v1 1/4] riscv: dts: starfive: Add Orange Pi RV from upstream Linux for-next

[E Shattow]

Import dts for Orange Pi RV as per-board automatic inclusion. This
commit should be reverted when devicetree-rebasing release candidate for
Linux 6.19 is sync'ed.

Signed-off-by: E Shattow <e@freeshell.de>
---
 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi | 76 +++++++++++++++++++
 1 file changed, 76 insertions(+)
 create mode 100644 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi

diff --git a/arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi b/arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
new file mode 100644
index 00000000000..053c35992ec
--- /dev/null
+++ b/arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
@@ -0,0 +1,76 @@
+// SPDX-License-Identifier: GPL-2.0 OR MIT
+/*
+ * Copyright (C) 2025 Icenowy Zheng <uwu@icenowy.me>
+ */
+
+/dts-v1/;
+#include "jh7110-common.dtsi"
+
+/ {
+	model = "Xunlong Orange Pi RV";
+	compatible = "xunlong,orangepi-rv", "starfive,jh7110";
+
+	/* This regulator is always on by hardware */
+	reg_vcc3v3_pcie: regulator-vcc3v3-pcie {
+		compatible = "regulator-fixed";
+		regulator-name = "vcc3v3-pcie";
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
+		regulator-always-on;
+	};
+
+	wifi_pwrseq: wifi-pwrseq {
+		compatible = "mmc-pwrseq-simple";
+		reset-gpios = <&sysgpio 62 GPIO_ACTIVE_LOW>;
+	};
+};
+
+&gmac0 {
+	assigned-clocks = <&aoncrg JH7110_AONCLK_GMAC0_TX>;
+	assigned-clock-parents = <&aoncrg JH7110_AONCLK_GMAC0_RMII_RTX>;
+	starfive,tx-use-rgmii-clk;
+	status = "okay";
+};
+
+&mmc0 {
+	#address-cells = <1>;
+	#size-cells = <0>;
+	cap-sd-highspeed;
+	mmc-pwrseq = <&wifi_pwrseq>;
+	vmmc-supply = <&reg_vcc3v3_pcie>;
+	vqmmc-supply = <&vcc_3v3>;
+	status = "okay";
+
+	ap6256: wifi@1 {
+		compatible = "brcm,bcm43456-fmac", "brcm,bcm4329-fmac";
+		reg = <1>;
+		/* TODO: out-of-band IRQ on GPIO21, lacking pinctrl support */
+	};
+};
+
+&mmc1 {
+	cd-gpios = <&sysgpio 41 GPIO_ACTIVE_HIGH>;
+};
+
+&pcie0 {
+	status = "okay";
+};
+
+&pcie1 {
+	status = "okay";
+};
+
+&phy0 {
+	rx-internal-delay-ps = <1500>;
+	tx-internal-delay-ps = <1500>;
+	motorcomm,rx-clk-drv-microamp = <3970>;
+	motorcomm,rx-data-drv-microamp = <2910>;
+	motorcomm,tx-clk-adj-enabled;
+	motorcomm,tx-clk-10-inverted;
+	motorcomm,tx-clk-100-inverted;
+	motorcomm,tx-clk-1000-inverted;
+};
+
+&pwmdac {
+	status = "okay";
+};
-- 
2.50.0

[RFC PATCH v1 2/4] board: starfive: visionfive2: Add Orange Pi RV selection by product_id

[E Shattow]

Add identifier for Orange Pi RV to dts selection callback in SPL, and to
fdtfile environment variable default value selection in payload.

Signed-off-by: E Shattow <e@freeshell.de>
---
 board/starfive/visionfive2/spl.c                  | 3 +++
 board/starfive/visionfive2/starfive_visionfive2.c | 2 ++
 2 files changed, 5 insertions(+)

diff --git a/board/starfive/visionfive2/spl.c b/board/starfive/visionfive2/spl.c
index 2d9431d2976..684605278c0 100644
--- a/board/starfive/visionfive2/spl.c
+++ b/board/starfive/visionfive2/spl.c
@@ -131,6 +131,9 @@ int board_fit_config_name_match(const char *name)
 		    !strncmp(get_product_id_from_eeprom(), "MARC", 4) &&
 		    !get_mmc_size_from_eeprom()) {
 		return 0;
+	} else if (!strcmp(name, "starfive/jh7110-orangepi-rv") &&
+		    !strncmp(get_product_id_from_eeprom(), "XOPIRV", 6)) {
+		return 0;
 	} else if (!strcmp(name, "starfive/jh7110-pine64-star64") &&
 		    !strncmp(get_product_id_from_eeprom(), "STAR64", 6)) {
 		return 0;
diff --git a/board/starfive/visionfive2/starfive_visionfive2.c b/board/starfive/visionfive2/starfive_visionfive2.c
index 6c39fd4af35..d59622f6b64 100644
--- a/board/starfive/visionfive2/starfive_visionfive2.c
+++ b/board/starfive/visionfive2/starfive_visionfive2.c
@@ -63,6 +63,8 @@ static void set_fdtfile(void)
 		} else {
 			fdtfile = "starfive/jh7110-milkv-marscm-lite.dtb";
 		}
+	} else if (!strncmp(get_product_id_from_eeprom(), "XOPIRV", 6)) {
+		fdtfile = "starfive/jh7110-orangepi-rv.dtb";
 	} else if (!strncmp(get_product_id_from_eeprom(), "STAR64", 6)) {
 		fdtfile = "starfive/jh7110-pine64-star64.dtb";
 	} else if (!strncmp(get_product_id_from_eeprom(), "VF7110A", 7)) {
-- 
2.50.0

[RFC PATCH v1 3/4] riscv: dts: Add placeholder files for pending upstream Orange Pi RV

[E Shattow]

Create placeholder file for Orange Pi RV in dts/upstream to placate the
build system. This is required when building on a dts that is not yet
landed in devicetree-rebasing and adopted as an dtsi include.

This placeholder file is empty and should be superseded when
devicetree-rebasing release candidate for Linux 6.19 is sync'ed.

Signed-off-by: E Shattow <e@freeshell.de>
---
 dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts

diff --git a/dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts b/dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts
new file mode 100644
index 00000000000..e69de29bb2d
-- 
2.50.0

[RFC PATCH v1 4/4] configs: starfive: Add Orange Pi RV to visionfive2

[E Shattow]

Add Orange Pi RV to visionfive2

Signed-off-by: E Shattow <e@freeshell.de>
---
 configs/starfive_visionfive2_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/starfive_visionfive2_defconfig b/configs/starfive_visionfive2_defconfig
index fa83ecfa10f..1dd35c59553 100644
--- a/configs/starfive_visionfive2_defconfig
+++ b/configs/starfive_visionfive2_defconfig
@@ -79,7 +79,7 @@ CONFIG_CMD_WGET=y
 CONFIG_CMD_BOOTSTAGE=y
 CONFIG_OF_BOARD=y
 CONFIG_DEVICE_TREE_INCLUDES="starfive-visionfive2-u-boot.dtsi"
-CONFIG_OF_LIST="starfive/jh7110-deepcomputing-fml13v01 starfive/jh7110-milkv-mars starfive/jh7110-milkv-marscm-emmc starfive/jh7110-milkv-marscm-lite starfive/jh7110-pine64-star64 starfive/jh7110-starfive-visionfive-2-v1.2a starfive/jh7110-starfive-visionfive-2-v1.3b"
+CONFIG_OF_LIST="starfive/jh7110-deepcomputing-fml13v01 starfive/jh7110-milkv-mars starfive/jh7110-milkv-marscm-emmc starfive/jh7110-milkv-marscm-lite starfive/jh7110-orangepi-rv starfive/jh7110-pine64-star64 starfive/jh7110-starfive-visionfive-2-v1.2a starfive/jh7110-starfive-visionfive-2-v1.3b"
 CONFIG_MULTI_DTB_FIT=y
 CONFIG_ENV_OVERWRITE=y
 CONFIG_ENV_IS_IN_SPI_FLASH=y
-- 
2.50.0

Re: [RFC PATCH v1 0/4] Add upstream board Xunlong Orange Pi RV

[Heinrich Schuchardt]

Am 26. November 2025 23:15:25 MEZ schrieb E Shattow <e@freeshell.de>:
>Xunlong Orange Pi RV patches are now queued up for the next merge window
>to Linux v6.19, so let's introduce support for this board.
>
>Note: The content of EEPROM is not known to be unique on this board, and
>in this RFC there is a placeholder value of "XOPIRV".

If OrangePi is not providing a unique value, shouldn't we create a separate defconfig (including the vf2 one) and override the output of the eeprom reading function by a configuration value?

That way we can reuse most code and avoid that users have to update the EEPROM to "XOPIRV".

Best regards

Heinrich

>
>E Shattow (4):
>  riscv: dts: starfive: Add Orange Pi RV from upstream Linux for-next
>  board: starfive: visionfive2: Add Orange Pi RV selection by product_id
>  riscv: dts: Add placeholder files for pending upstream Orange Pi RV
>  configs: starfive: Add Orange Pi RV to visionfive2
>
> arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi | 76 +++++++++++++++++++
> board/starfive/visionfive2/spl.c              |  3 +
> .../visionfive2/starfive_visionfive2.c        |  2 +
> configs/starfive_visionfive2_defconfig        |  2 +-
> .../src/riscv/starfive/jh7110-orangepi-rv.dts |  0
> 5 files changed, 82 insertions(+), 1 deletion(-)
> create mode 100644 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
> create mode 100644 dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts
>
>
>base-commit: c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9

Re: [RFC PATCH v1 0/4] Add upstream board Xunlong Orange Pi RV

[E Shattow]

On 11/26/25 14:34, Heinrich Schuchardt wrote:
> Am 26. November 2025 23:15:25 MEZ schrieb E Shattow <e@freeshell.de>:
>> Xunlong Orange Pi RV patches are now queued up for the next merge window
>> to Linux v6.19, so let's introduce support for this board.
>>
>> Note: The content of EEPROM is not known to be unique on this board, and
>> in this RFC there is a placeholder value of "XOPIRV".
> 
> If OrangePi is not providing a unique value, shouldn't we create a separate defconfig (including the vf2 one) and override the output of the eeprom reading function by a configuration value?
> 
> That way we can reuse most code and avoid that users have to update the EEPROM to "XOPIRV".
> 
> Best regards
> 
> Heinrich
> 
>>
>> E Shattow (4):
>>  riscv: dts: starfive: Add Orange Pi RV from upstream Linux for-next
>>  board: starfive: visionfive2: Add Orange Pi RV selection by product_id
>>  riscv: dts: Add placeholder files for pending upstream Orange Pi RV
>>  configs: starfive: Add Orange Pi RV to visionfive2
>>
>> arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi | 76 +++++++++++++++++++
>> board/starfive/visionfive2/spl.c              |  3 +
>> .../visionfive2/starfive_visionfive2.c        |  2 +
>> configs/starfive_visionfive2_defconfig        |  2 +-
>> .../src/riscv/starfive/jh7110-orangepi-rv.dts |  0
>> 5 files changed, 82 insertions(+), 1 deletion(-)
>> create mode 100644 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
>> create mode 100644 dts/upstream/src/riscv/starfive/jh7110-orangepi-rv.dts
>>
>>
>> base-commit: c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9
> 

Sure I'd like more testing data about these boards, I don't have the
board myself so I don't know the answer to that.

What is the content of EEPROM, for reference?

If it's all the same as VisionFive 2 and boots with dts from VisionFive
2 (1.3b?) then it might not be needed to do more than add documentation
for the board to reference the VisionFive 2 and explain how to properly
set fdtfile. Inventing a new board identifier when the manufacturer has
not provided one sounds convenient to me, and it is not to the exclusion
of a separate board config just for that special situation. The
documentation can explain either or both situations, expanding how to
compile for the board.

How does network and eMMC function with the series applied, not changing
the EEPROM content (remains what I was understood is the same as
VisionFive 2), and manually setting the fdtfile variable?

-E

Re: [RFC PATCH v1 0/4] Add upstream board Xunlong Orange Pi RV

[Icenowy Zheng]

在 2025-11-26星期三的 15:42 -0800，E Shattow写道：
> 
> On 11/26/25 14:34, Heinrich Schuchardt wrote:
> > Am 26. November 2025 23:15:25 MEZ schrieb E Shattow
> > <e@freeshell.de>:
> > > Xunlong Orange Pi RV patches are now queued up for the next merge
> > > window
> > > to Linux v6.19, so let's introduce support for this board.
> > > 
> > > Note: The content of EEPROM is not known to be unique on this
> > > board, and
> > > in this RFC there is a placeholder value of "XOPIRV".
> > 
> > If OrangePi is not providing a unique value, shouldn't we create a
> > separate defconfig (including the vf2 one) and override the output
> > of the eeprom reading function by a configuration value?
> > 
> > That way we can reuse most code and avoid that users have to update
> > the EEPROM to "XOPIRV".
> > 
> > Best regards
> > 
> > Heinrich
> > 
> > > 
> > > E Shattow (4):
> > >  riscv: dts: starfive: Add Orange Pi RV from upstream Linux for-
> > > next
> > >  board: starfive: visionfive2: Add Orange Pi RV selection by
> > > product_id
> > >  riscv: dts: Add placeholder files for pending upstream Orange Pi
> > > RV
> > >  configs: starfive: Add Orange Pi RV to visionfive2
> > > 
> > > arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi | 76
> > > +++++++++++++++++++
> > > board/starfive/visionfive2/spl.c              |  3 +
> > > .../visionfive2/starfive_visionfive2.c        |  2 +
> > > configs/starfive_visionfive2_defconfig        |  2 +-
> > > .../src/riscv/starfive/jh7110-orangepi-rv.dts |  0
> > > 5 files changed, 82 insertions(+), 1 deletion(-)
> > > create mode 100644 arch/riscv/dts/jh7110-orangepi-rv-u-boot.dtsi
> > > create mode 100644 dts/upstream/src/riscv/starfive/jh7110-
> > > orangepi-rv.dts
> > > 
> > > 
> > > base-commit: c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9
> > 
> 
> Sure I'd like more testing data about these boards, I don't have the
> board myself so I don't know the answer to that.
> 
> What is the content of EEPROM, for reference?

```
root@opirv [ ~ ] # i2cdump 5 0x50
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-5, address 0x50, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 53 46 56 46 02 00 02 00 88 00 00 00 01 00 01 00    SFVF?.?.?...?.?.
10: 58 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    X...............
20: 00 00 00 00 00 00 00 00 20 20 53 74 61 72 46 69    ........  StarFi
30: 76 65 20 54 65 63 68 6e 6f 6c 6f 67 79 20 43 6f    ve Technology Co
40: 2e 2c 20 4c 74 64 2e 00 00 00 56 46 37 31 31 30    ., Ltd....VF7110
50: 42 31 2d 32 32 32 38 2d 44 30 30 34 45 30 30 30    B1-2228-D004E000
60: 2d 30 30 30 30 30 32 37 31 00 6d da 04 00 02 00    -00000271.m??.?.
70: 14 00 00 00 02 00 01 41 c0 74 2b fc f4 0e 6c cf    ?...?.?A?t+???l?
80: 39 00 00 00 00 00 f4 9e ff ff ff ff ff ff ff ff    9.....??........
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
```

From my OPi RV, where the original Linux upstream DT is developed.

> 
> If it's all the same as VisionFive 2 and boots with dts from
> VisionFive
> 2 (1.3b?) then it might not be needed to do more than add
> documentation
> for the board to reference the VisionFive 2 and explain how to
> properly
> set fdtfile. Inventing a new board identifier when the manufacturer
> has
> not provided one sounds convenient to me, and it is not to the
> exclusion
> of a separate board config just for that special situation. The
> documentation can explain either or both situations, expanding how to
> compile for the board.
> 
> How does network and eMMC function with the series applied, not
> changing
> the EEPROM content (remains what I was understood is the same as
> VisionFive 2), and manually setting the fdtfile variable?
> 
> -E