Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751744AbdG1JpS (ORCPT ); Fri, 28 Jul 2017 05:45:18 -0400 Received: from smtp.csie.ntu.edu.tw ([140.112.30.61]:52582 "EHLO smtp.csie.ntu.edu.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbdG1JpQ (ORCPT ); Fri, 28 Jul 2017 05:45:16 -0400 MIME-Version: 1.0 In-Reply-To: <20170728092818.23419-3-clabbe.montjoie@gmail.com> References: <20170728092818.23419-1-clabbe.montjoie@gmail.com> <20170728092818.23419-3-clabbe.montjoie@gmail.com> From: Chen-Yu Tsai Date: Fri, 28 Jul 2017 17:44:51 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 2/3] ARM: sunxi: h3/h5: Add sun8i-h3-ephy compatible To: Corentin Labbe Cc: Rob Herring , Mark Rutland , Maxime Ripard , Chen-Yu Tsai , Russell King , Giuseppe Cavallaro , alexandre.torgue@st.com, Icenowy Zheng , netdev , devicetree , linux-arm-kernel , linux-kernel , linux-sunxi Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1733 Lines: 44 On Fri, Jul 28, 2017 at 5:28 PM, Corentin Labbe wrote: > This patch adds the sun8i-h3-ephy compatible to the internal PHY. > > Signed-off-by: Corentin Labbe > --- > arch/arm/boot/dts/sunxi-h3-h5.dtsi | 3 ++- To avoid repeating the past, this patch, if approved, will be merged through the sunxi tree, not netdev nor net-next. > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm/boot/dts/sunxi-h3-h5.dtsi b/arch/arm/boot/dts/sunxi-h3-h5.dtsi > index 4b599b5d26f6..7aaa837c2388 100644 > --- a/arch/arm/boot/dts/sunxi-h3-h5.dtsi > +++ b/arch/arm/boot/dts/sunxi-h3-h5.dtsi > @@ -421,7 +421,8 @@ > #address-cells = <1>; > #size-cells = <0>; > int_mii_phy: ethernet-phy@1 { > - compatible = "ethernet-phy-ieee802.3-c22"; > + compatible = "allwinner,sun8i-h3-ephy", > + "ethernet-phy-ieee802.3-c22"; Are you expecting people to override this properly? As it currently is, any external phy at address 1 will simply reuse the same device node. And if they don't override the property correctly, the driver will end up trying to use the internal phy, while the user is expecting the external one to be used. Maybe you could move this to some other address, maybe the last valid one, or second last valid one? ChenYu > reg = <1>; > clocks = <&ccu CLK_BUS_EPHY>; > resets = <&ccu RST_BUS_EPHY>; > -- > 2.13.0 >