Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: [Intel-xe] [PATCH v2 3/6] drm/xe/pat: trim the tgl PAT table
Date: Thu, 14 Sep 2023 16:31:16 +0100	[thread overview]
Message-ID: <20230914153112.455547-11-matthew.auld@intel.com> (raw)
In-Reply-To: <20230914153112.455547-8-matthew.auld@intel.com>

We don't seem to use the 4-7 pat indexes, even though they are defined
by the HW. In the next patch userspace will be able to directly set the
pat_index as part of vm_bind and we don't want to allow setting 4-7.
Simplest is to just ignore them here.

Suggested-by: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Pallavi Mishra <pallavi.mishra@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
---
 drivers/gpu/drm/xe/xe_pat.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_pat.c b/drivers/gpu/drm/xe/xe_pat.c
index aa2c5eb88266..fb490982fd99 100644
--- a/drivers/gpu/drm/xe/xe_pat.c
+++ b/drivers/gpu/drm/xe/xe_pat.c
@@ -38,10 +38,6 @@ static const u32 tgl_pat_table[] = {
 	[1] = TGL_PAT_WC,
 	[2] = TGL_PAT_WT,
 	[3] = TGL_PAT_UC,
-	[4] = TGL_PAT_WB,
-	[5] = TGL_PAT_WB,
-	[6] = TGL_PAT_WB,
-	[7] = TGL_PAT_WB,
 };
 
 static const u32 pvc_pat_table[] = {
-- 
2.41.0


  parent reply	other threads:[~2023-09-14 15:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 15:31 [Intel-xe] [PATCH v2 0/6] PAT and cache coherency support Matthew Auld
2023-09-14 15:31 ` [Intel-xe] [PATCH v2 1/6] drm/xe/uapi: Add support for cache and coherency mode Matthew Auld
2023-09-14 23:47   ` Matt Roper
2023-09-15  7:37     ` Matthew Auld
2023-09-21 20:07   ` Souza, Jose
2023-09-25  8:06     ` Matthew Auld
2023-09-25 18:26       ` Souza, Jose
2023-09-26  8:07         ` Matthew Auld
2023-09-26 15:59           ` Souza, Jose
2023-09-14 15:31 ` [Intel-xe] [PATCH v2 2/6] drm/xe: move pat_table into device info Matthew Auld
2023-09-14 23:53   ` Matt Roper
2023-09-14 15:31 ` Matthew Auld [this message]
2023-09-14 18:07   ` [Intel-xe] [PATCH v2 3/6] drm/xe/pat: trim the tgl PAT table Matt Roper
2023-09-14 15:31 ` [Intel-xe] [PATCH v2 4/6] drm/xe/pat: annotate pat_index with coherency mode Matthew Auld
2023-09-15  0:08   ` Matt Roper
2023-09-14 15:31 ` [Intel-xe] [PATCH v2 5/6] drm/xe/migrate: rather use pte_encode helpers Matthew Auld
2023-09-15 22:19   ` Matt Roper
2023-09-14 15:31 ` [Intel-xe] [PATCH v2 6/6] drm/xe/uapi: support pat_index selection with vm_bind Matthew Auld
2023-09-15 22:24   ` Matt Roper
2023-09-25  8:07     ` Matthew Auld
2023-09-25 21:56   ` Rodrigo Vivi
2023-09-26  8:17     ` Matthew Auld
2023-09-27 19:30       ` Rodrigo Vivi
2023-09-14 18:16 ` [Intel-xe] ✗ CI.Patch_applied: failure for PAT and cache coherency support (rev2) Patchwork
2023-09-18 15:51 ` [Intel-xe] [PATCH v2 0/6] PAT and cache coherency support Souza, Jose
2023-09-21 17:19   ` Souza, Jose
2023-09-25 13:12     ` Matthew Auld
2023-09-21 20:10 ` [Intel-xe] ✗ CI.Patch_applied: failure for PAT and cache coherency support (rev3) 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=20230914153112.455547-11-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --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