All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915: Do vrr push before sampling the freame counter
Date: Mon, 8 Nov 2021 19:36:41 +0000	[thread overview]
Message-ID: <23cfa70e122b46dc800eaee07345da99@intel.com> (raw)
In-Reply-To: <20211020223339.669-3-ville.syrjala@linux.intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ville Syrjala
> Sent: Thursday, October 21, 2021 4:04 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: Navare, Manasi D <manasi.d.navare@intel.com>
> Subject: [Intel-gfx] [PATCH 2/4] drm/i915: Do vrr push before sampling the freame
> counter

Nit: typo in frame

> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Do the vrr push before we sample the frame counter to know when the commit has
> been latched. Doing these in the wrong order could lead us to complete the flip
> before it has actually happened.
> 
> Cc: Manasi Navare <manasi.d.navare@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_crtc.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c
> b/drivers/gpu/drm/i915/display/intel_crtc.c
> index 254e67141a77..0f8b48b6911c 100644
> --- a/drivers/gpu/drm/i915/display/intel_crtc.c
> +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
> @@ -542,6 +542,9 @@ void intel_pipe_update_end(struct intel_crtc_state
> *new_crtc_state)
> 
>  	trace_intel_pipe_update_end(crtc, end_vbl_count, scanline_end);
> 
> +	/* Send VRR Push to terminate Vblank */
> +	intel_vrr_send_push(new_crtc_state);
> +

This looks right to me.  We are at risk of arming vblank before the push,
i.e. actual vblank termination.

With the typo fixed:
Reviewed-by: Uma Shankar <uma.shankar@intel.com>

>  	/*
>  	 * Incase of mipi dsi command mode, we need to set frame update
>  	 * request for every commit.
> @@ -568,9 +571,6 @@ void intel_pipe_update_end(struct intel_crtc_state
> *new_crtc_state)
> 
>  	local_irq_enable();
> 
> -	/* Send VRR Push to terminate Vblank */
> -	intel_vrr_send_push(new_crtc_state);
> -
>  	if (intel_vgpu_active(dev_priv))
>  		return;
> 
> --
> 2.32.0


  reply	other threads:[~2021-11-08 19:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 22:33 [Intel-gfx] [PATCH 0/4] drm/i915: (near)atomic gamma LUT updates via vblank workers Ville Syrjala
2021-10-20 22:33 ` [Intel-gfx] [PATCH 1/4] drm/i915: Move function prototypes to the correct header Ville Syrjala
2021-10-21 10:26   ` Jani Nikula
2021-10-20 22:33 ` [Intel-gfx] [PATCH 2/4] drm/i915: Do vrr push before sampling the freame counter Ville Syrjala
2021-11-08 19:36   ` Shankar, Uma [this message]
2021-10-20 22:33 ` [Intel-gfx] [PATCH 3/4] drm/i915: Use vblank workers for gamma updates Ville Syrjala
2021-10-21 10:35   ` Jani Nikula
2021-10-21 10:42     ` Ville Syrjälä
2021-10-21 12:51       ` Jani Nikula
2021-11-08 20:41   ` Shankar, Uma
2021-10-20 22:33 ` [Intel-gfx] [PATCH 4/4] drm/i915: Use unlocked register accesses for LUT loads Ville Syrjala
2021-11-08 20:59   ` Shankar, Uma
2021-11-09 22:56     ` Ville Syrjälä
2021-10-21  0:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: (near)atomic gamma LUT updates via vblank workers Patchwork
2021-10-21  1:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-10-21  1:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-21  7:11 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-10-26 22:02 ` [Intel-gfx] [PATCH 0/4] " Lyude Paul

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=23cfa70e122b46dc800eaee07345da99@intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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.