On Mon, Oct 14, 2019 at 10:20:15PM +0200, Heiner Kallweit wrote: > On 14.10.2019 21:51, Stefan Wahren wrote: > > [add more recipients] > > > > Am 14.10.19 um 21:25 schrieb Daniel Wagner: > >> Moving the phy_prepare_link() up in phy_connect_direct() ensures that > >> phydev->adjust_link is set when the phy_check_link_status() is called. > >> > >> diff --git a/drivers/net/phy/phy_device.c > >> b/drivers/net/phy/phy_device.c index 9d2bbb13293e..2a61812bcb0d 100644 > >> --- a/drivers/net/phy/phy_device.c +++ b/drivers/net/phy/phy_device.c > >> @@ -951,11 +951,12 @@ int phy_connect_direct(struct net_device *dev, > >> struct phy_device *phydev, if (!dev) return -EINVAL; > >> > >> + phy_prepare_link(phydev, handler); > >> + > >> rc = phy_attach_direct(dev, phydev, phydev->dev_flags, interface); > >> if (rc) > > If phy_attach_direct() fails we may have to reset phydev->adjust_link to NULL, > as we do in phy_disconnect(). Apart from that change looks good to me.
Sorry, but it doesn't look good to me. I think there's a deeper question here - why is the phy state machine trying to call the link change function during attach? At this point, the PHY hasn't been "started" so it shouldn't be doing that. Note the documentation, specifically phy.rst's "Keeping Close Tabs on the PAL" section. Drivers are at liberty to use phy_prepare_link() _after_ phy_attach(), which means there is a window for phydev->adjust_link to be NULL. It should _not_ be called at this point. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up According to speedtest.net: 11.9Mbps down 500kbps up
