From: Andrew Lunn <andrew@lunn.ch>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: Robert Marko <robert.marko@sartura.hr>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
gregkh@linuxfoundation.org, nicolas.ferre@microchip.com,
mturquette@baylibre.com, sboyd@kernel.org,
richardcochran@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
daniel.machon@microchip.com, UNGLinuxDriver@microchip.com,
luka.perkov@sartura.hr,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: Re: [PATCH 4/4] arm64: dts: microchip: add LAN969x support
Date: Sat, 6 Dec 2025 19:06:41 +0100 [thread overview]
Message-ID: <d98b3069-861c-456d-8637-67e36dc107bb@lunn.ch> (raw)
In-Reply-To: <a8185e0f-a3a2-44df-af37-1ad505ce9a7b@tuxon.dev>
On Sat, Dec 06, 2025 at 03:53:42PM +0200, Claudiu Beznea wrote:
> > + port29: port@29 {
> > + reg = <29>;
> > + microchip,bandwidth = <1000>;
> > + phys = <&serdes 11>;
> > + phy-handle = <&phy3>;
> > + phy-mode = "rgmii";
>
> >From chekpatch:
>
> WARNING: phy-mode "rgmii" without comment -- delays on the PCB should be
> described, otherwise use "rgmii-id"
> #779: FILE: arch/arm64/boot/dts/microchip/lan9696-ev23x71a.dts:750:
> + phy-mode = "rgmii";
>
> > + rx-internal-delay-ps = <1000>;
> > + tx-internal-delay-ps = <1000>;
> > + };
I did a very quick scan of the patch and missed that. It is great that
checkpatch is now commenting about "rgmii".
1ns is very odd. You need a total of 2ns, so where is the rest coming
from? This definitely needs a comment explaining what is going on.
Also, RGMII typically does not need a SERDES, unless there is
something like an SGMII to RGMII converter being used. So is the phys
property needed?
Andrew
next prev parent reply other threads:[~2025-12-06 18:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 12:21 [PATCH 1/4] dt-bindings: usb: Add Microchip LAN969x support Robert Marko
2025-12-03 12:21 ` [PATCH 2/4] dt-bindings: arm: Document Microchip LAN969x Robert Marko
2025-12-03 19:19 ` Conor Dooley
2025-12-08 10:30 ` Robert Marko
2025-12-08 17:10 ` Conor Dooley
2025-12-12 10:09 ` Robert Marko
2025-12-12 17:55 ` Conor Dooley
2025-12-03 12:21 ` [PATCH 3/4] include: dt-bindings: add LAN969x clock bindings Robert Marko
2025-12-03 19:22 ` Conor Dooley
2025-12-03 12:21 ` [PATCH 4/4] arm64: dts: microchip: add LAN969x support Robert Marko
2025-12-03 19:21 ` Conor Dooley
2025-12-15 11:36 ` Robert Marko
2025-12-15 12:32 ` Nicolas Ferre
2025-12-15 13:31 ` Robert Marko
2025-12-06 13:53 ` Claudiu Beznea
2025-12-06 18:06 ` Andrew Lunn [this message]
2025-12-08 17:15 ` Conor Dooley
2025-12-06 11:27 ` [PATCH 1/4] dt-bindings: usb: Add Microchip " Claudiu Beznea
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=d98b3069-861c-456d-8637-67e36dc107bb@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=horatiu.vultur@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=richardcochran@gmail.com \
--cc=robert.marko@sartura.hr \
--cc=robh@kernel.org \
--cc=sboyd@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