All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH] drm/xe/display: Append dma_buf fences to framebuffer fences
Date: Fri, 16 Jun 2023 17:29:05 +0300	[thread overview]
Message-ID: <ZIxxsWUVFvH7_OKr@intel.com> (raw)
In-Reply-To: <DM4PR11MB6360A0F1846E78E51FE0A2D0F45BA@DM4PR11MB6360.namprd11.prod.outlook.com>

On Thu, Jun 15, 2023 at 11:10:55AM +0000, Shankar, Uma wrote:
> 
> 
> > -----Original Message-----
> > From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of José Roberto
> > de Souza
> > Sent: Wednesday, June 7, 2023 1:50 AM
> > To: intel-xe@lists.freedesktop.org
> > Subject: [Intel-xe] [PATCH] drm/xe/display: Append dma_buf fences to framebuffer
> > fences
> > 
> > This is required to comply with KMS page flip requirements, and it is the only way to
> > synchronize framebuffer scanouts in Xe KMD.
> > 
> > UMDs are expected to attach a syncobj that will be signaled at the end of the GPU
> > job that is rendering in the framebuffer.
> > This way, the compositor can send jobs to the GPU to render the framebuffer and
> > without having to wait for it to complete, queue the page flip in KMS.
> > 
> > This fixes display glitches.
> 
> Looks Good to me.
> Reviewed-by: Uma Shankar <uma.shankar@intel.com>
> 
> @Ville: Can you also check this once and confirm.

Needs an actual explanation why the current code doesn't work.

> 
> Regards,
> Uma Shankar
> 
> > Link: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8923
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_atomic_plane.c | 13 ++++++++++++-
> >  1 file changed, 12 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> > b/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> > index b756561f08bd1..a3f30a319e4c0 100644
> > --- a/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> > +++ b/drivers/gpu/drm/i915/display/intel_atomic_plane.c
> > @@ -32,6 +32,7 @@
> >   */
> > 
> >  #include <drm/drm_atomic_helper.h>
> > +#include <drm/drm_gem_atomic_helper.h>
> >  #include <drm/drm_blend.h>
> >  #include <drm/drm_fourcc.h>
> > 
> > @@ -1120,10 +1121,20 @@ intel_prepare_plane_fb(struct drm_plane *_plane,
> > 
> >  	return ret;
> >  #else
> > +	int ret;
> > +
> >  	if (!intel_fb_obj(new_plane_state->hw.fb))
> >  		return 0;
> > 
> > -	return intel_plane_pin_fb(new_plane_state);
> > +	ret = intel_plane_pin_fb(new_plane_state);
> > +	if (ret)
> > +		return ret;
> > +
> > +	ret = drm_gem_plane_helper_prepare_fb(_plane, _new_plane_state);
> > +	if (ret)
> > +		intel_plane_unpin_fb(new_plane_state);
> > +
> > +	return ret;
> >  #endif
> >  }
> > 
> > --
> > 2.41.0
> 

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2023-06-16 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 20:19 [Intel-xe] [PATCH] drm/xe/display: Append dma_buf fences to framebuffer fences José Roberto de Souza
2023-06-06 20:22 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-06-06 20:22 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-06-06 20:24 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-06-06 20:27 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-06-06 20:28 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-06-06 20:29 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-06-06 20:55 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-06-15 11:10 ` [Intel-xe] [PATCH] " Shankar, Uma
2023-06-16 14:29   ` Ville Syrjälä [this message]
2023-06-16 21:49     ` Souza, Jose
2023-06-16 21:34   ` Souza, Jose

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZIxxsWUVFvH7_OKr@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=uma.shankar@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.