From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Kurt Kanzenbach <kurt@linutronix.de>, Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH net-next] net: stmmac: stm32: Set TSO/TBS Tx queues default settings
Date: Sun, 30 Aug 2026 09:44:25 +0200 [thread overview]
Message-ID: <8b798b8a-0fb3-4978-8d9d-38616ab25741@bootlin.com> (raw)
In-Reply-To: <5693c628-dffb-46c4-8f7c-5a5a6c101660@bootlin.com>
Hi,
On 8/21/26 15:41, Maxime Chevallier wrote:
> Hi Kurt,
(Sorry Kurt this has nothing to do with your patch, I'm following-up with
some stuff I said on that thread)
>> However, we need to keep track of what SoC implementation can enable TBS
>> on which queue. For gmac4 we can probably reuse tbs_en and for xgmac
>> there's is capability field tbs_ch_num. Let's see.
>
> Thanks for tackling this, let me know if you need testing. In the past weeks
> I've been looking deep in my drawers as well as on various online shops, and
> I'm starting to have a farily comprehensive set of stmmac-enabled devices
> (although I couldn't get my hands on XGMAC, AgileX5 devkits appear to be way
> outside my budget).
Made an intersting finding yesterday, maybe it's already known stuff, but it turns
out it's easier to find a DRIVER for XGMAC than an actual device...
Looking at register layouts and at some then-removed copyright notices from the history,
it seems we have not one, not two, but three different drivers upstream for the same
DWXGMAC IP :
- stmmac's dwxgmac
- AMD's XGBE drives a designware XGMAC
- Samsung's SXGBE also drives a designware XGMAC
No wonder the xgbe selftests were doing the same as the stmmac selftests :)
I think reuniting the codebases isn't gonna happen in the near future, however it
could be a good idea to hack stmmac to work on amd HW could be a good way to validate
the stmmac dwxgmac code, with another reference driver...
Maxime
next prev parent reply other threads:[~2026-08-30 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 6:28 [PATCH net-next] net: stmmac: stm32: Set TSO/TBS Tx queues default settings Kurt Kanzenbach
2026-08-17 17:33 ` Jakub Kicinski
2026-08-18 6:57 ` Kurt Kanzenbach
2026-08-18 14:53 ` Jakub Kicinski
2026-08-19 7:35 ` Kurt Kanzenbach
2026-08-20 21:45 ` Jakub Kicinski
2026-08-21 7:22 ` Kurt Kanzenbach
2026-08-21 13:41 ` Maxime Chevallier
2026-08-30 7:44 ` Maxime Chevallier [this message]
2026-08-31 12:21 ` Kurt Kanzenbach
2026-08-21 20:25 ` 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=8b798b8a-0fb3-4978-8d9d-38616ab25741@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lorenzo@kernel.org \
--cc=mcoquelin.stm32@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