[PATCH 0/7] Fixes and worarounds for GuC issues

[Dave Gordon <david.s.gordon@intel.com>]

Several issues have been found around the general area of resetting
and reloading the GuC.  These include the failure of the DMA engine
to capture header data and/or flag the result of the data hashing
operation performed during transfer. Another area of concern relates to
the hibernate-and-resume cycle, where the firmware reload may fail or
the doorbell hardware may be left in an inconsistant state.

This set of patches provides solutions (or in some cases workarounds)
for the various issues identified in this area.

Arun Siluvery (1):
  drm/i915/guc: Reset GuC and retry on firmware load failure

Dave Gordon (6):
  drm/i915/guc: always reset GuC before loading firmware
  drm/i915/guc: add doorbell map to debugfs/i915_guc_info
  drm/i915/guc: move guc_ring_doorbell() nearer to callsite
  drm/i915/guc: refactor doorbell management code
  drm/i915/guc: (re)initialise doorbell h/w when enabling GuC submission
  drm/i915/guc: disable GuC submission earlier during GuC (re)load

 drivers/gpu/drm/i915/i915_debugfs.c        |   7 +
 drivers/gpu/drm/i915/i915_drv.h            |   1 +
 drivers/gpu/drm/i915/i915_guc_reg.h        |  11 +-
 drivers/gpu/drm/i915/i915_guc_submission.c | 264 ++++++++++++++++++-----------
 drivers/gpu/drm/i915/i915_reg.h            |   1 +
 drivers/gpu/drm/i915/intel_guc_loader.c    |  54 +++++-
 drivers/gpu/drm/i915/intel_uncore.c        |  19 +++
 7 files changed, 252 insertions(+), 105 deletions(-)

Cc: Alex Dai <yu.dai@intel.com>
Cc: Arun Siluvery <arun.siluvery@linux.intel.com>

-- 
1.9.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx