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 12/20] drm/i915/display: Extend WA 14015406119 for PSR2
Date: Thu, 27 Feb 2025 16:06:15 +0530 [thread overview]
Message-ID: <ac0e162a-0b0a-4a8c-b77b-9a272f2c30dd@intel.com> (raw)
In-Reply-To: <Z78dSlvSmDfF6zRD@intel.com>
On 2/26/2025 7:25 PM, Ville Syrjälä wrote:
> On Mon, Feb 24, 2025 at 11:47:09AM +0530, Ankit Nautiyal wrote:
>> Wa_14015406119 is required for PSR1/2 while working with fixed refresh
>> rate with VRR timing generator.
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
>> index 0db84af1063a..752ed44d8892 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>> @@ -2508,8 +2508,9 @@ static bool intel_crtc_needs_wa_14015401596(const struct intel_crtc_state *crtc_
>> {
>> struct intel_display *display = to_intel_display(crtc_state);
>>
>> - return intel_vrr_possible(crtc_state) && crtc_state->has_psr &&
>> - IS_DISPLAY_VER(display, 13, 14);
>> + return intel_vrr_possible(crtc_state) &&
>> + (crtc_state->has_psr || crtc_state->has_sel_update) &&
> I presume you wanted some kind of use_vrr_tg_always() check here instead
> of that has_sel_update thing (which is a nop since it should never be
> set unless has_psr is also set)?
Thanks for pointing this out.
I think I misunderstood the flags. Its clearly documented that `has_psr`
is always set for psr1/2, panel replay.
Also we already have check for vrr_possible which checks flipline, so
this is covered for our case.
I'll drop this patch.
Regards,
Ankit
>
>> + IS_DISPLAY_VER(display, 13, 14);
>> }
>>
>> static int intel_crtc_vblank_delay(const struct intel_crtc_state *crtc_state)
>> --
>> 2.45.2
next prev parent reply other threads:[~2025-02-27 10:36 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 6:16 [PATCH 00/20] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-02-24 6:16 ` [PATCH 01/20] drm/i915/vrr: Remove unwanted comment Ankit Nautiyal
2025-02-26 13:06 ` Ville Syrjälä
2025-02-24 6:16 ` [PATCH 02/20] drm/i915:vrr: Separate out functions to compute vmin and vmax Ankit Nautiyal
2025-02-26 12:59 ` Ville Syrjälä
2025-02-27 10:13 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 03/20] drm/i915/vrr: Make helpers for cmrr and vrr timings Ankit Nautiyal
2025-02-26 13:07 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 04/20] drm/i915/vrr: Disable CMRR Ankit Nautiyal
2025-02-26 13:08 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 05/20] drm/i915/vrr: Track vrr.enable only for variable timing Ankit Nautiyal
2025-02-26 13:10 ` Ville Syrjälä
2025-02-27 10:16 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 06/20] drm/i915/vrr: Use crtc_vtotal for vmin Ankit Nautiyal
2025-02-26 13:11 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 07/20] drm/i915/vrr: Prepare for fixed refresh rate timings Ankit Nautiyal
2025-02-26 13:13 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 08/20] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2025-02-26 13:27 ` Ville Syrjälä
2025-02-27 10:19 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 09/20] drm/i915/hdmi: Use VRR Timing generator for HDMI Ankit Nautiyal
2025-02-26 13:30 ` Ville Syrjälä
2025-02-27 10:31 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 10/20] drm/i915/dp_mst: Use VRR Timing generator for DP MST Ankit Nautiyal
2025-02-26 13:30 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 11/20] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-02-26 13:45 ` Ville Syrjälä
2025-02-27 10:33 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 12/20] drm/i915/display: Extend WA 14015406119 for PSR2 Ankit Nautiyal
2025-02-26 13:55 ` Ville Syrjälä
2025-02-27 10:36 ` Nautiyal, Ankit K [this message]
2025-02-24 6:17 ` [PATCH 13/20] drm/i915/vrr: Handle joiner with vrr Ankit Nautiyal
2025-02-24 13:47 ` Nautiyal, Ankit K
2025-02-26 15:14 ` Ville Syrjälä
2025-02-27 10:37 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 14/20] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-02-26 14:01 ` Ville Syrjälä
2025-02-27 10:39 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 15/20] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-02-26 14:01 ` Ville Syrjälä
2025-02-24 6:17 ` [PATCH 16/20] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-02-26 15:00 ` Ville Syrjälä
2025-02-27 10:28 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 17/20] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-02-26 15:06 ` Ville Syrjälä
2025-02-26 16:04 ` Ville Syrjälä
2025-02-27 10:44 ` Nautiyal, Ankit K
2025-02-27 10:42 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 18/20] drm/i915/vrr: Use fixed timings for platforms that support VRR Ankit Nautiyal
2025-02-26 15:11 ` Ville Syrjälä
2025-02-27 11:01 ` Nautiyal, Ankit K
2025-02-27 21:05 ` Ville Syrjälä
2025-02-28 12:31 ` Nautiyal, Ankit K
2025-02-24 6:17 ` [PATCH 19/20] drm/i915/vrr: Always use VRR timing generator for MTL+ Ankit Nautiyal
2025-02-24 6:17 ` [PATCH 20/20] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-02-24 17:59 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev5) Patchwork
2025-02-24 17:59 ` ✓ CI.checkpatch: " Patchwork
2025-02-24 18:00 ` ✓ CI.KUnit: " Patchwork
2025-02-24 18:17 ` ✓ CI.Build: " Patchwork
2025-02-24 18:19 ` ✓ CI.Hooks: " Patchwork
2025-02-24 18:21 ` ✗ CI.checksparse: warning " Patchwork
2025-02-24 18:39 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-24 20:03 ` ✗ Xe.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=ac0e162a-0b0a-4a8c-b77b-9a272f2c30dd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox