From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Jia Wang <wangjia@ultrarisc.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Jose Abreu <joabreu@synopsys.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next 3/3] net: stmmac: Add UltraRISC DP1000 GMAC support
Date: Tue, 1 Sep 2026 11:05:11 +0200 [thread overview]
Message-ID: <e4050d49-29cc-4fc7-aec5-53c8dd9dbc97@bootlin.com> (raw)
In-Reply-To: <178825152454.3900827.17398212265347300430.b4-reply@b4>
Hi,
On 9/1/26 10:32, Jia Wang wrote:
> On 2026-09-01 09:29 +0200, Maxime Chevallier wrote:
>> Hello,
>>
>> On 9/1/26 03:27, Jia Wang wrote:
>>> The DP1000 GMAC integration provides fixed TX and RX RGMII clock delays
>>> that cannot be disabled. For boards without PCB delays, "rgmii-id"
>>> describes the link, but passing that mode unchanged to the PHY would enable
>>> a second set of delays.
>>>
>>> Use phy_fix_phy_mode_for_mac_delays() to translate "rgmii-id" to "rgmii"
>>> before attaching the PHY. Reject other RGMII modes because the fixed MAC
>>> delays cannot be combined with them without duplicating or omitting a
>>> delay.
[...]
>
> Thanks. I enabled CONFIG_STMMAC_SELFTESTS and ran the test on the Milk-V
> Titan with the new glue driver:
>
> 1. MAC Loopback 0
> 2. MMC Counters 0
> 3. EEE -95
> 4. Hash Filter MC 0
> 5. Perfect Filter UC -95
> 6. MC Filter -95
> 7. UC Filter -95
> 8. Flow Control 0
> 9. RSS -95
> 10. VLAN Filtering -110
> 11. VLAN Filtering (perf) -110
> 12. Double VLAN Filter -110
> 13. Double VLAN Filter (perf) -110
> 14. Flexible RX Parser -95
> 15. SA Insertion (desc) 0
> 16. SA Replacement (desc) 0
> 17. SA Insertion (reg) 0
> 18. SA Replacement (reg) 0
> 19. VLAN TX Insertion -110
> 20. SVLAN TX Insertion -110
> 21. L3 DA Filtering -95
> 22. L3 SA Filtering -95
> 23. L4 DA TCP Filtering -95
> 24. L4 SA TCP Filtering -95
> 25. L4 DA UDP Filtering -95
> 26. L4 SA UDP Filtering -95
> 27. ARP Offload -110
> 28. Jumbo Frame 0
> 29. Multichannel Jumbo -95
> 30. Split Header 0
> 31. TBS (ETF Scheduler) -95
Awesome, that's pretty-much what I expected, nothing too bad stands out :)
Code itself looks good, no obvious error, so
Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Maxime
next prev parent reply other threads:[~2026-09-01 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 1:27 [PATCH net-next 0/3] net: stmmac: Add UltraRISC DP1000 GMAC support Jia Wang
2026-09-01 1:27 ` [PATCH net-next 1/3] dt-bindings: net: snps,dwmac: Add UltraRISC DP1000 compatible Jia Wang
2026-09-01 17:46 ` Conor Dooley
2026-09-02 9:35 ` Jia Wang
2026-09-01 1:27 ` [PATCH net-next 2/3] dt-bindings: net: Add UltraRISC DP1000 GMAC Jia Wang
2026-09-01 17:47 ` Conor Dooley
2026-09-01 1:27 ` [PATCH net-next 3/3] net: stmmac: Add UltraRISC DP1000 GMAC support Jia Wang
2026-09-01 7:29 ` Maxime Chevallier
2026-09-01 8:32 ` Jia Wang
2026-09-01 9:05 ` Maxime Chevallier [this message]
2026-09-01 13:48 ` Andrew Lunn
2026-09-03 7:47 ` Jia Wang
2026-09-03 12:10 ` Andrew Lunn
2026-09-03 12:30 ` Maxime Chevallier
2026-09-04 6:01 ` Jia Wang
2026-09-07 5:48 ` Jia Wang
2026-09-07 7:28 ` Maxime Chevallier
2026-09-07 7:36 ` Jia Wang
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=e4050d49-29cc-4fc7-aec5-53c8dd9dbc97@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=robh@kernel.org \
--cc=wangjia@ultrarisc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.