From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandru Marginean <alexandru.marginean@nxp.com>,
"michael@walle.cc" <michael@walle.cc>,
"olteanv@gmail.com" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH RFC net-next 11/13] net: phylink: re-implement interface configuration with PCS
Date: Mon, 20 Jul 2020 13:44:05 +0100 [thread overview]
Message-ID: <20200720124405.GT1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <VI1PR0402MB387151248ABD93EAA9C2E454E07B0@VI1PR0402MB3871.eurprd04.prod.outlook.com>
On Mon, Jul 20, 2020 at 11:40:44AM +0000, Ioana Ciornei wrote:
> On 6/30/20 5:29 PM, Russell King wrote:
> > With PCS support, how we implement interface reconfiguration is not up
> > to the job; we end up reconfiguring the PCS for an interface change
> > while the link could potentially be up. In order to solve this, add
> > two additional MAC methods for interface configuration, one to prepare
> > for the change, and one to finish the change.
> >
> > This allows mvneta and mvpp2 to shutdown what they require prior to the
> > MAC and PCS configuration calls, and then restart as appropriate.
> >
> > This impacts ksettings_set(), which now needs to identify whether the
> > change is a minor tweak to the advertisement masks or whether the
> > interface mode has changed, and call the appropriate function for that
> > update.
> >
> > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> > ---
> > drivers/net/phy/phylink.c | 80 ++++++++++++++++++++++++++-------------
> > include/linux/phylink.h | 48 +++++++++++++++++++++++
> > 2 files changed, 102 insertions(+), 26 deletions(-)
> >
> > diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
> > index 09f4aeef15c7..a31a00fb4974 100644
> > --- a/drivers/net/phy/phylink.c
> > +++ b/drivers/net/phy/phylink.c
> > @@ -433,23 +433,47 @@ static void phylink_mac_pcs_an_restart(struct phylink *pl)
> > }
> > }
> >
> > -static void phylink_pcs_config(struct phylink *pl, bool force_restart,
> > - const struct phylink_link_state *state)
> > +static void phylink_change_interface(struct phylink *pl, bool restart,
> > + const struct phylink_link_state *state)
> > {
> > - bool restart = force_restart;
> > + int err;
> > +
> > + phylink_dbg(pl, "change interface %s\n", phy_modes(state->interface));
> >
> > - if (pl->pcs_ops && pl->pcs_ops->pcs_config(pl->config,
> > - pl->cur_link_an_mode,
> > - state->interface,
> > - state->advertising,
> > - !!(pl->link_config.pause &
> > - MLO_PAUSE_AN)))
> > - restart = true;
> > + if (pl->mac_ops->mac_prepare) {
> > + err = pl->mac_ops->mac_prepare(pl->config, pl->cur_link_an_mode,
> > + state->interface);
> > + if (err < 0) {
> > + phylink_err(pl, "mac_prepare failed: %pe\n",
> > + ERR_PTR(err));
> > + return;
> > + }
> > + }
> >
> > phylink_mac_config(pl, state);
> >
> > + if (pl->pcs_ops) {
> > + err = pl->pcs_ops->pcs_config(pl->config, pl->cur_link_an_mode,
> > + state->interface,
> > + state->advertising,
> > + !!(pl->link_config.pause &
> > + MLO_PAUSE_AN));
> > + if (err < 0)
> > + phylink_err(pl, "pcs_config failed: %pe\n",
> > + ERR_PTR(err));
> > + if (err > 0)
> > + restart = true;
> > + }
> > if (restart)
> > phylink_mac_pcs_an_restart(pl);
> > +
> > + if (pl->mac_ops->mac_finish) {
> > + err = pl->mac_ops->mac_finish(pl->config, pl->cur_link_an_mode,
> > + state->interface);
> > + if (err < 0)
> > + phylink_err(pl, "mac_prepare failed: %pe\n",
> > + ERR_PTR(err));
> > + }
> > }
> >
> > /*
> > @@ -555,7 +579,7 @@ static void phylink_mac_initial_config(struct phylink *pl, bool force_restart)
> > link_state.link = false;
> >
> > phylink_apply_manual_flow(pl, &link_state);
> > - phylink_pcs_config(pl, force_restart, &link_state);
> > + phylink_change_interface(pl, force_restart, &link_state);
> > }
> >
> > static const char *phylink_pause_to_str(int pause)
> > @@ -674,7 +698,7 @@ static void phylink_resolve(struct work_struct *w)
> > phylink_link_down(pl);
> > cur_link_state = false;
> > }
> > - phylink_pcs_config(pl, false, &link_state);
> > + phylink_change_interface(pl, false, &link_state);
> > pl->link_config.interface = link_state.interface;
> > } else if (!pl->pcs_ops) {
> > /* The interface remains unchanged, only the speed,
> > @@ -1450,22 +1474,26 @@ int phylink_ethtool_ksettings_set(struct phylink *pl,
> > return -EINVAL;
> >
> > mutex_lock(&pl->state_mutex);
> > - linkmode_copy(pl->link_config.advertising, config.advertising);
> > - pl->link_config.interface = config.interface;
> > pl->link_config.speed = config.speed;
> > pl->link_config.duplex = config.duplex;
> > - pl->link_config.an_enabled = kset->base.autoneg !=
> > - AUTONEG_DISABLE;
> > -
> > - if (pl->cur_link_an_mode == MLO_AN_INBAND &&
> > - !test_bit(PHYLINK_DISABLE_STOPPED, &pl->phylink_disable_state)) {
> > - /* If in 802.3z mode, this updates the advertisement.
> > - *
> > - * If we are in SGMII mode without a PHY, there is no
> > - * advertisement; the only thing we have is the pause
> > - * modes which can only come from a PHY.
> > - */
> > - phylink_pcs_config(pl, true, &pl->link_config);
> > + pl->link_config.an_enabled = kset->base.autoneg != AUTONEG_DISABLE;
> > +
> > + if (pl->link_config.interface != config.interface) {
>
>
> I cannot seem to understand where in this function config.interface
> could become different from pl->link_config.interface.
>
> Is there something obvious that I am missing?
The validate() method is free to change the interface if required -
there's a helper that MACs can use to achieve that for switching
between 1000base-X and 2500base-X. Useful if you have a FC SFP
plugged in capable of 2500base-X, but want to communicate with a
1000base-X link partner.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-07-20 12:44 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 14:27 [PATCH RFC net-next 00/13] Phylink PCS updates Russell King - ARM Linux admin
2020-06-30 14:28 ` [PATCH RFC net-next 01/13] net: phylink: update ethtool reporting for fixed-link modes Russell King
2020-06-30 18:15 ` Florian Fainelli
2020-06-30 14:28 ` [PATCH RFC net-next 02/13] net: phylink: rejig link state tracking Russell King
2020-06-30 18:15 ` Florian Fainelli
2020-06-30 14:28 ` [PATCH RFC net-next 03/13] net: phylink: rearrange resolve mac_config() call Russell King
2020-06-30 18:32 ` Florian Fainelli
2020-06-30 14:28 ` [PATCH RFC net-next 04/13] net: phylink: ensure link is down when changing interface Russell King
2020-06-30 18:32 ` Florian Fainelli
2020-06-30 14:28 ` [PATCH RFC net-next 05/13] net: phylink: update PCS when changing interface during resolution Russell King
2020-06-30 18:33 ` Florian Fainelli
2020-06-30 14:29 ` [PATCH RFC net-next 06/13] net: phylink: avoid mac_config calls Russell King
2020-06-30 19:04 ` Florian Fainelli
2020-06-30 14:29 ` [PATCH RFC net-next 07/13] net: phylink: simplify ksettings_set() implementation Russell King
2020-07-20 10:24 ` Ioana Ciornei
2020-06-30 14:29 ` [PATCH RFC net-next 08/13] net: phylink: simplify phy case for ksettings_set method Russell King
2020-07-20 10:44 ` Ioana Ciornei
2020-07-20 12:45 ` Russell King - ARM Linux admin
2020-06-30 14:29 ` [PATCH RFC net-next 09/13] net: phylink: simplify fixed-link " Russell King
2020-07-20 10:52 ` Ioana Ciornei
2020-06-30 14:29 ` [PATCH RFC net-next 10/13] net: phylink: in-band pause mode advertisement update for PCS Russell King
2020-06-30 16:19 ` Jakub Kicinski
2020-06-30 14:29 ` [PATCH RFC net-next 11/13] net: phylink: re-implement interface configuration with PCS Russell King
2020-07-20 11:40 ` Ioana Ciornei
2020-07-20 12:44 ` Russell King - ARM Linux admin [this message]
2020-07-20 13:02 ` Ioana Ciornei
2020-07-20 14:19 ` Russell King - ARM Linux admin
2020-06-30 14:29 ` [PATCH RFC net-next 12/13] net: phylink: add struct phylink_pcs Russell King
2020-07-01 10:47 ` Vladimir Oltean
2020-07-01 11:16 ` Russell King - ARM Linux admin
2020-07-01 11:24 ` Vladimir Oltean
2020-07-20 15:50 ` Ioana Ciornei
2020-07-20 16:26 ` Russell King - ARM Linux admin
2020-07-20 16:59 ` Ioana Ciornei
2020-07-20 18:16 ` Russell King - ARM Linux admin
2020-06-30 14:29 ` [PATCH RFC net-next 13/13] net: phylink: add interface to configure clause 22 PCS PHY Russell King
2020-07-01 10:52 ` Ioana Ciornei
2020-07-14 8:49 ` [PATCH RFC net-next 00/13] Phylink PCS updates Vladimir Oltean
2020-07-14 13:18 ` Russell King - ARM Linux admin
2020-07-14 21:22 ` Florian Fainelli
2020-07-15 9:53 ` Russell King - ARM Linux admin
2020-07-14 23:46 ` Vladimir Oltean
2020-07-15 11:21 ` Russell King - ARM Linux admin
2020-07-15 11:34 ` Russell King - ARM Linux admin
2020-07-15 12:31 ` Vladimir Oltean
2020-07-15 14:20 ` Andrew Lunn
2020-07-15 17:02 ` Russell King - ARM Linux admin
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=20200720124405.GT1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandru.marginean@nxp.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).