From: Andrew Lunn <andrew@lunn.ch>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH net] net: phy: qcom: at803x: Use the correct bit to disable extended next page
Date: Sat, 11 Apr 2026 16:10:23 +0200 [thread overview]
Message-ID: <4b386a4a-9743-4e79-8d3d-3576bb9de492@lunn.ch> (raw)
In-Reply-To: <20260410171021.1277138-1-maxime.chevallier@bootlin.com>
On Fri, Apr 10, 2026 at 07:10:20PM +0200, Maxime Chevallier wrote:
> As noted in the blamed commit, the AR8035 and other PHYs from this
> family advertise the Extended Next Page support by default, which may be
> understood by some partners as this PHY being multi-gig capable.
>
> The fix is to disable XNP advertising, which is done by setting bit 12
> of the Auto-Negotiation Advertisement Register (MII_ADVERTISE).
>
> The blamed commit incorrectly uses MDIO_AN_CTRL1_XNP, which is bit 13 as per
> 802.3 : 45.2.7.1 AN control register (Register 7.0)
>
> BIT 12 in MII_ADVERTISE is wrapped by ADVERTISE_RESV, used by some
> drivers such as the aquantia one. 802.3 Clause 28 defines bit 12 as
> Extended Next Page ability, at least in recent versions of the standard.
> Let's add a define for it and use it in the at803x driver.
I agree with this, it defines the C22 4.12 bit. And this is what the
at803x driver is using it for.
> static void at803x_link_change_notify(struct phy_device *phydev)
> diff --git a/include/uapi/linux/mii.h b/include/uapi/linux/mii.h
> index 39f7c44baf53..61d6edad4b94 100644
> --- a/include/uapi/linux/mii.h
> +++ b/include/uapi/linux/mii.h
> @@ -82,7 +82,8 @@
> #define ADVERTISE_100BASE4 0x0200 /* Try for 100mbps 4k packets */
> #define ADVERTISE_PAUSE_CAP 0x0400 /* Try for pause */
> #define ADVERTISE_PAUSE_ASYM 0x0800 /* Try for asymetric pause */
> -#define ADVERTISE_RESV 0x1000 /* Unused... */
> +#define ADVERTISE_XNP 0x1000 /* Extended Next Page */
> +#define ADVERTISE_RESV ADVERTISE_XNP /* Used to be reserved */
Should we keep ADVERTISE_RESV?
45.2.7.6 AN advertisement register
If the Auto-Negotiation advertisement register (register 4) is
present, (see 28.2.4.1.3), then this register is a copy of the
Auto-Negotiation advertisement register (register 4). In this case,
reads to the AN advertisement register (7.16) report the value of
the Auto-Negotiation advertisement register (register 4); writes to
the AN advertisement register (7.16) cause a write to occur to the
Auto-Negotiation advertisement register.
So MDIO_MMD_AN:MDIO_AN_ADVERTISE is a straight copy of MII_ADVERTISE.
ef4_mdio_write(efx, MDIO_MMD_AN, MDIO_AN_ADVERTISE, reg);
ret = phy_write_mmd(phydev, MDIO_MMD_AN, MDIO_AN_ADVERTISE, adv);
So ADVERTISE_XNP is just as valid in the other two drivers using
ADVERTISE_RESV. I think we should change those as well to
ADVERTISE_XNP and remove ADVERTISE_RESV?
Andrew
next prev parent reply other threads:[~2026-04-11 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 17:10 [PATCH net] net: phy: qcom: at803x: Use the correct bit to disable extended next page Maxime Chevallier
2026-04-11 14:10 ` Andrew Lunn [this message]
2026-04-11 16:54 ` Maxime Chevallier
2026-04-11 20:49 ` Andrew Lunn
2026-04-13 22:00 ` 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=4b386a4a-9743-4e79-8d3d-3576bb9de492@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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