[PATCH] arm: socfpga: Only do 'is OS booted from FIT' checking when VAB is enabled

[Tan, Ley Foon]

> -----Original Message-----
> From: Lim, Elly Siew Chin <elly.siew.chin.lim at intel.com>
> Sent: Monday, March 22, 2021 6:05 PM
> To: u-boot at lists.denx.de
> Cc: Marek Vasut <marex at denx.de>; Tan, Ley Foon
> <ley.foon.tan at intel.com>; See, Chin Liang <chin.liang.see at intel.com>;
> Simon Goldschmidt <simon.k.r.goldschmidt at gmail.com>; Chee, Tien Fong
> <tien.fong.chee at intel.com>; Westergreen, Dalon
> <dalon.westergreen at intel.com>; Simon Glass <sjg at chromium.org>; Gan,
> Yau Wai <yau.wai.gan at intel.com>; Lim, Elly Siew Chin
> <elly.siew.chin.lim at intel.com>
> 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 <elly.siew.chin.lim at intel.com>


Reviewed-by: Ley Foon Tan <ley.foon.tan at intel.com>