mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Alexey Charkov <alchark@gmail.com>, Andrew Lunn <andrew@lunn.ch>
Cc: Chaoyi Chen <kernel@airkyi.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Quentin Schulz <quentin.schulz@cherry.de>,
	Kever Yang <kever.yang@rock-chips.com>,
	Jonas Karlman <jonas@kwiboo.se>, John Clark <inindev@gmail.com>,
	FUKAUMI Naoki <naoki@radxa.com>,
	Jimmy Hon <honyuenkwun@gmail.com>,
	Dragan Simic <dsimic@manjaro.org>,
	Michael Riesch <michael.riesch@collabora.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Andy Yan <andy.yan@rock-chips.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add rk3576 evb2 board
Date: Thu, 8 Jan 2026 15:42:54 +0800	[thread overview]
Message-ID: <a545fec0-cb30-489a-b5e6-4ee87dcab41c@rock-chips.com> (raw)
In-Reply-To: <CABjd4YzsjZXe16XWgrHRG5shNA_DQJF45i1roahvfAfV4xdU0Q@mail.gmail.com>

Hello Alexey, Andrew,

On 1/8/2026 2:53 PM, Alexey Charkov wrote:
> On Wed, Jan 7, 2026 at 10:18 PM Andrew Lunn <andrew@lunn.ch> wrote:
>>
>>> +&gmac0 {
>>> +     clock_in_out = "output";
>>> +     phy-mode = "rgmii-rxid";
>>
>> rgmii-rxid is odd. Does the PCB really have an extra long TX clock
>> line, but a short RX clock line?
>>
>> Try changing this to rgmii-id, and drop the tx_delay property.
> 
> Actually it would be great if Rockchip could clarify the delay
> duration introduced by a single delay element in GMAC-IOMUX delay
> lines, which are controlled in the GMAC driver by the {tx,rx}_delay
> properties. Maybe we could then switch to using
> {tx,rx}_internal_delay_ps for fine-tuning the delays on the GMAC side
> as envisaged in DT bindings [1], and use phy-mode = "rgmii-id"
> throughout. Chaoyi, any chance you could ask around in your hardware
> team?
> 
> Currently though removing the delays at GMAC side altogether causes
> unstable link operation - see [2] for example.
> 
> [1] https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/net/ethernet-controller.yaml#L342-L347
> [2] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/commit/372f3e9ae62cc62cdf2543391ea57be6bb548a0c

Sorry, this problem has been discussed many times before. It's because 
the gmac on the Rockchip platform currently relies on setting the 
corresponding delay via phy-mode [3].

[3] https://lore.kernel.org/all/mqoyjn7mnq6tmt6n6oev4wa3herjaxlupml2fmcampwiajvj4a@r5zs4d3jdm5p/

The delay introduced by the delay line is not absolute. In reality,
it depends on factors such as the chip's design and process technology.

And for RK3576, you can assume that:
	
	time(ns) = 0.0579 * delay_line_count + 0.105

For example, tx_delay = <0x20> means:

	time = 0.0579 * 0x20 + 0.105 ns = 1.9578 ns

And I believe {tx,rx}_internal_delay_ps is indeed a good idea. 
I'll try to add them in v3. Thanks.

-- 
Best, 
Chaoyi

  reply	other threads:[~2026-01-08  7:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07  7:03 [PATCH v2 0/2] " Chaoyi Chen
2026-01-07  7:03 ` [PATCH v2 1/2] dt-bindings: arm: " Chaoyi Chen
2026-01-07  7:03 ` [PATCH v2 2/2] arm64: dts: " Chaoyi Chen
2026-01-07  7:56   ` Alexey Charkov
2026-01-07  8:21     ` Heiko Stübner
2026-01-07  9:57       ` Chaoyi Chen
2026-01-07 10:04         ` Chaoyi Chen
2026-01-07 14:54           ` Heiko Stübner
2026-01-07 14:56             ` Heiko Stübner
2026-01-07  9:50     ` Chaoyi Chen
2026-01-07 15:46   ` Quentin Schulz
2026-01-08  6:27     ` Chaoyi Chen
2026-01-08 10:07       ` Quentin Schulz
2026-01-08 10:41         ` Chaoyi Chen
2026-01-08 10:51           ` Quentin Schulz
2026-01-07 18:17   ` Andrew Lunn
2026-01-08  6:53     ` Alexey Charkov
2026-01-08  7:42       ` Chaoyi Chen [this message]
2026-01-08  8:01         ` Chaoyi Chen
2026-01-08  8:11           ` Alexey Charkov
2026-01-08  8:38             ` Chaoyi Chen
2026-01-08  8:49               ` Alexey Charkov
2026-01-08  9:02                 ` Chaoyi Chen
2026-01-08 13:53           ` Andrew Lunn
2026-01-08  6:50   ` Andy Yan
2026-01-08  8:04     ` [PATCH " Chaoyi Chen

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=a545fec0-cb30-489a-b5e6-4ee87dcab41c@rock-chips.com \
    --to=chaoyi.chen@rock-chips.com \
    --cc=alchark@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=andy.yan@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=honyuenkwun@gmail.com \
    --cc=inindev@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@airkyi.com \
    --cc=kever.yang@rock-chips.com \
    --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=michael.riesch@collabora.com \
    --cc=naoki@radxa.com \
    --cc=pbrobinson@gmail.com \
    --cc=quentin.schulz@cherry.de \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=shawn.lin@rock-chips.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

all inboxes | Powered by JetHome®