From: Matt Roper <matthew.d.roper@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 0/5] i915: Introduce Ponte Vecchio
Date: Tue, 10 May 2022 23:02:23 -0700 [thread overview]
Message-ID: <20220511060228.1179450-1-matthew.d.roper@intel.com> (raw)
Ponte Vecchio (PVC) is a new GPU based on the Xe_HPC architecture. As a
compute-focused platform, PVC has compute engines and enhanced copy
engines, but no render engine (there is no geometry pipeline) and no
display.
This is just a handful of early enablement patches, including some
initial support for the new copy engines (although we're not yet adding
those to the platform's engine list or exposing them to userspace just
yet).
v2:
- Drop replicated comment from forcewake patch completely and add an
additional commit to provide better documentation for forcewake and
shadowed register tables in a way that's clear for all platforms.
- Move gvt build fix to its own patch.
- Address various minor review feedback from Lucas, Tvrtko, and
Prathap.
v3:
- Flip the feature flag in the PIPE_CONTROL patch. (Lucas)
- Add two additional GuC-related patches.
Daniele Ceraolo Spurio (1):
drm/i915/guc: XEHPSDV and PVC do not use HuC
Matt Roper (3):
drm/i915/uncore: Reorganize and document shadow and forcewake tables
drm/i915/pvc: Add forcewake support
drm/i915/pvc: Add new BCS engines to GuC engine list
Stuart Summers (1):
drm/i915/pvc: Remove additional 3D flags from PIPE_CONTROL
drivers/gpu/drm/i915/gt/gen8_engine_cs.c | 18 +-
drivers/gpu/drm/i915/gt/intel_gpu_commands.h | 15 +-
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c | 2 +-
drivers/gpu/drm/i915/gt/uc/intel_uc.c | 4 +
drivers/gpu/drm/i915/i915_drv.h | 4 +
drivers/gpu/drm/i915/i915_pci.c | 10 +
drivers/gpu/drm/i915/intel_device_info.h | 1 +
drivers/gpu/drm/i915/intel_uncore.c | 267 +++++++++++++++---
drivers/gpu/drm/i915/selftests/intel_uncore.c | 2 +
9 files changed, 268 insertions(+), 55 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-11 6:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 6:02 Matt Roper [this message]
2022-05-11 6:02 ` [Intel-gfx] [PATCH v3 1/5] drm/i915/uncore: Reorganize and document shadow and forcewake tables Matt Roper
2022-05-24 17:25 ` Matt Atwood
2022-05-11 6:02 ` [Intel-gfx] [PATCH v3 2/5] drm/i915/pvc: Add forcewake support Matt Roper
2022-05-24 18:36 ` Matt Atwood
2022-05-11 6:02 ` [Intel-gfx] [PATCH v3 3/5] drm/i915/pvc: Remove additional 3D flags from PIPE_CONTROL Matt Roper
2022-05-24 18:37 ` Matt Atwood
2022-05-11 6:02 ` [Intel-gfx] [PATCH v3 4/5] drm/i915/pvc: Add new BCS engines to GuC engine list Matt Roper
2022-05-24 18:38 ` Matt Atwood
2022-05-11 6:02 ` [Intel-gfx] [PATCH v3 5/5] drm/i915/guc: XEHPSDV and PVC do not use HuC Matt Roper
2022-05-24 18:39 ` Matt Atwood
2022-05-11 6:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: Introduce Ponte Vecchio (rev4) Patchwork
2022-05-11 6:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-05-11 6:56 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-05-11 14:33 ` Matt Roper
2022-05-11 15:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-11 19:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-11 20:44 ` Matt Roper
2022-05-11 23:21 ` Vudum, Lakshminarayana
2022-05-11 23:17 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-05-24 19: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=20220511060228.1179450-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