From: Miguel Jesus Seron Gonzalez <info@gluon.es>
To: Dongjin Kim <tobetter@gmail.com>
Cc: Chukun Pan <amadeus@jmu.edu.cn>, Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: Change ethernet TXD timing delay value
Date: Mon, 19 Oct 2026 15:25:13 +0200 [thread overview]
Message-ID: <20261019132513.879-1-info@gluon.es> (raw)
In-Reply-To: <aKU1rJKzkkS4P+VT@anyang>
Hi Dongjin,
On Wed, Aug 20, 2025 at 11:40:44AM +0900, Dongjin Kim wrote:
> Thank you for suggesting me to try 'rgmii-id' again.
>
> I'd remember that 'rgmii-id' didn't work with the very early version of
> the board, however your suggestion works. Let me test the change with
> more boards and submit the new patch when it's done.
I ran into the same problem on an ODROID-M1 board marked
"REV 1.0 20211112", an earlier revision than the 20220613 one in your
patch, running Home Assistant OS (kernel 6.18.52). With the current
tx_delay = <0x4f>, about 6.6% of all TCP segments were retransmitted
at 1000 Mbit/s and larger HTTP transfers stalled.
I tested Chukun's suggestion (phy-mode = "rgmii-id", with tx_delay and
rx_delay removed; the driver reports "init for RGMII_ID") on the same
board, on a 1000 Mbit/s full-duplex link. It works fine on this early
revision as well:
- 3 retransmitted TCP segments out of 24929 (0.012%) over 3 h 49 min
of uptime, and no RX/TX errors
- 90 sequential requests for large files (22.5 MB in total): no
failures, 1.4 s in total, the slowest one 47 ms
- 120 parallel requests (75 MB in total): no failures, 1.2 s
For comparison, tx_delay = <0x35> gave 0.03% retransmissions on the
same board.
Are you still planning to send a v3 with rgmii-id? If you don't have
time for it, I'd be happy to send it with Chukun's Suggested-by. Either
way, for the rgmii-id version:
Tested-by: Miguel Jesus Seron Gonzalez <info@gluon.es>
Thanks,
Miguel
prev parent reply other threads:[~2026-10-19 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 7:55 [PATCH v2] arm64: dts: rockchip: Change ethernet TXD timing delay value Dongjin Kim
2025-08-19 15:10 ` Chukun Pan
2025-08-20 2:40 ` Dongjin Kim
2026-10-19 13:25 ` Miguel Jesus Seron Gonzalez [this message]
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=20261019132513.879-1-info@gluon.es \
--to=info@gluon.es \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=tobetter@gmail.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