Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Cc: matthew.d.roper@intel.com
Subject: Re: [Intel-gfx] [PATCH 0/4] Drop support for pre-production DG2 hardware
Date: Wed, 16 Aug 2023 12:11:19 +0300	[thread overview]
Message-ID: <87v8df9wso.fsf@intel.com> (raw)
In-Reply-To: <20230815173611.142687-6-matthew.d.roper@intel.com>

On Tue, 15 Aug 2023, Matt Roper <matthew.d.roper@intel.com> wrote:
> 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.

Did not review, but in general

Acked-by: Jani Nikula <jani.nikula@intel.com>


>
>
> Matt Roper (4):
>   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
>
>  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              |  20 --
>  drivers/gpu/drm/i915/intel_clock_gating.c     |   8 -
>  11 files changed, 66 insertions(+), 376 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center

      parent reply	other threads:[~2023-08-16  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 17:36 [Intel-gfx] [PATCH 0/4] Drop support for pre-production DG2 hardware Matt Roper
2023-08-15 17:36 ` [Intel-gfx] [PATCH 1/4] drm/i915/dg2: Recognize pre-production hardware Matt Roper
2023-08-16 18:08   ` Matt Atwood
2023-08-15 17:36 ` [Intel-gfx] [PATCH 2/4] drm/i915/dg2: Drop pre-production display workarounds Matt Roper
2023-08-16 18:14   ` Matt Atwood
2023-08-15 17:36 ` [Intel-gfx] [PATCH 3/4] drm/i915/dg2: Drop pre-production GT workarounds Matt Roper
2023-08-15 17:50   ` Dixit, Ashutosh
2023-08-15 17:36 ` [Intel-gfx] [PATCH 4/4] drm/i915: Tidy workaround definitions Matt Roper
2023-08-16 20:07   ` Matt Atwood
2023-08-15 19:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Drop support for pre-production DG2 hardware Patchwork
2023-08-15 19:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-15 19:27 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-16  9:11 ` Jani Nikula [this message]

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=87v8df9wso.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox