From: Andrew Lunn <andrew@lunn.ch>
To: Andre.Edich@microchip.com
Cc: netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
steve.glendinning@shawell.net,
Parthiban.Veerasooran@microchip.com
Subject: Re: [PATCH net-next 3/8] smsc95xx: add PAL support to use external PHY drivers
Date: Tue, 30 Jun 2020 03:19:14 +0200 [thread overview]
Message-ID: <20200630011914.GE597495@lunn.ch> (raw)
In-Reply-To: <26c4eee749db5a5430fa9df9c12651dd34bdbaa6.camel@microchip.com>
> +static int smsc95xx_start_phy(struct usbnet *dev)
> +{
> + struct smsc95xx_priv *pdata = (struct smsc95xx_priv *)(dev-
> >data[0]);
> + struct net_device *net = dev->net;
> + int ret;
> +
> + ret = smsc95xx_reset(dev);
> + if (ret < 0)
> + return ret;
> +
> + /* attach the mac to the phy */
> + ret = phy_connect_direct(net, pdata->phydev,
> + &smsc95xx_handle_link_change,
> + PHY_INTERFACE_MODE_MII);
> + if (ret) {
> + netdev_err(net, "can't attach PHY to %s\n", pdata-
> >mdiobus->id);
> + return ret;
> + }
> +
> + phy_attached_info(net->phydev);
> + phy_start(net->phydev);
> + mii_nway_restart(&dev->mii);
Is mii_nway_restart() needed? phy_start will start auto-neg if needed.
It looks like after this patch you have a mixture of old MII and new
phylib. Does that work? If somebody doing a git bisect was to land on
one of these intermediary patches, so they have working Ethernet?
Andrew
next prev parent reply other threads:[~2020-06-30 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 13:11 [PATCH net-next 3/8] smsc95xx: add PAL support to use external PHY drivers Andre.Edich
2020-06-30 1:19 ` Andrew Lunn [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-29 20:01 Andre.Edich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200630011914.GE597495@lunn.ch \
--to=andrew@lunn.ch \
--cc=Andre.Edich@microchip.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).