From: Swati Sharma <swati2.sharma@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [v5 07/10] tests/i915/kms_dsc: add test summary
Date: Fri, 28 Jul 2023 15:04:46 +0530 [thread overview]
Message-ID: <20230728093449.950073-8-swati2.sharma@intel.com> (raw)
In-Reply-To: <20230728093449.950073-1-swati2.sharma@intel.com>
Add test summary giving overall summary of subtests.
v2: -drop DSC1.2 reference (Ankit)
Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
---
tests/i915/kms_dsc.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/tests/i915/kms_dsc.c b/tests/i915/kms_dsc.c
index 25fd410a9..7c51c2ddc 100644
--- a/tests/i915/kms_dsc.c
+++ b/tests/i915/kms_dsc.c
@@ -42,6 +42,24 @@ IGT_TEST_DESCRIPTION("Test to validate display stream compression");
#define TEST_DSC_FORMAT (1<<1)
#define TEST_DSC_OUTPUT_FORMAT (1<<2)
+/*
+ * Starting from gen11, intel driver supports DSC1.1. For validating
+ * DSC, the first step is to verify if the sink supports DSC.
+ * If the sink does support DSC, we will validate different
+ * scenarios by forcing dsc. Outline of the tests is as follows:
+ * (i) basic modeset (ii) input bpc (iii) pixel formats
+ * (iv) output formats
+ * In the basic subtest, we perform modeset with default parameters.
+ * Input bpc and pixel formats subtests, we perform modeset
+ * with different input bpc (12/10/8) and pixel formats (YUV/RGB),
+ * respectively. From MTL+, we can verify DSC YCBCR420 output format.
+ * The tests are executed with the RGB444 output format by default.
+ * However, in the output-format subtest, we verify different
+ * output formats (RGB/YCBCR444/YCBCR420). Also, test is added to
+ * validate output formats with different input bpc (12/10/8).
+ */
+
+
typedef struct {
int drm_fd;
uint32_t devid;
--
2.25.1
next prev parent reply other threads:[~2023-07-28 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 9:34 [igt-dev] [v5 00/10] DSC Fractional BPP Val Support Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 01/10] tests/i915/kms_dsc: add new test flag Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 02/10] tests/i915/kms_dsc: use uint32_t " Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 03/10] tests/i915/kms_dsc: use #define for default bpc Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 04/10] tests/i915/kms_dsc: update if conditions Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 05/10] tests/i915/kms_dsc: use igt_get_pipe_current_bpc() Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 06/10] tests/i915/kms_dsc: add test validating output formats with input bpc Swati Sharma
2023-07-28 9:34 ` Swati Sharma [this message]
2023-07-28 9:34 ` [igt-dev] [v5 08/10] lib/dsc: add helpers for vdsc fractional bpp debugfs entry Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 09/10] tests/i915/kms_dsc: enable validation for vdsc fractional bpp Swati Sharma
2023-07-28 9:34 ` [igt-dev] [v5 10/10] tests/i915/kms_dsc: add test to validate fractional bpp with input bpc Swati Sharma
2023-07-28 10:28 ` [igt-dev] ○ CI.xeBAT: info for DSC Fractional BPP Val Support (rev7) Patchwork
2023-07-28 10:34 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-01 6:33 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-01 8:15 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=20230728093449.950073-8-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