All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
	<mitulkumar.ajitkumar.golani@intel.com>
Subject: Re: [PATCH 02/16] drm/i915/vrr: Avoid reading vrr.enable based on fixed_rr check
Date: Fri, 21 Mar 2025 23:10:05 +0530	[thread overview]
Message-ID: <f87ce829-e83f-4e5e-b9ae-bcb63cbf2fcf@intel.com> (raw)
In-Reply-To: <Z92jIvuSzV257-VZ@intel.com>


On 3/21/2025 11:04 PM, Ville Syrjälä wrote:
> On Tue, Mar 18, 2025 at 01:05:26PM +0530, Ankit Nautiyal wrote:
>> Currently, vrr.enable is intended only for variable refresh rate timings.
>> At this point, we do not set fixed refresh rate timings, but the GOP can,
>> which creates a problem during the readback of vrr.enable.
>>
>> The GOP enables the VRR timing generator with fixed timings, while the
>> driver only recognizes the VRR timing generator as enabled with
>> variable timings. This discrepancy causes an issue due to the
>> fixed refresh rate check during readback. Since the VRR timing generator
>> is enabled and we do not support fixed timings, the readback should set
>> vrr.enable so that the driver can disable the VRR timing generator.
>> However, the current check does not allow this.
>>
>> Therefore, remove the fixed refresh rate check during readback.
>>
>> Fixes: 27217f9d1856 ("drm/i915/vrr: Track vrr.enable only for variable timing")
>> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_vrr.c | 3 +--
>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index aa65a6933ddb..6bdcdfed4b9b 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -657,8 +657,7 @@ void intel_vrr_get_config(struct intel_crtc_state *crtc_state)
>>   		}
>>   	}
>>   
>> -	crtc_state->vrr.enable = trans_vrr_ctl & VRR_CTL_VRR_ENABLE &&
>> -				 !intel_vrr_is_fixed_rr(crtc_state);
>> +	crtc_state->vrr.enable = trans_vrr_ctl & VRR_CTL_VRR_ENABLE;
> Doesn't this break the state checker when we use the VRR timing
> generator for fixed refresh modes?

Yes right, but currently those changes are not merged yet.

I have something like this [1], when we add support for VRR TG with 
fixed refresh rate.

[1] https://patchwork.freedesktop.org/patch/643470/?series=134383&rev=16


Regards,

Ankit


>
>>   
>>   	/*
>>   	 * #TODO: For Both VRR and CMRR the flag I915_MODE_FLAG_VRR is set for mode_flags.
>> -- 
>> 2.45.2

  reply	other threads:[~2025-03-21 17:40 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 [this message]
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
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=f87ce829-e83f-4e5e-b9ae-bcb63cbf2fcf@intel.com \
    --to=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.