[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5AGv2ykKmL631A6O2yas-1ffmFaZdHFGMxrFx93G9t8XA@mail.gmail.com>
Date: Wed, 3 Sep 2025 20:37:39 -0300
From: Fabio Estevam <festevam@...il.com>
To: Frank Li <Frank.Li@....com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
Russell King <linux@...linux.org.uk>, devicetree@...r.kernel.org, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
hs@...ladev.com
Subject: Re: [PATCH 05/16] ARM: dts: imx6qdl-aristainetos2: rename
ethernet-phy to ethernet-phy@0
Hi Frank,
Thanks for working on this series.
On Wed, Sep 3, 2025 at 5:20 PM Frank Li <Frank.Li@....com> wrote:
>
> Rename ethernet-phy to ethernet-phy@0 to fix below CHECK_DTB warnings:
> arch/arm/boot/dts/nxp/imx/imx6dl-aristainetos2_4.dtb: ethernet@...8000 (fsl,imx6q-fec): mdio: Unevaluated properties are not allowed ('ethernet-phy' was unexpected)
....
> - ethphy: ethernet-phy {
> + ethphy: ethernet-phy@0 {
> compatible = "ethernet-phy-ieee802.3-c22";
> + reg = <0>;
Are you sure the Ethernet PHY is actually at address 0?
The board schematics are often needed to get this information.
I'm adding Heiko on CC in case he can confirm.
Powered by blists - more mailing lists