diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2018-02-20 13:42:08 +0000 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2018-02-20 19:03:59 +0000 |
commit | 1c9b6b133e658f9efde8706124f185fde3f273bb (patch) | |
tree | 1b7bb0031e1a2f044ed430bf4d11c1e42543adfc /drivers/gpu/drm/i915/intel_engine_cs.c | |
parent | e3c017f15f7ee4c088697d41ee4260986c42a885 (diff) | |
download | linux-1c9b6b133e658f9efde8706124f185fde3f273bb.tar.gz linux-1c9b6b133e658f9efde8706124f185fde3f273bb.tar.bz2 linux-1c9b6b133e658f9efde8706124f185fde3f273bb.zip |
drm/i915/fbc: Use PLANE_HAS_FENCE to determine if the plane is fenced
Rather than trusting the cached value of plane_state->vma->fence to
imply whether the plane_state itself holds a reference on the
framebuffer's fence, use the information provided in the
plane_state->flags (PLANE_HAS_FENCE). Note that we still assume that FBC
is entirely bounded by the plane_state active life span; it's not clear
if that is a safe assumption.
Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180220134208.24988-4-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/intel_engine_cs.c')
0 files changed, 0 insertions, 0 deletions