intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Animesh Manna <animesh.manna@intel.com>, intel-gfx@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, jouni.hogander@intel.com,
	arun.r.murthy@intel.com, ankit.k.nautiyal@intel.com,
	mitulkumar.ajitkumar.golani@intel.com,
	Animesh Manna <animesh.manna@intel.com>
Subject: Re: [PATCH v12 3/3] drm/i915/display: Introduve intel_vrr_possible
Date: Wed, 02 Oct 2024 14:11:18 +0300	[thread overview]
Message-ID: <87frpeu5d5.fsf@intel.com> (raw)
In-Reply-To: <20240927042509.4081753-4-animesh.manna@intel.com>

On Fri, 27 Sep 2024, Animesh Manna <animesh.manna@intel.com> wrote:
> @@ -246,7 +251,8 @@ void intel_vrr_compute_config_late(struct intel_crtc_state *crtc_state)
>  	struct intel_display *display = to_intel_display(crtc_state);
>  	struct drm_display_mode *adjusted_mode = &crtc_state->hw.adjusted_mode;
>  
> -	if (!crtc_state->vrr.flipline)
> +	//if (!crtc_state->vrr.flipline)
> +	if (!intel_vrr_possible(crtc_state))
>  		return;
>  
>  	if (DISPLAY_VER(display) >= 13) {
> @@ -286,7 +292,8 @@ void intel_vrr_set_transcoder_timings(const struct intel_crtc_state *crtc_state)
>  		intel_de_rmw(display, CHICKEN_TRANS(cpu_transcoder),
>  			     0, PIPE_VBLANK_WITH_DELAY);
>  
> -	if (!crtc_state->vrr.flipline) {
> +	//if (!crtc_state->vrr.flipline) {
> +	if (!intel_vrr_possible(crtc_state)) {
>  		intel_de_write(display,
>  			       TRANS_VRR_CTL(display, cpu_transcoder), 0);
>  		return;

What's the point of even sending this? What am I supposed to do with
this? The series is at v12. We should aim at converging to merge at
maybe v3 or v5 or so, at the latest. There are legitimate cases where v1
or v2 are RFC-like, figuring out the direction etc., but the goal for
every single version after that should be that it's the last.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2024-10-02 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  4:25 [PATCH v12 0/3] Vrr refactoring and panel replay workaround Animesh Manna
2024-09-27  4:25 ` [PATCH v12 1/3] drm/i915/vrr: Split vrr-compute-config in two phases Animesh Manna
2024-09-27  4:25 ` [PATCH v12 2/3] drm/i915/panelreplay: Panel replay workaround with VRR Animesh Manna
2024-09-27  4:25 ` [PATCH v12 3/3] drm/i915/display: Introduve intel_vrr_possible Animesh Manna
2024-10-02 11:11   ` Jani Nikula [this message]
2024-09-27 20:55 ` ✗ Fi.CI.SPARSE: warning for Vrr refactoring and panel replay workaround (rev3) Patchwork
2024-09-27 21:06 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-28 20:24 ` ✗ Fi.CI.IGT: 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=87frpeu5d5.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=animesh.manna@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jouni.hogander@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).