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 22:49:21 +0200 [thread overview]
Message-ID: <dbd60257-3327-466d-865b-2ca9c6af8370@lunn.ch> (raw)
In-Reply-To: <c37f182e-cbb4-4f0b-817a-759d39940212@bootlin.com>
> > 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
>
> I agree with that yes and I've considered converting these drivers once
> we have net merged into net-next should this patch be applied :)
Ah, sorry, missed the patch was targeting net. Please do submit a
cleanup for net-next later on.
> That said, ADVERTISE_RESV is in uapi, is it even possible to remove it ?
Good point. It probably does have to stay.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2026-04-11 20:49 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
2026-04-11 16:54 ` Maxime Chevallier
2026-04-11 20:49 ` Andrew Lunn [this message]
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=dbd60257-3327-466d-865b-2ca9c6af8370@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