[PATCH 2/3] drm/xe/guc: Add more GuC error codes to ABI
Matthew Brost
matthew.brost at intel.com
Tue Jun 25 21:48:01 UTC 2024
On Tue, Jun 25, 2024 at 04:12:57PM +0200, Michal Wajdeczko wrote:
> There are many more error codes used that the GuC firmware can
> return in the RESPONSE_FAILURE message. Add to the ABI header
> those which are more likely to be seen by the PF or VF drivers.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
> Cc: Matthew Brost <matthew.brost at intel.com>
Reviewed-by: Matthew Brost <matthew.brost at intel.com>
> ---
> drivers/gpu/drm/xe/abi/guc_errors_abi.h | 31 +++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/abi/guc_errors_abi.h b/drivers/gpu/drm/xe/abi/guc_errors_abi.h
> index d0b5fed6876f..2c627a21648f 100644
> --- a/drivers/gpu/drm/xe/abi/guc_errors_abi.h
> +++ b/drivers/gpu/drm/xe/abi/guc_errors_abi.h
> @@ -8,10 +8,41 @@
>
> enum xe_guc_response_status {
> XE_GUC_RESPONSE_STATUS_SUCCESS = 0x0,
> + XE_GUC_RESPONSE_ERROR_PROTOCOL = 0x04,
> + XE_GUC_RESPONSE_INVALID_STATE = 0x0A,
> + XE_GUC_RESPONSE_UNSUPPORTED_VERSION = 0x0B,
> + XE_GUC_RESPONSE_INVALID_VFID = 0x0C,
> + XE_GUC_RESPONSE_UNPROVISIONED_VF = 0x0D,
> + XE_GUC_RESPONSE_INVALID_EVENT = 0x0E,
> XE_GUC_RESPONSE_NOT_SUPPORTED = 0x20,
> + XE_GUC_RESPONSE_UNKNOWN_ACTION = 0x30,
> + XE_GUC_RESPONSE_ACTION_ABORTED = 0x31,
> + XE_GUC_RESPONSE_NO_PERMISSION = 0x40,
> + XE_GUC_RESPONSE_CANNOT_COMPLETE_ACTION = 0x41,
> + XE_GUC_RESPONSE_INVALID_KLV_DATA = 0x50,
> + XE_GUC_RESPONSE_INVALID_PARAMS = 0x60,
> + XE_GUC_RESPONSE_INVALID_BUFFER_RANGE = 0x70,
> + XE_GUC_RESPONSE_INVALID_BUFFER = 0x71,
> + XE_GUC_RESPONSE_INVALID_GGTT_ADDRESS = 0x80,
> + XE_GUC_RESPONSE_PENDING_ACTION = 0x90,
> + XE_GUC_RESPONSE_INVALID_SIZE = 0x102,
> + XE_GUC_RESPONSE_MALFORMED_KLV = 0x103,
> + XE_GUC_RESPONSE_INVALID_KLV_KEY = 0x105,
> + XE_GUC_RESPONSE_DATA_TOO_LARGE = 0x106,
> + XE_GUC_RESPONSE_VF_MIGRATED = 0x107,
> XE_GUC_RESPONSE_NO_ATTRIBUTE_TABLE = 0x201,
> XE_GUC_RESPONSE_NO_DECRYPTION_KEY = 0x202,
> XE_GUC_RESPONSE_DECRYPTION_FAILED = 0x204,
> + XE_GUC_RESPONSE_VGT_DISABLED = 0x300,
> + XE_GUC_RESPONSE_CTB_FULL = 0x301,
> + XE_GUC_RESPONSE_VGT_UNAUTHORIZED_REQUEST = 0x302,
> + XE_GUC_RESPONSE_CTB_INVALID = 0x303,
> + XE_GUC_RESPONSE_CTB_NOT_REGISTERED = 0x304,
> + XE_GUC_RESPONSE_CTB_IN_USE = 0x305,
> + XE_GUC_RESPONSE_CTB_INVALID_DESC = 0x306,
> + XE_GUC_RESPONSE_CTB_SOURCE_INVALID_DESCRIPTOR = 0x30D,
> + XE_GUC_RESPONSE_CTB_DESTINATION_INVALID_DESCRIPTOR = 0x30E,
> + XE_GUC_RESPONSE_INVALID_CONFIG_STATE = 0x30F,
> XE_GUC_RESPONSE_STATUS_GENERIC_FAIL = 0xF000,
> };
>
> --
> 2.43.0
>
More information about the Intel-xe
mailing list