Both spl_board_init and spl_soc_init are available as ways to run
specific code in the SPL's board_init_r. Use the former for init
code that is specific to the SoC and leave spl_board_init available
for boards to use.

Signed-off-by: Paul Kocialkowski <pa...@sys-base.io>
---
 arch/arm/Kconfig                  | 2 +-
 arch/arm/mach-omap2/boot-common.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index ba0359fed5ad..656f588a97c0 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -802,7 +802,7 @@ config ARCH_OMAP2PLUS
        bool "TI OMAP2+"
        select CPU_V7A
        select GPIO_EXTRA_HEADER
-       select SPL_BOARD_INIT if SPL
+       select SPL_SOC_INIT if SPL
        select SPL_STACK_R if SPL
        select SUPPORT_SPL
        imply TI_SYSC if DM && OF_CONTROL
diff --git a/arch/arm/mach-omap2/boot-common.c 
b/arch/arm/mach-omap2/boot-common.c
index e1ea3515ac10..21b204074e80 100644
--- a/arch/arm/mach-omap2/boot-common.c
+++ b/arch/arm/mach-omap2/boot-common.c
@@ -269,7 +269,7 @@ skip_ipu1:
                debug("%s: IPU2 failed to start (%d)\n", __func__, ret);
 }
 
-void spl_board_init(void)
+void spl_soc_init(void)
 {
        /* Prepare console output */
        preloader_console_init();
-- 
2.45.2

Reply via email to