summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-stm32mp/include/mach/bbu.h
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2022-06-02 11:01:31 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2022-06-03 09:17:27 +0200
commit0a7bbd4e6ca36a311e4f2232c3d757faf58d7a8e (patch)
tree664f75e1bf88e2e3b939d6aadb2d12dd3a80429a /arch/arm/mach-stm32mp/include/mach/bbu.h
parentcfe5484eb2cac97373da85706732678ab34cedc7 (diff)
downloadbarebox-0a7bbd4e6ca36a311e4f2232c3d757faf58d7a8e.tar.gz
barebox-0a7bbd4e6ca36a311e4f2232c3d757faf58d7a8e.tar.xz
filetype: differentiate between STM32MP FSBL and SSBL images
We have some special handling for legacy (non-FIP) STM32 images: We have a bootm handler for chainloading and an update handler for use with GPT ssbl partitions. Both aren't applicable to the TF-A image used as FSBL. As barebox always has 0x00000000 at offset 0xfc and TF-A alrways has 0x10000000, we can use that to differentiate between the two images to make sure we refuse TF-A images when barebox images are expected. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220602090133.3190450-6-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'arch/arm/mach-stm32mp/include/mach/bbu.h')
-rw-r--r--arch/arm/mach-stm32mp/include/mach/bbu.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/mach-stm32mp/include/mach/bbu.h b/arch/arm/mach-stm32mp/include/mach/bbu.h
index d49fb045ea..3a6951a8f1 100644
--- a/arch/arm/mach-stm32mp/include/mach/bbu.h
+++ b/arch/arm/mach-stm32mp/include/mach/bbu.h
@@ -10,7 +10,7 @@ static inline int stm32mp_bbu_mmc_register_handler(const char *name,
unsigned long flags)
{
return bbu_register_std_file_update(name, flags, devicefile,
- filetype_stm32_image_v1);
+ filetype_stm32_image_ssbl_v1);
}
#endif /* MACH_STM32MP_BBU_H_ */