Michal Wajdeczko 1d087cb7d8 drm/xe/guc: Fix handling of GUC_HXG_TYPE_NO_RESPONSE_BUSY
If GuC responds with the NO_RESPONSE_BUSY message, we extend
our timeout while waiting for the actual response, but we wrongly
assumed that the next message will be RESPONSE_SUCCESS, missing
that we still can get RESPONSE_FAILURE.

Change the condition for the expected message type, using only
common bits from RESPONSE_SUCCESS and RESPONSE_FAILURE (as they
differ, by ABI design, only by the last bit).

v2: add comment/checks to the code (Matt)

Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2023-12-21 11:44:38 -05:00
..
2023-12-08 16:27:00 +10:00
2023-11-27 13:56:32 -06:00
2023-11-27 13:56:32 -06:00
2023-11-27 13:56:32 -06:00
2023-11-15 10:56:44 +01:00
2023-11-03 15:44:25 -10:00
2023-12-08 16:27:00 +10:00
2023-11-28 15:32:24 +01:00
2023-11-27 13:56:32 -06:00
2023-12-04 09:42:32 +01:00
2023-12-08 16:27:00 +10:00
2023-11-28 11:55:56 +01:00