Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Kaison <dkx@t-chip.com.cn>
Cc: Rob Herring <robh@kernel.org>, Jimmy Hon <honyuenkwun@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>, Wayne Chou <zxf@t-chip.com.cn>,
	Quentin Schulz <quentin.schulz@cherry.de>,
	Dragan Simic <dsimic@manjaro.org>,
	Jonas Karlman <jonas@kwiboo.se>, FUKAUMI Naoki <naoki@radxa.com>,
	Peter Robinson <pbrobinson@gmail.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 devicetree for the ROC-RK3588-RT
Date: Wed, 10 Sep 2025 14:15:33 +0200	[thread overview]
Message-ID: <ec8a3649-3f8f-40b7-a534-041b3523efe4@lunn.ch> (raw)
In-Reply-To: <76B19AD42CA555FC+fff44db30522cf270802ec31912a9c19d29b2d39.camel@t-chip.com.cn>

On Wed, Sep 10, 2025 at 10:55:22AM +0800, Kaison wrote:
> hi,
> I'm very sorry. Due to the default configuration of my email, I didn't
> receive your email normally. I have fixed this issue.
> 
> On Tue, 2025-09-09 at 14:31 +0200, Andrew Lunn wrote:
> > > - 2x Gigabit Ethernet, 1x 2.5G Ethernet
> > 
> > I actually only see the 2x 1G. Is the 2.5G not supported yet?
> The 2.5G Ethernet is based on the Realtek RTL8125 network controller of
> PCIe 2.0x1.

Ah, O.K. Maybe add a comment, because i was looking for something
integrated into the SoC, not a PCIe device.

> > > +&gmac0 {
> > > +	clock_in_out = "output";
> > > +	phy-handle = <&rgmii_phy0>;
> > > +	phy-mode = "rgmii-rxid";
> > > +	pinctrl-names = "default";
> > > +	pinctrl-0 = <&gmac0_miim
> > > +		     &gmac0_tx_bus2
> > > +		     &gmac0_rx_bus2
> > > +		     &gmac0_rgmii_clk
> > > +		     &gmac0_rgmii_bus>;
> > > +	tx_delay = <0x47>;
> > 
> > What happened about my comment that "rgmii-rxid" is probably wrong?
> > 
> > If you think it is correct, you should reply with a
> > justification. Maybe PCB is very odd? In which case, a comment would
> > be good to explain who it is odd.
> The Ethernet part of the board is designed with reference to the
> rockchip evb1 board. 
> 
> link: 
> https://github.com/Firefly-rk-linux/docs/blob/rk3588/firefly-public/en/Common/GMAC/Rockchip_Developer_Guide_Linux_GMAC_RGMII_Delayline_EN.pdf
> 
> 
> The document describes the usage of the rgmii-rxid mode:
> 
> When the hardware enables the RX delay of the PHY. Need to turn off the
> RX delay of the GMAC, and the dts configuration mode becomes "rgmii-
> rxid".

Vendors get this wrong as well, and give you bad advice. Please look
at:

https://elixir.bootlin.com/linux/v6.16.5/source/Documentation/devicetree/bindings/net/ethernet-controller.yaml#L264

	Andrew

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

      reply	other threads:[~2025-09-10 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  1:31 [PATCH v2 0/2] Add support for Firefly ROC-RK3588-RT Kaison Deng
2025-09-09  1:31 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add " Kaison Deng
2025-09-09  7:22   ` Krzysztof Kozlowski
2025-09-10  5:47     ` Kaison Deng
2025-09-10  7:10       ` Krzysztof Kozlowski
2025-09-09  1:31 ` [PATCH v2 2/2] arm64: dts: rockchip: Add devicetree for the ROC-RK3588-RT Kaison Deng
2025-09-09 12:31   ` Andrew Lunn
2025-09-10  2:55     ` Kaison
2025-09-10 12:15       ` 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=ec8a3649-3f8f-40b7-a534-041b3523efe4@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dkx@t-chip.com.cn \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=honyuenkwun@gmail.com \
    --cc=jonas@kwiboo.se \
    --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=naoki@radxa.com \
    --cc=pbrobinson@gmail.com \
    --cc=quentin.schulz@cherry.de \
    --cc=robh@kernel.org \
    --cc=zxf@t-chip.com.cn \
    /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