Commit 68ccb9b2 authored by Matt Roper's avatar Matt Roper Committed by Rodrigo Vivi

drm/xe: Drop vram_id

The VRAM ID is always the tile ID; there's no need to track it
separately within a GT.
Reviewed-by: default avatarLucas De Marchi <lucas.demarchi@intel.com>
Link: https://lore.kernel.org/r/20230601215244.678611-17-matthew.d.roper@intel.comSigned-off-by: default avatarMatt Roper <matthew.d.roper@intel.com>
Signed-off-by: default avatarRodrigo Vivi <rodrigo.vivi@intel.com>
parent ed006ba5
...@@ -32,7 +32,6 @@ struct xe_subplatform_desc { ...@@ -32,7 +32,6 @@ struct xe_subplatform_desc {
struct xe_gt_desc { struct xe_gt_desc {
enum xe_gt_type type; enum xe_gt_type type;
u8 vram_id;
u32 mmio_adj_limit; u32 mmio_adj_limit;
u32 mmio_adj_offset; u32 mmio_adj_offset;
}; };
...@@ -261,7 +260,6 @@ static const struct xe_device_desc dg2_desc = { ...@@ -261,7 +260,6 @@ static const struct xe_device_desc dg2_desc = {
static const struct xe_gt_desc pvc_gts[] = { static const struct xe_gt_desc pvc_gts[] = {
{ {
.type = XE_GT_TYPE_REMOTE, .type = XE_GT_TYPE_REMOTE,
.vram_id = 1,
.mmio_adj_limit = 0, .mmio_adj_limit = 0,
.mmio_adj_offset = 0, .mmio_adj_offset = 0,
}, },
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment