From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/8] drm/i915: Drop the min plane width w/a adl+
Date: Sat, 11 Oct 2025 02:33:39 +0300 [thread overview]
Message-ID: <aOmX00H3rqm5W9cC@intel.com> (raw)
In-Reply-To: <20251009223819.GD1207432@mdroper-desk1.amr.corp.intel.com>
On Thu, Oct 09, 2025 at 03:38:19PM -0700, Matt Roper wrote:
> On Fri, Oct 10, 2025 at 12:13:06AM +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > ADL+ no longer need the plane min width w/a (Wa_14011264657 or
>
> Nitpick: For clarity you might want to write this as "ADL-P and beyond"
> since ADL-S (which uses display version 12) actually does still need
> Wa_14011264657.
I always follow the bspec convention: ADL is the real ADL (ADL-P/N,
RPL-something or another). Bspec doesn't even know what ADL-P is.
And ADL-S I don't even think about. It's just a TGL in my book.
Except in those rare special cases where there is a real difference,
like with the PHYs.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-10-10 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 21:13 [PATCH 0/8] drm/i915: Some universal plane fixes and cleanups Ville Syrjala
2025-10-09 21:13 ` [PATCH 1/8] drm/i915: Rewrite icl_min_plane_width() Ville Syrjala
2025-10-09 21:13 ` [PATCH 2/8] drm/i915: Drop the min plane width w/a adl+ Ville Syrjala
2025-10-09 22:38 ` Matt Roper
2025-10-10 23:33 ` Ville Syrjälä [this message]
2025-10-09 21:13 ` [PATCH 3/8] drm/i915: Implement .min_plane_width() for PTL+ Ville Syrjala
2025-10-09 21:13 ` [PATCH 4/8] drm/i915: Start checking plane min size for the chroma plane Ville Syrjala
2025-10-09 21:13 ` [PATCH 5/8] drm/i915: Introduce intel_plane_min_height() Ville Syrjala
2025-10-09 21:13 ` [PATCH 6/8] drm/i915: Remove pointless crtc hw.enable check Ville Syrjala
2025-10-09 21:13 ` [PATCH 7/8] drm/i915: Extract glk_plane_has_planar() Ville Syrjala
2025-10-09 21:13 ` [PATCH 8/8] drm/i915: Unify the logic in {skl,glk}_plane_has_*() Ville Syrjala
2025-10-09 21:37 ` ✓ CI.KUnit: success for drm/i915: Some universal plane fixes and cleanups Patchwork
2025-10-09 22:23 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-09 22:41 ` ✗ i915.CI.BAT: failure " Patchwork
2025-10-10 6:33 ` ✗ Xe.CI.Full: " Patchwork
2025-10-12 19:39 ` ✓ i915.CI.BAT: success for drm/i915: Some universal plane fixes and cleanups (rev2) Patchwork
2025-10-28 9:36 ` [PATCH 0/8] drm/i915: Some universal plane fixes and cleanups Juha-Pekka Heikkilä
2025-10-28 20:58 ` Ville Syrjälä
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=aOmX00H3rqm5W9cC@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.