Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
	<ville.syrjala@linux.intel.com>,
	<mitulkumar.ajitkumar.golani@intel.com>
Subject: Re: [RESEND PATCH 0/8] VRR Refactor
Date: Thu, 13 Mar 2025 19:01:19 +0530	[thread overview]
Message-ID: <19fe5ae0-5873-43a9-9a3d-b13adc8eb708@intel.com> (raw)
In-Reply-To: <20250311093751.1329043-1-ankit.k.nautiyal@intel.com>


On 3/11/2025 3:07 PM, Ankit Nautiyal wrote:
> To move away from legacy timing generator and always use VRR timing
> generator, some refactoring is required in existing VRR code.
>
> This series is a spinoff from the original series [1], tackling only VRR
> refactoring patches from the main series.
>
> [1] https://patchwork.freedesktop.org/series/141152/


Thanks for the reviews, merged to drm-intel-next.

Regards,

Ankit

>
> Ankit Nautiyal (8):
>    drm/i915/vrr: Remove unwanted comment
>    drm/i915:vrr: Separate out functions to compute vmin and vmax
>    drm/i915/vrr: Make helpers for cmrr and vrr timings
>    drm/i915/vrr: Disable CMRR
>    drm/i915/vrr: Track vrr.enable only for variable timing
>    drm/i915/vrr: Use crtc_vtotal for vmin
>    drm/i915/vrr: Prepare for fixed refresh rate timings
>    drm/i915/display: Enable MSA Ignore Timing PAR only when in not
>      fixed_rr mode
>
>   .../drm/i915/display/intel_dp_link_training.c |  15 +-
>   drivers/gpu/drm/i915/display/intel_vrr.c      | 185 ++++++++++++++----
>   2 files changed, 166 insertions(+), 34 deletions(-)
>

      parent reply	other threads:[~2025-03-13 13:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  9:37 [RESEND PATCH 0/8] VRR Refactor Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 1/8] drm/i915/vrr: Remove unwanted comment Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 2/8] drm/i915:vrr: Separate out functions to compute vmin and vmax Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 3/8] drm/i915/vrr: Make helpers for cmrr and vrr timings Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 4/8] drm/i915/vrr: Disable CMRR Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 5/8] drm/i915/vrr: Track vrr.enable only for variable timing Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 6/8] drm/i915/vrr: Use crtc_vtotal for vmin Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 7/8] drm/i915/vrr: Prepare for fixed refresh rate timings Ankit Nautiyal
2025-03-11  9:37 ` [RESEND PATCH 8/8] drm/i915/display: Enable MSA Ignore Timing PAR only when in not fixed_rr mode Ankit Nautiyal
2025-03-11  9:57 ` ✓ CI.Patch_applied: success for VRR Refactor Patchwork
2025-03-11  9:58 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 10:00 ` ✓ CI.KUnit: " Patchwork
2025-03-11 10:19 ` ✓ CI.Build: " Patchwork
2025-03-11 10:21 ` ✓ CI.Hooks: " Patchwork
2025-03-11 10:22 ` ✓ CI.checksparse: " Patchwork
2025-03-11 10:44 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12  3:44 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-13 13:31 ` Nautiyal, Ankit K [this message]

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=19fe5ae0-5873-43a9-9a3d-b13adc8eb708@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