From: Andrew Lunn <andrew@lunn.ch>
To: Pufan Jin <2254650260@qq.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add EmbedFire LubanCat 4 board
Date: Mon, 6 Jul 2026 23:34:00 +0200 [thread overview]
Message-ID: <647b653e-d602-46d3-bbc1-0d3fa132696e@lunn.ch> (raw)
In-Reply-To: <tencent_BF5741F8151925AFF7A3026460204C2B3108@qq.com>
On Tue, Jul 07, 2026 at 05:20:35AM +0800, Pufan Jin wrote:
> On Sun, Jul 05, 2026 at 05:11:58PM +0200, Andrew Lunn wrote:
> > > + /* The board has 1.5ns delays on RX lines; TX delay is provided by the MAC. */
> >
> > That is pretty unusual. How is this RX delay done?
>
> You're right to question this, and I apologise -- the comment was
> inaccurate. I re-checked the board schematic and both TXC and RXC
> have ~2ns of trace delay added on the PCB (annotated as
> "TXC / RXC : delays 2ns" next to the RGMII bus).
O.K. So both having delays on the PCB is what i would call "somewhat
unusual", vs "pretty unusual" for a single delay.
> Since the PCB already provides the required clock skew on both
> directions, for v2 I will switch to:
>
> phy-mode = "rgmii";
>
> and drop both the tx_delay property and the misleading comment.
Please correct the comment. One issue we have is that many boards use
"rgmii" and are broken. You have a board which uses "rgmii" and it is
in fact correct. It is good to explain why it is correct, otherwise
people could think it is just another broken board.
Andrew
prev parent reply other threads:[~2026-07-06 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260705135014.1004166-1-2254650260@qq.com>
2026-07-05 13:50 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add EmbedFire LubanCat 4 board LemonFan-maker
2026-07-05 14:37 ` Conor Dooley
2026-07-05 14:38 ` Conor Dooley
2026-07-06 21:24 ` Pufan Jin
2026-07-05 13:50 ` [PATCH 2/2] arm64: dts: " LemonFan-maker
2026-07-05 14:00 ` sashiko-bot
2026-07-05 15:11 ` Andrew Lunn
2026-07-06 21:20 ` Pufan Jin
2026-07-06 21:34 ` Andrew Lunn [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=647b653e-d602-46d3-bbc1-0d3fa132696e@lunn.ch \
--to=andrew@lunn.ch \
--cc=2254650260@qq.com \
--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