From: Badal Nilawar <badal.nilawar@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, lucas.demarchi@intel.com,
john.c.harrison@intel.com, matthew.d.roper@intel.com
Subject: [PATCH 0/2] Add support for Wa KLVs
Date: Tue, 19 Mar 2024 21:38:57 +0530 [thread overview]
Message-ID: <20240319160859.2672825-1-badal.nilawar@intel.com> (raw)
Add infra to opt-in GuC Wa via KLV interface.
Enable Wa_14019882105 for LNL A step
Badal Nilawar (2):
drm/xe/guc: Add support for w/a KLVs
drm/xe/lnl: Enable GuC Wa_14019882105
drivers/gpu/drm/xe/abi/guc_klvs_abi.h | 7 +++
drivers/gpu/drm/xe/xe_guc_ads.c | 83 ++++++++++++++++++++++++++-
drivers/gpu/drm/xe/xe_guc_ads_types.h | 2 +
drivers/gpu/drm/xe/xe_guc_fwif.h | 5 +-
drivers/gpu/drm/xe/xe_wa_oob.rules | 1 +
5 files changed, 95 insertions(+), 3 deletions(-)
--
2.25.1
next reply other threads:[~2024-03-19 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 16:08 Badal Nilawar [this message]
2024-03-19 15:59 ` ✓ CI.Patch_applied: success for Add support for Wa KLVs (rev2) Patchwork
2024-03-19 15:59 ` ✓ CI.checkpatch: " Patchwork
2024-03-19 16:00 ` ✓ CI.KUnit: " Patchwork
2024-03-19 16:08 ` [PATCH v2 1/2] drm/xe/guc: Add support for w/a KLVs Badal Nilawar
2024-03-20 20:40 ` John Harrison
2024-03-22 17:15 ` Daniele Ceraolo Spurio
2024-03-25 14:35 ` Nilawar, Badal
2024-03-19 16:08 ` [PATCH v2 2/2] drm/xe/lnl: Enable GuC Wa_14019882105 Badal Nilawar
2024-03-20 20:43 ` John Harrison
2024-03-19 16:11 ` ✓ CI.Build: success for Add support for Wa KLVs (rev2) Patchwork
2024-03-19 16:16 ` ✓ CI.Hooks: " Patchwork
2024-03-19 16:18 ` ✓ CI.checksparse: " Patchwork
2024-03-19 16:41 ` ✓ CI.BAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-03-15 11:21 [PATCH 0/2] Add support for Wa KLVs Badal Nilawar
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=20240319160859.2672825-1-badal.nilawar@intel.com \
--to=badal.nilawar@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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