From: Andrew Lunn <andrew@lunn.ch>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: javen <javen_xu@realsil.com.cn>,
hkallweit1@gmail.com, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
daniel@makrotopia.org, linux@armlinux.org.uk,
enelsonmoore@gmail.com, daniel@thingy.jp
Subject: Re: [PATCH net-next v6 2/7] net: phy: phylink: add helper to modify pause
Date: Fri, 10 Jul 2026 19:02:17 +0200 [thread overview]
Message-ID: <18a5cd81-49ab-4b97-ba68-121e22cba874@lunn.ch> (raw)
In-Reply-To: <0c188a7d-3637-4e08-9ac8-c1d824b461ed@bootlin.com>
On Fri, Jul 10, 2026 at 12:05:06PM +0200, Maxime Chevallier wrote:
> Hi,
>
> On 7/9/26 12:02, javen wrote:
> > From: Javen Xu <javen_xu@realsil.com.cn>
> >
> > For Realtek nics, when we enable jumbo, pause are not supported. So we
> > must check the pause capabilities from ourself and lp.
> >
> > Signed-off-by: Javen Xu <javen_xu@realsil.com.cn>
> > ---
> > Changes in v5:
> > - no changes, new file
> >
> > Changes in v6:
> > - rename phylink_update_mac_pause_capabilities(), this function only
> > changes mac pause capability
> > - set asym pause and pause according to config->pause tx and rx
> > - add phydev->lock when change pl->phydev->advertising
> > ---
> > drivers/net/phy/phylink.c | 87 +++++++++++++++++++++++++++++++++++++++
> > include/linux/phylink.h | 2 +
> > 2 files changed, 89 insertions(+)
> >
> > diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
> > index 59dfe35afa54..9e9cd79301d6 100644
> > --- a/drivers/net/phy/phylink.c
> > +++ b/drivers/net/phy/phylink.c
> > @@ -1828,6 +1828,93 @@ int phylink_set_fixed_link(struct phylink *pl,
> > }
> > EXPORT_SYMBOL_GPL(phylink_set_fixed_link);
> >
> > +/**
> > + * phylink_update_mac_pause_capabilities() - Dynamically update MAC pause
> > + * @pl: a pointer to a &struct phylink returned from phylink_create()
> > + * @mac_pause: the new MAC pause capabilities mask
> > + *
> > + * This function allows a MAC driver to dynamically change its pause state,
> > + * such as losing/gaining Pause frame support based on MTU size.
> > + * It recalculates supported link modes and triggers renegotiation if needed.
> > + */
> > +void phylink_update_mac_pause_capabilities(struct phylink *pl, unsigned long mac_pause)
> > +{
> > + struct phylink_link_state *config = &pl->link_config;
> > + unsigned long old_pause, caps_added, caps_removed;
> > + bool pause_adv, asym_adv;
> > +
> > + ASSERT_RTNL();
> > +
> > + if (mac_pause & ~(MAC_SYM_PAUSE | MAC_ASYM_PAUSE)) {
> > + phylink_err(pl, "Attempted to dynamically change non-pause MAC capabilities\n");
> > + return;
> > + }
> > +
> > + old_pause = pl->config->mac_capabilities & (MAC_SYM_PAUSE | MAC_ASYM_PAUSE);
> > + caps_added = mac_pause & ~old_pause;
> > + caps_removed = old_pause & ~mac_pause;
> > +
> > + if (!caps_added && !caps_removed)
> > + return;
> > +
> > + mutex_lock(&pl->state_mutex);
> > +
> > + pl->config->mac_capabilities &= ~(MAC_SYM_PAUSE | MAC_ASYM_PAUSE);
> > + pl->config->mac_capabilities |= mac_pause;
> > +
> > + if (caps_removed & MAC_SYM_PAUSE)
> > + linkmode_clear_bit(ETHTOOL_LINK_MODE_Pause_BIT, pl->supported);
> > + if (caps_removed & MAC_ASYM_PAUSE)
> > + linkmode_clear_bit(ETHTOOL_LINK_MODE_Asym_Pause_BIT, pl->supported);
> > +
> > + linkmode_and(config->advertising, config->advertising, pl->supported);
> > +
> > + if (caps_added & MAC_SYM_PAUSE) {
> > + linkmode_set_bit(ETHTOOL_LINK_MODE_Pause_BIT, pl->supported);
> > + if (pl->phydev && !phylink_test(pl->phydev->supported, Pause))
> > + linkmode_clear_bit(ETHTOOL_LINK_MODE_Pause_BIT, pl->supported);
>
> Why look at what the PHY can do here ? You shouldn't need to.
I question the whole idea here. Why is this so complex? phylink should
already have all the needed code, once you change
pl->config->mac_capabilities you just need to call that code. Yes, it
might need refactoring into a helper, but that would be a preparatory
patch.
Once you start reusing existing code, i then wounder if it is just as
simple to allow any of the mac_capabilities to be changed, not just
pause?
Andrew
next prev parent reply other threads:[~2026-07-10 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 10:02 [PATCH net-next v6 0/7] r8169: add support for phylink javen
2026-07-09 10:02 ` [PATCH net-next v6 1/7] r8169: add speed in private struct javen
2026-07-09 10:02 ` [PATCH net-next v6 2/7] net: phy: phylink: add helper to modify pause javen
2026-07-10 10:05 ` Maxime Chevallier
2026-07-10 17:02 ` Andrew Lunn [this message]
2026-07-11 19:33 ` Maxime Chevallier
2026-07-09 10:02 ` [PATCH net-next v6 3/7] r8169: add support for phylink javen
2026-07-09 10:02 ` [PATCH net-next v6 4/7] r8169: add support for RTL8116af javen
2026-07-09 10:02 ` [PATCH net-next v6 5/7] r8169: add support for RTL8127atf javen
2026-07-09 10:02 ` [PATCH net-next v6 6/7] r8169: add ltr support for RTL8117 series javen
2026-07-09 10:02 ` [PATCH net-next v6 7/7] r8169: fix RTL8116af can not enter s0idle and c10 javen
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=18a5cd81-49ab-4b97-ba68-121e22cba874@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=daniel@thingy.jp \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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