On 01/11/2018 09:19 PM, Yogesh Gaur wrote: > For for case of lazyapply method, API fdt_fixup_board_enet() gets invoked > before DPL being deployed. > This leads to an issue that fsl-mc fdt fixup status marked as fail and > dprc driver didn't get registered in linux boot. > > Fixes this issue by calling fdt_fixup_board_enet() for case when > DPL is deployed successfully in lazyapply method. > > Signed-off-by: Yogesh Gaur <[email protected]> > --- > drivers/net/fsl-mc/mc.c | 6 +++++- > include/fdt_support.h | 3 +++ > 2 files changed, 8 insertions(+), 1 deletion(-) > > diff --git a/drivers/net/fsl-mc/mc.c b/drivers/net/fsl-mc/mc.c > index f36fe06..ab2cce1 100644 > --- a/drivers/net/fsl-mc/mc.c > +++ b/drivers/net/fsl-mc/mc.c > @@ -1415,7 +1415,11 @@ int fsl_mc_ldpaa_exit(bd_t *bd) > bool mc_boot_status = false; > > if (bd && mc_lazy_dpl_addr && !fsl_mc_ldpaa_exit(NULL)) { > - mc_apply_dpl(mc_lazy_dpl_addr); > + err = mc_apply_dpl(mc_lazy_dpl_addr); > +#ifdef CONFIG_FSL_MC_ENET
Is this really needed? We have this in Makefile drivers/net/Makefile:72:obj-$(CONFIG_FSL_MC_ENET) += fsl-mc/ York _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
