Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [PATCH i-g-t] tests/kms_ccs: Test XRGB2101010
Date: Mon,  6 May 2024 16:37:48 +0300	[thread overview]
Message-ID: <20240506133748.30321-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

I want to enable 10bpc CCS support for i915. To that end start
testing it.

Note that we are faking things a bit because rendercopy will
still use a 8:8:8:8 format here (plumbing the full pixel format,
as opposed to just bpp, would require quite a bit more work).
However this seems to work fine, I suspect due to:
- we only do 1:1: copies of data
- the compression is lossless

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 tests/intel/kms_ccs.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tests/intel/kms_ccs.c b/tests/intel/kms_ccs.c
index a5cb3b3b4f27..c91370a9abe7 100644
--- a/tests/intel/kms_ccs.c
+++ b/tests/intel/kms_ccs.c
@@ -197,6 +197,7 @@ static const struct {
 static const uint32_t formats[] = {
 	DRM_FORMAT_XYUV8888,
 	DRM_FORMAT_XRGB8888,
+	DRM_FORMAT_XRGB2101010,
 	DRM_FORMAT_YUYV,
 	DRM_FORMAT_NV12,
 	DRM_FORMAT_P012,
@@ -635,6 +636,7 @@ static uint32_t blt_compression_format(struct blt_copy_data *blt,
 {
 	switch (fb->drm_format) {
 	case DRM_FORMAT_XRGB8888:
+	case DRM_FORMAT_XRGB2101010:
 	case DRM_FORMAT_P010:
 	case DRM_FORMAT_P012:
 	case DRM_FORMAT_P016:
@@ -849,7 +851,8 @@ static bool try_config(data_t *data, enum test_fb_flags fb_flags,
 		return false;
 
 	if (is_ccs_cc_modifier(data->ccs_modifier) &&
-	    data->format != DRM_FORMAT_XRGB8888)
+	    data->format != DRM_FORMAT_XRGB8888 &&
+	    data->format != DRM_FORMAT_XRGB2101010)
 		return false;
 
 	if ((fb_flags & FB_MISALIGN_AUX_STRIDE) ||
-- 
2.43.2


             reply	other threads:[~2024-05-06 13:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 13:37 Ville Syrjala [this message]
2024-05-06 15:41 ` ✗ Fi.CI.BAT: failure for tests/kms_ccs: Test XRGB2101010 Patchwork
2024-05-06 16:55 ` ✓ CI.xeBAT: success " Patchwork
2024-05-06 18:39 ` ✗ CI.xeFULL: failure " Patchwork
2024-05-06 21:56 ` ✓ Fi.CI.BAT: success for tests/kms_ccs: Test XRGB2101010 (rev2) Patchwork
2024-05-06 22:47 ` ✗ CI.xeBAT: failure " Patchwork
2024-05-07  3:17 ` ✗ CI.xeFULL: " Patchwork
2024-05-07  7:09 ` ✗ Fi.CI.IGT: " Patchwork
2024-05-08 11:45 ` [PATCH i-g-t] tests/kms_ccs: Test XRGB2101010 Juha-Pekka Heikkila

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=20240506133748.30321-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.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