WIFI-14849 When device is booting,it causes lan/wan ports bridge toge…

[jackcybertan]

When the device is booting, LAN/WAN ports will be in bridge state for a while, it will cause clients on the LAN side getting IP address from WAN side's DHCP server. It's wrong behavior. This PR is used for fixing this issue.
This situation usually occurs when device uses IPQ5018+QCA8337 switch chip.
I change that mdio driver bring up from kernel to module autoload and seprate lan/wan port to different group in dts file.

[blogic]

please explain in the patch why this is needed

[jackcybertan]

When mdio driver is brought up by kernel, it will reset phy. It will cause lan/wan in bridge mode. I want to shorten the time interval between the start-up of mdio phy driver and switch driver, so I have to turn the mdio driver into a module, let the switch driver's module can be inserted after the mdio driver's module is inserted.

[blogic]

@phwhite comments?

[phwhite]

@blogic I’ve tested this patch on the RAP630W, and it’s working well. I haven’t yet had time to confirm that it won’t affect other ipq50xx platforms. Given the internal time pressure to deploy this fix for a customer site running 630W, we’ve decided to apply it selectively for that platform only.

To achieve this, I modified build.sh to apply target-specific patches prior to building. The downside is that these patched files appear as uncommitted changes in git status. I spent several hours exploring alternatives, but I couldn’t get device build pre-hooks or other mechanisms in the OpenWRT tree to work with the target/linux/feeds changes—likely due to my limited experience in this area.

If you’d like, I can open a PR with this target-specific patching approach in case you’d consider using it instead of applying the patch across all ipq50xx platforms.

[blogic]

merged, Thanks !