Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shekhar Chauhan <shekhar.chauhan@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: shekhar.chauhan@intel.com, ashutosh.dixit@intel.com
Subject: [PATCH v7 0/2] Wa_14026633728
Date: Fri,  8 May 2026 07:43:27 +0530	[thread overview]
Message-ID: <20260508021329.876072-1-shekhar.chauhan@intel.com> (raw)

This series introduces Wa_14026633728. For it's introduction, changes
are made in lib/intel_wa to ensure we check from debugfs whether a
workaround is enabled via the KMD or not.

v1: Add workaround patch.
v2: Fix commit title, description and code description.
v3: Check if the wa exists and reuse it, also, fix a warning for C90
rule.
v4: Moved from a single patch to a series of 2 patches, made a mistake
on the numbering. After v3, v5 follows.
v5: Introduce changes in lib/intel_wa to ensure we are properly checking
the debugfs file for the workaround.
v6: Roll back to original design for increasing oa_exponent to keep it
simple.
v7: Removed a comment and fixed tabs vs spaces issue in xe_oa test.

Shekhar Chauhan (2):
  lib/intel_wa: Check for device workarounds
  tests/intel/xe_oa: Wa_14026633728

 lib/intel_wa.c      | 40 ++++++++++++++++++++++++++--------------
 tests/intel/xe_oa.c | 13 +++++++++++++
 2 files changed, 39 insertions(+), 14 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-05-08  2:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  2:13 Shekhar Chauhan [this message]
2026-05-08  2:13 ` [PATCH v7 1/2] lib/intel_wa: Check for device workarounds Shekhar Chauhan
2026-05-08  2:13 ` [PATCH v7 2/2] tests/intel/xe_oa: Wa_14026633728 Shekhar Chauhan
2026-05-08  4:10   ` Dixit, Ashutosh
2026-05-13 21:38     ` Dixit, Ashutosh
2026-05-08 20:56   ` Dixit, Ashutosh
2026-05-08  3:05 ` ✓ Xe.CI.BAT: success for Wa_14026633728 Patchwork
2026-05-08  3:23 ` ✓ i915.CI.BAT: " Patchwork
2026-05-08 14:09 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-08 19:56 ` ✗ i915.CI.Full: " 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=20260508021329.876072-1-shekhar.chauhan@intel.com \
    --to=shekhar.chauhan@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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