spacemit: k1-bananapi-f3: Fix the power source of USB3 nodes

Define the system 5V fixed regulator (vcc5v0_sys) supplied by the DC input. As per the schematics, vcc5v0_sys is the input power source for the VCC5V0_HUB and 5V_VBUS reglators. Update these regulators to correctly reference vcc5v0_sys as their parent (vin-supply).

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++++++++++++
 1 file changed, 12 insertions(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +0 -0

index 5790d927b93d..9727ecdd9f6b 100644

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +11 -0

+		compatible = "regulator-fixed";
+		regulator-name = "vcc5v0_sys";
+		regulator-min-microvolt = <5000000>;
+		regulator-max-microvolt = <5000000>;
+		regulator-boot-on;
+		regulator-always-on;
+		vin-supply = <&reg_dc_in>;
+	};
+
 	reg_vcc_4v: regulator-vcc-4v {
 		compatible = "regulator-fixed";
 		regulator-name = "vcc_4v";

@@ -66,6 +76,7 @@ regulator-usb3-vbus-5v {
 		regulator-min-microvolt = <5000000>;
 		regulator-max-microvolt = <5000000>;
 		regulator-always-on;
+		vin-supply = <&reg_vcc5v0_sys>;
 		gpio = <&gpio K1_GPIO(97) GPIO_ACTIVE_HIGH>;
 		enable-active-high;
 	};

@@ -75,6 +86,7 @@ usb3_hub_5v: regulator-usb3-hub-5v {
 		regulator-name = "USB30_HUB";
 		regulator-min-microvolt = <5000000>;
 		regulator-max-microvolt = <5000000>;
+		vin-supply = <&reg_vcc5v0_sys>;
 		gpio = <&gpio K1_GPIO(123) GPIO_ACTIVE_HIGH>;
 		enable-active-high;
 	};

Signature · 1 line

2.50.1

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -1

@@ -366,7 +366,7 @@ &usb_dwc3 {
 	hub_2_0: hub@1 {
 		compatible = "usb2109,2817";
 		reg = <0x1>;
-		vdd-supply = <&usb3_hub_5v>;
+		vdd-supply = <&reg_5v_vbus>;
 		peer-hub = <&hub_3_0>;
 		reset-gpios = <&gpio K1_GPIO(124) GPIO_ACTIVE_LOW>;
 	};

Hi Anand,

Quoted 21 lines · Anand Moon

Define the system 5V fixed regulator (vcc5v0_sys) supplied by the DC input. As per the schematics, vcc5v0_sys is the input power source for the VCC5V0_HUB and 5V_VBUS reglators. Update these regulators to correctly reference vcc5v0_sys as their parent (vin-supply).

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++++++++++++
 1 file changed, 12 insertions(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +0 -0

index 5790d927b93d..9727ecdd9f6b 100644
@@ -50,6 +50,16 @@ reg_dc_in: regulator-dc-in-12v {
              regulator-always-on;
      };
 

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts reg_dc_in: regulator-dc-in-12v { · line 53

Quoted 1 line

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

+     reg_vcc5v0_sys: regulator-vcc5v0-sys {

This will fall into the catogery of "non-controllable & serve no devices" see similar comment for 'reg_dc_in' which raised by Krzysztof

https://lore.kernel.org/all/[email protected]/

or should I ask, what's the real problem if regulator has no vin-supply?

Any probe failure or something bad happen? (besides /sys/../regulator_summay)

Quoted 30 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +11 -1

+             compatible = "regulator-fixed";
+             regulator-name = "vcc5v0_sys";
+             regulator-min-microvolt = <5000000>;
+             regulator-max-microvolt = <5000000>;
+             regulator-boot-on;
+             regulator-always-on;
+             vin-supply = <&reg_dc_in>;
+     };
+
      reg_vcc_4v: regulator-vcc-4v {
              compatible = "regulator-fixed";
              regulator-name = "vcc_4v";

@@ -66,6 +76,7 @@ regulator-usb3-vbus-5v {
              regulator-min-microvolt = <5000000>;
              regulator-max-microvolt = <5000000>;
              regulator-always-on;
+             vin-supply = <&reg_vcc5v0_sys>;
              gpio = <&gpio K1_GPIO(97) GPIO_ACTIVE_HIGH>;
              enable-active-high;
      };

@@ -75,6 +86,7 @@ usb3_hub_5v: regulator-usb3-hub-5v {
              regulator-name = "USB30_HUB";
              regulator-min-microvolt = <5000000>;
              regulator-max-microvolt = <5000000>;
+             vin-supply = <&reg_vcc5v0_sys>;
              gpio = <&gpio K1_GPIO(123) GPIO_ACTIVE_HIGH>;
              enable-active-high;
      };
--

Quoted 2 lines

2.50.1

--
Yixun Lan (dlan)

Hi,

Quoted 13 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -1

@@ -366,7 +366,7 @@ &usb_dwc3 {
      hub_2_0: hub@1 {
              compatible = "usb2109,2817";
              reg = <0x1>;
-             vdd-supply = <&usb3_hub_5v>;
+             vdd-supply = <&reg_5v_vbus>;
              peer-hub = <&hub_3_0>;
              reset-gpios = <&gpio K1_GPIO(124) GPIO_ACTIVE_LOW>;
      };

@@ -374,7 +374,7 @@ hub_2_0: hub@1 {
      hub_3_0: hub@2 {
              compatible = "usb2109,817";
              reg = <0x2>;

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts hub_2_0: hub@1 { · line 380

Quoted 5 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -1

-             vdd-supply = <&usb3_hub_5v>;
+             vdd-supply = <&reg_5v_vbus>;
              peer-hub = <&hub_2_0>;
              reset-gpios = <&gpio K1_GPIO(124) GPIO_ACTIVE_LOW>;
      };

This is incorrect. The hub is powered by vcc5v0_hub. According to the schematic, 5v_vbus provides the VBUS for the USB3 ports.

Hi,

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts reg_5v_vbus: regulator-usb3-vbus-5v { · line 86

Quoted 4 lines

      usb3_hub_5v: regulator-usb3-hub-5v {
              compatible = "regulator-fixed";

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -1

-             regulator-name = "USB30_HUB";
+             regulator-name = "VCC5V0_HUB";

Suggested changes:

        vcc5v0_hub: regulator-vcc5v0-hub {
                compatible = "regulator-fixed";
                regulator-name = "vcc5v0_hub";

Quoted 3 lines

              regulator-min-microvolt = <5000000>;
              regulator-max-microvolt = <5000000>;

+ regulator-always-on;

Why always on?

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts &usb_dwc3 { · line 366

Quoted 7 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

@@ -361,6 +362,7 @@ &usb_dwc3 {
      dr_mode = "host";
      #address-cells = <1>;
      #size-cells = <0>;
+     vbus-supply = <&usb3_hub_5v>;
      status = "okay";

This is incorrect. See the previous reply.

The PCIe 3.3V fixed regulator node (pcie_vcc_3v3) lacked a parent supply reference. Wire it to the 5V system rail (reg_vcc5v0_sys) via the vin-supply property to reflect the actual board power tree. This ensures correct regulator hierarchy in DTS and allows drivers to resolve supply dependencies cleanly during probe.

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
v2: new patch in this series.

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 1 +
 1 file changed, 1 insertion(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -1

index 3dbdf53b6d8e..6c06480ba100 100644
@@ -39,6 +39,7 @@ pcie_vcc_3v3: regulator-pcie-vcc3v3 {
                regulator-min-microvolt = <3300000>;
                regulator-max-microvolt = <3300000>;
                regulator-always-on;
+               vin-supply = <&reg_vcc5v0_sys>;
        };
 
        reg_dc_in: regulator-dc-in-12v {
--

2.50.1

Hi Yixun,

Thanks for your review comments.

Quoted 29 lines · Yixun Lan

Hi Anand,

Quoted 18 lines · Anand Moon

Define the system 5V fixed regulator (vcc5v0_sys) supplied by the DC input. As per the schematics, vcc5v0_sys is the input power source for the VCC5V0_HUB and 5V_VBUS reglators. Update these regulators to correctly reference vcc5v0_sys as their parent (vin-supply).

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++++++++++++
 1 file changed, 12 insertions(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +0 -0

index 5790d927b93d..9727ecdd9f6b 100644

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts reg_dc_in: regulator-dc-in-12v { · line 53

Quoted 4 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

@@ -50,6 +50,16 @@ reg_dc_in: regulator-dc-in-12v {
              regulator-always-on;
      };
 
+     reg_vcc5v0_sys: regulator-vcc5v0-sys {

This will fall into the catogery of "non-controllable & serve no devices" see similar comment for 'reg_dc_in' which raised by Krzysztof

Quoted 3 lines

https://lore.kernel.org/all/[email protected]/

or should I ask, what's the real problem if regulator has no vin-supply?

If the device tree is not configured with the correct power source it will affect performance.

Quoted 1 line

Any probe failure or something bad happen? (besides /sys/../regulator_summay)

Not really; the regulator summary just confirms the PMIC used the correct power source.
with te device ip blocks.

Bananapi F3 schematics.
[1] https://drive.google.com/file/d/19iLJ5xnCB_oK8VeQjkPGjzAn39WYyylv/view
(page 24)

Please check the shematics VCC5V0_SYS page 4 VCC5V0_SYS->USB_VCC5V0->HDMI_VCC5V0->FAN_VCC5V0->VCC3V3_SYS

Please check the shematics VCC5V0_SYS page 24 VCC5V0_SYS input for VCC5V0_HUB and 5V_VBUS give the USB hub, which is enabled by USB3_PWREN (gpio pin)>

Plese check power tree page 4
USBVBUS->SY8386J UXXX -> PCIE_VCC3V3 for pcie vin source

So, this series tries to fix the vin source for USB 3.0 and PCIe nodes.

Hi Anand,

Quoted 36 lines · Anand Moon

Hi Yixun,

Thanks for your review comments.

Quoted 31 lines · Yixun Lan

Hi Anand,

Quoted 18 lines · Anand Moon

Define the system 5V fixed regulator (vcc5v0_sys) supplied by the DC input. As per the schematics, vcc5v0_sys is the input power source for the VCC5V0_HUB and 5V_VBUS reglators. Update these regulators to correctly reference vcc5v0_sys as their parent (vin-supply).

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++++++++++++
 1 file changed, 12 insertions(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +0 -0

index 5790d927b93d..9727ecdd9f6b 100644

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts reg_dc_in: regulator-dc-in-12v { · line 53

Quoted 4 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

@@ -50,6 +50,16 @@ reg_dc_in: regulator-dc-in-12v {
              regulator-always-on;
      };
 
+     reg_vcc5v0_sys: regulator-vcc5v0-sys {

This will fall into the catogery of "non-controllable & serve no devices" see similar comment for 'reg_dc_in' which raised by Krzysztof

https://lore.kernel.org/all/[email protected]/

Quoted 5 lines

Quoted 1 line

or should I ask, what's the real problem if regulator has no vin-supply?

If the device tree is not configured with the correct power source it will affect performance.

Please elaborate, or provide enough evidence to prove this, because the conclusion you gave here contradicts with what Krzysztof pointed out

Quoted 7 lines

Quoted 2 lines

Any probe failure or something bad happen? (besides /sys/../regulator_summay)

Not really; the regulator summary just confirms the PMIC used the correct power source.
with te device ip blocks.

then I see it's unnecessary to add this

Quoted 11 lines

Bananapi F3 schematics.
[1] https://drive.google.com/file/d/19iLJ5xnCB_oK8VeQjkPGjzAn39WYyylv/view
(page 24)

Please check the shematics VCC5V0_SYS page 4 VCC5V0_SYS->USB_VCC5V0->HDMI_VCC5V0->FAN_VCC5V0->VCC3V3_SYS

Please check the shematics VCC5V0_SYS page 24 VCC5V0_SYS input for VCC5V0_HUB and 5V_VBUS give the USB hub, which is enabled by USB3_PWREN (gpio pin)>

Quoted 5 lines

Plese check power tree page 4
USBVBUS->SY8386J UXXX -> PCIE_VCC3V3 for pcie vin source

So, this series tries to fix the vin source for USB 3.0 and PCIe nodes.

This is not what I ask..

--
Yixun Lan (dlan)

Hi Yixun,

Quoted 40 lines · Yixun Lan

Hi Anand,

Quoted 36 lines · Anand Moon

Hi Yixun,

Thanks for your review comments.

Quoted 31 lines · Yixun Lan

Hi Anand,

Quoted 18 lines · Anand Moon

Define the system 5V fixed regulator (vcc5v0_sys) supplied by the DC input. As per the schematics, vcc5v0_sys is the input power source for the VCC5V0_HUB and 5V_VBUS reglators. Update these regulators to correctly reference vcc5v0_sys as their parent (vin-supply).

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++++++++++++
 1 file changed, 12 insertions(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +0 -0

index 5790d927b93d..9727ecdd9f6b 100644

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts reg_dc_in: regulator-dc-in-12v { · line 53

Quoted 4 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

@@ -50,6 +50,16 @@ reg_dc_in: regulator-dc-in-12v {
              regulator-always-on;
      };
 
+     reg_vcc5v0_sys: regulator-vcc5v0-sys {

This will fall into the catogery of "non-controllable & serve no devices" see similar comment for 'reg_dc_in' which raised by Krzysztof

https://lore.kernel.org/all/[email protected]/

Quoted 7 lines

Quoted 5 lines

Quoted 1 line

or should I ask, what's the real problem if regulator has no vin-supply?

If the device tree is not configured with the correct power source it will affect performance.

Please elaborate, or provide enough evidence to prove this, because the conclusion you gave here contradicts with what Krzysztof pointed out

I don’t have the schematic for that board, so I skipped replying.

Please refer to the POWER TREE diagram, which provides a clear visualization of the power sources.

This board accepts two primary power sources: a 12 V DC input and USB Type‑C power.
From the schematic’s power tree (page 4):

Type‑C → DC_IN→ SY8386J (Uxxx) → PI PMIC

According to the block diagram, the SY8386J regulator IC is responsible for generating the VCC5V0_SYS rail VCC4V0_SYS (see page 13).

USBVBUS → SY8386J → VCC5V0_SYS
USBVBUS → SY8386J → VCC4V0_SYS

USBVBUS ( TypeC port) --> DC_IN--> 12V

In this design, the SY8386J operates as a step‑down converter, supplying both VCC4V0_SYS and VCC5V0_SYS rails and P! PMIC.

SY8386 is a high-efficiency synchronous step-down DC/DC regulator capable of delivering up to 6A with wide input voltage support and multiple protection features.
Datasheet [1] https://datasheet4u.com/download_new.php?id=1604744

I have tried to elaborate as clearly as I can.

Quoted 20 lines

Quoted 7 lines

Quoted 2 lines

Any probe failure or something bad happen? (besides /sys/../regulator_summay)

Not really; the regulator summary just confirms the PMIC used the correct power source.
with te device ip blocks.

then I see it's unnecessary to add this

Quoted 11 lines

Bananapi F3 schematics.
[1] https://drive.google.com/file/d/19iLJ5xnCB_oK8VeQjkPGjzAn39WYyylv/view
(page 24)

Please check the shematics VCC5V0_SYS page 4 VCC5V0_SYS->USB_VCC5V0->HDMI_VCC5V0->FAN_VCC5V0->VCC3V3_SYS

Please check the shematics VCC5V0_SYS page 24 VCC5V0_SYS input for VCC5V0_HUB and 5V_VBUS give the USB hub, which is enabled by USB3_PWREN (gpio pin)>

Quoted 6 lines

Quoted 5 lines

Plese check power tree page 4
USBVBUS->SY8386J UXXX -> PCIE_VCC3V3 for pcie vin source

So, this series tries to fix the vin source for USB 3.0 and PCIe nodes.

This is not what I ask..

Opps, I tried, but I wasn’t able to clearly elaborate on how the power sources are distributed across the various peripherals.

Hi Anand,

Quoted 48 lines · Anand Moon

Hi Yixun,

Quoted 45 lines · Yixun Lan

Hi Anand,

Quoted 41 lines · Anand Moon

Hi Yixun,

Thanks for your review comments.

Quoted 25 lines · Yixun Lan

Hi Anand,

Quoted 21 lines · Anand Moon

Define the system 5V fixed regulator (vcc5v0_sys) supplied by the DC input. As per the schematics, vcc5v0_sys is the input power source for the VCC5V0_HUB and 5V_VBUS reglators. Update these regulators to correctly reference vcc5v0_sys as their parent (vin-supply).

Cc Han Gao <[email protected]>

Cc Ze Huang <[email protected]>

Cc Chukun Pan <[email protected]>

Signed-off-by Anand Moon <[email protected]>

---
 arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++++++++++++
 1 file changed, 12 insertions(+)

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +0 -0

index 5790d927b93d..9727ecdd9f6b 100644
@@ -50,6 +50,16 @@ reg_dc_in: regulator-dc-in-12v {
              regulator-always-on;
      };
 

Quoted 7 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts reg_dc_in: regulator-dc-in-12v { · line 53

Quoted 1 line

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

+     reg_vcc5v0_sys: regulator-vcc5v0-sys {

This will fall into the catogery of "non-controllable & serve no devices" see similar comment for 'reg_dc_in' which raised by Krzysztof

https://lore.kernel.org/all/[email protected]/

or should I ask, what's the real problem if regulator has no vin-supply?

If the device tree is not configured with the correct power source it will affect performance.

Quoted 4 lines

Quoted 2 lines

Please elaborate, or provide enough evidence to prove this, because the conclusion you gave here contradicts with what Krzysztof pointed out

I don’t have the schematic for that board, so I skipped replying.

No, you didn't answer my question, I was asking why "affect performance", and you just gave me the opposite conclusion

Let me elaborate, the reg_vcc5v0_sys is a regulator that has no software or GPIO control, so no need software control from the kernel/driver perspective, which also mean it will be automatically enabled from hardware perspective once the board power up - "non-controllable" in Krzysztof's reply

the reg_vcc5v0_sys currently only serve as vin for other regulator which is not a device (e.g not USB, PCIe, eMMC..) - "serve no devices" in Krzysztof's reply..

and by introducing reg_vcc5v0_sys, kernel driver need to do additional work to go through probe procedure and register the regulator device, consumer depend on it need to wait, this will hurt performance, slow down system boot and even consume more memory..

By dropping reg_vcc5v0_sys, it will result as a stripped power source tree, this is only downside I can see, but doesn't really hurt..

Quoted 21 lines

Please refer to the POWER TREE diagram, which provides a clear visualization of the power sources.

This board accepts two primary power sources: a 12 V DC input and USB Type‑C power.
From the schematic’s power tree (page 4):

Type‑C → DC_IN→ SY8386J (Uxxx) → PI PMIC

According to the block diagram, the SY8386J regulator IC is responsible for generating the VCC5V0_SYS rail VCC4V0_SYS (see page 13).

USBVBUS → SY8386J → VCC5V0_SYS
USBVBUS → SY8386J → VCC4V0_SYS

USBVBUS ( TypeC port) --> DC_IN--> 12V

In this design, the SY8386J operates as a step‑down converter, supplying both VCC4V0_SYS and VCC5V0_SYS rails and P! PMIC.

Quoted 4 lines

SY8386 is a high-efficiency synchronous step-down DC/DC regulator capable of delivering up to 6A with wide input voltage support and multiple protection features.
Datasheet [1] https://datasheet4u.com/download_new.php?id=1604744

so right, SY8386 is a passive device which need no software control, non-controllable..

Quoted 25 lines

I have tried to elaborate as clearly as I can.

Quoted 23 lines

Quoted 7 lines

Quoted 2 lines

Any probe failure or something bad happen? (besides /sys/../regulator_summay)

Not really; the regulator summary just confirms the PMIC used the correct power source.
with te device ip blocks.

then I see it's unnecessary to add this

Quoted 14 lines

Bananapi F3 schematics.
[1] https://drive.google.com/file/d/19iLJ5xnCB_oK8VeQjkPGjzAn39WYyylv/view
(page 24)

Please check the shematics VCC5V0_SYS page 4 VCC5V0_SYS->USB_VCC5V0->HDMI_VCC5V0->FAN_VCC5V0->VCC3V3_SYS

Please check the shematics VCC5V0_SYS page 24 VCC5V0_SYS input for VCC5V0_HUB and 5V_VBUS give the USB hub, which is enabled by USB3_PWREN (gpio pin)>

Plese check power tree page 4
USBVBUS->SY8386J UXXX -> PCIE_VCC3V3 for pcie vin source

Quoted 5 lines

Quoted 3 lines

Quoted 2 lines

So, this series tries to fix the vin source for USB 3.0 and PCIe nodes.

This is not what I ask..

Opps, I tried, but I wasn’t able to clearly elaborate on how the power sources are distributed across the various peripherals.

Hope I make it clear this time..

--
Yixun Lan (dlan)

Review

Quoted 2 lines

(quoted diff) +1 -1

-             vdd-supply = <&usb3_hub_5v>;
+             vdd-supply = <&reg_5v_vbus>;

As per the schematics USB3_PWREN (GPIO97) pin is used to power the USB hub ports 5V_VBUS, please check this again.

VCC5V0_SYS -> USB3_PWREN -> 5V_VBUS

5V_VBUS is used to power all the USB3_TypeA_Dual ports.

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

@@ -39,6 +39,7 @@ pcie_vcc_3v3: regulator-pcie-vcc3v3 {
 		regulator-min-microvolt = <3300000>;
 		regulator-max-microvolt = <3300000>;
 		regulator-always-on;
+		vin-supply = <&reg_vcc5v0_sys>;
 	};
 

Plese check power tree page 4

USBVBUS->SY8386J UXXX -> PCIE_VCC3V3 for pcie vin source

USBVBUS is power source from the typec port.

Hi,

Quoted 6 lines

arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +1 -0

@@ -39,6 +39,7 @@ pcie_vcc_3v3: regulator-pcie-vcc3v3 {
              regulator-min-microvolt = <3300000>;
              regulator-max-microvolt = <3300000>;
              regulator-always-on;
+             vin-supply = <&reg_vcc5v0_sys>;
      };

Quoted 5 lines

Plese check power tree page 4

USBVBUS->SY8386J UXXX -> PCIE_VCC3V3 for pcie vin source

USBVBUS is power source from the typec port.

So this isn't from VCC5V0_SYS. USBVBUS and DC_IN can be considered as the same power source.