From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915/vrr: Stop writing VRR_CTL_IGN_MAX_SHIFT for MTL onwards
Date: Mon, 14 Apr 2025 05:45:23 +0000 [thread overview]
Message-ID: <d07d03c0272fa309dd34ac60aac2d7d268a30524.camel@intel.com> (raw)
In-Reply-To: <08dfcf42-b58a-48b1-a602-de2a6f783d18@intel.com>
On Wed, 2025-04-09 at 13:30 +0530, Nautiyal, Ankit K wrote:
>
> 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>
This is now pushed to drm-intel-next. Thank you for checking my patch.
BR,
Jouni Högander
>
>
> > 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-14 5:45 UTC|newest]
Thread overview: 8+ 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 6:53 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-04-09 7:42 ` Saarinen, Jani
2025-04-09 8:00 ` [PATCH v2] " Nautiyal, Ankit K
2025-04-09 9:07 ` Hogander, Jouni
2025-04-14 5:45 ` Hogander, Jouni [this message]
2025-04-09 9:50 ` ✓ i915.CI.BAT: success for " Patchwork
2025-04-09 21:44 ` ✓ i915.CI.Full: " 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=d07d03c0272fa309dd34ac60aac2d7d268a30524.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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