Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751994AbdG1G4N (ORCPT ); Fri, 28 Jul 2017 02:56:13 -0400 Received: from lucky1.263xmail.com ([211.157.147.135]:53578 "EHLO lucky1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751843AbdG1G4L (ORCPT ); Fri, 28 Jul 2017 02:56:11 -0400 X-263anti-spam: KSV:0; X-MAIL-GRAY: 1 X-MAIL-DELIVERY: 0 X-KSVirus-check: 0 X-ABS-CHECKED: 4 X-RL-SENDER: david.wu@rock-chips.com X-FST-TO: linux-kernel@vger.kernel.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: david.wu@rock-chips.com X-UNIQUE-TAG: X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH v2 05/11] net: stmmac: dwmac-rk: Add internal phy support To: Florian Fainelli , Andrew Lunn Cc: davem@davemloft.net, heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com, catalin.marinas@arm.com, will.deacon@arm.com, olof@lixom.net, linux@armlinux.org.uk, arnd@arndb.de, peppe.cavallaro@st.com, alexandre.torgue@st.com, huangtao@rock-chips.com, hwg@rock-chips.com, netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <1501160156-30328-1-git-send-email-david.wu@rock-chips.com> <1501160540-30662-1-git-send-email-david.wu@rock-chips.com> <20170727134834.GD18666@lunn.ch> <65ae1747-4dff-b1d8-8aa3-684fc8c7809a@gmail.com> From: "David.Wu" Message-ID: <69ad9443-ff65-8e49-df68-7e5e6c812d45@rock-chips.com> Date: Fri, 28 Jul 2017 14:56:03 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <65ae1747-4dff-b1d8-8aa3-684fc8c7809a@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 809 Lines: 18 Hi Florian, 在 2017/7/28 0:54, Florian Fainelli 写道: > - if you need knowledge about this PHY connection type prior to binding > the PHY device and its driver (that is, before of_phy_connect()) we > could add a boolean property e.g: "phy-is-internal" that allows us to > know that, or we can have a new phy-mode value, e.g: "internal-rmii" > which describes that, either way would probably be fine, but the former > scales better > Using "phy-is-internal" is very helpful, but it is easy to confuse with the real internal PHY, may we use the other words like phy is inlined????. > Then again, using phy-mode = "internal" even though this is Reduced MII > is not big of a deal IMHO as long as there is no loss of information and > that internal de-facto means internal reduced MII for instance. > --