summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/i915/i915_mm.c
diff options
context:
space:
mode:
authorMatt Roper <matthew.d.roper@intel.com>2020-03-11 19:22:57 +0300
committerMatt Roper <matthew.d.roper@intel.com>2020-03-13 19:01:44 +0300
commitd0ed510a8eb12915aedf1cdc28bd1707fbe6c9c0 (patch)
tree11a1ba60e6d5486da08fa45ba0cef08292cc5c4f /drivers/gpu/drm/i915/i915_mm.c
parentaa64f8e1cf235f2e36615dba57c2c50d06181f84 (diff)
downloadlinux-d0ed510a8eb12915aedf1cdc28bd1707fbe6c9c0.tar.xz
drm/i915: Add Wa_1604278689:icl,ehl
The bspec description for this workaround tells us to program 0xFFFF_FFFF into both FBC_RT_BASE_ADDR_REGISTER_* registers, but we've previously found that this leads to failures in CI. Our suspicion is that the failures are caused by this valid turning on the "address valid bit" even though we're intentionally supplying an invalid address. Experimentation has shown that setting all bits _except_ for the RT_VALID bit seems to avoid these failures. v2: - Mask off the RT_VALID bit. Experimentation with CI trybot indicates that this is necessary to avoid reset failures on BCS. v3: - Program RT_BASE before RT_BASE_UPPER so that the valid bit is turned off by the first write. (Chris) Bspec: 11388 Bspec: 33451 Signed-off-by: Matt Roper <matthew.d.roper@intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20200311162300.1838847-4-matthew.d.roper@intel.com Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
Diffstat (limited to 'drivers/gpu/drm/i915/i915_mm.c')
0 files changed, 0 insertions, 0 deletions