From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/3] drm/i915: Fix scanline_offset for LNL+ and BMG+
Date: Thu, 20 Feb 2025 09:30:01 +0000 [thread overview]
Message-ID: <1143dadb36dc3d3572e4e4b2daca73497589db04.camel@intel.com> (raw)
In-Reply-To: <20250207215406.19348-2-ville.syrjala@linux.intel.com>
On Fri, 2025-02-07 at 23:54 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Turns out LNL+ and BMG+ no longer have the weird extra scanline
> offset for HDMI outputs. Fix intel_crtc_scanline_offset()
> accordingly so that scanline evasion/etc. works correctly on
> HDMI outputs on these new platforms.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_vblank.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_vblank.c
> b/drivers/gpu/drm/i915/display/intel_vblank.c
> index 4efd4f7d497a..7b240ce681a0 100644
> --- a/drivers/gpu/drm/i915/display/intel_vblank.c
> +++ b/drivers/gpu/drm/i915/display/intel_vblank.c
> @@ -222,7 +222,9 @@ int intel_crtc_scanline_offset(const struct
> intel_crtc_state *crtc_state)
> * However if queried just before the start of vblank we'll
> get an
> * answer that's slightly in the future.
> */
> - if (DISPLAY_VER(display) == 2)
> + if (DISPLAY_VER(display) >= 20 || display-
> >platform.battlemage)
Based on what Matt Roper wrote in response to cover letter you could
consider changing this to:
if (DISPLAY_VERx100(display) >= 1401)
What do you think?
BR,
Jouni Högander
> + return 1;
> + else if (DISPLAY_VER(display) == 2)
> return -1;
> else if (HAS_DDI(display) && intel_crtc_has_type(crtc_state,
> INTEL_OUTPUT_HDMI))
> return 2;
next prev parent reply other threads:[~2025-02-20 9:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 21:54 [PATCH 0/3] drm/i915: Fix scanline_offset for LNL+/BMG+ Ville Syrjala
2025-02-07 21:54 ` [PATCH 1/3] drm/i915: Fix scanline_offset for LNL+ and BMG+ Ville Syrjala
2025-02-20 9:30 ` Hogander, Jouni [this message]
2025-03-20 11:23 ` Shankar, Uma
2025-02-07 21:54 ` [PATCH 2/3] drm/i915: Reverse the scanline_offset if ladder Ville Syrjala
2025-02-20 10:02 ` Hogander, Jouni
2025-02-07 21:54 ` [PATCH 3/3] drm/i915: Replace the HAS_DDI() in intel_crtc_scanline_offset() with specific platform checks Ville Syrjala
2025-02-20 9:58 ` Hogander, Jouni
2025-02-07 22:41 ` [PATCH 0/3] drm/i915: Fix scanline_offset for LNL+/BMG+ Lucas De Marchi
2025-02-10 16:05 ` Gustavo Sousa
2025-02-10 16:16 ` Ville Syrjälä
2025-02-10 18:10 ` Lucas De Marchi
2025-02-10 20:02 ` Ville Syrjälä
2025-02-10 21:49 ` Matt Roper
2025-02-07 22:54 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2025-02-08 2:44 ` ✓ i915.CI.BAT: success " Patchwork
2025-02-08 17:47 ` ✗ i915.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=1143dadb36dc3d3572e4e4b2daca73497589db04.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--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