summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/i915/intel_guc_fw.h
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2018-11-14 23:07:27 +0200
committerVille Syrjälä <ville.syrjala@linux.intel.com>2018-11-28 21:51:51 +0200
commit5f2e511205bbc40b6f58f7d2125c10bd39007748 (patch)
treef8066f09158a01084ad2561b9651aa3ac784da7c /drivers/gpu/drm/i915/intel_guc_fw.h
parentff43bc379e16c9195323cb88ac0c9f4d0613d07a (diff)
drm/i915: Commit skl+ planes in an order that avoids ddb overlaps
skl+ can go belly up if there are overlapping ddb allocations between planes. If we could absolutely guarantee that we can perform the atomic update within a single frame we shouldn't have to worry about this. But we can't rely on that so let's steal the ddb overlap check trick from skl_update_crtcs() and apply it to the plane updates. Since each step of the sequence is free from ddb overlaps we don't have to worry about a vblank sneaking up on us in the middle of the sequence. The partial state that gets latched by the hardware will be safe. And unlike skl_update_crtcs() we don't have to intoduce any extra vblank waits on account of only having to worry about a single pipe. v2: Fix typo in commit msg (Matt) Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20181114210729.16185-12-ville.syrjala@linux.intel.com Reviewed-by: Matt Roper <matthew.d.roper@intel.com> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_guc_fw.h')
0 files changed, 0 insertions, 0 deletions