From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Vinay Belgaumkar" <vinay.belgaumkar@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for drm/xe/lnl: Apply Wa_22019338487
Date: Mon, 10 Jun 2024 19:57:44 -0000 [thread overview]
Message-ID: <171804946453.51549.18210554006894230962@a6498e030952> (raw)
In-Reply-To: <20240610185231.1451157-1-vinay.belgaumkar@intel.com>
== Series Details ==
Series: drm/xe/lnl: Apply Wa_22019338487
URL : https://patchwork.freedesktop.org/series/134691/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
51ce9f6cd981d42d7467409d7dbc559a450abc1e
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit ba3e626fafdc17108257dd7413f92c7752642e5d
Author: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Date: Mon Jun 10 11:52:31 2024 -0700
drm/xe/lnl: Apply Wa_22019338487
This WA requires us to limit media GT frequency requests to a certain
cap value during driver load. Freq limits are restored after load
completes, so perf will not be affected during normal operations.
During normal driver operation, this WA requires dummy writes to media
offset 0x380D8C after every ~63 GGTT writes. This will ensure completion
of the LMEM writes originating from Gunit.
During driver unload(before FLR), the WA requires that we set requested
frequency to the cap value again.
Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
+ /mt/dim checkpatch bf9d891af55d3785eb9438efb053c991bf2b4b10 drm-intel
ba3e626fafdc drm/xe/lnl: Apply Wa_22019338487
next prev parent reply other threads:[~2024-06-10 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 18:52 [PATCH v2] drm/xe/lnl: Apply Wa_22019338487 Vinay Belgaumkar
2024-06-10 19:57 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-10 19:57 ` Patchwork [this message]
2024-06-10 19:59 ` ✓ CI.KUnit: " Patchwork
2024-06-10 20:13 ` ✓ CI.Build: " Patchwork
2024-06-10 20:13 ` [PATCH v2] " Rodrigo Vivi
2024-06-14 22:40 ` Belgaumkar, Vinay
2024-06-10 20:16 ` ✓ CI.Hooks: success for " Patchwork
2024-06-10 20:17 ` ✓ CI.checksparse: " Patchwork
2024-06-10 21:23 ` ✗ CI.BAT: failure " Patchwork
2024-06-10 23:19 ` ✓ CI.FULL: success " 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=171804946453.51549.18210554006894230962@a6498e030952 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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