summaryrefslogtreecommitdiffstats
path: root/arch/arm
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2014-03-06 15:41:55 +0100
committerJason Cooper <jason@lakedaemon.net>2014-03-06 20:08:05 +0000
commit0d2e63782cd2ce0a987ffc73f3b2c4afe8375f4c (patch)
tree94de9fe3b95629b85d8df60cac65304fb6b25451 /arch/arm
parentebe021e2688a1f6aaa092f8ea6e72899a2c61a91 (diff)
downloadlinux-0d2e63782cd2ce0a987ffc73f3b2c4afe8375f4c.tar.bz2
ARM: mvebu: use the correct phy connection mode on Armada 385 DB
On Armada 385 DB, while the "rgmii" PHY connection mode works fine with the generic PHY driver, it fails to work when the Marvell PHY driver is enabled in the kernel configuration, due to a finer handling of the PHY configuration. This is due to the fact that the phy connection mode should instead be "rgmii-id", i.e with the TX/RX delay mechanisms enabled. This fixes the network operation on Armada 385 DB with CONFIG_MARVELL_PHY=y. Without this patch and this option enabled, one would only get messages such as: mvneta f1070000.ethernet eth1: bad rx status 0cc10000 (crc error), size=70 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm')
-rw-r--r--arch/arm/boot/dts/armada-385-db.dts4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/boot/dts/armada-385-db.dts b/arch/arm/boot/dts/armada-385-db.dts
index 01b6cc76ddc8..9a136428ec29 100644
--- a/arch/arm/boot/dts/armada-385-db.dts
+++ b/arch/arm/boot/dts/armada-385-db.dts
@@ -62,13 +62,13 @@
ethernet@30000 {
status = "okay";
phy = <&phy1>;
- phy-mode = "rgmii";
+ phy-mode = "rgmii-id";
};
ethernet@70000 {
status = "okay";
phy = <&phy0>;
- phy-mode = "rgmii";
+ phy-mode = "rgmii-id";
};
mdio {