Hi Michael, On 2026-05-05T00:47:48, Michael Srba <[email protected]> wrote: > mach-snapdragon: boot0.h: split out msm8916_boot0.h > > Prepare for supporting alternative boot0.h per-SoC by splitting out > the existing msm8916-specific code. > > There is now a selection mechanism to choose a specific boot0.h > in the Kconfig. BOOT0_MSM8916_PSCI_WORKAROUND is the only option > right now, but more can be added. The toplevel boot0.h additionally > enables conditionally performing the include only in u-boot proper, > or only in SPL. > > Signed-off-by: Michael Srba <[email protected]> > > arch/arm/mach-snapdragon/Kconfig | 16 ++++++ > arch/arm/mach-snapdragon/include/mach/boot0.h | 58 > +++------------------- > .../mach-snapdragon/include/mach/msm8916_boot0.h | 54 ++++++++++++++++++++ > configs/dragonboard410c_defconfig | 1 + > 4 files changed, 77 insertions(+), 52 deletions(-)
> diff --git a/arch/arm/mach-snapdragon/include/mach/boot0.h > b/arch/arm/mach-snapdragon/include/mach/boot0.h > @@ -1,54 +1,8 @@ > /* SPDX-License-Identifier: GPL-2.0+ */ > +#if defined(CONFIG_SPL_BUILD) > b reset > +#else > +#if defined(CONFIG_BOOT0_MSM8916_PSCI_WORKAROUND) > +#include 'msm8916_boot0.h' > +#endif > +#endif When neither CONFIG_SPL_BUILD nor BOOT0_MSM8916_PSCI_WORKAROUND is set, this expands to nothing, so start.S falls through into _TEXT_BASE etc. Is that intended? Reviewed-by: Simon Glass <[email protected]> Regards, Simon
