From: Sk Anirban <sk.anirban@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, badal.nilawar@intel.com,
riana.tauro@intel.com, karthik.poosa@intel.com,
raag.jadav@intel.com, soham.purkait@intel.com,
mallesh.koujalagi@intel.com, vinay.belgaumkar@intel.com,
daniele.ceraolospurio@intel.com, nishanth.p.reddy@intel.com,
rodrigo.vivi@intel.com, matthew.d.roper@intel.com,
Sk Anirban <sk.anirban@intel.com>
Subject: [PATCH v4 0/1] drm/xe/guc: Add Wa_14025883347 for GuC DMA failure on reset
Date: Mon, 2 Feb 2026 16:23:14 +0530 [thread overview]
Message-ID: <20260202105313.3338094-3-sk.anirban@intel.com> (raw)
Prevent GuC firmware DMA failures during GuC-only reset by disabling
idle flow and verifying SRAM handling completion. Without this, reset
can be issued while SRAM handler is copying WOPCM to SRAM,
causing GuC HW to get stuck.
v2: Modify error message (Badal)
Rename reg bit name (Daniele)
Update WA skip condition (Daniele)
Update SRAM handling logic (Daniele)
v3: Reorder WA call (Badal)
Wait for GuC ready status (Daniele)
v4: Update reg name (Badal)
Add comment (Daniele)
Add extended graphics version (Daniele)
Modify rules
Sk Anirban (1):
drm/xe/guc: Add Wa_14025883347 for GuC DMA failure on reset
drivers/gpu/drm/xe/regs/xe_guc_regs.h | 8 ++++++
drivers/gpu/drm/xe/xe_guc.c | 38 +++++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_wa_oob.rules | 3 +++
3 files changed, 49 insertions(+)
--
2.43.0
next reply other threads:[~2026-02-02 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 10:53 Sk Anirban [this message]
2026-02-02 10:53 ` [PATCH v4 1/1] drm/xe/guc: Add Wa_14025883347 for GuC DMA failure on reset Sk Anirban
2026-02-02 19:47 ` Daniele Ceraolo Spurio
2026-02-03 23:36 ` Matt Roper
2026-02-04 18:55 ` Daniele Ceraolo Spurio
2026-02-06 11:34 ` Nilawar, Badal
2026-02-02 20:38 ` ✓ CI.KUnit: success for drm/xe/guc: Add Wa_14025883347 for GuC DMA failure on reset (rev4) Patchwork
2026-02-02 21:11 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-09 20:02 ` 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=20260202105313.3338094-3-sk.anirban@intel.com \
--to=sk.anirban@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nishanth.p.reddy@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=soham.purkait@intel.com \
--cc=vinay.belgaumkar@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