From: Robert Marko Date: Tue, 13 Feb 2024 20:48:52 +0000 (+0100) Subject: qualcommax: remove usage of malibu_first_phy_addr X-Git-Url: http://git.lede-project.org./?a=commitdiff_plain;h=deda92c16c9f716d9585113c98546e421419dddb;p=openwrt%2Fstaging%2Fmans0n.git qualcommax: remove usage of malibu_first_phy_addr Now that Malibu (QCA807x) PHY is using the upstream driver, we dont need support to define address of the first PHY in package, so remove the malibu_first_phy_addr DTS property. Signed-off-by: Robert Marko --- diff --git a/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8072-301w.dts b/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8072-301w.dts index 4dcacdf297..58eefc30ba 100644 --- a/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8072-301w.dts +++ b/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8072-301w.dts @@ -414,7 +414,6 @@ switch_lan_bmp = <(ESS_PORT1 | ESS_PORT2 | ESS_PORT3 | ESS_PORT4 | ESS_PORT6)>; /* lan port bitmap */ switch_wan_bmp = ; /* wan port bitmap */ - malibu_first_phy_addr = <16>; /* PHY addr of the first malibu PHY */ switch_mac_mode = ; /* mac mode for uniphy instance0*/ switch_mac_mode1 = ; /* mac mode for uniphy instance1*/ switch_mac_mode2 = ; /* mac mode for uniphy instance2*/ diff --git a/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8074-ess.dtsi b/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8074-ess.dtsi index 6f98e01b9a..76838b86c5 100644 --- a/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8074-ess.dtsi +++ b/target/linux/qualcommax/files/arch/arm64/boot/dts/qcom/ipq8074-ess.dtsi @@ -23,24 +23,6 @@ switch_access_mode = "local bus"; switch_cpu_bmp = ; /* cpu port bitmap */ switch_inner_bmp = ; /*inner port bitmap*/ - /* This is a special binding that controls how the malibu PHY are - * init. This value reflect the PHY addr of the first malibu PHY. - * Malibu PHY are in a bundle of 5 PHY. - * Some device might have some port not connected. - * SSDK still needs the addrs of the first PHY (even if not connected) - * to correctly setup the malibu PHY. - * - * This is needed as previously SSDK based this on the port bmp, but - * this can be problematic now that we specify correct bmp. - * - * Most common configuration have the malibu PHY placed at 0. - * But some device might have it placed at address 16. - * To drive the correct value, check the port id of the malibu PHY - * and try to understand what is the first one in devices where some - * port are missing. port_phyinfo is normally the way to go to derive - * this value in the few special cases. - */ - malibu_first_phy_addr = <0>; clocks = <&gcc GCC_CMN_12GPLL_AHB_CLK>, <&gcc GCC_CMN_12GPLL_SYS_CLK>, <&gcc GCC_UNIPHY0_AHB_CLK>,