From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
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 20:18:44 +0100 [thread overview]
Message-ID: <ee26c05c-a7dd-4334-b359-353449e50662@bootlin.com> (raw)
In-Reply-To: <aXzzxeRsbnF8-nAq@shell.armlinux.org.uk>
On 30/01/2026 19:09, Russell King (Oracle) wrote:
> 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!
>
Just rebuilt a kernel w/ debugfs support, and indeed I have :
[...]
10/100 Mbps: Y
1000 Mbps: Y
Half duplex: Y
[...]
So looks like the if() isn't taken :)
Maxime
next prev parent reply other threads:[~2026-01-30 19:18 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)
2026-01-30 19:18 ` Maxime Chevallier [this message]
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=ee26c05c-a7dd-4334-b359-353449e50662@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--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=linux@armlinux.org.uk \
--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