bootmode: add display_init_required()
Some of the Chrome OS boards were directly calling vboot called in some form after contorting around #ifdef preprocessor macros. The reasoning is that Chrome OS doesn't always do display initialization during startup. It's runtime dependent. While this is a requirement that doesn't mean vboot functions should be sprinkled around in the mainboard and chipset code. Instead provide one function, display_init_required(), that provides the policy for determining display initialization action. For Chrome OS devices this function honors vboot_skip_display_init() and all other configurations default to initializing display. Change-Id: I403213e22c0e621e148773597a550addfbaf3f7e Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/11490 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com>
This commit is contained in:
@@ -30,6 +30,8 @@ int get_wipeout_mode_switch(void);
|
||||
int get_lid_switch(void);
|
||||
|
||||
|
||||
/* Return 1 if display initialization is required. 0 if not. */
|
||||
int display_init_required(void);
|
||||
int gfx_get_init_done(void);
|
||||
void gfx_set_init_done(int done);
|
||||
|
||||
|
Reference in New Issue
Block a user