On Sat, 2016-12-03 at 00:47 +0100, Martin Blumenstingl wrote: > This resets the ethernet PHY during boot to get the PHY into a > "clean" > state. While here also specify the phy-handle of the ethmac node to > make the PHY configuration similar to the one we have on GXL devices. > > Signed-off-by: Martin Blumenstingl <martin.blumenstingl@xxxxxxxxxxxxx > m> > Tested-by: Neil Armstrong <narmstrong@xxxxxxxxxxxx> > --- > arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi | 15 > +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi > b/arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi > index 203be28..2abc553 100644 > --- a/arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi > +++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi > @@ -134,10 +134,25 @@ > pinctrl-names = "default"; > }; > > +&mdio0 { > + ethernet_phy0: ethernet-phy@0 { > + compatible = "ethernet-phy-ieee802.3-c22"; > + reg = <0>; Sorry for the late reply. I just tried on the p200 and this patch (serie) breaks the network on it. The PHY is not detected anymore. >From the KSZ9031 Datasheet : "PHY Address 0h is supported as the unique PHY address only; it is not supported as the broadcast PHY address [...]" So we can't just use the broadcast address here: reg should be <3>. > + }; > +}; > + > ðmac { > status = "okay"; > pinctrl-0 = <ð_rgmii_pins>; > pinctrl-names = "default"; > + > + phy-handle = <ðernet_phy0>; > + > + snps,reset-gpio = <&gpio GPIOZ_14 0>; > + snps,reset-delays-us = <0 10000 1000000>; > + snps,reset-active-low; > + > + phy-mode = "rgmii"; We can't define this in p20x. actually the p201 uses an rmii. I have not idea about gpio reset, or the phy address for the p201. I suppose it would be better to move this to meson-gxbb_p200.dts I don't know if anybody has a p201, but until we can confirm a working Ethernet configuration, we should probably drop it for the p201 Of course the problem was already there before this patch ... > }; > > &ir { -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html