Re: [PATCH v1] net: ldpaa_eth: fix error logics of unconfigured DPMACs

On Mon, Aug 24, 2026 at 03:47:58PM +0200, Vincent Jardin wrote:
>ldpaa_eth_bind() returned -EINVAL for a DPMAC node without
>phy-connection-type.
>
>That is not "skip this device", it is "the tree is broken":
>the DM core propagates it out of lists_bind_fdt() and
>dm_scan_fdt(), initr_dm() fails, and U-Boot stops before the prompt with
>
>  ldpaa_eth ethernet@1: incorrect phy mode
>  initcall_run_r(): initcall initr_dm() failed
>  ### ERROR ### Please RESET the board ###
>
>for a MAC nobody asked U-Boot to drive.
>
>Why it matters: device trees imported from Linux enable
>every DPMAC and leave the phy description to the board file, because the
>kernel's dpaa2 driver does not need one for an MC-managed MAC. U-Boot's
>own Layerscape .dtsi instead ships all eighteen disabled for the board to
>opt into. So the moment a board takes its SoC description from
>dts/upstream, every DPMAC it does not configure in U-Boot is enabled and
>unconfigured, and one of them is enough to stop the boot.
>
>Signed-off-by: Vincent Jardin <[email protected]>
>

Acked-by: Peng Fan <[email protected]>