x86: Drop FSP error defines and use EFI instead
authorSimon Glass <sjg@chromium.org>
Thu, 13 Aug 2015 01:33:07 +0000 (19:33 -0600)
committerSimon Glass <sjg@chromium.org>
Fri, 14 Aug 2015 15:50:13 +0000 (09:50 -0600)
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>
arch/x86/include/asm/fsp/fsp_types.h
arch/x86/lib/fsp/fsp_common.c

index f32d8273a0e159adb96fbe023cc999c6760d6eca..4fe69f23752ca851a9ff2cddf4b3be51b901c54c 100644 (file)
@@ -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
index 6f72c6dc7bb1f5d3a91433d43d11f8d3fe19a6b5..d564cb9043eb84fa6ec1abbfe966708655ce644a 100644 (file)
@@ -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");