From: Matthew Auld <matthew.auld@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
Subject: [PATCH i-g-t v2 1/3] lib/intel_device_info: set has_flatccs on LNL
Date: Thu, 1 Feb 2024 10:30:15 +0000 [thread overview]
Message-ID: <20240201103017.321466-1-matthew.auld@intel.com> (raw)
Xe2 supports flat CCS based compression, including igpu. Currently
HAS_FLATCCS() is incorrectly returning false on LNL.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
---
lib/intel_device_info.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/intel_device_info.c b/lib/intel_device_info.c
index a669797c3..64b5246b7 100644
--- a/lib/intel_device_info.c
+++ b/lib/intel_device_info.c
@@ -509,6 +509,7 @@ static const struct intel_device_info intel_lunarlake_info = {
.graphics_rel = 4,
.display_ver = 20,
.has_4tile = true,
+ .has_flatccs = true,
.is_lunarlake = true,
.codename = "lunarlake",
.cmds_info = &xe2_cmds_info,
--
2.43.0
next reply other threads:[~2024-02-01 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 10:30 Matthew Auld [this message]
2024-02-01 10:30 ` [PATCH i-g-t v2 2/3] tests/intel/xe_ccs: require flat CCS on xe2 Matthew Auld
2024-02-01 21:14 ` Zbigniew Kempczyński
2024-02-02 5:34 ` Jahagirdar, Akshata
2024-02-02 7:31 ` Zbigniew Kempczyński
2024-02-05 5:45 ` Jahagirdar, Akshata
2024-02-02 9:48 ` Zbigniew Kempczyński
2024-02-01 10:30 ` [PATCH i-g-t v2 3/3] tests/intel/xe_pat: assert flat CSS support for xe2 Matthew Auld
2024-02-02 5:49 ` Jahagirdar, Akshata
2024-02-01 13:06 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/3] lib/intel_device_info: set has_flatccs on LNL Patchwork
2024-02-01 13:46 ` ✓ CI.xeBAT: " Patchwork
2024-02-01 15:20 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-02 5:33 ` [PATCH i-g-t v2 1/3] " Jahagirdar, Akshata
2024-02-02 11:24 ` Kamil Konieczny
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=20240201103017.321466-1-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=akshata.jahagirdar@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