All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
	"Golani,
	Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com>
Subject: Re: [PATCH 06/16] drm/i915/display: Move intel_psr_post_plane_update() at the later
Date: Mon, 24 Mar 2025 06:37:31 +0000	[thread overview]
Message-ID: <b8ebb22ee29b6052bb915f72e5e26faafb233afa.camel@intel.com> (raw)
In-Reply-To: <Z92lNhLy9r1PvJvB@intel.com>

On Fri, 2025-03-21 at 19:43 +0200, Ville Syrjälä wrote:
> On Tue, Mar 18, 2025 at 01:05:30PM +0530, Ankit Nautiyal wrote:
> > In intel_post_plane_update() there are things which might need to
> > do
> > vblank waits, so enabling PSR as early as we do now is simply
> > counter-productive. Therefore move intel_psr_post_plane_update() at
> > the
> > last of intel_post_plane_update().
> > 
> > Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c
> > b/drivers/gpu/drm/i915/display/intel_display.c
> > index 246da49af00b..4a0083fdfb05 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -1048,8 +1048,6 @@ static void intel_post_plane_update(struct
> > intel_atomic_state *state,
> >  		intel_atomic_get_new_crtc_state(state, crtc);
> >  	enum pipe pipe = crtc->pipe;
> >  
> > -	intel_psr_post_plane_update(state, crtc);
> > -
> >  	intel_frontbuffer_flip(dev_priv, new_crtc_state->fb_bits);
> >  
> >  	if (new_crtc_state->update_wm_post && new_crtc_state-
> > >hw.active)
> > @@ -1078,6 +1076,8 @@ static void intel_post_plane_update(struct
> > intel_atomic_state *state,
> >  
> >  	if (audio_enabling(old_crtc_state, new_crtc_state))
> >  		intel_encoders_audio_enable(state, crtc);
> > +
> > +	intel_psr_post_plane_update(state, crtc);
> 
> Jouni, do you recall any specific reason for the current order?

I can't recall any specific reason. Also went through the sequence. I
think this change should be fine.

BR,

Jouni Högander

> 
> >  }
> >  
> >  static void intel_post_plane_update_after_readout(struct
> > intel_atomic_state *state,
> > -- 
> > 2.45.2
> 


  reply	other threads:[~2025-03-24  6:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  7:35 [PATCH 00/16] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 01/16] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 02/16] drm/i915/vrr: Avoid reading vrr.enable based on fixed_rr check Ankit Nautiyal
2025-03-21 17:34   ` Ville Syrjälä
2025-03-21 17:40     ` Nautiyal, Ankit K
2025-03-21 17:45       ` Ville Syrjälä
2025-03-18  7:35 ` [PATCH 03/16] drm/i915/hdmi: Use VRR Timing generator for HDMI for fixed_rr Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 04/16] drm/i915/dp_mst: Use VRR Timing generator for DP MST " Ankit Nautiyal
2025-03-21 17:42   ` Ville Syrjälä
2025-03-18  7:35 ` [PATCH 05/16] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 06/16] drm/i915/display: Move intel_psr_post_plane_update() at the later Ankit Nautiyal
2025-03-21 17:43   ` Ville Syrjälä
2025-03-24  6:37     ` Hogander, Jouni [this message]
2025-03-18  7:35 ` [PATCH 07/16] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 08/16] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 09/16] drm/i915/vrr: Set vrr.enable for VRR TG with fixed_rr Ankit Nautiyal
2025-03-21 17:44   ` Ville Syrjälä
2025-03-18  7:35 ` [PATCH 10/16] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-03-19 14:36   ` Ville Syrjälä
2025-03-20  5:39     ` Nautiyal, Ankit K
2025-03-24 12:10       ` Nautiyal, Ankit K
2025-03-20  4:20   ` Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 11/16] drm/i915/vrr: Use fixed timings for platforms that support VRR Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 12/16] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 13/16] drm/i915/display: Move vrr.guardband/pipeline_full out of !fastset block Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 14/16] drm/i915/vrr: Allow fixed_rr with pipe joiner Ankit Nautiyal
2025-03-18  7:35 ` [PATCH 15/16] drm/i915/vrr: Always use VRR timing generator for PTL+ Ankit Nautiyal
2025-03-21 17:47   ` Ville Syrjälä
2025-03-18  7:35 ` [PATCH 16/16] drm/i915/vrr: Set trans_vrr_ctl in intel_vrr_set_transcoder_timings() Ankit Nautiyal
2025-03-18  7:57 ` ✗ CI.Patch_applied: failure for Use VRR timing generator for fixed refresh rate modes (rev9) Patchwork
2025-03-18  8:16 ` ✗ Fi.CI.SPARSE: warning for Use VRR timing generator for fixed refresh rate modes (rev14) Patchwork
2025-03-18  8:37 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-20  5:37 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev10) Patchwork
2025-03-20  5:37 ` ✓ CI.checkpatch: " Patchwork
2025-03-20  5:38 ` ✓ CI.KUnit: " Patchwork
2025-03-20  5:55 ` ✓ CI.Build: " Patchwork
2025-03-20  5:57 ` ✓ CI.Hooks: " Patchwork
2025-03-20  5:58 ` ✗ CI.checksparse: warning " Patchwork
2025-03-20  6:18 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-20  7:17 ` ✓ Xe.CI.Full: " Patchwork
2025-03-21  6:05 ` ✗ Fi.CI.SPARSE: warning for Use VRR timing generator for fixed refresh rate modes (rev16) Patchwork
2025-03-21  6:26 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-21  8:17 ` ✗ i915.CI.Full: failure " Patchwork

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=b8ebb22ee29b6052bb915f72e5e26faafb233afa.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=mitulkumar.ajitkumar.golani@intel.com \
    --cc=ville.syrjala@linux.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.