Re: [PATCH v2 4/4] ARM: ls1021a: initial Ethernet and mdio configuration

[Sascha Hauer <s.hauer@pengutronix.de>]

Hi Renaud,

On Wed, Feb 04, 2026 at 11:46:21AM +0000, Renaud Barbier wrote:
> diff --git a/arch/arm/dts/fsl-ls1021a-iot.dts b/arch/arm/dts/fsl-ls1021a-iot.dts
> index d7e8bcc7ed..33282c8f52 100644
> --- a/arch/arm/dts/fsl-ls1021a-iot.dts
> +++ b/arch/arm/dts/fsl-ls1021a-iot.dts
> @@ -69,6 +69,34 @@ &i2c2 {
>  	status = "disabled";
>  };
>  
> +&enet0 {
> +	status = "disabled";
> +};
> +
> +&enet1 {
> +	tbi-handle = <&tbi1>;
> +	phy-handle = <&phy3>;
> +	phy-mode = "sgmii";
> +	/* Disable property as transmit fails without a DMA sync */
> +	/delete-property/ dma-coherent;
> +};
> +
> +&enet2 {
> +	status = "disabled";
> +};
> +
> +&mdio0 {
> +	/* Rename the compatible name property as the mdio register offset
> +	 * in the gianfar driver depends on this name. Once the driver
> +	 * is in sync with Linux, it may be gone.
> +	 */
> +	compatible = "fsl,etsec2-mdio";

What am I missing here? The "fsl,etsec2-mdio" compatible is introduced
in your patch series and the original "gianfar" compatible is unused in
barebox, so why not use the original "gianfar" compatible?

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |