From: Russell King <rmk+kernel@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Vivien Didelot <vivien.didelot@gmail.com>
Subject: [PATCH net-next 8/8] net: dsa: mv88e6xxx: use PHY_DETECT in mac_link_up/mac_link_down
Date: Sat, 14 Mar 2020 10:16:03 +0000 [thread overview]
Message-ID: <E1jD3pr-0006E5-WE@rmk-PC.armlinux.org.uk> (raw)
In-Reply-To: <20200314101431.GF25745@shell.armlinux.org.uk>
Use the status of the PHY_DETECT bit to determine whether we need to
force the MAC settings in mac_link_up() and mac_link_down().
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
---
drivers/net/dsa/mv88e6xxx/chip.c | 53 +++++++++++++++++---------------
1 file changed, 29 insertions(+), 24 deletions(-)
diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c
index 03bc15a97591..221593261e8f 100644
--- a/drivers/net/dsa/mv88e6xxx/chip.c
+++ b/drivers/net/dsa/mv88e6xxx/chip.c
@@ -464,6 +464,22 @@ static int mv88e6xxx_phy_is_internal(struct dsa_switch *ds, int port)
return port < chip->info->num_internal_phys;
}
+static int mv88e6xxx_port_ppu_updates(struct mv88e6xxx_chip *chip, int port)
+{
+ u16 reg;
+ int err;
+
+ err = mv88e6xxx_port_read(chip, port, MV88E6XXX_PORT_STS, ®);
+ if (err) {
+ dev_err(chip->dev,
+ "p%d: %s: failed to read port status\n",
+ port, __func__);
+ return err;
+ }
+
+ return !!(reg & MV88E6XXX_PORT_STS_PHY_DETECT);
+}
+
static int mv88e6xxx_serdes_pcs_get_state(struct dsa_switch *ds, int port,
struct phylink_link_state *state)
{
@@ -692,20 +708,14 @@ static void mv88e6xxx_mac_link_down(struct dsa_switch *ds, int port,
ops = chip->info->ops;
- /* Internal PHYs propagate their configuration directly to the MAC.
- * External PHYs depend on whether the PPU is enabled for this port.
- * FIXME: we should be using the PPU enable state here. What about
- * an automedia port?
- */
- if (!mv88e6xxx_phy_is_internal(ds, port) && ops->port_set_link) {
- mv88e6xxx_reg_lock(chip);
+ mv88e6xxx_reg_lock(chip);
+ if (!mv88e6xxx_port_ppu_updates(chip, port) && ops->port_set_link)
err = ops->port_set_link(chip, port, LINK_FORCED_DOWN);
- mv88e6xxx_reg_unlock(chip);
+ mv88e6xxx_reg_unlock(chip);
- if (err)
- dev_err(chip->dev,
- "p%d: failed to force MAC link down\n", port);
- }
+ if (err)
+ dev_err(chip->dev,
+ "p%d: failed to force MAC link down\n", port);
}
static void mv88e6xxx_mac_link_up(struct dsa_switch *ds, int port,
@@ -720,13 +730,8 @@ static void mv88e6xxx_mac_link_up(struct dsa_switch *ds, int port,
ops = chip->info->ops;
- /* Internal PHYs propagate their configuration directly to the MAC.
- * External PHYs depend on whether the PPU is enabled for this port.
- * FIXME: we should be using the PPU enable state here. What about
- * an automedia port?
- */
- if (!mv88e6xxx_phy_is_internal(ds, port)) {
- mv88e6xxx_reg_lock(chip);
+ mv88e6xxx_reg_lock(chip);
+ if (!mv88e6xxx_port_ppu_updates(chip, port)) {
/* FIXME: for an automedia port, should we force the link
* down here - what if the link comes up due to "other" media
* while we're bringing the port up, how is the exclusivity
@@ -747,13 +752,13 @@ static void mv88e6xxx_mac_link_up(struct dsa_switch *ds, int port,
if (ops->port_set_link)
err = ops->port_set_link(chip, port, LINK_FORCED_UP);
+ }
error:
- mv88e6xxx_reg_unlock(chip);
+ mv88e6xxx_reg_unlock(chip);
- if (err && err != -EOPNOTSUPP)
- dev_err(ds->dev,
- "p%d: failed to configure MAC link up\n", port);
- }
+ if (err && err != -EOPNOTSUPP)
+ dev_err(ds->dev,
+ "p%d: failed to configure MAC link up\n", port);
}
static int mv88e6xxx_stats_snapshot(struct mv88e6xxx_chip *chip, int port)
--
2.20.1
next prev parent reply other threads:[~2020-03-15 1:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 10:14 [PATCH REPOST net-next 0/8] net: dsa: improve serdes integration Russell King - ARM Linux admin
2020-03-14 10:15 ` [PATCH net-next 1/8] net: dsa: warn if phylink_mac_link_state returns error Russell King
2020-03-14 18:34 ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 2/8] net: dsa: mv88e6xxx: use BMCR definitions for serdes control register Russell King
2020-03-14 18:35 ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 3/8] net: dsa: mv88e6xxx: configure interface settings in mac_config Russell King
2020-03-14 18:38 ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 4/8] net: dsa: mv88e6xxx: extend phylink to Serdes PHYs Russell King
2020-03-14 18:47 ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 5/8] net: dsa: mv88e6xxx: fix Serdes link changes Russell King
2020-03-14 18:48 ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 6/8] net: dsa: mv88e6xxx: combine port_set_speed and port_set_duplex Russell King
2020-03-14 18:49 ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 7/8] net: dsa: mv88e6xxx: remove port_link_state functions Russell King
2020-03-14 21:29 ` Andrew Lunn
2020-03-14 10:16 ` Russell King [this message]
2020-03-14 21:31 ` [PATCH net-next 8/8] net: dsa: mv88e6xxx: use PHY_DETECT in mac_link_up/mac_link_down Andrew Lunn
2020-03-14 18:33 ` [PATCH REPOST net-next 0/8] net: dsa: improve serdes integration Andrew Lunn
2020-03-16 0:11 ` David Miller
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=E1jD3pr-0006E5-WE@rmk-PC.armlinux.org.uk \
--to=rmk+kernel@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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).