* [PATCH net-next] net: dsa: motorcomm: Resync SMI slave after interrupted MDIO access
@ 2026-11-11 16:39 David Yang
0 siblings, 0 replies; only message in thread
From: David Yang @ 2026-11-11 16:39 UTC (permalink / raw)
To: netdev
Cc: David Yang, Andrew Lunn, Vladimir Oltean, David S. Miller,
Eric Dumazet, Jakub Kicinski, Paolo Abeni, linux-kernel
A register access over MDIO is 4 frames: 2 address writes followed by
2 data reads or writes. The SMI slave tracks the phase in a state
machine, so an access interrupted between frames, e.g. on an MDIO bus
error, leaves the machine in an unknown state, and every following
access fails or acts on a stale address until the machine is realigned.
The driver so far assumed every access succeeds, and relied on manual
resetting when the state machine wedged. However, without a dedicated
reset line, the reset itself goes through the same SMI interface,
causing the chicken-and-egg problem.
Realign the machine before the next access does its own work. Also, the
initial value is unsynced, so any stale state is not inherited.
Signed-off-by: David Yang <mmyangfl@gmail.com>
---
drivers/net/dsa/motorcomm/chip.c | 106 +++++++++++++++++++++++++++++++
1 file changed, 106 insertions(+)
diff --git a/drivers/net/dsa/motorcomm/chip.c b/drivers/net/dsa/motorcomm/chip.c
index 33e5fc127244..8b6c9739b684 100644
--- a/drivers/net/dsa/motorcomm/chip.c
+++ b/drivers/net/dsa/motorcomm/chip.c
@@ -94,10 +94,98 @@ struct yt921x_reg_mdio {
* Keep this because we need switchid to form MII regaddrs anyway.
*/
unsigned char switchid;
+
+ bool synced;
};
/* TODO: SPI/I2C */
+/* An SMI register access is 4 MDIO frames. An interrupted access leaves the
+ * machine in an unknown state, and every following access fails or acts on a
+ * stale address.
+ *
+ * The driver used to assume every access succeeds, and relied on manual
+ * resetting when the state machine wedged. However, without a dedicated reset
+ * line, the reset itself goes through the same SMI interface, causing the
+ * chicken-and-egg problem. Furthermore, our driver verifies chip id before
+ * firing the reset, so that can never be triggered reliably.
+ *
+ * (A/D: address/data, H/L: hi/lo byte, r/w: read/write)
+ *
+ * State Input Next Comment
+ * ----- ----- ---- -------
+ * AH aw AL
+ * AH dr AH `0xdead` sentinel
+ * AL aw DH
+ * AL dr AL `0xdead` sentinel
+ * DHr aw AH abort, frame discarded
+ * DHr dr DLr
+ * DLr aw AH abort, frame discarded
+ * DLr dr AH the access is done
+ * DHw aw AH abort, frame discarded
+ * DHw dw DLw
+ * DLw aw AL abort, frame consumed as next access's addr-hi
+ * DLw dr ? `0xdead` sentinel; stay or advance undetermined
+ * DLw dw AH the access commits
+ *
+ * The table lists the whitelisted frames only; any other REGAD/op combination
+ * is not characterized and is never emitted here.
+ *
+ * The resync sequence is dr, dr, aw, aw, dr, dr, plus one more dr as a sanity
+ * check: the machine must be back at AH, which reads the `0xdead` sentinel.
+ */
+static int yt921x_reg_mdio_resync(struct yt921x_reg_mdio *mdio)
+{
+ struct mii_bus *bus = mdio->bus;
+ int addr = mdio->addr;
+ u32 reg_addr;
+ u32 reg_data;
+ int res;
+
+ mutex_lock_nested(&bus->mdio_lock, MDIO_MUTEX_NESTED);
+
+ reg_addr = YT921X_SMI_SWITCHID(mdio->switchid) | YT921X_SMI_ADDR |
+ YT921X_SMI_READ;
+ reg_data = YT921X_SMI_SWITCHID(mdio->switchid) | YT921X_SMI_DATA |
+ YT921X_SMI_READ;
+
+ /* dr */
+ res = __mdiobus_read(bus, addr, reg_data);
+ if (res < 0)
+ goto end;
+ /* dr */
+ res = __mdiobus_read(bus, addr, reg_data);
+ if (res < 0)
+ goto end;
+ /* aw */
+ res = __mdiobus_write(bus, addr, reg_addr, 0);
+ if (res)
+ goto end;
+ /* aw */
+ res = __mdiobus_write(bus, addr, reg_addr, 0);
+ if (res)
+ goto end;
+ /* dr */
+ res = __mdiobus_read(bus, addr, reg_data);
+ if (res < 0)
+ goto end;
+ /* dr */
+ res = __mdiobus_read(bus, addr, reg_data);
+ if (res < 0)
+ goto end;
+ /* AH --dr--> AH */
+ res = __mdiobus_read(bus, addr, reg_data);
+ if (res < 0)
+ goto end;
+ res = res != 0xdead ? -EIO : 0;
+
+end:
+ mutex_unlock(&bus->mdio_lock);
+
+ mdio->synced = !res;
+ return res;
+}
+
static int yt921x_reg_mdio_read(void *context, u32 reg, u32 *valp)
{
struct yt921x_reg_mdio *mdio = context;
@@ -108,6 +196,12 @@ static int yt921x_reg_mdio_read(void *context, u32 reg, u32 *valp)
u32 val;
int res;
+ if (!mdio->synced) {
+ res = yt921x_reg_mdio_resync(mdio);
+ if (res)
+ return res;
+ }
+
/* Hold the mdio bus lock to avoid (un)locking for 4 times */
mutex_lock_nested(&bus->mdio_lock, MDIO_MUTEX_NESTED);
@@ -136,6 +230,9 @@ static int yt921x_reg_mdio_read(void *context, u32 reg, u32 *valp)
end:
mutex_unlock(&bus->mdio_lock);
+
+ if (res)
+ mdio->synced = false;
return res;
}
@@ -148,6 +245,12 @@ static int yt921x_reg_mdio_write(void *context, u32 reg, u32 val)
u32 reg_data;
int res;
+ if (!mdio->synced) {
+ res = yt921x_reg_mdio_resync(mdio);
+ if (res)
+ return res;
+ }
+
mutex_lock_nested(&bus->mdio_lock, MDIO_MUTEX_NESTED);
reg_addr = YT921X_SMI_SWITCHID(mdio->switchid) | YT921X_SMI_ADDR |
@@ -172,6 +275,9 @@ static int yt921x_reg_mdio_write(void *context, u32 reg, u32 val)
end:
mutex_unlock(&bus->mdio_lock);
+
+ if (res)
+ mdio->synced = false;
return res;
}
--
2.53.0
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-11-11 16:40 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-11-11 16:39 [PATCH net-next] net: dsa: motorcomm: Resync SMI slave after interrupted MDIO access David Yang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®