From: Matt Roper <matthew.d.roper@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: matthew.d.roper@intel.com,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
Jakub Kolakowski <jakub1.kolakowski@intel.com>
Subject: [PATCH 2/2] drm/xe/sriov: Drop TIMESTAMP_OVERRIDE from Xe2 runtime regs
Date: Thu, 12 Sep 2024 14:56:01 -0700 [thread overview]
Message-ID: <20240912215559.4070443-4-matthew.d.roper@intel.com> (raw)
In-Reply-To: <20240912215559.4070443-3-matthew.d.roper@intel.com>
TIMESTAMP_OVERRIDE is never used to initialize the GT clock frequency on
Xe2 platforms (and the register itself no longer exists on LNL) so drop
it from the list of runtime registers.
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
---
drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
index 924e75b94aec..a5bd577227d4 100644
--- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
+++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
@@ -173,7 +173,6 @@ static const struct xe_reg ver_2000_runtime_regs[] = {
XE2_GT_GEOMETRY_DSS_2, /* _MMIO(0x9154) */
CTC_MODE, /* _MMIO(0xa26c) */
HUC_KERNEL_LOAD_INFO, /* _MMIO(0xc1dc) */
- TIMESTAMP_OVERRIDE, /* _MMIO(0x44074) */
};
static const struct xe_reg *pick_runtime_regs(struct xe_device *xe, unsigned int *count)
--
2.45.2
next prev parent reply other threads:[~2024-09-12 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 21:56 [PATCH 1/2] drm/xe: Don't try to derive GT clock freq from display register on Xe2 Matt Roper
2024-09-12 21:56 ` Matt Roper [this message]
2024-09-13 13:40 ` [PATCH 2/2] drm/xe/sriov: Drop TIMESTAMP_OVERRIDE from Xe2 runtime regs Michal Wajdeczko
2024-09-12 22:30 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Don't try to derive GT clock freq from display register on Xe2 Patchwork
2024-09-12 22:30 ` ✓ CI.checkpatch: " Patchwork
2024-09-12 22:31 ` ✓ CI.KUnit: " Patchwork
2024-09-12 22:43 ` ✓ CI.Build: " Patchwork
2024-09-12 22:45 ` ✓ CI.Hooks: " Patchwork
2024-09-12 22:47 ` ✓ CI.checksparse: " Patchwork
2024-09-12 23:02 ` ✓ CI.BAT: " Patchwork
2024-09-13 14:36 ` [PATCH 1/2] " Lucas De Marchi
2024-09-13 15:25 ` ✗ CI.FULL: failure for series starting with [1/2] " 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=20240912215559.4070443-4-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=michal.wajdeczko@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