From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Swati Sharma <swati2.sharma@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [v2 9/9] tests/i915/kms_dsc: add test summary
Date: Mon, 24 Jul 2023 12:07:02 +0530 [thread overview]
Message-ID: <014c1ca0-4d86-5bef-03bb-9427bf5f3318@intel.com> (raw)
In-Reply-To: <20230704173107.842296-10-swati2.sharma@intel.com>
On 7/4/2023 11:01 PM, Swati Sharma wrote:
> Add test summary giving overall summary of subtests.
>
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
> tests/i915/kms_dsc.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/tests/i915/kms_dsc.c b/tests/i915/kms_dsc.c
> index d46a5e74d..2933c6cfb 100644
> --- a/tests/i915/kms_dsc.c
> +++ b/tests/i915/kms_dsc.c
> @@ -43,6 +43,27 @@ IGT_TEST_DESCRIPTION("Test to validate display stream compression");
> #define TEST_DSC_OUTPUT_FORMAT (1<<2)
> #define TEST_DSC_FRACTIONAL_BPP (1<<3)
>
> +/*
> + * Starting from gen11, i915 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 the following
> + * scenarios. In all the scenarios, we are forcing dsc.
> + * (i) basic modeset (ii) input bpc (iii) pixel formats
> + * (iv) output formats (v) fractional bpp
> + * 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. With the support of DSC1.2 from MTL, we can
Can drop ref to DSC1.2 here.
Otherwise LGTM.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Regards,
Ankit
> + * verify fractional bpp and DSC YCBCR420 output format. The tests
> + * are executed with the RGB444 output format by default. However,
> + * in the output-format subtest, we verify output formats
> + * (RGB/YCBCR444/YCBCR420). Fractional bpp is tested with default
> + * parameter. In this, driver will ignore integer compressed bpp
> + * value and will do modeset with fractional bpp only. Also,
> + * tests are added to validate output format and fractional bpp
> + * with different input bpc.
> + */
> +
> typedef struct {
> int drm_fd;
> uint32_t devid;
next prev parent reply other threads:[~2023-07-24 6:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 17:30 [igt-dev] [v2 0/9] DSC Fractional BPP Val Support Swati Sharma
2023-07-04 17:30 ` [igt-dev] [v2 1/9] tests/i915/kms_dsc: add new test flag Swati Sharma
2023-07-24 5:08 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 2/9] tests/i915/kms_dsc: use uint32_t " Swati Sharma
2023-07-24 5:18 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 3/9] tests/i915/kms_dsc: use #define for default bpc Swati Sharma
2023-07-24 5:23 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 4/9] tests/i915/kms_dsc: add get_status() Swati Sharma
2023-07-24 5:29 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 5/9] tests/i915/kms_dsc: add subtest Swati Sharma
2023-07-24 5:40 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 6/9] lib/dsc: add helpers for vdsc fractional bpp debugfs entry Swati Sharma
2023-07-24 6:12 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 7/9] tests/i915/kms_dsc: enable validation for vdsc fractional bpp Swati Sharma
2023-07-24 6:32 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 8/9] tests/i915/kms_dsc: add subtest Swati Sharma
2023-07-24 5:32 ` Nautiyal, Ankit K
2023-07-04 17:31 ` [igt-dev] [v2 9/9] tests/i915/kms_dsc: add test summary Swati Sharma
2023-07-24 6:37 ` Nautiyal, Ankit K [this message]
2023-07-04 18:22 ` [igt-dev] ✗ Fi.CI.BAT: failure for DSC Fractional BPP Val Support (rev3) Patchwork
2023-07-20 12:12 ` [igt-dev] ✗ GitLab.Pipeline: warning for DSC Fractional BPP Val Support (rev4) Patchwork
2023-07-20 12:44 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-07-20 13:02 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-07-20 17:05 ` [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=014c1ca0-4d86-5bef-03bb-9427bf5f3318@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=swati2.sharma@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