From: Heiner Kallweit <hkallweit1@gmail.com>
To: Michael Walle <michael@walle.cc>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Vladimir Oltean <olteanv@gmail.com>
Subject: Re: [PATCH v2 net-next] net: phy: at803x: remove at803x_aneg_done()
Date: Thu, 18 Mar 2021 21:10:50 +0100 [thread overview]
Message-ID: <d4dd656a-fd30-51d2-f9bb-55ff4b4dce9b@gmail.com> (raw)
In-Reply-To: <20210318194431.14811-1-michael@walle.cc>
On 18.03.2021 20:44, Michael Walle wrote:
> Here is what Vladimir says about it:
>
> at803x_aneg_done() keeps the aneg reporting as "not done" even when
> the copper-side link was reported as up, but the in-band autoneg has
> not finished.
>
> That was the _intended_ behavior when that code was introduced, and
> Heiner have said about it [1]:
>
> | That's not nice from the PHY:
> | It signals "link up", and if the system asks the PHY for link details,
> | then it sheepishly says "well, link is *almost* up".
>
> If the specification of phy_aneg_done behavior does not include
> in-band autoneg (and it doesn't), then this piece of code does not
> belong here.
>
> The fact that we can no longer trigger this code from phylib is yet
> another reason why it fails at its intended (and wrong) purpose and
> should be removed.
>
> Removing the SGMII link check, would just keep the call to
> genphy_aneg_done(), which is also the fallback. Thus we can just remove
> at803x_aneg_done() altogether.
>
> [1] https://lore.kernel.org/netdev/fdf0074a-2572-5914-6f3e-77202cbf96de@gmail.com/
>
> Suggested-by: Vladimir Oltean <olteanv@gmail.com>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
Reviewed-by: Heiner Kallweit <hkallweit1@gmail.com>
next prev parent reply other threads:[~2021-03-18 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 19:44 [PATCH v2 net-next] net: phy: at803x: remove at803x_aneg_done() Michael Walle
2021-03-18 19:47 ` Michael Walle
2021-03-18 20:10 ` Heiner Kallweit [this message]
2021-03-19 19:10 ` patchwork-bot+netdevbpf
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=d4dd656a-fd30-51d2-f9bb-55ff4b4dce9b@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
/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).