Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: matthew.d.roper@intel.com
Subject: [Intel-gfx] [PATCH v2 0/5] Drop support for pre-production DG2 hardware
Date: Wed, 16 Aug 2023 14:42:02 -0700	[thread overview]
Message-ID: <20230816214201.534095-7-matthew.d.roper@intel.com> (raw)

We generally only keep support for pre-production steppings and
workarounds around in the driver until the next major platform is
implemented.  Now that MTL is in good shape in i915 (and subsequent
platforms like LNL are being implemented solely on the Xe driver) it's
time to drop the DG2 pre-production hardware support.

DG2 production hardware always has display stepping C0 or later.  On the
GT side, production hardware starts with C0 (for DG2-G10), B1 (for
DG2-G11), and A1 (for DG2-G12).  This means we can drop quite a few
pre-production workarounds, and simplify the handling of several others.

v2:
 - Split removal of Wa_16011777198 out to a separate patch since it
   allows us to garbage collect a little bit of other code as well.
   Review is easier in a standalone patch.

Matt Roper (5):
  drm/i915/dg2: Recognize pre-production hardware
  drm/i915/dg2: Drop pre-production display workarounds
  drm/i915/dg2: Drop pre-production GT workarounds
  drm/i915: Tidy workaround definitions
  drm/i915/dg2: Drop Wa_16011777198

 drivers/gpu/drm/i915/display/intel_display.c  |   2 +-
 .../drm/i915/display/skl_universal_plane.c    |   4 -
 drivers/gpu/drm/i915/gt/intel_lrc.c           |  34 +-
 drivers/gpu/drm/i915/gt/intel_mocs.c          |  21 +-
 drivers/gpu/drm/i915/gt/intel_rc6.c           |   6 +-
 drivers/gpu/drm/i915/gt/intel_workarounds.c   | 301 +++---------------
 drivers/gpu/drm/i915/gt/uc/intel_guc.c        |  20 +-
 drivers/gpu/drm/i915/i915_driver.c            |   3 +
 drivers/gpu/drm/i915/i915_drv.h               |  23 --
 drivers/gpu/drm/i915/i915_perf.c              |  32 --
 drivers/gpu/drm/i915/i915_perf_types.h        |   6 -
 drivers/gpu/drm/i915/intel_clock_gating.c     |   8 -
 12 files changed, 66 insertions(+), 394 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-08-16 21:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 21:42 Matt Roper [this message]
2023-08-16 21:42 ` [Intel-gfx] [PATCH v2 1/5] drm/i915/dg2: Recognize pre-production hardware Matt Roper
2023-08-16 21:42 ` [Intel-gfx] [PATCH v2 2/5] drm/i915/dg2: Drop pre-production display workarounds Matt Roper
2023-08-16 21:42 ` [Intel-gfx] [PATCH v2 3/5] drm/i915/dg2: Drop pre-production GT workarounds Matt Roper
2023-08-17 21:21   ` Matt Atwood
2023-08-16 21:42 ` [Intel-gfx] [PATCH v2 4/5] drm/i915: Tidy workaround definitions Matt Roper
2023-08-16 21:42 ` [Intel-gfx] [PATCH v2 5/5] drm/i915/dg2: Drop Wa_16011777198 Matt Roper
2023-08-16 21:44   ` Matt Roper
2023-08-16 21:48   ` [Intel-gfx] [PATCH v3 " Matt Roper
2023-08-16 23:14     ` Dixit, Ashutosh
2023-08-17  0:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Drop support for pre-production DG2 hardware (rev3) Patchwork
2023-08-17  0:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-17  0:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-17 12:34 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-08-17 22:28   ` Matt Roper

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=20230816214201.534095-7-matthew.d.roper@intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=intel-gfx@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