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 0/2] Fix vrr.enable handling and add logging for fixed_rr
Date: Mon, 24 Mar 2025 14:00:32 +0530 [thread overview]
Message-ID: <67891807-51ff-4b31-abe3-862dcd5e8f2b@intel.com> (raw)
In-Reply-To: <20250322044345.3827137-1-ankit.k.nautiyal@intel.com>
On 3/22/2025 10:13 AM, Ankit Nautiyal wrote:
> This series is split from the main series [1] for merging the fixes early,
> while other patches of the series are still in review:
>
> The commit:
> a27217f9d1856 ("drm/i915/vrr: Track vrr.enable only for variable timing")
> adds a change in reading the vrr.enable, which is causing issue when GOP
> enables VRR timing generator with fixed timings.
>
> Add the fixed_rr status in crtc_state_dump and remove the check for
> fixed_rr during readout.
>
> [1] Use VRR timing generator for fixed refresh rate modes
> https://patchwork.freedesktop.org/series/134383/
>
> Ankit Nautiyal (2):
> drm/i915/display: Add fixed_rr to crtc_state dump
> drm/i915/vrr: Avoid reading vrr.enable based on fixed_rr check
Thanks for the reviews, patches are pushed to drm-intel-next.
Regards,
Ankit
>
> drivers/gpu/drm/i915/display/intel_crtc_state_dump.c | 3 ++-
> drivers/gpu/drm/i915/display/intel_vrr.c | 4 +---
> drivers/gpu/drm/i915/display/intel_vrr.h | 1 +
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2025-03-24 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 4:43 [RESEND 0/2] Fix vrr.enable handling and add logging for fixed_rr Ankit Nautiyal
2025-03-22 4:43 ` [RESEND 1/2] drm/i915/display: Add fixed_rr to crtc_state dump Ankit Nautiyal
2025-03-22 4:43 ` [RESEND 2/2] drm/i915/vrr: Avoid reading vrr.enable based on fixed_rr check Ankit Nautiyal
2025-03-22 5:00 ` ✓ CI.Patch_applied: success for Fix vrr.enable handling and add logging for fixed_rr (rev2) Patchwork
2025-03-22 5:00 ` ✓ CI.checkpatch: " Patchwork
2025-03-22 5:01 ` ✓ CI.KUnit: " Patchwork
2025-03-22 5:18 ` ✓ CI.Build: " Patchwork
2025-03-22 5:20 ` ✓ CI.Hooks: " Patchwork
2025-03-22 5:22 ` ✓ CI.checksparse: " Patchwork
2025-03-22 5:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-22 6:42 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-24 8:30 ` Nautiyal, Ankit K [this message]
2025-03-25 13:48 ` 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=67891807-51ff-4b31-abe3-862dcd5e8f2b@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