x86: Drop FSP error defines and use EFI instead
Now that we have an efi.h header we can use that for FSP error defines. Drop the FSP ones. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
This commit is contained in:
parent
ecfeadabb7
commit
ecf674b772
@ -68,15 +68,4 @@ struct efi_guid {
|
||||
#define SIGNATURE_64(A, B, C, D, E, F, G, H) \
|
||||
(SIGNATURE_32(A, B, C, D) | ((u64)(SIGNATURE_32(E, F, G, H)) << 32))
|
||||
|
||||
/*
|
||||
* Define FSP API return status code.
|
||||
* Compatiable with EFI_STATUS defined in PI Spec.
|
||||
*/
|
||||
#define FSP_SUCCESS 0
|
||||
#define FSP_INVALID_PARAM 0x80000002
|
||||
#define FSP_UNSUPPORTED 0x80000003
|
||||
#define FSP_DEVICE_ERROR 0x80000007
|
||||
#define FSP_NOT_FOUND 0x8000000E
|
||||
#define FSP_ALREADY_STARTED 0x80000014
|
||||
|
||||
#endif
|
||||
|
@ -46,7 +46,7 @@ void board_final_cleanup(void)
|
||||
/* call into FspNotify */
|
||||
debug("Calling into FSP (notify phase INIT_PHASE_BOOT): ");
|
||||
status = fsp_notify(NULL, INIT_PHASE_BOOT);
|
||||
if (status != FSP_SUCCESS)
|
||||
if (status)
|
||||
debug("fail, error code %x\n", status);
|
||||
else
|
||||
debug("OK\n");
|
||||
|
Loading…
Reference in New Issue
Block a user