Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751654AbdG1IUE (ORCPT ); Fri, 28 Jul 2017 04:20:04 -0400 Received: from lucky1.263xmail.com ([211.157.147.135]:54850 "EHLO lucky1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbdG1IUC (ORCPT ); Fri, 28 Jul 2017 04:20:02 -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 01/11] net: phy: Add rockchip phy driver support To: Florian Fainelli , davem@davemloft.net, heiko@sntech.de, andrew@lunn.ch, 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 Cc: 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> <1501160156-30328-2-git-send-email-david.wu@rock-chips.com> <807c43ee-8421-c0b3-8aea-6091bef07a4c@gmail.com> From: "David.Wu" Message-ID: Date: Fri, 28 Jul 2017 16:19:52 +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: <807c43ee-8421-c0b3-8aea-6091bef07a4c@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: 602 Lines: 21 Hi Florian, 在 2017/7/28 0:51, Florian Fainelli 写道: >> +} >> + >> +static int rockchip_internal_phy_config_init(struct phy_device *phydev) >> +{ >> + int val; >> + >> + /* >> + * The auto MIDX has linked problem on some board, >> + * workround to disable auto MDIX. >> + */ > If this a board-specific problem you may consider register a PHY fixup > for the affected boards, or introduce a specific property to illustrate > that MDI-X is broken. You mean is that if I need disable Auto-mdix, then I'm going to add a property to DTS, from here to decide whether or not to close Auto-mdix? >