lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <sGs7xDSqFTh3IlaINxzE4GvtEWPKTTL252AMKaa9ktXAWg-EvzJ7cHHYfFIg3ga3A68lQpo_rxEYHTj8ULaCCscjHILi0vzuRwPCpslpL54=@proton.me>
Date: Mon, 13 Oct 2025 11:43:45 +0000
From: Zoo Moo <zoomoo100@...ton.me>
To: Marcin Wojtas <marcin.s.wojtas@...il.com>
Cc: "Russell King (Oracle)" <linux@...linux.org.uk>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Marvell 375 and Marvel 88E1514 Phy network problem: mvpp2 or DTS related?

On Saturday, 11 October 2025 at 19:27, Marcin Wojtas <marcin.s.wojtas@...il.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?
Download attachment "publickey - zoomoo100@...ton.me - 0x1C985C6F.asc" of type "application/pgp-keys" (836 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (344 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ