All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Nidhi Gupta <nidhi1.gupta@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_concurrent: Skip the subtest if the resolution is not supported
Date: Thu, 5 May 2022 11:23:38 +0530	[thread overview]
Message-ID: <b2d623fb-b5b9-5853-e2d5-4b62b8f63d86@intel.com> (raw)
In-Reply-To: <20220504220013.20671-1-nidhi1.gupta@intel.com>

On 5/5/2022 3:30 AM, Nidhi Gupta wrote:
> The kms_concurrent is about testing mode setting with
> reducing the resolution and then again increasing it,
> for this the test will take the high resolution supported
> by the connector and then calculate the lowest resolution,
> if the calculated resolution is not supported by the connector
> it will assign the default resolution of 1024x 768 without
> checking.
>
> Adding the check to skip the subtest if the default
> resolution is not supported by the connector.

Hi,

Please update the commit message. We're skipping if , "mode_lo->vdisplay 
 > mode_hi->vdisplay". Mention the same.

Also, I think its better to move this check inside "get_lowres_mode()".  
Before returning 1024x768 mode, we could use the same check used in the 
loop, "mode->vdisplay < limit", and skip the test if this is not met.

Thanks,
Karthik.B.S
>
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
>   tests/kms_concurrent.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/tests/kms_concurrent.c b/tests/kms_concurrent.c
> index 82b2021e..fdef6b26 100644
> --- a/tests/kms_concurrent.c
> +++ b/tests/kms_concurrent.c
> @@ -272,6 +272,8 @@ test_resolution_with_output(data_t *data, enum pipe pipe, int max_planes, igt_ou
>   		mode_hi = igt_output_get_mode(output);
>   		mode_lo = get_lowres_mode(data, mode_hi, output);
>   
> +		igt_skip_on(mode_lo->vdisplay > mode_hi->vdisplay);
> +
>   		/* switch to lower resolution */
>   		igt_output_override_mode(output, mode_lo);
>   		free(mode_lo);


  parent reply	other threads:[~2022-05-05  5:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 22:00 [igt-dev] [PATCH i-g-t] tests/kms_concurrent: Skip the subtest if the resolution is not supported Nidhi Gupta
2022-05-04 22:40 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-05-05  3:33 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-05-05  5:53 ` Karthik B S [this message]
2022-05-05 12:30   ` [igt-dev] [PATCH i-g-t] " Gupta, Nidhi1
2022-05-06 11:39     ` Kahola, Mika
2022-05-09 12:01 Nidhi Gupta

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=b2d623fb-b5b9-5853-e2d5-4b62b8f63d86@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=nidhi1.gupta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.