arm64: dts: ti: k3-am62-phycore-som: Enable cpsw_mac_syscon in U-Boot

Add the "bootph-all" property to cpsw_mac_syscon.

This fuse region contains the internal MAC address. Without this syscon node enabled, this interface will get a random MAC during network boot. This is problematic because the AM62x network boot is using BOOTP protocol for some binaries and this protocol does not support dynamic lease expiration. Therefore, the DHCP server can run out of free IP addresses.

---
Changes in v2:
Moved changes from k2-am62-main.dsti to k3-am62-phycore-som.dtsi

 arch/arm64/boot/dts/ti/k3-am62-phycore-som.dtsi | 4 ++++
 1 file changed, 4 insertions(+)

index eeca643fedbe..beeac481e683 100644
@@ -219,6 +219,10 @@ &cpsw_port1 {
 	bootph-all;
 };
 
+&cpsw_mac_syscon {
+	bootph-all;
+};
+
 &cpsw3g_mdio {
 	pinctrl-names = "default";
 	pinctrl-0 = <&main_mdio1_pins_default>;

2.25.1

Add the "bootph-all" property to cpsw_mac_syscon.

This fuse region contains the internal MAC address. Without this syscon node enabled, this interface will get a random MAC during network boot. This is problematic because the AM62Ax network boot is using BOOTP protocol for some binaries and this protocol does not support dynamic lease expiration. Therefore, the DHCP server can run out of free IP addresses.

---
Changes in v2:
Moved changes from k2-am62a-main.dsti to k3-am62a-phycore-som.dtsi

 arch/arm64/boot/dts/ti/k3-am62a-phycore-som.dtsi | 5 +++++
 1 file changed, 5 insertions(+)

index b3d012a5a26a..7f00576a4bd2 100644
@@ -197,6 +197,11 @@ &cpsw_port1 {
 	bootph-all;
 };
 
+
+&cpsw_mac_syscon {
+	bootph-all;
+};
+
 &cpsw3g_mdio {
 	pinctrl-names = "default";
 	pinctrl-0 = <&main_mdio1_pins_default>;

2.25.1

Hi Daniel Schultz,

I have applied the following to branch ti-k3-dts-next on [1] with cosmetic fixups. Thank you!

[1/2] arm64: dts: ti: k3-am62-phycore-som: Enable cpsw_mac_syscon in U-Boot

      commit: d468b7b8a6fe3d21df5a186d04f9d6124ef66d4d
[2/2] arm64: dts: ti: k3-am62a-phycore-som: Enable cpsw_mac_syscon in U-Boot
      commit: a9bd8d35a88e0bf72ebf5a803eb4c7f8e4731e3e

All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git

Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
https://ti.com/opensource