Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jiaxing Hu <gahing@gahingwoo.com>
To: andrew@lunn.ch
Cc: heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arm64: dts: rockchip: Add ArmSoM CM5 and CM5-IO
Date: Fri, 17 Jul 2026 10:51:37 +1200	[thread overview]
Message-ID: <20260716225137.2544880-1-gahing@gahingwoo.com> (raw)
In-Reply-To: <e99f752a-da1f-498d-9305-089b9d736e70@lunn.ch>

> Try setting phy-mode to rgmii-id, and these delays to 0, or removing
> them.

You are right. The PCB does not use long clock lines, so rgmii-id is the
correct description and the delays should not be in the DT. Most rk3576
boards upstream already use rgmii-id with no tx_delay/rx_delay.

I will switch to rgmii-id, let the YT8531 add both delays internally, drop
tx_delay/rx_delay, and re-test the 1000 Mbit/s link on the board before I
send v4.

Thanks,
Jiaxing


  reply	other threads:[~2026-07-16 23:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16  9:50 [PATCH v3 0/2] arm64: dts: rockchip: Add ArmSoM CM5 and CM5-IO Jiaxing Hu
2026-07-16  9:51 ` [PATCH v3 1/2] dt-bindings: arm: " Jiaxing Hu
2026-07-16  9:51 ` [PATCH v3 2/2] arm64: dts: " Jiaxing Hu
2026-07-16 18:42   ` Andrew Lunn
2026-07-16 22:51     ` Jiaxing Hu [this message]
2026-07-16 18:35 ` [PATCH v3 0/2] " Heiko Stuebner
2026-07-16 22:51   ` Jiaxing Hu
  -- strict thread matches above, loose matches on Subject: below --
2026-07-16  8:17 Jiaxing Hu
2026-07-16  8:17 ` [PATCH v3 1/2] dt-bindings: arm: " Jiaxing Hu
2026-07-16  8:17 ` [PATCH v3 2/2] arm64: dts: " Jiaxing Hu

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=20260716225137.2544880-1-gahing@gahingwoo.com \
    --to=gahing@gahingwoo.com \
    --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