From: Duan Andy <fugang.duan@freescale.com>
To: "plyatov@gmail.com" <plyatov@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>
CC: Florian Fainelli <f.fainelli@gmail.com>, Joe Perches <joe@perches.com>,
        Zhou David <luwei.zhou@freescale.com>,
        Richard Cochran <richardcochran@gmail.com>,
        "David S. Miller" <davem@davemloft.net>,
        "Uwe Kleine-K?nig" <u.kleine-koenig@pengutronix.de>,
        Fabio Estevam <Fabio.Estevam@freescale.com>,
        Lothar Wa?mann <LW@KARO-electronics.de>,
        "Li Frank" <Frank.Li@freescale.com>
Subject: RE: Buggy cable detection on i.MX51, fec driver and LAN8700 PHY
Thread-Topic: Buggy cable detection on i.MX51, fec driver and LAN8700 PHY
Thread-Index: AQHQyHudbApnKT1390CHNwBmxCZfo53wFjzA
Date: Tue, 28 Jul 2015 01:24:33 +0000
Message-ID: <BN3PR0301MB1219FE298512C24ABC97BE5FF58D0@BN3PR0301MB1219.namprd03.prod.outlook.com>
References: <55B6453C.10500@gmail.com>
In-Reply-To: <55B6453C.10500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
bn3pr0301mb1298: X-MS-Exchange-Organization-RulesExecuted
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jul 2015 01:24:33.8745
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 710a03f5-10f6-4d38-9ff4-a80b81da590d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0301MB1298
X-Microsoft-Exchange-Diagnostics: 1;BN3PR0301MB1316;2:gsBJIOrI+ZS1QXRn/oijhN6Ns6J1TjOkU7EFiWQATgKF3BxpzOS1HKuB72xVmkELotXOkHZkjpLy7oNjT5mGJjU/QDsy5OB/wq1rQPjB/xFIiY1x++Iou6ORxpxMKUb9ehAQ/G0AHTS41uOnsjCMBwrbRL2hodJEk/Ar4EJWkIo=;3:plkzaFPwOVoBoad+z8Juui0J+YzVsl7z+vd1QxwioS0yUkrckh7iLLIf3MPDUFqQkquwJFUOOJSL82KuDDUCRGlOEJiIGh6mzUmWy3+nTbrdaFnNJATQsw403F+jgpp11NBTlL1KFzjPmOjb7U32tg==;25:hsK3GdiBGdSzmqbtfKtpyZHfWFlAI0DHVhVpnBUcWY+QkXa7oTITiygoFwjy417Y/zL6PvHHfZ/2+aFqUoeN+c5/zlrornnLPW+qugffHDF5u7vS0GTQMSL24aHx3qxqW6IRzqbHQwSYImwhWnNy6EQ8Rgf8htr/zeJgiaHTyfzi6Fqs000/xNvil5ch8J04bME3QnaxYsCZwVj2R2n2S1wcb+Axd0rOhPvr1FdaAMopHYaTx295Z2Ky+ZZuoLn7FvSxFctYNBuzAUsJyn6eIw==
X-Microsoft-Exchange-Diagnostics: 1;BN3PR0301MB1316;20:DlUZstorUnv2icBVfkpIdaCxyi8oJ+r/z7LdqC1v2k/4YXFdxQUoLfEFsyl5JA6ZDN6jSOBzJxgm6GlKi/bMsotH0wy2v3IO2AM9PXRrSFVBwVall+XO0i1FuP1qRTeA6Uk4IOxzBqBr6tJgD5C9mTWhGd/E0nETxAnGkTOyBZnWsTsQ6ipOnLLHvkdgRgu4wyt1PUWI8sbrdf0sjdGiAC9EgaG0jnzsGZePsoZHm3WPNCq4dlwIAEyPcexl61CA3IAFjK3bnqm21IXSbv+Lspgi8JaPmIfbVyMSNKHzIAPkBjIZjVRCayCy3ECw0t5P++uUXIIC3tlSPItdqc2zGsJhQ0wu3Y4GUeBn7XToEGDB+icFwBCD0csneuD0Xx3AYbQZhIjhHRDoTUawnBfNwiN3/quikoEP/uz1ZQY8l23UttpyTCUH8BrF36r9KVs2PDY8knWszP28aCUDZ/SJo3zsITh81xg2i/omdF4whO10gUCKwzJL0lNoV/2o0k4a;23:aj3XTHF2lVf8zcGaweuiOUSxDXFtLeIDyDFqYEj8kMAjkFcrfeb67Ea/aa2a1fARN8or/JKp1sIpa6KtNU6+XhvEqQ3/hoQ+eGt+HF38hQQ6UT8f6HGp7VfKk1JtnRkoAmbBYWxixVhzyamNXA8xgaIi56Tt/hjw2Ds/fv7gM0UHEwzg/WTeLju8xTBNmAY1
X-OriginatorOrg: freescale.com
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id t6S1Oh4X013087
Content-Length: 2430
Lines: 55

From: Igor Plyatov <plyatov@gmail.com> Sent: Monday, July 27, 2015 10:51 PM
> To: linux-kernel@vger.kernel.org; netdev@vger.kernel.org
> Cc: Florian Fainelli; Joe Perches; Zhou Luwei-B45643; Duan Fugang-B38611;
> Richard Cochran; David S. Miller; Uwe Kleine-König; Estevam Fabio-R49496;
> Lothar Waßmann; Li Frank-B20596
> Subject: Buggy cable detection on i.MX51, fec driver and LAN8700 PHY
> 
> Dear all,
> 
> very often we observe issue with Ethernet cable detection during cable
> unplugging and plugging.
> 
> We use Voipac i.MX51 SOMs (System On Modules). They are based on
> Freescale i.MX51 CPU with LAN7800 PHY in MII mode. The schematic of PHY
> connection is very similar to the Freescale i.MX51 Babbage board.
> 
> The Ethernet interface eth0 is configured statically for simplicity, but
> same issue exists with DHCP configuration.
> 
> I did a lot of tests to determine stability of Ethernet cable detection
> by the "fec" Ethernet driver.
> 
> In normal operation, if I unplug the Ethernet cable, then "fec" driver
> prints "fec 83fec000.ethernet eth0: Link is Down" and green LED (Ethernet
> medium detected) is OFF.
> If I plug cable back, then "fec" driver print "fec 83fec000.ethernet
> eth0: Link is Up - 100Mbps/Full - flow control off" and green LED is ON.
> 
> But sometimes, after cable plugging, "fec" driver does not print anything
> on the console and green LED does not show detection of Ethernet cable.
> Frequency of issue appearing is a random value.
> Sometimes issue appears after second cable unplugging/plugging, but
> sometimes - after 10-20 unplugging/plugging.
> 
> The issue was tested and exists on kernels from linux-3.8.5 till current
> linux-4.2-rc4-cbfe8fa6cd672011c755c3cd85c9ffd4e2d10a6f.
> 
> Same tests was made with different versions of the Barebox bootloader and
> cable detection works flawless.
> 
> Please, help to resolve issue with Linux drivers.
> 
> Best wishes.
> --
> Igor Plyatov

For phy cable detection issue, mostly it is phy device issue like:
-	Phy is not stable, maybe the phy initial setting is not right.
-	MDIO bus read is not right, maybe MDIO/MDC pin drive strength (timing) doesn't match spec requirement.

You can measure the MDIO timing firstly, and then check the phy setting.

Regards,
Andy
????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m????????????I?