From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/3] drm/i915: Fix scanline_offset for LNL+/BMG+
Date: Fri, 7 Feb 2025 23:54:03 +0200 [thread overview]
Message-ID: <20250207215406.19348-1-ville.syrjala@linux.intel.com> (raw)
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Something has changed in the hardware on LNL/BMG because
HDMI outputs no longer have the extra scanline offset.
I confirmed that MTL still has the old behaviour, which
is a bit weird since both MTL and BMG have display ver 14
vs. LNL is version 20. But can't argue with actual
hardware behaviour.
Ville Syrjälä (3):
drm/i915: Fix scanline_offset for LNL+ and BMG+
drm/i915: Reverse the scanline_offset if ladder
drm/i915: Replace the HAS_DDI() in intel_crtc_scanline_offset() with
specific platform checks
drivers/gpu/drm/i915/display/intel_vblank.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
--
2.45.3
next reply other threads:[~2025-02-07 21:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 21:54 Ville Syrjala [this message]
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
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=20250207215406.19348-1-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.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