Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
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] [v4 04/10] tests/i915/kms_dsc: update if condition
Date: Fri, 28 Jul 2023 14:15:26 +0530	[thread overview]
Message-ID: <5ccdedfa-f6a0-ceeb-57e2-79b8c32480db@intel.com> (raw)
In-Reply-To: <20230728074913.939188-5-swati2.sharma@intel.com>


On 7/28/2023 1:19 PM, Swati Sharma wrote:
> Check is_dsc_output_format_supported() iff test flag is set to
> OUTPUT_FORMAT.
>
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> ---
>   tests/i915/kms_dsc.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/kms_dsc.c b/tests/i915/kms_dsc.c
> index 7b9bae91a..266918f74 100644
> --- a/tests/i915/kms_dsc.c
> +++ b/tests/i915/kms_dsc.c
> @@ -238,8 +238,9 @@ static void test_dsc(data_t *data, uint32_t test_type, int bpc,
>   		if (!is_dsc_supported_by_sink(data->drm_fd, data->output))
>   			continue;
>   
> -		if (!is_dsc_output_format_supported(data->drm_fd, data->disp_ver,
> -						    data->output, data->output_format))
> +		if ((test_type & TEST_DSC_OUTPUT_FORMAT) &&
> +		    (!is_dsc_output_format_supported(data->drm_fd, data->disp_ver,
> +						     data->output, data->output_format)))
>   			continue;

The change look good.

Makes sense to check for output format constraint, only when we are 
forcing the output format.

>   
>   		if (!check_gen11_dp_constraint(data->drm_fd, data->output, data->pipe))

Perhaps this check and the first check: is_dsc_output_format_supported 
can be together.

Also realized that check_gen11_bpc_constraint which come later should 
not be in the loop, as it does not depend on either pipe or output.

So lets move that outside the loop.


Regards,

Ankit

  reply	other threads:[~2023-07-28  8:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  7:49 [igt-dev] [v4 00/10] DSC Fractional BPP Val Support Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 01/10] tests/i915/kms_dsc: add new test flag Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 02/10] tests/i915/kms_dsc: use uint32_t " Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 03/10] tests/i915/kms_dsc: use #define for default bpc Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 04/10] tests/i915/kms_dsc: update if condition Swati Sharma
2023-07-28  8:45   ` Nautiyal, Ankit K [this message]
2023-07-28  7:49 ` [igt-dev] [v4 05/10] tests/i915/kms_dsc: use igt_get_pipe_current_bpc() Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 06/10] tests/i915/kms_dsc: add test validating output formats with input bpc Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 07/10] lib/dsc: add helpers for vdsc fractional bpp debugfs entry Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 08/10] tests/i915/kms_dsc: enable validation for vdsc fractional bpp Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 09/10] tests/i915/kms_dsc: add test to validate fractional bpp with input bpc Swati Sharma
2023-07-28  7:49 ` [igt-dev] [v4 10/10] tests/i915/kms_dsc: add test summary Swati Sharma

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=5ccdedfa-f6a0-ceeb-57e2-79b8c32480db@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