[PATCH v2 3/3] fixup! arm: dts: k3-am62: Bump dtsi from linux v6.5-rc1

[Roger Quadros]

On 21/07/2023 16:07, Maxime Ripard wrote:
> Dropping ranges entirely doesn't work since the register offset on the
> MDIO device node will now be completely off, so we need to adjust it to
> the right value without the translation.
> 
> We also need to have an empty ranges property for the reg address to be
> properly evaluated.
> 
> Signed-off-by: Maxime Ripard <mripard at kernel.org>
> ---
>  arch/arm/dts/k3-am625-sk-u-boot.dtsi | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/dts/k3-am625-sk-u-boot.dtsi b/arch/arm/dts/k3-am625-sk-u-boot.dtsi
> index db814ed02a7e..77c9e4cb87f7 100644
> --- a/arch/arm/dts/k3-am625-sk-u-boot.dtsi
> +++ b/arch/arm/dts/k3-am625-sk-u-boot.dtsi
> @@ -119,8 +119,8 @@
>  };
>  
>  &cpsw3g {
> -	/delete-property/ ranges;

cpsw-phy-sel will be broken in u-boot after you remove /delete-property/ ranges.
To fix this up we need to teach the am65-cpsw driver to fetch
the cpsw-phy-sel address from the phys property instead and drop
the cpsw-phy-sel child.

>  	bootph-pre-ram;
> +	ranges;

You don't have to add ranges here. am62-main.dtsi should have it in
the cpsw3g node.

>  
>  	cpsw-phy-sel at 04044 {
>  		compatible = "ti,am64-phy-gmii-sel";
> @@ -129,6 +129,10 @@
>  	};
>  };
>  
> +&cpsw3g_mdio {
> +	reg = <0x0 0x8000f00 0x0 0x100>;
> +};
> +

This should not be required. The u-boot driver is still hard-coding
the MDIO address and Linux should get the right address based on
address translation of the child cpsw3g_mdio node.

>  &cpsw_port1 {
>  	bootph-pre-ram;
>  };
> 

-- 
cheers,
-roger