Hi Andrea, On Fri, Oct 31, 2025 at 4:46 AM Andrea Calabrese <[email protected]> wrote:
> --- /dev/null > +++ b/configs/imx6ulz_smm_m2d_defconfig > @@ -0,0 +1,82 @@ > +CONFIG_ARM=y > +CONFIG_ARCH_MX6=y > +CONFIG_TEXT_BASE=0x87800000 > +CONFIG_SYS_MALLOC_LEN=0x1000000 > +CONFIG_SYS_MALLOC_F_LEN=0x18000 > +CONFIG_SPL_GPIO=y > +CONFIG_SPL_LIBCOMMON_SUPPORT=y > +CONFIG_SPL_LIBGENERIC_SUPPORT=y > +CONFIG_NR_DRAM_BANKS=1 > +CONFIG_ENV_SIZE=0x20000 > +CONFIG_ENV_OFFSET=0x400000 > +CONFIG_MX6ULL=y > +CONFIG_TARGET_MX6ULZ_SMM_M2=y imx6ulz_smm_m2b_defconfig, imx6ulz_smm_m2_defconfig and imx6ulz_smm_m2d_defconfig are the same, except for the CONFIG_TARGET_ line. I suggest introducing a <configs/imx6ulz_smm_m2.config> with the standard part and then including this header file and the CONFIG_TARGET_ line in each defconfig. Take a look at some examples: configs/imx6_dhcom_drc02_defconfig:#include <configs/dh_imx6.config> configs/imx6_dhcom_pdk2_defconfig:#include <configs/dh_imx6.config> configs/imx6_dhcom_picoitx_defconfig:#include <configs/dh_imx6.config> The idea here is to simplify maintenance and prevent duplicate defconfig settings.
