From: Daniel Golle <daniel@makrotopia.org>
To: "Chester A. Unal" <chester.a.unal@arinc9.com>,
Daniel Golle <daniel@makrotopia.org>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Alexander Couzens <lynxis@fe80.eu>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Russell King <rmk+kernel@armlinux.org.uk>,
Sean Wang <sean.wang@mediatek.com>,
Landen Chao <Landen.Chao@mediatek.com>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH net v2 0/6] net: dsa: mt7530: fix remaining swallowed MDIO access errors
Date: Tue, 4 Aug 2026 04:10:17 +0100 [thread overview]
Message-ID: <cover.1785811140.git.daniel@makrotopia.org> (raw)
The original series, "net: dsa: mt7530: fix swallowed MDIO read
errors", landed on net as its v1 [1] just before its v2 [2] was sent.
This series started from the fixes in that original v2 which its v1
had not already carried: the two standalone patches that original v2
grew from the Sashiko AI review of its v1 (the mtk-lynxi read check
and the regmap IRQ serialization), plus, split into patches of their
own, the companion fixes original v2 had folded into the
already-applied patches -- the unchecked bus->read() in core_rmw() and
the unchecked PHY_IAC command writes in the MT7531 indirect PHY access
functions.
The Sashiko AI review of this series' own v1 [3] then flagged two more
swallowed MDIO errors of the same kind, added here as patches of their
own: the unchecked CORE_PLL_GROUP4 read-modify-write in mt7531_setup(),
and the unchecked ATC/VTCR command-register writes in mt7530_fdb_cmd()
and mt7530_vlan_cmd().
The remaining non-fix changes from the original v2, dropping a
redundant read-back and improving the poll failure messages, will
follow via net-next.
Changes in this series (v2), relative to its v1 [3]:
* patch 1: also report the link as down (state->link = false) on the
failed-read path; phylink presets state->link, so the previous bare
return reported a failed read as link-up (Sashiko AI review). Kept
Andrew's Reviewed-by given the small, in-spirit change -- please
re-confirm.
* new patch 4: check the CORE_PLL_GROUP4 read-modify-write in
mt7531_setup(), the call site exposed once patch 3 makes the MT7531
indirect c45 access propagate command-write failures.
* new patch 5: propagate MT7530_ATC / MT7530_VTCR command-register
write errors in mt7530_fdb_cmd() and mt7530_vlan_cmd() instead of
polling a BUSY bit that a failed write never set.
* collected Reviewed-by: Andrew Lunn on patches 1-3 and 6.
[1] https://lore.kernel.org/netdev/cover.1785213071.git.daniel@makrotopia.org/
[2] https://lore.kernel.org/netdev/cover.1785368701.git.daniel@makrotopia.org/
[3] https://lore.kernel.org/netdev/cover.1785427248.git.daniel@makrotopia.org/
Daniel Golle (6):
net: pcs: mtk-lynxi: check regmap reads in mtk_pcs_lynxi_get_state()
net: dsa: mt7530: check bus->read() error in core_rmw()
net: dsa: mt7530: error out on failed PHY_IAC command writes
net: dsa: mt7530: check CORE_PLL_GROUP4 access in mt7531_setup()
net: dsa: mt7530: check command register writes in fdb and vlan cmd
net: dsa: mt7530: serialize the regmap IRQ chip like every other user
drivers/net/dsa/mt7530.c | 86 +++++++++++++++++++++++++++------
drivers/net/pcs/pcs-mtk-lynxi.c | 7 ++-
2 files changed, 75 insertions(+), 18 deletions(-)
base-commit: af39eb111ce6b5eba9c08513b62c4868eb7e7fd5
next reply other threads:[~2026-08-04 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 3:10 Daniel Golle [this message]
2026-08-04 3:10 ` [PATCH net v2 1/6] net: pcs: mtk-lynxi: check regmap reads in mtk_pcs_lynxi_get_state() Daniel Golle
2026-08-04 3:10 ` [PATCH net v2 2/6] net: dsa: mt7530: check bus->read() error in core_rmw() Daniel Golle
2026-08-04 3:10 ` [PATCH net v2 3/6] net: dsa: mt7530: error out on failed PHY_IAC command writes Daniel Golle
2026-08-04 3:10 ` [PATCH net v2 4/6] net: dsa: mt7530: check CORE_PLL_GROUP4 access in mt7531_setup() Daniel Golle
2026-08-04 3:10 ` [PATCH net v2 5/6] net: dsa: mt7530: check command register writes in fdb and vlan cmd Daniel Golle
2026-08-04 3:11 ` [PATCH net v2 6/6] net: dsa: mt7530: serialize the regmap IRQ chip like every other user Daniel Golle
2026-08-07 23:50 ` [PATCH net v2 0/6] net: dsa: mt7530: fix remaining swallowed MDIO access errors patchwork-bot+netdevbpf
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=cover.1785811140.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=Landen.Chao@mediatek.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chester.a.unal@arinc9.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lynxis@fe80.eu \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sean.wang@mediatek.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