Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Govindapillai, Vinod" <vinod.govindapillai@intel.com>
Cc: "Lankhorst, Maarten" <maarten.lankhorst@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Syrjala, Ville" <ville.syrjala@intel.com>
Subject: Re: [PATCH v1] drm/xe: avoid the async_flip update in the initial plane config
Date: Fri, 14 Jun 2024 08:41:29 +0000	[thread overview]
Message-ID: <7900bcab17ca0d66f6e2cb99cb0676ccdf5ed719.camel@intel.com> (raw)
In-Reply-To: <ac0608c9ca5ed21a4f4f119f747f61f9130ad1ac.camel@intel.com>

On Fri, 2024-06-14 at 08:23 +0000, Govindapillai, Vinod wrote:
> On Fri, 2024-06-14 at 07:11 +0000, Hogander, Jouni wrote:
> > On Fri, 2024-04-19 at 17:09 +0300, Vinod Govindapillai wrote:
> > > Async flip call is not needed. The updated fb mapping is updated
> > > as part of the fixup_initial_plane_config() call. Otherwise we
> > > end up updating the PLAN_SURF register twice with the same info.
> > 
> > async_flip is writing PLANE_CTL as well. Is it ok to leave that
> > out?
> 
> Thanks for the review Jouni!
> 
> Yes.. that is not needed for the initial plane config. The i915
> counterpart don't have this either!
> I had confirmed this with Maarten and Ville. According to Maarten,
> most likely this part was copied
> from i915 which got dropped when refactoring.

Reviewed-by: Jouni Högander <jouni.hogander@intel.com>

> 
> BR
> Vinod
> 
> > 
> > BR,
> > 
> > Jouni Högander
> > 
> > > 
> > > v2: avoid async_flip instead of removing fixup call (Ville)
> > > 
> > > Signed-off-by: Vinod Govindapillai
> > > <vinod.govindapillai@intel.com>
> > > ---
> > >  drivers/gpu/drm/xe/display/xe_plane_initial.c | 10 ----------
> > >  1 file changed, 10 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > b/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > index 9693c56d386b..b5f8381b593d 100644
> > > --- a/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > +++ b/drivers/gpu/drm/xe/display/xe_plane_initial.c
> > > @@ -189,8 +189,6 @@ intel_find_initial_plane_obj(struct
> > > intel_crtc
> > > *crtc,
> > >                 to_intel_plane(crtc->base.primary);
> > >         struct intel_plane_state *plane_state =
> > >                 to_intel_plane_state(plane->base.state);
> > > -       struct intel_crtc_state *crtc_state =
> > > -               to_intel_crtc_state(crtc->base.state);
> > >         struct drm_framebuffer *fb;
> > >         struct i915_vma *vma;
> > >  
> > > @@ -236,14 +234,6 @@ intel_find_initial_plane_obj(struct
> > > intel_crtc
> > > *crtc,
> > >         atomic_or(plane->frontbuffer_bit,
> > > &to_intel_frontbuffer(fb)-
> > > > bits);
> > >  
> > >         plane_config->vma = vma;
> > > -
> > > -       /*
> > > -        * Flip to the newly created mapping ASAP, so we can re-
> > > use
> > > the
> > > -        * first part of GGTT for WOPCM, prevent flickering, and
> > > prevent
> > > -        * the lookup of sysmem scratch pages.
> > > -        */
> > > -       plane->check_plane(crtc_state, plane_state);
> > > -       plane->async_flip(plane, crtc_state, plane_state, true);
> > >         return;
> > >  
> > >  nofb:
> > 
> 


      reply	other threads:[~2024-06-14  8:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 14:09 [PATCH v1] drm/xe: avoid the async_flip update in the initial plane config Vinod Govindapillai
2024-04-19 17:56 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-19 17:57 ` ✓ CI.checkpatch: " Patchwork
2024-04-19 17:57 ` ✓ CI.KUnit: " Patchwork
2024-04-19 18:09 ` ✓ CI.Build: " Patchwork
2024-04-19 18:16 ` ✓ CI.Hooks: " Patchwork
2024-04-19 18:23 ` ✓ CI.checksparse: " Patchwork
2024-04-19 19:30 ` ✗ CI.BAT: failure " Patchwork
2024-04-21 10:57 ` ✗ CI.FULL: " Patchwork
2024-04-23 12:07 ` ✓ CI.Patch_applied: success for drm/xe: avoid the async_flip update in the initial plane config (rev2) Patchwork
2024-04-23 12:07 ` ✓ CI.checkpatch: " Patchwork
2024-04-23 12:08 ` ✓ CI.KUnit: " Patchwork
2024-04-23 12:26 ` ✓ CI.Build: " Patchwork
2024-04-23 12:29 ` ✓ CI.Hooks: " Patchwork
2024-04-23 12:31 ` ✓ CI.checksparse: " Patchwork
2024-04-23 12:54 ` ✓ CI.BAT: " Patchwork
2024-04-23 19:15 ` ✓ CI.FULL: " Patchwork
2024-06-14  7:11 ` [PATCH v1] drm/xe: avoid the async_flip update in the initial plane config Hogander, Jouni
2024-06-14  8:23   ` Govindapillai, Vinod
2024-06-14  8:41     ` Hogander, Jouni [this message]

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=7900bcab17ca0d66f6e2cb99cb0676ccdf5ed719.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=ville.syrjala@intel.com \
    --cc=vinod.govindapillai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox