From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: [PATCH 2/3] drm/xe/rtp: Don't whitelist OA head pointer registers
Date: Mon, 13 Apr 2026 20:52:43 -0700 [thread overview]
Message-ID: <20260414035244.741342-3-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20260414035244.741342-1-ashutosh.dixit@intel.com>
OA head pointer registers are not used by UMD's and do not need to be
whitelisted. Only MMIO trigger, tail pointer and OA buffer registers need
to be whitelisted. OA head pointer is sometimes provided to the
WHITELIST_OA_MMIO_TRG to have the correct register offset alignment for
RING_FORCE_TO_NONPRIV_RANGE_4.
Fixes: ed455775c5a6 ("drm/xe/rtp: Refactor OAG MMIO trigger register whitelisting")
Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
---
drivers/gpu/drm/xe/xe_reg_whitelist.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_reg_whitelist.c b/drivers/gpu/drm/xe/xe_reg_whitelist.c
index a4124f00c467f..09dcb6a422797 100644
--- a/drivers/gpu/drm/xe/xe_reg_whitelist.c
+++ b/drivers/gpu/drm/xe/xe_reg_whitelist.c
@@ -90,9 +90,9 @@ static const struct xe_rtp_entry_sr register_whitelist[] = {
RING_FORCE_TO_NONPRIV_ACCESS_RW))
},
-#define WHITELIST_OA_MMIO_TRG(trg, head) \
+#define WHITELIST_OA_MMIO_TRG(trg, tail_buf) \
WHITELIST(trg, RING_FORCE_TO_NONPRIV_ACCESS_RW), \
- WHITELIST(head, RING_FORCE_TO_NONPRIV_ACCESS_RD | RING_FORCE_TO_NONPRIV_RANGE_4)
+ WHITELIST(tail_buf, RING_FORCE_TO_NONPRIV_ACCESS_RD | RING_FORCE_TO_NONPRIV_RANGE_4)
#define WHITELIST_OAG_MMIO_TRG \
WHITELIST_OA_MMIO_TRG(OAG_MMIOTRIGGER, OAG_OAHEADPTR)
--
2.48.1
next prev parent reply other threads:[~2026-04-14 3:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 3:52 [PATCH 0/3] drm/xe/rtp: OA register whitelist fixes Ashutosh Dixit
2026-04-14 3:52 ` [PATCH 1/3] drm/xe/rtp: Don't whitelist OA status registers Ashutosh Dixit
2026-04-14 3:52 ` Ashutosh Dixit [this message]
2026-04-14 3:52 ` [PATCH 3/3] drm/xe/rtp: Fix offset alignment for MERT WHITELIST_OA_MERT_MMIO_TRG Ashutosh Dixit
2026-04-14 4:00 ` ✗ CI.checkpatch: warning for drm/xe/rtp: OA register whitelist fixes Patchwork
2026-04-14 4:01 ` ✓ CI.KUnit: success " Patchwork
2026-04-14 5:14 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-14 8:04 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-14 15:28 ` [PATCH 0/3] " Gustavo Sousa
2026-04-15 3:38 ` Dixit, Ashutosh
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=20260414035244.741342-3-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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