From: Andrew Lunn <andrew@lunn.ch>
To: Dennis Ostermann <dennis.ostermann@renesas.com>
Cc: Russell King <linux@armlinux.org.uk>,
"nikita.yoush" <nikita.yoush@cogentembedded.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michael Dege <michael.dege@renesas.com>,
Christian Mardmoeller <christian.mardmoeller@renesas.com>
Subject: Re: [PATCH] net: phy: phy_ethtool_ksettings_set: Allow any supported speed
Date: Tue, 3 Dec 2024 15:45:09 +0100 [thread overview]
Message-ID: <1ff52755-ef24-4e4b-a671-803db37b58fc@lunn.ch> (raw)
In-Reply-To: <TYCPR01MB1047854DA050E52CADB04393A8E362@TYCPR01MB10478.jpnprd01.prod.outlook.com>
On Tue, Dec 03, 2024 at 02:05:07PM +0000, Dennis Ostermann wrote:
> Hi,
>
> according to IEE 802.3-2022, ch. 125.2.4.3, Auto-Negotiation is optional for 2.5GBASE-T1
>
> > 125.2.4.3 Auto-Negotiation, type single differential-pair media
> > Auto-Negotiation (Clause 98) may be used by 2.5GBASE-T1 and 5GBASE-T1 devices to detect the
> > abilities (modes of operation) supported by the device at the other end of a link segment, determine common
> > abilities, and configure for joint operation. Auto-Negotiation is performed upon link startup through the use
> > of half-duplex differential Manchester encoding.
> > The use of Clause 98 Auto-Negotiation is optional for 2.5GBASE-T1 and 5GBASE-T1 PHYs
>
> So, purposed change could make sense for T1 PHYs.
The proposed change it too liberal. We need the PHY to say it supports
2.5GBASE-T1, not 2.5GBASE-T. We can then allow 2.5GBASE-T1 to not use
autoneg, but 2.5GBASE-T has to use autoneg.
Andrew
next prev parent reply other threads:[~2024-12-03 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 8:33 Nikita Yushchenko
2024-12-02 9:03 ` Maxime Chevallier
2024-12-02 9:20 ` Nikita Yushchenko
2024-12-02 9:59 ` Maxime Chevallier
2024-12-02 10:10 ` Russell King (Oracle)
2024-12-02 10:17 ` Nikita Yushchenko
2024-12-02 10:23 ` Russell King (Oracle)
2024-12-02 11:09 ` Nikita Yushchenko
2024-12-02 12:30 ` Russell King (Oracle)
2024-12-02 15:51 ` Nikita Yushchenko
2024-12-02 16:03 ` Russell King (Oracle)
2024-12-03 11:01 ` Nikita Yushchenko
2024-12-03 15:15 ` Russell King (Oracle)
2024-12-03 14:05 ` Dennis Ostermann
2024-12-03 14:45 ` Andrew Lunn [this message]
2024-12-03 15:21 ` Russell King (Oracle)
2024-12-03 15:51 ` Maxime Chevallier
2024-12-03 16:37 ` Russell King (Oracle)
2024-12-02 14:32 ` Andrew Lunn
2024-12-02 10:03 ` Russell King (Oracle)
2024-12-03 14:02 ` Nikita Yushchenko
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=1ff52755-ef24-4e4b-a671-803db37b58fc@lunn.ch \
--to=andrew@lunn.ch \
--cc=christian.mardmoeller@renesas.com \
--cc=davem@davemloft.net \
--cc=dennis.ostermann@renesas.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=michael.dege@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=nikita.yoush@cogentembedded.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
all inboxes | Powered by JetHome®