diff options
| author |   Michel Thierry <michel.thierry@intel.com> | 2017-08-18 10:23:42 -0700 |
|---|---|---|
| committer |   Chris Wilson <chris@chris-wilson.co.uk> | 2017-08-22 12:27:18 +0100 |
| commit | 41e61020e821487489526e50b8e2e223342b7b93 (patch) | |
| tree | b096c6a0e27a68c869053d7e1378a55d45a5d956 /drivers/gpu/drm/i915/i915_pci.c | |
| parent | drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp (diff) | |
| download | linux-dev-41e61020e821487489526e50b8e2e223342b7b93.tar.xz linux-dev-41e61020e821487489526e50b8e2e223342b7b93.zip | |
drm/i915: Re-enable per-engine reset for Broxton
The corruption in CSB mmio reads we were seeing has been tracked down to
incorrectly touching forcewake of all domains, following an engine reset.
It is still a mistery why we only catched this in Broxton, since it
could happen in any platform.
With that fix already merged, commit 4055dc75d6b5 ("drm/i915: Stop
touching forcewake following a gen6+ engine reset"), lets try to enable
per-engine resets in Broxton one more time.
This reverts commit f188258bde0f ("drm/i915: Disable per-engine reset for
Broxton").
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Michel Thierry <michel.thierry@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20170818172342.7282-1-michel.thierry@intel.com
Tested-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to '')
| -rw-r--r-- | drivers/gpu/drm/i915/i915_pci.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c index 09d97e0990b7..a1e6b696bcfa 100644 --- a/drivers/gpu/drm/i915/i915_pci.c +++ b/drivers/gpu/drm/i915/i915_pci.c @@ -398,7 +398,6 @@ static const struct intel_device_info intel_broxton_info = { GEN9_LP_FEATURES, .platform = INTEL_BROXTON, .ddb_size = 512, - .has_reset_engine = false, }; static const struct intel_device_info intel_geminilake_info = { |