diff options
author | Ovidiu Panait <ovidiu.panait@windriver.com> | 2020-07-24 14:12:15 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2020-08-06 14:26:35 -0400 |
commit | 81e7cb1e71fb216589b4e2fd3eb498ec72489a09 (patch) | |
tree | 542292e5a5b908ef71f32d82a7ad01d654c4f9b3 /common | |
parent | ba7431031f657ff18203c9598496e0288809ae17 (diff) |
board_f: Introduce arch_setup_bdinfo initcall
Certain architectures (ppc, mips, sh, m68k) use setup board_part1 and
setup_board_part2 calls during pre-relocation init to populate gd->bd
boardinfo fields. This makes the generic init sequence cluttered with
arch-specific ifdefs.
In order to clean these arch-specific sequences from generic init,
introduce arch_setup_bdinfo weak initcall so that everyone can define their
own bdinfo setup routines.
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
Diffstat (limited to 'common')
-rw-r--r-- | common/board_f.c | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/common/board_f.c b/common/board_f.c index 72446f6da5..4356431488 100644 --- a/common/board_f.c +++ b/common/board_f.c @@ -598,11 +598,16 @@ static int display_new_sp(void) return 0; } -int setup_bdinfo(void) +__weak int arch_setup_bdinfo(void) { return 0; } +int setup_bdinfo(void) +{ + return arch_setup_bdinfo(); +} + #if defined(CONFIG_M68K) || defined(CONFIG_MIPS) || defined(CONFIG_PPC) || \ defined(CONFIG_SH) static int setup_board_part1(void) |