From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: lucas.demarchi@intel.com
Subject: [igt-dev] [PATCH 1/2] lib/igt_draw: Use intel_get_uc_mocs to get MOCS value
Date: Thu, 19 Jan 2023 22:27:01 +0530 [thread overview]
Message-ID: <20230119165702.9558-2-jeevan.b@intel.com> (raw)
In-Reply-To: <20230119165702.9558-1-jeevan.b@intel.com>
Use intel_get_uc_mocs instead of hardcoding to get table entry.
Signed-off-by: Jeevan B <jeevan.b@intel.com>
Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
lib/igt_draw.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/igt_draw.c b/lib/igt_draw.c
index 975d65cd..58ce0539 100644
--- a/lib/igt_draw.c
+++ b/lib/igt_draw.c
@@ -36,6 +36,7 @@
#include "i830_reg.h"
#include "i915/gem_create.h"
#include "i915/gem_mman.h"
+#include "i915/intel_mocs.h"
#ifndef PAGE_ALIGN
#ifndef PAGE_SIZE
@@ -702,8 +703,7 @@ static void draw_rect_blt(int fd, struct cmd_data *cmd_data,
pitch = tiling ? buf->stride / 4 : buf->stride;
intel_bb_out(ibb, XY_FAST_COLOR_BLT | blt_cmd_depth);
- /* DG2 MOCS entry 2 is "UC - Non-Coherent; GO:Memory" */
- intel_bb_out(ibb, blt_cmd_tiling | 2 << 21 | (pitch-1));
+ intel_bb_out(ibb, blt_cmd_tiling | intel_get_uc_mocs(fd) << 21 | (pitch-1));
intel_bb_out(ibb, (rect->y << 16) | rect->x);
intel_bb_out(ibb, ((rect->y + rect->h) << 16) | (rect->x + rect->w));
intel_bb_emit_reloc_fenced(ibb, dst->handle, 0,
--
2.19.1
next prev parent reply other threads:[~2023-01-19 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:57 [igt-dev] [PATCH 0/2] lib/igt_draw: Change MOCS settings for MTL Jeevan B
2023-01-19 16:57 ` Jeevan B [this message]
2023-01-19 16:57 ` [igt-dev] [PATCH 2/2] lib/igt_draw: Add MOCS values " Jeevan B
2023-01-19 17:47 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_draw: Change MOCS settings " Patchwork
2023-01-20 21:44 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-23 13:52 ` Kamil Konieczny
2023-01-24 3:32 ` Yedireswarapu, SaiX Nandan
2023-01-24 1:59 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 9:10 [igt-dev] [PATCH 0/2] " Jeevan B
2023-01-13 9:10 ` [igt-dev] [PATCH 1/2] lib/igt_draw: Use intel_get_uc_mocs to get MOCS value Jeevan B
2023-01-13 11:32 ` Zbigniew Kempczyński
2023-01-16 19:15 ` Kamil Konieczny
2023-01-18 10:12 ` B, Jeevan
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=20230119165702.9558-2-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@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