Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kunal Joshi <kunal1.joshi@intel.com>
To: Arundhati Hagaragi <arundhati.hagaragi@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/kms_universal_plane:Added subtest description
Date: Mon, 1 Feb 2021 10:43:16 +0530	[thread overview]
Message-ID: <20210201051316.GA593586@intel.com> (raw)
In-Reply-To: <20210129074917.2480118-1-arundhati.hagaragi@intel.com>

On 2021-01-29 at 13:19:17 +0530, Arundhati Hagaragi wrote:
> Added description for all subtests
> 
> Signed-off-by: Arundhati Hagaragi <arundhati.hagaragi@intel.com>
> Cc: Joshi, Kunal1 <kunal1.joshi@intel.com>
> 
> v2: removed extra bracket and semicolon.
> ---
>  tests/kms_universal_plane.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/tests/kms_universal_plane.c b/tests/kms_universal_plane.c
> index 46d6d180..aae3fc52 100644
> --- a/tests/kms_universal_plane.c
> +++ b/tests/kms_universal_plane.c
> @@ -758,26 +758,32 @@ run_tests_for_pipe(data_t *data, enum pipe pipe)
>  		igt_require_f(valid_tests, "no valid crtc/connector combinations found\n");
>  	}
>  
> +	igt_describe("Check the switching between different primary plane fbs with CRTC off");
>  	igt_subtest_f("universal-plane-pipe-%s-functional",
>  		      kmstest_pipe_name(pipe))
>  		for_each_valid_output_on_pipe(&data->display, pipe, output)
>  			functional_test_pipe(data, pipe, output);
>  
> +	igt_describe("Test for scale-up or scale-down using universal plane API without covering CRTC");
>  	igt_subtest_f("universal-plane-pipe-%s-sanity",
>  		      kmstest_pipe_name(pipe))
>  		for_each_valid_output_on_pipe(&data->display, pipe, output)
>  			sanity_test_pipe(data, pipe, output);
>  
> +	igt_describe("Check pageflips while primary plane is disabled before IOCTL or between IOCTL"
> +			" and pageflip execution");
>  	igt_subtest_f("disable-primary-vs-flip-pipe-%s",
>  		      kmstest_pipe_name(pipe))
>  		for_each_valid_output_on_pipe(&data->display, pipe, output)
>  			pageflip_test_pipe(data, pipe, output);
>  
> +	igt_describe("Check for cursor leaks after performing cursor operations");
>  	igt_subtest_f("cursor-fb-leak-pipe-%s",
>  		      kmstest_pipe_name(pipe))
>  		for_each_valid_output_on_pipe(&data->display, pipe, output)
>  			cursor_leak_test_pipe(data, pipe, output);
>  
> +	igt_describe("Check if pageflip succeeds in windowed setting");
>  	igt_subtest_f("universal-plane-gen9-features-pipe-%s",
>  		      kmstest_pipe_name(pipe))
>  		for_each_valid_output_on_pipe(&data->display, pipe, output)
> -- 
> 2.25.1
> 

LGTM
Reviewed-by: Kunal Joshi <kunal1.joshi@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      parent reply	other threads:[~2021-02-01  5:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  7:49 [igt-dev] [PATCH i-g-t v2] tests/kms_universal_plane:Added subtest description Arundhati Hagaragi
2021-01-29  9:00 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_universal_plane:Added subtest description (rev2) Patchwork
2021-01-29 15:19 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-02-01  5:13 ` Kunal Joshi [this message]

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=20210201051316.GA593586@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=arundhati.hagaragi@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