public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>,
	 Oliver Neukum <oneukum@suse.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	 "David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	 Paolo Abeni <pabeni@redhat.com>,
	linux-usb@vger.kernel.org,  linux-kernel@vger.kernel.org,
	 Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
	 Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH] PHY: Fix no autoneg corner case
Date: Thu, 28 Nov 2024 07:31:48 +0100	[thread overview]
Message-ID: <m3wmgnhnsb.fsf@t19.piap.pl> (raw)
In-Reply-To: <c57a8f12-744c-4855-bd18-2197a8caf2a2@lunn.ch> (Andrew Lunn's message of "Wed, 27 Nov 2024 18:37:36 +0100")

Andrew,

Andrew Lunn <andrew@lunn.ch> writes:

>> Unfortunately it's initially set based on the supported capability
>> rather than the actual hw setting.
>
> We need a clear definition of 'initially', and when does it actually
> matter.
>
> Initially, things like speed, duplex and set to UNKNOWN. They don't
> make any sense until the link is up. phydev->advertise is set to
> phydev->supported, so that we advertise all the capabilities of the
> PHY. However, at probe, this does not really matter, it is only when
> phy_start() is called is the hardware actually configured with what it
> should advertise, or even if it should do auto-neg or not.
>
> In the end, this might not matter.

Nevertheless, it seems it does matter.

>> While in most cases there is no
>> difference (i.e., autoneg is supported and on by default), certain
>> adapters (e.g. fiber optics) use fixed settings, configured in hardware.
>
> If the hardware is not capable of supporting autoneg, why is autoneg
> in phydev->supported? To me, that is the real issue here.

Well, autoneg *IS* supported by the PHY in this case.
No autoneg in phydev->supported would mean I can't enable it if needed,
wouldn't it?

It is supported but initially disabled.

With current code, PHY correctly connects to the other side, all the
registers are valid etc., the PHY indicates, for example, a valid link
with 100BASE-FX full duplex etc.

Yet the Linux netdev, ethtool etc. indicate no valid link, autoneg on,
and speed/duplex unknown. It's just completely inconsistent with the
real hardware state.

It seems the phy/phylink code assumes the PHY starts with autoneg
enabled (if supported). This is simply an incorrect assumption.

BTW if the code meant to enable autoneg, it would do exactly that -
enable it by writing to PHY command register. Then the hw and sw state
would be consistent again (though initial configuration would be
ignored, not very nice). Now the code doesn't enable autoneg, it only
*indicates* it's enabled and in reality it's not.
-- 
Krzysiek
PAMIĘTAJ: WRÓG TEŻ TO CZYTA

  reply	other threads:[~2024-11-28  6:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27  8:56 [PATCH] PHY: Fix no autoneg corner case Krzysztof Hałasa
2024-11-27 17:37 ` Andrew Lunn
2024-11-28  6:31   ` Krzysztof Hałasa [this message]
2024-11-28 14:54     ` Andrew Lunn
2024-11-28 19:35       ` Heiner Kallweit
2024-11-29  6:17       ` Krzysztof Hałasa
2024-11-29  6:49         ` Heiner Kallweit
2024-12-02  7:57           ` Krzysztof Hałasa
2025-03-19 21:00             ` Heiner Kallweit

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=m3wmgnhnsb.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jtornosm@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=pabeni@redhat.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