Messages in this thread | | | From | Alvin Šipraga <> | Subject | [PATCH net-next 0/2] net: dsa: realtek: fix PHY register read corruption | Date | Wed, 16 Feb 2022 17:04:58 +0100 |
| |
From: Alvin Šipraga <alsi@bang-olufsen.dk>
These two patches fix the issue reported by Arınç where PHY register reads sometimes return garbage data.
MAINTAINERS: Please can you help me with the targetting of these two patches? This bug is present ca. 5.16, when the SMI version of the rtl8365mb driver was introduced. But now in net-next we have the MDIO interface from Luiz, where the issue is also present. I am sending what I think is an ideal patch series, but should I split it up and send the SMI-related changes to net and the MDIO changes to net-next? If so, how would I go about splitting it while preventing merge conflicts and build errors?
For now I am sending it to net-next so that the whole thing can be reviewed. If it's applied, I would gladly backport the fix to the stable tree for 5.16, but I am still confused about what to do for 5.17.
Thanks for your help.
Alvin Šipraga (2): net: dsa: realtek: allow subdrivers to externally lock regmap net: dsa: realtek: rtl8365mb: serialize indirect PHY register access
drivers/net/dsa/realtek/realtek-mdio.c | 46 +++++++++++++++++++++- drivers/net/dsa/realtek/realtek-smi.c | 48 +++++++++++++++++++++-- drivers/net/dsa/realtek/realtek.h | 2 + drivers/net/dsa/realtek/rtl8365mb.c | 54 ++++++++++++++++---------- 4 files changed, 124 insertions(+), 26 deletions(-)
-- 2.35.0
| |