From: Swati Sharma <swati2.sharma@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [v2] tests/intel/kms_dsc: add new constraint
Date: Fri, 5 Jan 2024 14:32:43 +0530 [thread overview]
Message-ID: <20240105090243.58192-1-swati2.sharma@intel.com> (raw)
If output max bpc is less than min dsc bpc (8) which is supported
by intel driver, don't execute test.
v2: -club all checks together (Ankit)
Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1066
Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
---
tests/intel/kms_dsc.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tests/intel/kms_dsc.c b/tests/intel/kms_dsc.c
index 3433e0907..b5c0fa6ab 100644
--- a/tests/intel/kms_dsc.c
+++ b/tests/intel/kms_dsc.c
@@ -63,6 +63,7 @@ IGT_TEST_DESCRIPTION("Test to validate display stream compression");
#define LEN 20
#define DEFAULT_BPC 0
+#define MIN_DSC_BPC 8
#define TEST_DSC_BASIC (0<<0)
#define TEST_DSC_BPC (1<<0)
@@ -279,8 +280,9 @@ static void test_dsc(data_t *data, uint32_t test_type, int bpc,
data->output = output;
data->pipe = pipe;
- if (!(is_dsc_supported_by_sink(data->drm_fd, data->output) &&
- check_gen11_dp_constraint(data->drm_fd, data->output, data->pipe)))
+ if (!is_dsc_supported_by_sink(data->drm_fd, data->output) ||
+ !check_gen11_dp_constraint(data->drm_fd, data->output, data->pipe) ||
+ igt_get_output_max_bpc(data->drm_fd, output->name) < MIN_DSC_BPC)
continue;
if ((test_type & TEST_DSC_OUTPUT_FORMAT) &&
--
2.25.1
next reply other threads:[~2024-01-05 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 9:02 Swati Sharma [this message]
2024-01-05 9:50 ` ✓ Fi.CI.BAT: success for tests/intel/kms_dsc: add new constraint (rev2) Patchwork
2024-01-05 9:57 ` ✓ CI.xeBAT: " Patchwork
2024-01-05 11:17 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-05 15:49 ` [v2] tests/intel/kms_dsc: add new constraint Nautiyal, Ankit K
2024-01-05 15:49 ` Nautiyal, Ankit K
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=20240105090243.58192-1-swati2.sharma@intel.com \
--to=swati2.sharma@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