From: sai.gowtham.ch@intel.com
To: igt-dev@lists.freedesktop.org, sai.gowtham.ch@intel.com
Subject: [PATCH i-g-t] lib/intel_cmds_info: Add MEM_COPY/SET support for Lunarlake
Date: Tue, 9 Jan 2024 15:26:02 +0530 [thread overview]
Message-ID: <20240109095602.9620-1-sai.gowtham.ch@intel.com> (raw)
From: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
Enable MEM_COPY/SET instructions support for Lunarlake, which
allows to validate MEM_COPY/SET tests.
Signed-off-by: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
---
lib/intel_cmds_info.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/intel_cmds_info.c b/lib/intel_cmds_info.c
index 56073bd6d..669d3e500 100644
--- a/lib/intel_cmds_info.c
+++ b/lib/intel_cmds_info.c
@@ -182,6 +182,8 @@ const struct intel_cmds_info xe2_cmds_info = {
.blt_cmds = {
[XY_FAST_COPY] = &dg2_xy_fast_copy,
[XY_BLOCK_COPY] = &xe2_xy_block_copy,
+ [MEM_COPY] = &pvc_mem_copy,
+ [MEM_SET] = &pvc_mem_set,
}
};
--
2.39.1
next reply other threads:[~2024-01-09 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 9:56 sai.gowtham.ch [this message]
2024-01-09 11:39 ` ✗ Fi.CI.BAT: failure for lib/intel_cmds_info: Add MEM_COPY/SET support for Lunarlake Patchwork
2024-01-09 12:24 ` ✓ CI.xeBAT: success " Patchwork
2024-01-10 18:30 ` [PATCH i-g-t] " Zbigniew Kempczyński
2024-01-11 6:51 ` Kumar, Janga Rahul
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=20240109095602.9620-1-sai.gowtham.ch@intel.com \
--to=sai.gowtham.ch@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