Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Swati Sharma <swati2.sharma@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [v10 5/5] tests/intel/kms_dsc: remove redundant documentation
Date: Mon, 18 Sep 2023 13:51:28 +0300	[thread overview]
Message-ID: <a9a3561e-70b7-64d7-c40f-dea543bd2f19@gmail.com> (raw)
In-Reply-To: <20230918054926.238027-6-swati2.sharma@intel.com>

Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>

On 18.9.2023 8.49, Swati Sharma wrote:
> With the introduction of testplan documentation, test documentation
> seems redundant. Remove it.
> 
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
>   tests/intel/kms_dsc.c | 21 ---------------------
>   1 file changed, 21 deletions(-)
> 
> diff --git a/tests/intel/kms_dsc.c b/tests/intel/kms_dsc.c
> index 9b137ef87..59a1e670b 100644
> --- a/tests/intel/kms_dsc.c
> +++ b/tests/intel/kms_dsc.c
> @@ -69,27 +69,6 @@ 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, 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 (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. 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).
> - * Lastly, fractional bpp is tested with default parameters.
> - * In this, driver will ignore integer compressed bpp value and
> - * will do modeset with fractional bpp only. Test is added to
> - * validate fractional bpp with different input bpc (12/10/8).
> - */
> -
>   typedef struct {
>   	int drm_fd;
>   	uint32_t devid;

  reply	other threads:[~2023-09-18 10:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  5:49 [igt-dev] [v10 0/5] DSC Fractional BPP Val Support Swati Sharma
2023-09-18  5:49 ` [igt-dev] [v10 1/5] lib/dsc: fix documentation style Swati Sharma
2023-09-18  5:49 ` [igt-dev] [v10 2/5] lib/dsc: add helpers for vdsc fractional bpp debugfs entry Swati Sharma
2023-09-18  5:49 ` [igt-dev] [v10 3/5] tests/intel/kms_dsc: enable validation for vdsc fractional bpp Swati Sharma
2023-09-18  5:49 ` [igt-dev] [v10 4/5] tests/intel/kms_dsc: add test to validate fractional bpp with input bpc Swati Sharma
2023-09-18  5:49 ` [igt-dev] [v10 5/5] tests/intel/kms_dsc: remove redundant documentation Swati Sharma
2023-09-18 10:51   ` Juha-Pekka Heikkila [this message]
2023-09-18  8:41 ` [igt-dev] ✓ CI.xeBAT: success for DSC Fractional BPP Val Support (rev12) Patchwork
2023-09-18  8:44 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-19  9:24 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-20  5:01 ` 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=a9a3561e-70b7-64d7-c40f-dea543bd2f19@gmail.com \
    --to=juhapekka.heikkila@gmail.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