From: Adrian Kossmann <adrian.kossmann@posteo.de>
To: andrew@lunn.ch
Cc: adrian.kossmann@posteo.de, conor+dt@kernel.org,
devicetree@vger.kernel.org, heiko@sntech.de, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh@kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: Adjust RGMII TXD/RXD delays for the Rock Pi E
Date: Fri, 12 Dec 2025 23:50:13 +0000 [thread overview]
Message-ID: <20251212234957.591812-1-adrian.kossmann@posteo.de> (raw)
In-Reply-To: <57e99fa1-0e59-4129-bcae-b94df46447e7@lunn.ch>
Hi Andrew,
> rgmii means the PCB provides the delay. I doubt that is the
> case.
Yes, however, to my understanding, there are two kinds of delays that
influence RGMII timing: Delays that are added onto the clock signal
(TXC/RXC) and delays added to the data signal (TXD/RXD) by the GMAC.
The link provided by you describes delays that are either introduced by
longer clock traces on the PCB (rgmii phy-mode) or by programmable clock delays
(rgmii-id phy-mode). Delays for TXD timing and RXD timing are described in [1]
and are implemented by the Rockchip Ethernet driver which is bound to node
gmac2io according to [2]. The example DT binding in [1] as well as other
mainline DTS of devices that use the RK3328 seem to adjust RGMII timing
via TXD and RXD delays and setting phy-mode to rgmii, despite having
programmable TXC/RXC delays, at least according to the technical
manual of the RK3328. So, in this case this may be an exception
from the usual convention that any RGMII phy mode other than
'rgmii-id' is probably wrong.
Of course, I may have overlooked something or misunderstood, and I
would appreciate further guidance in this case.
[1] https://www.kernel.org/doc/Documentation/devicetree/bindings/net/rockchip-dwmac.txt
[2] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/tree/arch/arm64/boot/dts/rockchip/rk3328.dtsi#n982
Adrian
prev parent reply other threads:[~2025-12-12 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 22:02 [PATCH v2] arm64: dts: rockchip: Adjust RGMII TXD/RXD delays for the Rock Pi E Adrian Kossmann
2025-12-12 22:25 ` Andrew Lunn
2025-12-12 23:50 ` Adrian Kossmann [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=20251212234957.591812-1-adrian.kossmann@posteo.de \
--to=adrian.kossmann@posteo.de \
--cc=andrew@lunn.ch \
--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 \
/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