From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/vrr: Stop writing VRR_CTL_IGN_MAX_SHIFT for MTL onwards
Date: Wed, 9 Apr 2025 13:30:55 +0530 [thread overview]
Message-ID: <08dfcf42-b58a-48b1-a602-de2a6f783d18@intel.com> (raw)
In-Reply-To: <20250409054909.968531-1-jouni.hogander@intel.com>
On 4/9/2025 11:19 AM, Jouni Högander wrote:
> According to Bspec VRR_CTL_IGN_MAX_SHIFT doesn't exist for MTL and
> onwards. On LunarLake and onwards Bit 30 is "Mask Block PkgC" instead. Stop
> writing the bit for MeteorLake and onwards
>
> v2: "Ignore Max Shift" bit doesn't exist on MeteorLake either
>
> Bspec: 68925
Perhaps you can add 50508 or 71956 for MTL.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vrr.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
> index 633a66f6b73b..c6565baf815a 100644
> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
> @@ -444,7 +444,10 @@ static u32 trans_vrr_ctl(const struct intel_crtc_state *crtc_state)
> {
> struct intel_display *display = to_intel_display(crtc_state);
>
> - if (DISPLAY_VER(display) >= 13)
> + if (DISPLAY_VER(display) >= 14)
> + return VRR_CTL_FLIP_LINE_EN |
> + XELPD_VRR_CTL_VRR_GUARDBAND(crtc_state->vrr.guardband);
> + else if (DISPLAY_VER(display) >= 13)
> return VRR_CTL_IGN_MAX_SHIFT | VRR_CTL_FLIP_LINE_EN |
> XELPD_VRR_CTL_VRR_GUARDBAND(crtc_state->vrr.guardband);
> else
next prev parent reply other threads:[~2025-04-09 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 5:49 [PATCH v2] drm/i915/vrr: Stop writing VRR_CTL_IGN_MAX_SHIFT for MTL onwards Jouni Högander
2025-04-09 5:57 ` ✓ CI.Patch_applied: success for " Patchwork
2025-04-09 5:57 ` ✓ CI.checkpatch: " Patchwork
2025-04-09 5:58 ` ✓ CI.KUnit: " Patchwork
2025-04-09 6:15 ` ✓ CI.Build: " Patchwork
2025-04-09 6:17 ` ✓ CI.Hooks: " Patchwork
2025-04-09 6:18 ` ✓ CI.checksparse: " Patchwork
2025-04-09 7:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-09 8:00 ` Nautiyal, Ankit K [this message]
2025-04-09 9:07 ` [PATCH v2] " Hogander, Jouni
2025-04-14 5:45 ` Hogander, Jouni
2025-04-09 8:05 ` ✗ Xe.CI.Full: failure for " Patchwork
2025-04-10 5:29 ` Hogander, Jouni
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=08dfcf42-b58a-48b1-a602-de2a6f783d18@intel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox