From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Hesselbarth Subject: Re: [PATCH v5 09/10] ARM: dts: berlin: add the Ethernet node Date: Mon, 29 Sep 2014 16:34:02 +0200 Message-ID: <54296DDA.8000400@gmail.com> References: <1411742036-23520-1-git-send-email-antoine.tenart@free-electrons.com> <1411742036-23520-10-git-send-email-antoine.tenart@free-electrons.com> <5425A178.4050501@cogentembedded.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: thomas.petazzoni@free-electrons.com, zmxu@marvell.com, devicetree@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, alexandre.belloni@free-electrons.com, jszhang@marvell.com, linux-arm-kernel@lists.infradead.org To: Sergei Shtylyov , Antoine Tenart Return-path: In-Reply-To: <5425A178.4050501@cogentembedded.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 09/26/2014 07:25 PM, Sergei Shtylyov wrote: > On 09/26/2014 06:33 PM, Antoine Tenart wrote: >> This patch adds the Ethernet node, enabling the network unit on Berlin >> BG2Q SoCs. > >> Signed-off-by: Antoine Tenart >> Acked-by: Arnd Bergmann >> --- >> arch/arm/boot/dts/berlin2q.dtsi | 17 +++++++++++++++++ >> 1 file changed, 17 insertions(+) > >> diff --git a/arch/arm/boot/dts/berlin2q.dtsi >> b/arch/arm/boot/dts/berlin2q.dtsi >> index 902eddb19cd8..d442b22fd1ea 100644 >> --- a/arch/arm/boot/dts/berlin2q.dtsi >> +++ b/arch/arm/boot/dts/berlin2q.dtsi >> @@ -114,6 +114,23 @@ >> #interrupt-cells = <3>; >> }; >> >> + eth0: ethernet@b90000 { >> + compatible = "marvell,pxa168-eth"; >> + reg = <0xb90000 0x10000>; >> + clocks = <&chip CLKID_GETH0>; >> + interrupts = ; >> + /* set by bootloader */ >> + local-mac-address = [00 00 00 00 00 00]; >> + #address-cells = <1>; >> + #size-cells = <0>; >> + phy-handle = <ðphy0>; >> + status = "disabled"; >> + >> + ethphy0: ethernet-phy@0 { >> + reg = <0>; >> + }; >> + }; >> + > > Hm, is the PHY internal to the Ethernet controller? Sergei, at least for BG2 and BG2CD the PHY is internal to the SoC. Also, MDIO bus is part of the ethernet IP, so placing the PHY inside the combined Ethernet/MDIO IP node is sane. Sebastian