All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	jouni.hogander@intel.com, animesh.manna@intel.com
Subject: Re: [PATCH 3/5] drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG
Date: Fri, 14 Nov 2025 17:10:19 +0200	[thread overview]
Message-ID: <aRdGW0RQ0ECX2A9_@intel.com> (raw)
In-Reply-To: <20251114052746.158751-4-ankit.k.nautiyal@intel.com>

On Fri, Nov 14, 2025 at 10:57:44AM +0530, Ankit Nautiyal wrote:
> As per bspec the LOBF is allowed when running in fixed refresh rate mode
> i.e. when flipline = vmin = vmax. Apparently this means we can allow
> LOBF only when VRR timing generator is running in fixed refresh rate
> mode.

The VRR TG requirement rather comes from the fact that we need
a non-zero window1, and that is only possible when using the
VRR TG.

> 
> Use the check intel_vrr_always_use_vrr_tg() to avoid LOBF with legacy
> timing generator. Also use intel_vrr_is_fixed_rr() to check for fixed
> refresh rate mode.
> 
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_alpm.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_alpm.c b/drivers/gpu/drm/i915/display/intel_alpm.c
> index 686e4d13f864..5cfb9345776a 100644
> --- a/drivers/gpu/drm/i915/display/intel_alpm.c
> +++ b/drivers/gpu/drm/i915/display/intel_alpm.c
> @@ -344,8 +344,8 @@ void intel_alpm_lobf_compute_config(struct intel_dp *intel_dp,
>  	if (crtc_state->has_psr)
>  		return;
>  
> -	if (crtc_state->vrr.vmin != crtc_state->vrr.vmax ||
> -	    crtc_state->vrr.vmin != crtc_state->vrr.flipline)
> +	if (!intel_vrr_always_use_vrr_tg(display) ||
> +	    !intel_vrr_is_fixed_rr(crtc_state))
>  		return;
>  
>  	if (!(intel_alpm_aux_wake_supported(intel_dp) ||
> -- 
> 2.45.2

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2025-11-14 15:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  5:27 [PATCH 0/5] LOBF fixes Ankit Nautiyal
2025-11-14  5:27 ` [PATCH 1/5] drm/i915/alpm: Compute LOBF late after guardband is already determined Ankit Nautiyal
2025-11-14  5:27 ` [PATCH 2/5] drm/i915/alpm: Allow LOBF only if window1 > alpm check_entry lines Ankit Nautiyal
2025-11-14 15:09   ` Ville Syrjälä
2025-11-17  7:34     ` Nautiyal, Ankit K
2025-11-14  5:27 ` [PATCH 3/5] drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG Ankit Nautiyal
2025-11-14 15:10   ` Ville Syrjälä [this message]
2025-11-14  5:27 ` [PATCH 4/5] drm/i915/alpm: Simplify and align LOBF checks in pre/post plane update Ankit Nautiyal
2025-11-14 15:15   ` Ville Syrjälä
2025-11-17  7:36     ` Nautiyal, Ankit K
2025-11-14  5:27 ` [PATCH 5/5] drm/i915/alpm: Disable LOBF around transitioning for LRR/seamless MN Ankit Nautiyal
2025-11-14  5:45 ` ✗ CI.checkpatch: warning for LOBF fixes Patchwork
2025-11-14  5:47 ` ✓ CI.KUnit: success " Patchwork
2025-11-14  6:05 ` ✗ CI.checksparse: warning " Patchwork
2025-11-14  6:29 ` ✓ Xe.CI.BAT: success " Patchwork
2025-11-14  7:40 ` ✓ i915.CI.BAT: " Patchwork
2025-11-14 12:28 ` ✓ Xe.CI.Full: " Patchwork
2025-11-14 23:08 ` ✓ i915.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-11-19 13:51 [PATCH 0/5] " Ankit Nautiyal
2025-11-19 13:51 ` [PATCH 3/5] drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG Ankit Nautiyal
2025-11-20  8:52   ` Michał Grzelak
2025-12-24  8:48 [PATCH 0/5] LOBF fixes Ankit Nautiyal
2025-12-24  8:48 ` [PATCH 3/5] drm/i915/alpm: Allow LOBF only for platform that have Always on VRR TG Ankit Nautiyal

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=aRdGW0RQ0ECX2A9_@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=animesh.manna@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jouni.hogander@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.