From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/3] i915: Initial workarounds for Xe_HP SDV and DG2
Date: Tue, 2 Nov 2021 15:25:08 -0700 [thread overview]
Message-ID: <20211102222511.534310-1-matthew.d.roper@intel.com> (raw)
This is the initial batch of workarounds for these two platforms. There
are still more workarounds to come in the future (e.g., related to other
functionality that hasn't landed yet like compute engines, multi-tile,
etc.).
Matt Roper (2):
drm/i915/dg2: Add initial gt/ctx/engine workarounds
drm/i915/dg2: Program recommended HW settings
Stuart Summers (1):
drm/i915/xehpsdv: Add initial workarounds
drivers/gpu/drm/i915/gt/intel_workarounds.c | 392 +++++++++++++++++++-
drivers/gpu/drm/i915/i915_reg.h | 154 +++++++-
drivers/gpu/drm/i915/intel_pm.c | 31 +-
3 files changed, 547 insertions(+), 30 deletions(-)
--
2.33.0
next reply other threads:[~2021-11-02 22:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 22:25 Matt Roper [this message]
2021-11-02 22:25 ` [Intel-gfx] [PATCH 1/3] drm/i915/xehpsdv: Add initial workarounds Matt Roper
2021-11-11 18:31 ` Clint Taylor
2021-11-02 22:25 ` [Intel-gfx] [PATCH 2/3] drm/i915/dg2: Add initial gt/ctx/engine workarounds Matt Roper
2021-11-03 21:30 ` Srivatsa, Anusha
2021-11-12 11:18 ` Petri Latvala
2021-11-12 12:05 ` Sarvela, Tomi P
2021-11-02 22:25 ` [Intel-gfx] [PATCH 3/3] drm/i915/dg2: Program recommended HW settings Matt Roper
2021-11-11 18:28 ` Clint Taylor
2021-11-02 23:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success for i915: Initial workarounds for Xe_HP SDV and DG2 Patchwork
2021-11-03 2:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-11 19:13 ` Matt Roper
2021-11-11 19:57 ` Vudum, Lakshminarayana
2021-11-12 10:02 ` Petri Latvala
2021-11-12 10:41 ` Petri Latvala
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=20211102222511.534310-1-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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