On 9/28/2017 5:10 PM, Chris Wilson wrote:
Quoting Sagar Arun Kamble (2017-09-27 10:30:32)
@@ -4607,13 +4611,14 @@ int i915_gem_resume(struct drm_i915_private *dev_priv)
mutex_lock(>struct_mutex);
i915_gem_restore_gtt_mappings(dev_priv);
+
Quoting Sagar Arun Kamble (2017-09-27 10:30:32)
> @@ -4607,13 +4611,14 @@ int i915_gem_resume(struct drm_i915_private *dev_priv)
>
> mutex_lock(>struct_mutex);
> i915_gem_restore_gtt_mappings(dev_priv);
> + i915_gem_restore_fences(dev_priv);
Seconded Michal's suggestion,
On 9/27/2017 9:17 PM, Michal Wajdeczko wrote:
On Wed, 27 Sep 2017 11:30:32 +0200, Sagar Arun Kamble
wrote:
This patch moves GuC suspend/resume handlers to corresponding GEM
handlers
and orders them properly in the runtime and system suspend/resume flows.
On Wed, 27 Sep 2017 11:30:32 +0200, Sagar Arun Kamble
wrote:
This patch moves GuC suspend/resume handlers to corresponding GEM
handlers
and orders them properly in the runtime and system suspend/resume flows.
i915_gem_restore_fences is GEM resumption task hence it
This patch moves GuC suspend/resume handlers to corresponding GEM handlers
and orders them properly in the runtime and system suspend/resume flows.
i915_gem_restore_fences is GEM resumption task hence it is moved to
i915_gem_resume from i915_restore_state.
v2: Removed documentation of