From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Linus Walleij <linusw@kernel.org>,
Luiz Angelo Daros de Luca <luizluca@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: "Oleksij Rempel" <o.rempel@pengutronix.de>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
"Russell King" <linux@armlinux.org.uk>,
netdev@vger.kernel.org,
"Alvin Šipraga" <alvin.sipraga@analog.com>
Subject: [PATCH net-next v1 1/1] net: phy: realtek: add MDI-X support for RTL8365MB-VC
Date: Tue, 29 Sep 2026 11:20:07 +0200 [thread overview]
Message-ID: <20260929092007.1184843-1-o.rempel@pengutronix.de> (raw)
Add MDI-X configuration and status reporting for the RTL8365MB-VC internal
PHYs. Without a driver hook genphy cannot reach the chip's crossover
control register, so forcing MDI/MDI-X with "ethtool -s <dev> mdix on|off"
is a no-op and "ethtool <dev>" cannot report the resolved MDI-X state on
this PHY.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
drivers/net/phy/realtek/realtek_main.c | 80 ++++++++++++++++++++++++++
1 file changed, 80 insertions(+)
diff --git a/drivers/net/phy/realtek/realtek_main.c b/drivers/net/phy/realtek/realtek_main.c
index 3b3352e2cdc6..e14960192e79 100644
--- a/drivers/net/phy/realtek/realtek_main.c
+++ b/drivers/net/phy/realtek/realtek_main.c
@@ -239,6 +239,16 @@
#define RTL_PHYSR_MASTER BIT(11)
#define RTL_PHYSR_SPEED_MASK (RTL_PHYSR_SPEEDL | RTL_PHYSR_SPEEDH)
+/* MDI-X control and status of the RTL8365MB-VC internal PHY. The resolved
+ * MDI-X state is reported in RTL_PHYSR; the configuration lives in a
+ * chip-specific control register. Both are only known to apply to this model.
+ * On this chip a set select/resolved bit means MDI, not MDI-X (measured).
+ */
+#define RTL8365MB_VC_PHYCR1 0x18
+#define RTL8365MB_VC_PHYCR1_MDIX_FORCE BIT(9)
+#define RTL8365MB_VC_PHYCR1_MDI BIT(8)
+#define RTL8365MB_VC_PHYSR_MDI BIT(1)
+
#define RTL_MDIO_PCS_EEE_ABLE 0xa5c4
#define RTL_MDIO_AN_EEE_ADV 0xa5d0
#define RTL_MDIO_AN_EEE_LPABLE 0xa5d2
@@ -3058,6 +3068,74 @@ static irqreturn_t rtl8221b_handle_interrupt(struct phy_device *phydev)
return IRQ_HANDLED;
}
+static int rtl8365mb_config_mdix(struct phy_device *phydev)
+{
+ u16 val;
+
+ switch (phydev->mdix_ctrl) {
+ case ETH_TP_MDI:
+ val = RTL8365MB_VC_PHYCR1_MDIX_FORCE |
+ RTL8365MB_VC_PHYCR1_MDI;
+ break;
+ case ETH_TP_MDI_X:
+ val = RTL8365MB_VC_PHYCR1_MDIX_FORCE;
+ break;
+ case ETH_TP_MDI_AUTO:
+ val = 0;
+ break;
+ default:
+ /* Leave the hardware configuration alone until user space
+ * asks for a specific mode.
+ */
+ return 0;
+ }
+
+ return phy_modify_changed(phydev, RTL8365MB_VC_PHYCR1,
+ RTL8365MB_VC_PHYCR1_MDIX_FORCE |
+ RTL8365MB_VC_PHYCR1_MDI, val);
+}
+
+static int rtl8365mb_config_aneg(struct phy_device *phydev)
+{
+ int ret;
+
+ ret = rtl8365mb_config_mdix(phydev);
+ if (ret < 0)
+ return ret;
+
+ /* The pair assignment is only evaluated while the link is brought up,
+ * so renegotiate if the crossover configuration changed.
+ */
+ return __genphy_config_aneg(phydev, ret);
+}
+
+static int rtl8365mb_read_status(struct phy_device *phydev)
+{
+ int ret;
+
+ ret = phy_read(phydev, RTL8365MB_VC_PHYCR1);
+ if (ret < 0)
+ return ret;
+
+ if (ret & RTL8365MB_VC_PHYCR1_MDIX_FORCE) {
+ if (ret & RTL8365MB_VC_PHYCR1_MDI)
+ phydev->mdix_ctrl = ETH_TP_MDI;
+ else
+ phydev->mdix_ctrl = ETH_TP_MDI_X;
+ } else {
+ phydev->mdix_ctrl = ETH_TP_MDI_AUTO;
+ }
+
+ ret = phy_read(phydev, RTL_PHYSR);
+ if (ret < 0)
+ return ret;
+
+ phydev->mdix = (ret & RTL8365MB_VC_PHYSR_MDI) ? ETH_TP_MDI :
+ ETH_TP_MDI_X;
+
+ return genphy_read_status(phydev);
+}
+
static struct phy_driver realtek_drvs[] = {
{
PHY_ID_MATCH_EXACT(0x00008201),
@@ -3354,6 +3432,8 @@ static struct phy_driver realtek_drvs[] = {
/* Interrupt handling analogous to RTL8366RB */
.config_intr = genphy_no_config_intr,
.handle_interrupt = genphy_handle_interrupt_no_ack,
+ .config_aneg = rtl8365mb_config_aneg,
+ .read_status = rtl8365mb_read_status,
.suspend = genphy_suspend,
.resume = genphy_resume,
}, {
--
2.47.3
next reply other threads:[~2026-09-29 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 9:20 Oleksij Rempel [this message]
2026-09-29 10:21 ` [PATCH net-next v1 1/1] net: phy: realtek: add MDI-X support for RTL8365MB-VC Alvin Šipraga
2026-09-30 10:59 ` Linus Walleij
2026-10-01 12:21 ` netdev-bot+sashiko
2026-10-02 17:17 ` Luiz Angelo Daros de Luca
2026-10-05 3:50 ` 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=20260929092007.1184843-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=alvin.sipraga@analog.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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