From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com, netdev@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 1/3] net: stmmac: clear half-duplex caps where unsupported
Date: Fri, 30 Jan 2026 18:09:09 +0000 [thread overview]
Message-ID: <aXzzxeRsbnF8-nAq@shell.armlinux.org.uk> (raw)
In-Reply-To: <9dfdeee0-7758-439b-a2a5-a7f243427cf4@bootlin.com>
On Fri, Jan 30, 2026 at 06:29:23PM +0100, Maxime Chevallier wrote:
> Hi,
>
> On 30/01/2026 12:10, Russell King (Oracle) wrote:
> > Where a core supports hardware features, but does not indicate support
> > for half-duplex, clear phylink's half-duplex 1G, 100M and 10M
> > capability bits to disallow half-duplex operation and advertisement of
> > these link modes.
> >
> > This will avoid the need for special code in the PCS driver to do this
> > based on the ESTATUS register bits, as the support in the PCS is
> > dependent on the same synthesis choice as the MAC core.
> >
> > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
>
> Gave it a quick test on socfpga, as this impacts all variants,
> and we seem to be good so,
>
> Tested-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
If you look at /sys/kernel/debug/stmmaceth/ethX/dma_cap, it should
say whether half duplex is supported (I guess in your case it will
be, it's probably very unlikely not to be.) However, would be worth
knowing whether the if() is taken or not!
--
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-01-30 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 11:10 [PATCH net-next 0/3] net: stmmac: pcs preparation Russell King (Oracle)
2026-01-30 11:10 ` [PATCH net-next 1/3] net: stmmac: clear half-duplex caps where unsupported Russell King (Oracle)
2026-01-30 17:29 ` Maxime Chevallier
2026-01-30 18:09 ` Russell King (Oracle) [this message]
2026-01-30 19:18 ` Maxime Chevallier
2026-01-30 11:10 ` [PATCH net-next 2/3] net: stmmac: move most PCS register definitions to stmmac_pcs.c Russell King (Oracle)
2026-01-30 11:10 ` [PATCH net-next 3/3] net: stmmac: handle integrated PCS phy_intf_sel separately Russell King (Oracle)
2026-01-31 16:37 ` [PATCH net-next 0/3] net: stmmac: pcs preparation Mohd Ayaan Anwar
2026-02-03 3:20 ` 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=aXzzxeRsbnF8-nAq@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.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