From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Matt Roper <matthew.d.roper@intel.com>,
gustavo.sousa@intel.com
Subject: Re: [PATCH 0/3] drm/i915: Fix scanline_offset for LNL+/BMG+
Date: Mon, 10 Feb 2025 18:16:58 +0200 [thread overview]
Message-ID: <Z6omejfSAI1NkOGj@intel.com> (raw)
In-Reply-To: <hwau7ipfc7kfmjtosaxhdiz5cjvc3y3dborr4l36lugrfw2s75@bb4p7hjsb7wa>
On Fri, Feb 07, 2025 at 04:41:11PM -0600, Lucas De Marchi wrote:
> On Fri, Feb 07, 2025 at 11:54:03PM +0200, Ville Syrjälä wrote:
> >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.
>
> <6>[ 210.368608] xe 0000:03:00.0: [drm] Found battlemage (device ID e20b) discrete display version 14.01 stepping B0
> vs
> <6>[ 412.999204] i915 0000:00:02.0: [drm] Found meteorlake (device ID 7d55) integrated display version 14.00 stepping C0
>
> So 14.01 vs 14.00. In the driver:
>
> static const struct {
> u16 ver;
> u16 rel;
> const struct intel_display_device_info *display;
> } gmdid_display_map[] = {
> { 14, 0, &xe_lpdp_display },
> { 14, 1, &xe2_hpd_display },
> ...
> }
>
> So maybe we need to check for the full version >= 1401 instead?
Just another pointless detail I don't want to have to remember.
Also it's already a huge pain in the backside trying to figure out
what new platform has what display ip. Someone really needs to at
least document this properly. Or perhaps we should just put the
expected display ip version back into the platform definition and
then just double check that the version we read from the GMD thing
matches our expectations.
Until the hardware people get their act together and the display ip
version actually has some real meaning we shouldn't use it outside
the major version IMO.
>
> +Matt Roper, +Gustavo who may know the right bspec to confirm this
> change in behavior
None of this stuff is in bspec.
>
> Lucas De Marchi
>
> >
> >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
> >
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-02-10 16:17 UTC|newest]
Thread overview: 22+ 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
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:36 ` ✓ CI.Patch_applied: success for drm/i915: Fix scanline_offset for LNL+/BMG+ Patchwork
2025-02-07 22:36 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-07 22:37 ` ✓ CI.KUnit: success " Patchwork
2025-02-07 22:41 ` [PATCH 0/3] " Lucas De Marchi
2025-02-10 16:05 ` Gustavo Sousa
2025-02-10 16:16 ` Ville Syrjälä [this message]
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:53 ` ✓ CI.Build: success for " Patchwork
2025-02-07 22:56 ` ✓ CI.Hooks: " Patchwork
2025-02-07 22:57 ` ✓ CI.checksparse: " Patchwork
2025-02-07 23:17 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-08 14:18 ` ✗ Xe.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=Z6omejfSAI1NkOGj@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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