linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Beck <xunil@tahomasoft.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Chukun Pan <amadeus@jmu.edu.cn>, Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: Add HINLINK H68K
Date: Sat, 30 Aug 2025 18:21:18 -0400	[thread overview]
Message-ID: <5285B176-5178-4F6F-8FB6-B898AC0EC939@tahomasoft.com> (raw)
In-Reply-To: <021c2e76-cbde-4a2e-a165-a61223cdff93@lunn.ch>



> On Aug 30, 2025, at 17:38, Andrew Lunn <andrew@lunn.ch> wrote:
> 
> 
>> 
>>> +&gmac0 {
>>> +    assigned-clocks = <&cru SCLK_GMAC0_RX_TX>, <&cru SCLK_GMAC0>;
>>> +    assigned-clock-parents = <&cru SCLK_GMAC0_RGMII_SPEED>;
>>> +    assigned-clock-rates = <0>, <125000000>;
>>> +    clock_in_out = "output";
>>> +    phy-handle = <&rgmii_phy0>;
>>> +    phy-mode = "rgmii-id";
>> 
>> Please change phy-mode here to "rgmii". This change will yield an ethernet
>> speed throughput change of a factor of 100+.
> 
> Rockchip by default do bad things with RGMII delays.
> 
>  tx_delay:
>    description: Delay value for TXD timing.
>    $ref: /schemas/types.yaml#/definitions/uint32
>    minimum: 0
>    maximum: 0x7F
>    default: 0x30
> 
>  rx_delay:
>    description: Delay value for RXD timing.
>    $ref: /schemas/types.yaml#/definitions/uint32
>    minimum: 0
>    maximum: 0x7F
>    default: 0x10
> 
> Try setting both of these to 0. And then use 'rgmii-id'.
> 
>    Andrew

Thank you!
> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-08-30 22:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 10:00 [PATCH 0/4] arm64: dts: rockchip: Add HINLINK H66K/H68K Chukun Pan
2025-08-18 10:00 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add HINLINK Chukun Pan
2025-08-18 10:00 ` [PATCH 2/4] dt-bindings: arm: rockchip: Add HINLINK H66K / H68K Chukun Pan
2025-08-18 10:00 ` [PATCH 3/4] arm64: dts: rockchip: Add HINLINK H68K Chukun Pan
2025-08-30 21:14   ` Erik Beck
2025-08-30 21:30     ` Andrew Lunn
2025-08-30 22:21       ` Erik Beck [this message]
2025-08-31 14:48         ` Erik Beck
2025-08-31 15:53           ` Andrew Lunn
2025-08-31 16:28             ` Erik Beck
2025-09-01  0:47               ` Andrew Lunn
2025-09-01  7:00     ` Chukun Pan
2025-09-01 10:24       ` Erik Beck
2025-09-01 14:06         ` Erik Beck
2025-09-02  7:00           ` Chukun Pan
2025-09-02 12:10             ` Erik Beck
2025-09-01 16:25         ` Erik Beck
2025-08-18 10:00 ` [PATCH 4/4] arm64: dts: rockchip: Add HINLINK H66K Chukun Pan
2025-08-18 17:27 ` [PATCH 0/4] arm64: dts: rockchip: Add HINLINK H66K/H68K Conor Dooley
2025-08-24 10:54 ` Heiko Stuebner
2025-08-30 21:11   ` Erik Beck
2025-08-30 21:26     ` Andrew Lunn
2025-08-30 22:20       ` Erik Beck
2025-08-31 13:55         ` Erik Beck

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=5285B176-5178-4F6F-8FB6-B898AC0EC939@tahomasoft.com \
    --to=xunil@tahomasoft.com \
    --cc=amadeus@jmu.edu.cn \
    --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;
as well as URLs for NNTP newsgroup(s).