From: Anusha Srivatsa <anusha.srivatsa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 00/10] Get stepping info from RUNTIME_INFO->step
Date: Thu, 8 Jul 2021 16:18:11 -0700 [thread overview]
Message-ID: <20210708231821.9163-1-anusha.srivatsa@intel.com> (raw)
The changes are added on top of Matt's series:
https://patchwork.freedesktop.org/series/92299/
This series modifies the way we get stepping indo for DMC
to load the right firmware for the right stepping/substepping
combinations.
Since we have a lookup table for BXT in intel_dmc.c and BXT
stepping changes were missing from Matt's series, I have added a
patch for it.
Anusha Srivatsa (3):
drm/i915/bxt: Use revid->stepping tables
drm/i915/step: Add intel_step_name() helper
drm/i915/dmc: Modify intel_get_stepping_info()
Matt Roper (7):
drm/i915: Make pre-production detection use direct revid comparison
drm/i915/skl: 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/display/intel_display_power.c | 2 +-
drivers/gpu/drm/i915/display/intel_dmc.c | 51 ++-----
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 | 81 ++--------
drivers/gpu/drm/i915/i915_drv.c | 8 +-
drivers/gpu/drm/i915/i915_drv.h | 80 ++--------
drivers/gpu/drm/i915/intel_pm.c | 2 +-
drivers/gpu/drm/i915/intel_step.c | 142 +++++++++++++++++-
drivers/gpu/drm/i915/intel_step.h | 8 +
11 files changed, 187 insertions(+), 195 deletions(-)
--
2.32.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-07-08 23:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 23:18 Anusha Srivatsa [this message]
2021-07-08 23:18 ` [Intel-gfx] [PATCH 01/10] drm/i915: Make pre-production detection use direct revid comparison Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 02/10] drm/i915/skl: Use revid->stepping tables Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 03/10] drm/i915/icl: " Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 04/10] drm/i915/jsl_ehl: " Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 05/10] drm/i915/rkl: " Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 06/10] drm/i915/dg1: " Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 07/10] drm/i915/cnl: Drop all workarounds Anusha Srivatsa
2021-07-08 23:18 ` [Intel-gfx] [PATCH 08/10] drm/i915/bxt: Use revid->stepping tables Anusha Srivatsa
2021-07-09 3:53 ` Matt Roper
2021-07-08 23:18 ` [Intel-gfx] [PATCH 09/10] drm/i915/step: Add intel_step_name() helper Anusha Srivatsa
2021-07-09 4:16 ` Matt Roper
2021-07-09 17:52 ` Lucas De Marchi
2021-07-09 18:36 ` Srivatsa, Anusha
2021-07-09 18:43 ` Lucas De Marchi
2021-07-08 23:18 ` [Intel-gfx] [PATCH 10/10] drm/i915/dmc: Modify intel_get_stepping_info() Anusha Srivatsa
2021-07-09 0:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Get stepping info from RUNTIME_INFO->step Patchwork
2021-07-09 0:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-07-09 1:03 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20210708231821.9163-1-anusha.srivatsa@intel.com \
--to=anusha.srivatsa@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 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.