From: Andrew Lunn <andrew@lunn.ch>
To: Prasanth <prasanth.padarthi10@gmail.com>
Cc: Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Billy Tsai <billy_tsai@aspeedtech.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC
Date: Mon, 31 Aug 2026 14:12:52 +0200 [thread overview]
Message-ID: <daf98fe8-70f9-410e-8a2a-042a671086c2@lunn.ch> (raw)
In-Reply-To: <CAMFFDGgTnNouukst3V1rEg0NCNMW-BZ6tM6+fbQc0zeXaOb72w@mail.gmail.com>
On Mon, Aug 31, 2026 at 06:43:46AM +0530, Prasanth wrote:
> Hi Andrew,
>
> I do not currently have the PCB layout or trace-length information, so I cannot
> prove that the board provides the TX delay externally.
>
> What I have validated on hardware is:
>
> rgmii: fails, with RX CRC errors and no valid RX traffic
> rgmii-rxid: passes, 5000/5000 packets, 0% loss, no RX CRC errors
> rgmii-id: also passes with the same traffic test
>
> This shows that the RTL8211F RX internal delay is required, but it does not
> establish where the TX delay is provided.
>
> Given that I cannot provide PCB-level evidence for the TX delay, would you
> prefer that I use rgmii-id for the next revision?
There has been a number of threads about the Aspeed SoC. It typically
has delays enabled in its MAC, by the bootloader. The Linux MAC driver
does not disable this, nor does it mask the value passed to the
PHY. So you see many Aspeed .dts files incorrectly using 'rgmii'. Over
the last couple of years i have been pointing out this problem, but
nobody has stepped up to fix the issue. Most DT developers just leave
the Ethernet node out, in order to get something merged.
You case is interesting, because you are not suggesting 'rgmii'. So it
could be there is more going on.
If you look in the email archives you should find the information
about where to configure the delay in the hardware. You might want to
read it out to understand how the bootloader has configured the
hardware.
Andrew
next prev parent reply other threads:[~2026-08-31 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 18:20 [PATCH v4 0/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC Prasanth Kumar Padarthi
2026-08-30 18:20 ` [PATCH v4 1/2] dt-bindings: arm: aspeed: Add ASRock Rack B650D4U Prasanth Kumar Padarthi
2026-08-30 18:20 ` [PATCH v4 2/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC Prasanth Kumar Padarthi
2026-08-31 12:36 ` Tan Siewert
2026-08-31 12:47 ` Prasanth
2026-08-30 20:23 ` [PATCH v4 0/2] " Andrew Lunn
2026-08-31 2:43 ` Prasanth
[not found] ` <CAMFFDGgTnNouukst3V1rEg0NCNMW-BZ6tM6+fbQc0zeXaOb72w@mail.gmail.com>
2026-08-31 12:12 ` Andrew Lunn [this message]
2026-08-31 12:50 ` Prasanth
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=daf98fe8-70f9-410e-8a2a-042a671086c2@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanth.padarthi10@gmail.com \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.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