[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c92ffbe9-dfb0-0fd7-680d-699c31902534@rock-chips.com>
Date: Fri, 28 Jul 2017 16:19:52 +0800
From: "David.Wu" <david.wu@...k-chips.com>
To: Florian Fainelli <f.fainelli@...il.com>, davem@...emloft.net,
heiko@...ech.de, andrew@...n.ch, robh+dt@...nel.org,
mark.rutland@....com, catalin.marinas@....com, will.deacon@....com,
olof@...om.net, linux@...linux.org.uk, arnd@...db.de
Cc: peppe.cavallaro@...com, alexandre.torgue@...com,
huangtao@...k-chips.com, hwg@...k-chips.com,
netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 01/11] net: phy: Add rockchip phy driver support
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?
>
Powered by blists - more mailing lists