From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH net-next 1/2] net: phy: don't stop state machine in case of MDIO error Date: Sun, 16 Dec 2018 09:42:51 +0100 Message-ID: <20181216084251.GD18287@lunn.ch> References: <6e57b405-e39e-91a1-c843-f461db9bc286@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Fainelli , David Miller , Fugang Duan , "netdev@vger.kernel.org" To: Heiner Kallweit Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:49234 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729758AbeLPIm4 (ORCPT ); Sun, 16 Dec 2018 03:42:56 -0500 Content-Disposition: inline In-Reply-To: <6e57b405-e39e-91a1-c843-f461db9bc286@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On Sat, Dec 15, 2018 at 05:18:33PM +0100, Heiner Kallweit wrote: > If we detect a MDIO error, it seems to be a little bit too aggressive > to stop the state machine and bring down the PHY completely. Hi Heiner My assumption is, if we get one MDIO error, we will gets lots more MDIO errors. This should be the sort of bus which either works, or it does not. In that situation, i think it does make sense to stop everything. I would like to know more about the FEC. Unfortunately, the commit adding the timeout handling code does not explain why it is needed. We might need to dig further backwards in time to figure it out. Andrew