From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH] net: phy: micrel: ksz9031: reconfigure autoneg after phy autoneg workaround Date: Thu, 21 Dec 2017 10:21:12 +0100 Message-ID: <20171221092112.GD6683@lunn.ch> References: <20171221004510.29715-1-grygorii.strashko@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Fainelli , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Sekhar Nori To: Grygorii Strashko Return-path: Content-Disposition: inline In-Reply-To: <20171221004510.29715-1-grygorii.strashko@ti.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, Dec 20, 2017 at 06:45:10PM -0600, Grygorii Strashko wrote: > Under some circumstances driver will perform PHY reset in > ksz9031_read_status() to fix autoneg failure case (idle error count = > 0xFF). When this happens ksz9031 will not detect link status change any > more when connecting to Netgear 1G switch (link can be recovered sometimes by > restarting netdevice "ifconfig down up"). Reproduced with TI am572x board > equipped with ksz9031 PHY while connecting to Netgear 1G switch. > > Fix the issue by reconfiguring autonegotiation after PHY reset in > ksz9031_read_status(). Hi Grygorii I can understand the fix. But i'm wondering if there is a better way to do this. Can you call phy_stop() and phy_start(). You then get the core phy code doing the same initialisation as what happened the first time. However, i know this is not easy. _read_status() is being called from the middle of the state machine, and trying to change the state of the state machine at this point is problematic. Andrew