> -----Original Message-----
> From: Lim, Elly Siew Chin <[email protected]>
> Sent: Monday, March 22, 2021 6:05 PM
> To: [email protected]
> Cc: Marek Vasut <[email protected]>; Tan, Ley Foon
> <[email protected]>; See, Chin Liang <[email protected]>;
> Simon Goldschmidt <[email protected]>; Chee, Tien Fong
> <[email protected]>; Westergreen, Dalon
> <[email protected]>; Simon Glass <[email protected]>; Gan,
> Yau Wai <[email protected]>; Lim, Elly Siew Chin
> <[email protected]>
> Subject: [PATCH] arm: socfpga: Only do 'is OS booted from FIT' checking
> when VAB is enabled
>
> Check CONFIG_SOCFPGA_SECURE_VAB_AUTH before perform 'is OS booted
> from FIT'
> checking in board_prep_linux function. And, fix typo of
> CONFIG_SOCFPGA_SECURE_VAB_AUTH_ALLOW_NON_FIT_IMAGE.
>
> CONFIG_FIT will be enabled in both ATF and VAB boot flow, thus,
> board_prep_linux function will always be called by both ATF and VAB boot
> flow.
>
> board_pre_linux function will do 'is OS booted from FIT' checking, and it will
> be called before board_fit_image_post_process function.
>
> VAB boot flow expects the OS is always booted from FIT and with VAB signed
> cerfiticate because the VAB authentication is implemented in
> board_fit_image_post_process function. So, VAB needs the 'is OS booted
> from FIT' checking in board_pre_linux function.
>
> However, for ATF boot flow, it is not a requirement that the OS must always
> booted from FIT. The OS can be booted from individual Image and kernel dtb
> file. Thus, we should not do 'if OS is booted from FIT'
> checking in board_prep_linux function.
>
> Signed-off-by: Siew Chin Lim <[email protected]>
Reviewed-by: Ley Foon Tan <[email protected]>
