Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Zoo Moo]

[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]

Hi,

Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.

Even though the eth0 device is detected with the tweaked DTS for the 6.6 kernel. Eth0 can send packets (according to ifconfig and ethtool -S), but nothing is ever received by the device or the router.

Even if I manually set an IP and MAC address for eth0 I cannot detect any packets leaving the DS215j as I cannot ping/telnet/nmap/wireshark the DS215J. There is also no LED activity on the network hub.

The eth0 interfaces works when booting the stock Synology DSM OS which is based on the very old Synology modified 3.x linux kernel. Source is available from:
https://global.synologydownload.com/download/ToolChain/Synology%20NAS%20GPL%20Source/7.1.1-42962/armada375/linux-3.x.txz

However, the Synology kernel does not use DTS and uses a custom build environment.
https://help.synology.com/developer-guide/

Please see the below thread for the gory details of attempting to get DS215j to work:

Debian on Synology DS215j
https://forum.doozan.com/read.php?2,138851


I've created the bugzilla issue with further details:

https://bugzilla.kernel.org/show_bug.cgi?id=220591

Cheers,
ZM


Sent with Proton Mail secure email.

[-- Attachment #1.2: publickey - zoomoo100@proton.me - 0x1C985C6F.asc --]
[-- Type: application/pgp-keys, Size: 836 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Russell King (Oracle)]

On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> Hi,
> 
> Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.

Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
isn't correct. Just a guess based on the problems that RGMII normally
causes.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Zoo Moo]

[-- Attachment #1.1: Type: text/plain, Size: 2881 bytes --]

Sent with Proton Mail secure email.

On Sunday, 21 September 2025 at 19:56, Russell King (Oracle) <linux@armlinux.org.uk> wrote:

> On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> 

> > Hi,
> > 

> > Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.
> 

> 

> Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
> isn't correct. Just a guess based on the problems that RGMII normally
> causes.

Hi Russell,

Thanks, we did try different drivers (gmii, sgmii), but they didn't help, details in this message https://forum.doozan.com/read.php?2,138851,139291#msg-139291.

I'm happy to try again if you think it will help with debugging.

The uboot log indicates the rgmii is the correct driver ("RGMII0 Module on MAC0"). Or is it misleading?

--------------------------------------------------
BootROM - 1.51
Booting from SPI flash


General initialization - Version: 1.0.0
High speed PHY - Version: 0.1.1 (COM-PHY-V20) 

USB2 UTMI PHY initialized succesfully
USB2 UTMI PHY initialized succesfully
High speed PHY - Ended Successfully

DDR3 Training Sequence - Ver 5.7.1
TWSI Read failed
Error reading from TWSI
DDR3 Training Sequence - Run with PBS.
DDR3 Training Sequence - Ended Successfully 

BootROM: Image checksum verification PASSED

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 

        | | | |___|  _ \ / _ \ / _ \| __| 

        | |_| |___| |_) | (_) | (_) | |_ 

         \___/    |____/ \___/ \___/ \__| 

 ** LOADER **


U-Boot 2013.01-g5d1ab78 (Oct 27 2015 - 11:38:34) Marvell version: 2014_T2.0p3

mvBoardTwsiGet: Twsi Read fail
mvBoardIoExpValSet: Error: Read from IO Expander failed
Board: SYNO-DS215j
SoC:   MV88F6720 Rev A0
       running 2 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
       CPU 0
       CPU    @ 800 [MHz]
       L2     @ 400 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 534 [MHz]
       DDR 16Bit Width, FastPath Memory Access, DLB Enabled
DRAM:  512 MiB

Map:   Code:		0x1fed2000:0x1ff93080
       BSS:		0x1ffefe10
       Stack:		0x1f9c1f20
       Heap:		0x1f9c2000:0x1fed2000

MMC:   MRVL_MMC: 0
SF: Detected MX25L6405D with page size 64 KiB, total 8 MiB
PCI-e 0: Detected No Link.
USB2.0 0: Host Mode
USB2.0 1: Device Mode
USB3.0 0: Host Mode
Board configuration detected:
	RGMII0 Module on MAC0
	PON ETH SERDES on MAC1 [SFP]
SERDES configuration:
	Lane #0: PCIe0
	Lane #1: SATA1
	Lane #2: SATA0
	Lane #3: USB3

Synology Model: DS215j
Fan Status: Good

[-- Attachment #1.2: publickey - zoomoo100@proton.me - 0x1C985C6F.asc --]
[-- Type: application/pgp-keys, Size: 836 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Russell King (Oracle)]

On Mon, Sep 22, 2025 at 08:58:49AM +0000, Zoo Moo wrote:
> Sent with Proton Mail secure email.
> 
> On Sunday, 21 September 2025 at 19:56, Russell King (Oracle) <linux@armlinux.org.uk> wrote:
> 
> > On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> > 
> 
> > > Hi,
> > > 
> 
> > > Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.
> > 
> 
> > 
> 
> > Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
> > isn't correct. Just a guess based on the problems that RGMII normally
> > causes.
> 
> Hi Russell,
> 
> Thanks, we did try different drivers (gmii, sgmii), but they didn't help, details in this message https://forum.doozan.com/read.php?2,138851,139291#msg-139291.

What I was meaning was not to try stuff like "SGMII", but try the _other_
three flavours of RGMII. In other words:

	rgmii
	rgmii-txid
	rgmii-rxid

If u-boot works, and it's using RGMII, then it's definitely one of the
four flavours of RGMII interface.

No need to post the failures of the testing to the forums - just say
here whether any of those result in packet flow or not. Nothing else
should change - the only difference between these modes are the timings
of the RGMII interface, and having the wrong mode is the most common
reason for RGMII not working.

Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Zoo Moo]

[-- Attachment #1.1: Type: text/plain, Size: 3389 bytes --]






Sent with Proton Mail secure email.

On Monday, 22 September 2025 at 19:22, Russell King (Oracle) <linux@armlinux.org.uk> wrote:

> On Mon, Sep 22, 2025 at 08:58:49AM +0000, Zoo Moo wrote:
> 

> > Sent with Proton Mail secure email.
> > 

> > On Sunday, 21 September 2025 at 19:56, Russell King (Oracle) linux@armlinux.org.uk wrote:
> > 

> > > On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> > 

> > > > Hi,
> > 

> > > > Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.
> > 

> > > Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
> > > isn't correct. Just a guess based on the problems that RGMII normally
> > > causes.
> > 

> > Hi Russell,
> > 

> > Thanks, we did try different drivers (gmii, sgmii), but they didn't help, details in this message https://forum.doozan.com/read.php?2,138851,139291#msg-139291.
> 

> 

> What I was meaning was not to try stuff like "SGMII", but try the other
> three flavours of RGMII. In other words:
> 

> rgmii
> rgmii-txid
> rgmii-rxid
> 

> If u-boot works, and it's using RGMII, then it's definitely one of the
> four flavours of RGMII interface.
> 

> No need to post the failures of the testing to the forums - just say
> here whether any of those result in packet flow or not. Nothing else
> should change - the only difference between these modes are the timings
> of the RGMII interface, and having the wrong mode is the most common
> reason for RGMII not working.
> 

> Thanks.
> 

> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

Thanks Russel,

I tried all flavours again (rgmii, rgmii-id, rgmii-txid and rgmii-rxid), but all resulted in the same outcome. 


ifconfig shows it sends packets, but nothing is received. I cannot detect it actually sending any packets from the device though.

For example:

root@(none):~# ifconfig eth0 192.168.27.111 netmask 255.255.255.0 up hw ether 00:11:22:33:44:55
[   31.727773][ T2055] mvpp2 f10f0000.ethernet eth0: PHY [f10c0054.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
[   31.738178][ T2055] mvpp2 f10f0000.ethernet eth0: configuring for phy/rgmii-txid link mode
[   36.007360][   T10] mvpp2 f10f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off

root@(none):~# dhclient eth0
root@(none):~# ifconfig eth0                                                   

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500                     

        inet 192.168.27.111  netmask 255.255.255.0  broadcast 192.168.27.255
        inet6 <IP6 ADDRESS>  prefixlen 64  scopeid 0x20<link>
        ether 00:11:22:33:44:55  txqueuelen 2048  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 71  bytes 4858 (4.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Do I need to adjust the internal delays? rx-internal-delay-ps/tx-internal-delay-ps

(reference: https://www.thegoodpenguin.co.uk/blog/linux-ethernet-phy-mode-bindings-explained/)

Is it something we can determine by looking at the Synology kernel source?

[-- Attachment #1.2: publickey - zoomoo100@proton.me - 0x1C985C6F.asc --]
[-- Type: application/pgp-keys, Size: 836 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Zoo Moo]

[-- Attachment #1.1: Type: text/plain, Size: 3563 bytes --]

On Wednesday, September 24th, 2025 at 11:33 AM, Zoo Moo <zoomoo100@proton.me> wrote:
> 

> On Monday, 22 September 2025 at 19:22, Russell King (Oracle) linux@armlinux.org.uk wrote:
> 

> > On Mon, Sep 22, 2025 at 08:58:49AM +0000, Zoo Moo wrote:
> > 

> > > Sent with Proton Mail secure email.
> > > 

> > > On Sunday, 21 September 2025 at 19:56, Russell King (Oracle) linux@armlinux.org.uk wrote:
> > > 

> > > > On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> > > 

> > > > > Hi,
> > > 

> > > > > Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.
> > > 

> > > > Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
> > > > isn't correct. Just a guess based on the problems that RGMII normally
> > > > causes.
> > > 

> > > Hi Russell,
> > > 

> > > Thanks, we did try different drivers (gmii, sgmii), but they didn't help, details in this message https://forum.doozan.com/read.php?2,138851,139291#msg-139291.
> > 

> > What I was meaning was not to try stuff like "SGMII", but try the other
> > three flavours of RGMII. In other words:
> > 

> > rgmii
> > rgmii-txid
> > rgmii-rxid
> > 

> > If u-boot works, and it's using RGMII, then it's definitely one of the
> > four flavours of RGMII interface.
> > 

> > No need to post the failures of the testing to the forums - just say
> > here whether any of those result in packet flow or not. Nothing else
> > should change - the only difference between these modes are the timings
> > of the RGMII interface, and having the wrong mode is the most common
> > reason for RGMII not working.
> > 

> > Thanks.
> > 

> > --
> > RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> > FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
> 

> 

> Thanks Russel,
> 

> I tried all flavours again (rgmii, rgmii-id, rgmii-txid and rgmii-rxid), but all resulted in the same outcome.
> 

> ifconfig shows it sends packets, but nothing is received. I cannot detect it actually sending any packets from the device though.
> 

> For example:
> 

> root@(none):~# ifconfig eth0 192.168.27.111 netmask 255.255.255.0 up hw ether 00:11:22:33:44:55
> [ 31.727773][ T2055] mvpp2 f10f0000.ethernet eth0: PHY [f10c0054.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
> [ 31.738178][ T2055] mvpp2 f10f0000.ethernet eth0: configuring for phy/rgmii-txid link mode
> [ 36.007360][ T10] mvpp2 f10f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
> 

> root@(none):~# dhclient eth0
> root@(none):~# ifconfig eth0
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> 

> inet 192.168.27.111 netmask 255.255.255.0 broadcast 192.168.27.255
> inet6 <IP6 ADDRESS> prefixlen 64 scopeid 0x20<link>
> 

> ether 00:11:22:33:44:55 txqueuelen 2048 (Ethernet)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 71 bytes 4858 (4.7 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> 

> Do I need to adjust the internal delays? rx-internal-delay-ps/tx-internal-delay-ps
> 

> (reference: https://www.thegoodpenguin.co.uk/blog/linux-ethernet-phy-mode-bindings-explained/)
> 

> Is it something we can determine by looking at the Synology kernel source?


Hi,

Any other suggestions I could try to debug this issue?

Appreciate any suggestions.

Cheers,
ZM

[-- Attachment #1.2: publickey - zoomoo100@proton.me - 0x1C985C6F.asc --]
[-- Type: application/pgp-keys, Size: 836 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Marcin Wojtas]

Hi ZM,

Have you checked pinctrl settings? The MDIO looks like properly
working, so I'd double-check if the pins that are assigned to RGMII in
U-Boot (I assume the interface works there), are not overriden by e.g.
wrong device tree configuration in kernel.

Best regards,
Marcin


śr., 1 paź 2025 o 05:05 Zoo Moo <zoomoo100@proton.me> napisał(a):
>
> On Wednesday, September 24th, 2025 at 11:33 AM, Zoo Moo <zoomoo100@proton.me> wrote:
> >
>
> > On Monday, 22 September 2025 at 19:22, Russell King (Oracle) linux@armlinux.org.uk wrote:
> >
>
> > > On Mon, Sep 22, 2025 at 08:58:49AM +0000, Zoo Moo wrote:
> > >
>
> > > > Sent with Proton Mail secure email.
> > > >
>
> > > > On Sunday, 21 September 2025 at 19:56, Russell King (Oracle) linux@armlinux.org.uk wrote:
> > > >
>
> > > > > On Sun, Sep 21, 2025 at 09:05:18AM +0000, Zoo Moo wrote:
> > > >
>
> > > > > > Hi,
> > > >
>
> > > > > > Bodhi from Doozan (https://forum.doozan.com) has been helping me try to get Debian to work on a Synology DS215j NAS. The DS215j is based on a Marvell Armada 375 (88F6720) and uses a Marvel 88E1514 PHY.
> > > >
>
> > > > > Probably wrong RGMII phy-mode. I see you're using rgmii-id. Maybe that
> > > > > isn't correct. Just a guess based on the problems that RGMII normally
> > > > > causes.
> > > >
>
> > > > Hi Russell,
> > > >
>
> > > > Thanks, we did try different drivers (gmii, sgmii), but they didn't help, details in this message https://forum.doozan.com/read.php?2,138851,139291#msg-139291.
> > >
>
> > > What I was meaning was not to try stuff like "SGMII", but try the other
> > > three flavours of RGMII. In other words:
> > >
>
> > > rgmii
> > > rgmii-txid
> > > rgmii-rxid
> > >
>
> > > If u-boot works, and it's using RGMII, then it's definitely one of the
> > > four flavours of RGMII interface.
> > >
>
> > > No need to post the failures of the testing to the forums - just say
> > > here whether any of those result in packet flow or not. Nothing else
> > > should change - the only difference between these modes are the timings
> > > of the RGMII interface, and having the wrong mode is the most common
> > > reason for RGMII not working.
> > >
>
> > > Thanks.
> > >
>
> > > --
> > > RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> > > FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
> >
>
> >
>
> > Thanks Russel,
> >
>
> > I tried all flavours again (rgmii, rgmii-id, rgmii-txid and rgmii-rxid), but all resulted in the same outcome.
> >
>
> > ifconfig shows it sends packets, but nothing is received. I cannot detect it actually sending any packets from the device though.
> >
>
> > For example:
> >
>
> > root@(none):~# ifconfig eth0 192.168.27.111 netmask 255.255.255.0 up hw ether 00:11:22:33:44:55
> > [ 31.727773][ T2055] mvpp2 f10f0000.ethernet eth0: PHY [f10c0054.mdio-mii:01] driver [Marvell 88E1510] (irq=POLL)
> > [ 31.738178][ T2055] mvpp2 f10f0000.ethernet eth0: configuring for phy/rgmii-txid link mode
> > [ 36.007360][ T10] mvpp2 f10f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
> >
>
> > root@(none):~# dhclient eth0
> > root@(none):~# ifconfig eth0
> > eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
> >
>
> > inet 192.168.27.111 netmask 255.255.255.0 broadcast 192.168.27.255
> > inet6 <IP6 ADDRESS> prefixlen 64 scopeid 0x20<link>
> >
>
> > ether 00:11:22:33:44:55 txqueuelen 2048 (Ethernet)
> > RX packets 0 bytes 0 (0.0 B)
> > RX errors 0 dropped 0 overruns 0 frame 0
> > TX packets 71 bytes 4858 (4.7 KiB)
> > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> >
>
> > Do I need to adjust the internal delays? rx-internal-delay-ps/tx-internal-delay-ps
> >
>
> > (reference: https://www.thegoodpenguin.co.uk/blog/linux-ethernet-phy-mode-bindings-explained/)
> >
>
> > Is it something we can determine by looking at the Synology kernel source?
>
>
> Hi,
>
> Any other suggestions I could try to debug this issue?
>
> Appreciate any suggestions.
>
> Cheers,
> ZM

Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

[Zoo Moo]

[-- Attachment #1.1: Type: text/plain, Size: 2724 bytes --]

On Saturday, 11 October 2025 at 19:27, Marcin Wojtas <marcin.s.wojtas@gmail.com> wrote:

> Hi ZM,
> 

> Have you checked pinctrl settings? The MDIO looks like properly
> working, so I'd double-check if the pins that are assigned to RGMII in
> U-Boot (I assume the interface works there), are not overriden by e.g.
> wrong device tree configuration in kernel.
> 

> Best regards,
> Marcin



Hi Marcin,

Thanks for the suggestion. I've looked at the pinctrl settings in the following files and there is nothing set for the 375.

arch/arm/boot/dts/marvell/armada-375.dtsi
arch/arm/boot/dts/marvell/armada-375-synology-ds215j.dts

The missing pinctrl also explain why the SATA drives are not powering up and detected in the Synology when booting the kernel. 

However, the WD MyCloud Gen2's ethernet and SATA do work without the pinctrl settings for SATA and MDIO being set (https://forum.doozan.com/read.php?2,94839,page=1).
Which is why the synology DS215J is hard to solve as it "should" work in a similar way.

arch/arm/boot/dts/marvell/armada-375-wd-mycloud-gen2.dts

None the less, I tried adding the pinctrl based on the information within the following files, but without success:

drivers/pinctrl/mvebu/pinctrl-armada-375.c
Documentation/devicetree/bindings/pinctrl/marvell,armada-375-pinctrl.txt


I added the following pin definitions to armada-375.dtsi:

mdio_pins: mdio-pins {
	marvell,pins = "mpp37", "mpp38";
	marvell,function = "ge";
};

ge0_rgmii_pins: ge0-rgmii-pins {
	marvell,pins = "mpp5", "mpp6", "mpp7", "mpp8",
			"mpp9", "mpp10", "mpp11", "mpp12",
			"mpp13", "mpp14", "mpp15", "mpp16";
	marvell,function = "ge0";
};

ge1_rgmii_pins: ge1-rgmii-pins {
	marvell,pins = "mpp24", "mpp25", "mpp26", "mpp27",
			"mpp28", "mpp29", "mpp30", "mpp31",
			"mpp32", "mpp33", "mpp34", "mpp35";
	marvell,function = "ge1";
};


Updated the armada-375-synology-ds215j.dts with the following pinctrl's.

&mdio {
	pinctrl-0 = <&mdio_pins>;
	pinctrl-names = "default";
	status = "okay";
	phy1: ethernet-phy@1 {
		reg = <1>;
	};
};

&ethernet {
        status = "okay";
};

&eth1 {
	pinctrl-0 = <&ge1_rgmii_pins>;
	pinctrl-names = "default";
	status = "okay";

	phy = <&phy1>;
	phy-mode = "rgmii-id";
};

However, this didn't fix the problem. The DTS must be missing some other pinctrl (like powering on the SATA's interfaces)?
Looking at the many DTS's for the armada-370 arch (e.g. arch/arm/boot/dts/marvell/armada-370-synology-ds213j.dts) shows the complexity of setting up the board. Whilst the 375 is missing much of similar looking settings.

Is there any obvious missing GPIO/pincrlt settings that are missing from the armada-375?

[-- Attachment #1.2: publickey - zoomoo100@proton.me - 0x1C985C6F.asc --]
[-- Type: application/pgp-keys, Size: 836 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]