From: Paolo Abeni <pabeni@redhat.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net 3/3] net: phy: as21xxx: force C45 OPs for AUTONEG
Date: Thu, 4 Jun 2026 13:07:16 +0200 [thread overview]
Message-ID: <16b81f1a-ae24-4a05-a348-0259f8935378@redhat.com> (raw)
In-Reply-To: <20260601105342.28865-3-ansuelsmth@gmail.com>
On 6/1/26 12:53 PM, Christian Marangi wrote:
> With further testing with 2.5G NIC, it was discovered that the PHY
> require the C45 OPs to configure and restart ANEG or speed higher than
> 1G doesn't function correctly.
>
> To force C45 OPs with generic PHY function, clear the C22 bit from
> devices_in_package bitmask.
>
> Fixes: 830877d89edc ("net: phy: Add support for Aeonsemi AS21xxx PHYs")
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Sashiko has a few comments here and on the previous patch:
https://sashiko.dev/#/patchset/20260601105342.28865-1-ansuelsmth%40gmail.com
could you please double check them?
next prev parent reply other threads:[~2026-06-04 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 10:53 [PATCH net 1/3] net: phy: as21xxx: handle corner case with link and autoneg complete Christian Marangi
2026-06-01 10:53 ` [PATCH net 2/3] net: phy: as21xxx: fix read_status speed handling Christian Marangi
2026-06-04 10:18 ` Maxime Chevallier
2026-06-01 10:53 ` [PATCH net 3/3] net: phy: as21xxx: force C45 OPs for AUTONEG Christian Marangi
2026-06-04 10:22 ` Maxime Chevallier
2026-06-04 11:07 ` Paolo Abeni [this message]
2026-06-04 10:14 ` [PATCH net 1/3] net: phy: as21xxx: handle corner case with link and autoneg complete Maxime Chevallier
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=16b81f1a-ae24-4a05-a348-0259f8935378@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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®