From: sashiko-bot@kernel.org
To: LemonFan-maker <2254650260@qq.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add EmbedFire LubanCat 4 board
Date: Sun, 05 Jul 2026 14:00:58 +0000 [thread overview]
Message-ID: <20260705140058.8D43E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <tencent_6D311DC5F405B157049538DD5B080082A10A@qq.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Contradiction between physical PCB RX delay and RGMII PHY mode setting, risking Gigabit Ethernet instability.
--
commit a30ca0bb9560e6ed7ecdf88333f509d579374640
Author: LemonFan-maker <2254650260@qq.com>
arm64: dts: rockchip: Add EmbedFire LubanCat 4 board
This commit adds basic device tree support for the EmbedFire LubanCat 4,
a single board computer based on the Rockchip RK3588S SoC. The enabled
peripherals allow the board to boot via serial, eMMC, or SD card, and
provide networking over Gigabit Ethernet.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-lubancat-4.dts b/arch/arm64/boot/dts/rockchip/rk3588s-lubancat-4.dts
> new file mode 100644
> index 0000000000000..f8c78df4a14ba
> --- /dev/null
> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-lubancat-4.dts
[ ... ]
> +&gmac1 {
> + clock_in_out = "output";
> + phy-handle = <&rgmii_phy1>;
> + /* The board has 1.5ns delays on RX lines; TX delay is provided by the MAC. */
> + phy-mode = "rgmii-rxid";
[Severity: Medium]
Is this phy-mode setting correct given the board's physical delay?
The comment states the board already provides 1.5ns of physical delay on the
RX lines. However, setting phy-mode to "rgmii-rxid" explicitly instructs the
PHY to add its own internal RX delay (typically ~2.0ns).
A total RX delay of ~3.5ns within a 4ns RGMII data window might shift the
clock edge out of the safe sampling region, which can cause packet loss
or link failure at Gigabit speeds.
Could you clarify if the comment about the board is outdated, or if a
different phy-mode (like "rgmii" or "rgmii-txid") was intended here?
> + pinctrl-0 = <&gmac1_miim
> + &gmac1_tx_bus2
> + &gmac1_rx_bus2
> + &gmac1_rgmii_clk
> + &gmac1_rgmii_bus>;
> + pinctrl-names = "default";
> + tx_delay = <0x1b>;
> + status = "okay";
> +};
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260705135014.1004166-1-2254650260@qq.com?part=2
next prev parent reply other threads:[~2026-07-05 14:00 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 [this message]
2026-07-05 15:11 ` Andrew Lunn
2026-07-06 21:20 ` Pufan Jin
2026-07-06 21:34 ` Andrew Lunn
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=20260705140058.8D43E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=2254650260@qq.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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