From: Vladimir Oltean <olteanv@gmail.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Antoine Tenart <atenart@kernel.org>,
Quentin Schulz <quentin.schulz@bootlin.com>,
Michael Walle <michael@walle.cc>,
netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Maxim Kochetkov <fido_max@inbox.ru>,
Bjarni Jonasson <bjarni.jonasson@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
UNGLinuxDriver@microchip.com
Subject: [PATCH net-next 1/2] net: phylink: explicitly configure in-band autoneg for PHYs that support it
Date: Fri, 12 Feb 2021 19:23:40 +0200 [thread overview]
Message-ID: <20210212172341.3489046-2-olteanv@gmail.com> (raw)
In-Reply-To: <20210212172341.3489046-1-olteanv@gmail.com>
From: Vladimir Oltean <vladimir.oltean@nxp.com>
Currently Linux has no control over whether a MAC-to-PHY interface uses
in-band signaling or not, even though phylink has the
managed = "in-band-status";
property which denotes that the MAC expects in-band signaling to be used.
The problem is really that if the in-band signaling is configurable in
both the PHY and the MAC, there is a risk that they are out of sync
unless phylink manages them both. Most if not all in-band autoneg state
machines follow IEEE 802.3 clause 37, which means that they will not
change the operating mode of the SERDES lane from control to data mode
unless in-band AN completed successfully. Therefore traffic will not
work.
It is particularly unpleasant that currently, we assume that PHYs which
have configurable in-band AN come pre-configured from a prior boot stage
such as U-Boot, because once the bootloader changes, all bets are off.
Let's introduce a new PHY driver method for configuring in-band autoneg,
and make phylink be its first user. The main PHY library does not call
phy_config_inband_autoneg, because it does not know what to configure it
to. Presumably, non-phylink drivers can also call phy_config_inband_autoneg
individually.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
---
drivers/net/phy/phy.c | 12 ++++++++++++
drivers/net/phy/phylink.c | 8 ++++++++
include/linux/phy.h | 8 ++++++++
3 files changed, 28 insertions(+)
diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
index fdb914b5b857..d6c63c54943e 100644
--- a/drivers/net/phy/phy.c
+++ b/drivers/net/phy/phy.c
@@ -748,6 +748,18 @@ static int phy_check_link_status(struct phy_device *phydev)
return 0;
}
+int phy_config_inband_aneg(struct phy_device *phydev, bool enabled)
+{
+ if (!phydev->drv)
+ return -EIO;
+
+ if (!phydev->drv->config_inband_aneg)
+ return -EOPNOTSUPP;
+
+ return phydev->drv->config_inband_aneg(phydev, enabled);
+}
+EXPORT_SYMBOL(phy_config_inband_aneg);
+
/**
* phy_start_aneg - start auto-negotiation for this PHY device
* @phydev: the phy_device struct
diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
index 84f6e197f965..ef3e947d5019 100644
--- a/drivers/net/phy/phylink.c
+++ b/drivers/net/phy/phylink.c
@@ -978,6 +978,14 @@ static int phylink_bringup_phy(struct phylink *pl, struct phy_device *phy,
return ret;
}
+ ret = phy_config_inband_aneg(phy,
+ (pl->cur_link_an_mode == MLO_AN_INBAND));
+ if (ret && ret != -EOPNOTSUPP) {
+ phylink_warn(pl, "failed to configure PHY in-band autoneg: %d\n",
+ ret);
+ return ret;
+ }
+
phy->phylink = pl;
phy->phy_link_change = phylink_phy_change;
diff --git a/include/linux/phy.h b/include/linux/phy.h
index c130788306c8..2260b512ffbf 100644
--- a/include/linux/phy.h
+++ b/include/linux/phy.h
@@ -746,6 +746,13 @@ struct phy_driver {
*/
int (*config_aneg)(struct phy_device *phydev);
+ /**
+ * @config_inband_aneg: Enable or disable in-band auto-negotiation for
+ * the system-side interface if the PHY operates in a mode that
+ * requires it: (Q)SGMII, USXGMII, 1000Base-X, etc.
+ */
+ int (*config_inband_aneg)(struct phy_device *phydev, bool enabled);
+
/** @aneg_done: Determines the auto negotiation result */
int (*aneg_done)(struct phy_device *phydev);
@@ -1394,6 +1401,7 @@ void phy_detach(struct phy_device *phydev);
void phy_start(struct phy_device *phydev);
void phy_stop(struct phy_device *phydev);
int phy_start_aneg(struct phy_device *phydev);
+int phy_config_inband_aneg(struct phy_device *phydev, bool enabled);
int phy_aneg_done(struct phy_device *phydev);
int phy_speed_down(struct phy_device *phydev, bool sync);
int phy_speed_up(struct phy_device *phydev);
--
2.25.1
next prev parent reply other threads:[~2021-02-12 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 17:23 [PATCH net-next 0/2] Let phylink manage in-band AN for the PHY Vladimir Oltean
2021-02-12 17:23 ` Vladimir Oltean [this message]
2021-02-12 22:40 ` [PATCH net-next 1/2] net: phylink: explicitly configure in-band autoneg for PHYs that support it Michael Walle
2021-02-13 0:18 ` Russell King - ARM Linux admin
2021-02-13 16:41 ` Michael Walle
2021-02-13 16:59 ` Andrew Lunn
2021-02-13 17:06 ` Russell King - ARM Linux admin
2021-02-13 0:36 ` Vladimir Oltean
2021-02-13 16:53 ` Michael Walle
2021-02-13 17:09 ` Michael Walle
2021-02-13 18:56 ` Vladimir Oltean
2021-02-13 19:57 ` Michael Walle
2021-02-13 20:12 ` Vladimir Oltean
2021-02-13 20:16 ` Russell King - ARM Linux admin
2021-02-14 10:35 ` Russell King - ARM Linux admin
2021-02-14 11:10 ` Vladimir Oltean
2021-02-14 13:18 ` Russell King - ARM Linux admin
2021-02-12 17:23 ` [PATCH net-next 2/2] net: phy: mscc: configure in-band auto-negotiation for VSC8514 Vladimir Oltean
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=20210212172341.3489046-2-olteanv@gmail.com \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=bjarni.jonasson@microchip.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=fido_max@inbox.ru \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=quentin.schulz@bootlin.com \
--cc=steen.hegelund@microchip.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).