From mboxrd@z Thu Jan 1 00:00:00 1970 From: Corentin Labbe Subject: Re: [PATCH v2 2/2] ARM: sun8i: bananapi-m3: Enable dwmac-sun8i Date: Fri, 10 Nov 2017 06:50:15 +0100 Message-ID: <20171110055015.GA11040@Red> References: <20171109082950.21124-1-clabbe.montjoie@gmail.com> <20171109082950.21124-3-clabbe.montjoie@gmail.com> Reply-To: clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Chen-Yu Tsai Cc: Russell King , Mark Rutland , Maxime Ripard , Rob Herring , devicetree , linux-arm-kernel , linux-kernel , linux-sunxi List-Id: devicetree@vger.kernel.org On Fri, Nov 10, 2017 at 11:48:11AM +0800, Chen-Yu Tsai wrote: > On Thu, Nov 9, 2017 at 4:29 PM, Corentin Labbe > wrote: > > The dwmac-sun8i hardware is present on the bananapi m3 > > It uses an external PHY rtl8211e via RGMII. > > > > This patch create the needed emac and phy nodes. > > > > Signed-off-by: Corentin Labbe > > --- > > arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts | 18 ++++++++++++++++++ > > 1 file changed, 18 insertions(+) > > > > diff --git a/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts b/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts > > index c606af3dbfed..45bdd5c17829 100644 > > --- a/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts > > +++ b/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts > > @@ -52,6 +52,7 @@ > > compatible = "sinovoip,bpi-m3", "allwinner,sun8i-a83t"; > > > > aliases { > > + ethernet0 = &emac; > > serial0 = &uart0; > > }; > > > > @@ -88,6 +89,23 @@ > > /* TODO GL830 USB-to-SATA bridge downstream w/ GPIO power controls */ > > }; > > > > +&emac { > > + pinctrl-names = "default"; > > + pinctrl-0 = <&emac_rgmii_pins>; > > + phy-handle = <&ext_rgmii_phy>; > > + phy-mode = "rgmii"; > > Schematics say PHY is power by DC1SW from the PMIC. > Not sure why you don't need that. Have you tested your patch? Tested on 4.14.0-rc5-next-20171018+ I will try to check which uboot is used, perhaps it's an old uboot with some PMIC hack. Thanks Regards