On Tue, Feb 20, 2018 at 01:42:07PM +0000, Chris Wilson wrote: > Use the information about the fence state from the time of pinning to > determine if the fbdev writes are going through a fence. This avoids any > confusion in cases where the fence may appear or disappear unconnected > to the use by fbdev. > > Suggested-by: Ville Syrjälä <[email protected]> > Signed-off-by: Chris Wilson <[email protected]> > Cc: Ville Syrjälä <[email protected]>
Reviewed-by: Ville Syrjälä <[email protected]> > --- > drivers/gpu/drm/i915/intel_fbdev.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/intel_fbdev.c > b/drivers/gpu/drm/i915/intel_fbdev.c > index 3d8ce3a62743..055f409f8b75 100644 > --- a/drivers/gpu/drm/i915/intel_fbdev.c > +++ b/drivers/gpu/drm/i915/intel_fbdev.c > @@ -48,7 +48,8 @@ > static void intel_fbdev_invalidate(struct intel_fbdev *ifbdev) > { > struct drm_i915_gem_object *obj = ifbdev->fb->obj; > - unsigned int origin = ifbdev->vma->fence ? ORIGIN_GTT : ORIGIN_CPU; > + unsigned int origin = > + ifbdev->vma_flags & PLANE_HAS_FENCE ? ORIGIN_GTT : ORIGIN_CPU; > > intel_fb_obj_invalidate(obj, origin); > } > -- > 2.16.1 -- Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
