From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Meghana Malladi <m-malladi@ti.com>
Cc: pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, hkallweit1@gmail.com, andrew@lunn.ch,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org, srk@ti.com,
Vignesh Raghavendra <vigneshr@ti.com>,
Roger Quadros <rogerq@kernel.org>,
danishanwar@ti.com
Subject: Re: [PATCH net] net: phy: dp83869: Set auto mdix bit for forced 100Base-Tx mode
Date: Wed, 11 Feb 2026 13:26:41 +0000 [thread overview]
Message-ID: <aYyDkaynWEm-WJdg@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260211131033.2525617-1-m-malladi@ti.com>
On Wed, Feb 11, 2026 at 06:40:32PM +0530, Meghana Malladi wrote:
> When using DP83869 in force 100Base-Tx mode, the PHY is required
> to have robust Auto-MDIX feature enabled from register 1Eh.
> Refer to 7.4.1.2 100BASE-TX section in the TRM [1] for more details.
>
> [1]: https://www.ti.com/lit/ds/symlink/dp83869hm.pdf
> Signed-off-by: Meghana Malladi <m-malladi@ti.com>
> ---
> drivers/net/phy/dp83869.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/net/phy/dp83869.c b/drivers/net/phy/dp83869.c
> index 1f381d7b13ff..70d759c45c6a 100644
> --- a/drivers/net/phy/dp83869.c
> +++ b/drivers/net/phy/dp83869.c
> @@ -110,6 +110,7 @@
>
> /* CFG4 bits */
> #define DP83869_INT_OE BIT(7)
> +#define DP83869_CFG4_ENABLE_AUTO_MDIX_100FD BIT(9)
>
> /* OP MODE */
> #define DP83869_OP_MODE_MII BIT(5)
> @@ -900,6 +901,23 @@ static int dp83869_phy_reset(struct phy_device *phydev)
> return dp83869_config_init(phydev);
> }
>
> +static void dp83869_link_change_notify(struct phy_device *phydev)
> +{
> + int cfg4;
> +
> + /* When using DP83869 in force 100Base-Tx mode, the PHY is required
> + * to have robust Auto-MDIX feature enabled
> + */
> + if (phydev->autoneg == AUTONEG_DISABLE &&
> + phydev->speed == SPEED_100 &&
> + phydev->duplex == DUPLEX_FULL) {
> + cfg4 = phy_read(phydev, DP83869_CFG4);
> + if (cfg4 >= 0) {
> + cfg4 |= DP83869_CFG4_ENABLE_AUTO_MDIX_100FD;
> + phy_write(phydev, DP83869_CFG4, cfg4);
> + }
> + }
Shouldn't this kind of configuration be done via .config_aneg() ?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-02-11 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 13:10 [PATCH net] net: phy: dp83869: Set auto mdix bit for forced 100Base-Tx mode Meghana Malladi
2026-02-11 13:26 ` Russell King (Oracle) [this message]
2026-02-11 13:53 ` Meghana Malladi
2026-02-11 14:04 ` Andrew Lunn
2026-02-11 14:09 ` Meghana Malladi
2026-02-11 14:04 ` Russell King (Oracle)
2026-02-11 14:12 ` Andrew Lunn
2026-02-12 6:21 ` Meghana Malladi
2026-02-12 13:06 ` Andrew Lunn
2026-02-15 14:56 ` Malladi, Meghana
2026-02-12 18:40 ` Maxime Chevallier
2026-02-15 14:45 ` [EXTERNAL] " Malladi, Meghana
2026-02-15 17:23 ` Andrew Lunn
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=aYyDkaynWEm-WJdg@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.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