From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 00/12] Minor revid/stepping and workaround cleanup
Date: Fri, 9 Jul 2021 20:37:12 -0700 [thread overview]
Message-ID: <20210710033724.2459367-1-matthew.d.roper@intel.com> (raw)
PCI revision IDs don't always map to GT and display IP steppings in an
intuitive/sensible way. On many of our recent platforms we've switched
to using revid->stepping lookup tables with the infrastructure in
intel_step.c to handle stepping lookups and comparisons. This series
converts several of our older platforms over to the same table-based
scheme; this is good not only for consistency, but also because some
upcoming DMC work will rely on table-based lookups. Going forward the
only place that revision ID's should really get used directly is when
checking to see if we're running on pre-production hardware.
Note: I haven't added the stepping tables for CFL and its derivatives
(WHL, AML) yet since there are so many different variants and the
steppings work a bit strangely on some of them. We don't have any
stepping-specific workarounds on these platforms, so the tables aren't
necessary until Anusha's DMC work arrives; I'll let her determine the
best way to handle the tables for those. Ditto for CML.
Let's also take the opportunity to drop a bit of effectively dead code
in the workarounds file too.
v2:
- Include an already-reviewed patch from Anusha's DMC series as the
first patch here that changes the naming of the revision ID tables,
and then adjust the naming of the new tables I add here to follow the
same convention.
- Drop the pre-production revisions for all gen11 and earlier
platforms; we're past the point where we usually drop the
pre-production support. intel_detect_preproduction_hw() is updated
with the proper revids for ICL to ensure we print an error and taint
the kernel if the kernel is loaded on a pre-production platform.
- ICL workarounds that only apply to pre-production steppings are
dropped.
- For platforms where GT stepping is always the same as display
stepping, we use a macro to assign them both at once to make it more
obvious how the platform works.
- Stepping tables for BXT and GLK are added. They're completely unused
in our current code (we have no stepping-specific workarounds), but
some DMC patches from Anusha will arrive shortly that require these.
Note that the BXT revision macros we had previously were completely
wrong; it's a good thing they weren't actually being used for
anything.
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
Anusha Srivatsa (1):
drm/i915/step: s/<platform>_revid_tbl/<platform>_revids
Matt Roper (11):
drm/i915: Make pre-production detection use direct revid comparison
drm/i915/skl: Use revid->stepping tables
drm/i915/kbl: Drop pre-production revision from stepping table
drm/i915/bxt: Use revid->stepping tables
drm/i915/glk: Use revid->stepping tables
drm/i915/icl: Use revid->stepping tables
drm/i915/jsl_ehl: Use revid->stepping tables
drm/i915/rkl: Use revid->stepping tables
drm/i915/dg1: Use revid->stepping tables
drm/i915/cnl: Drop all workarounds
drm/i915/icl: Drop workarounds that only apply to pre-production
steppings
.../drm/i915/display/intel_display_power.c | 2 +-
drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 2 +-
drivers/gpu/drm/i915/display/intel_psr.c | 4 +-
drivers/gpu/drm/i915/gt/intel_region_lmem.c | 2 +-
drivers/gpu/drm/i915/gt/intel_workarounds.c | 108 ++----------------
drivers/gpu/drm/i915/i915_drv.c | 9 +-
drivers/gpu/drm/i915/i915_drv.h | 79 ++-----------
drivers/gpu/drm/i915/intel_pm.c | 2 +-
drivers/gpu/drm/i915/intel_step.c | 104 ++++++++++++++---
drivers/gpu/drm/i915/intel_step.h | 4 +
10 files changed, 119 insertions(+), 197 deletions(-)
--
2.25.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-07-10 3:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 3:37 Matt Roper [this message]
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 01/12] drm/i915/step: s/<platform>_revid_tbl/<platform>_revids Matt Roper
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 02/12] drm/i915: Make pre-production detection use direct revid comparison Matt Roper
2021-07-13 17:20 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 03/12] drm/i915/skl: Use revid->stepping tables Matt Roper
2021-07-12 23:03 ` Srivatsa, Anusha
2021-07-13 17:51 ` Lucas De Marchi
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 04/12] drm/i915/kbl: Drop pre-production revision from stepping table Matt Roper
2021-07-13 17:22 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 05/12] drm/i915/bxt: Use revid->stepping tables Matt Roper
2021-07-12 23:04 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 06/12] drm/i915/glk: " Matt Roper
2021-07-12 21:11 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 07/12] drm/i915/icl: " Matt Roper
2021-07-13 19:23 ` Souza, Jose
2021-07-13 19:57 ` Lucas De Marchi
2021-07-13 19:59 ` Matt Roper
2021-07-13 20:02 ` Lucas De Marchi
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 08/12] drm/i915/jsl_ehl: " Matt Roper
2021-07-12 22:25 ` Srivatsa, Anusha
2021-07-13 16:14 ` [Intel-gfx] [PATCH v3 " Matt Roper
2021-07-13 16:56 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 09/12] drm/i915/rkl: " Matt Roper
2021-07-12 22:51 ` Srivatsa, Anusha
2021-07-12 22:56 ` Matt Roper
2021-07-13 17:08 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 10/12] drm/i915/dg1: " Matt Roper
2021-07-13 17:09 ` Srivatsa, Anusha
2021-07-13 17:29 ` [Intel-gfx] [PATCH v3 " Matt Roper
2021-07-13 17:33 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 11/12] drm/i915/cnl: Drop all workarounds Matt Roper
2021-07-12 22:55 ` Srivatsa, Anusha
2021-07-10 3:37 ` [Intel-gfx] [PATCH v2 12/12] drm/i915/icl: Drop workarounds that only apply to pre-production steppings Matt Roper
2021-07-13 17:13 ` Srivatsa, Anusha
2021-07-10 3:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Minor revid/stepping and workaround cleanup (rev2) Patchwork
2021-07-10 4:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-10 19:28 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-13 19:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Minor revid/stepping and workaround cleanup (rev4) Patchwork
2021-07-13 19:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " 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=20210710033724.2459367-1-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