From: Nidhi Gupta <nidhi1.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH v4 4/7] tests/kms_plane_alpha_blend: Limit the execution to single pipe & two planes
Date: Thu, 2 Feb 2023 10:45:06 +0530 [thread overview]
Message-ID: <20230202051509.28983-5-nidhi1.gupta@intel.com> (raw)
In-Reply-To: <20230202051509.28983-1-nidhi1.gupta@intel.com>
From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
As the execution is taking more time, limit the execution to single pipe
and two (first & last) planes.
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
tests/kms_plane_alpha_blend.c | 51 +++++++++++++++++++++++++++++++++--
1 file changed, 49 insertions(+), 2 deletions(-)
diff --git a/tests/kms_plane_alpha_blend.c b/tests/kms_plane_alpha_blend.c
index 38272ccb..dc943721 100644
--- a/tests/kms_plane_alpha_blend.c
+++ b/tests/kms_plane_alpha_blend.c
@@ -26,6 +26,8 @@
#include "igt.h"
+static bool extended = false;
+
IGT_TEST_DESCRIPTION("Test plane alpha and blending mode properties");
typedef struct {
@@ -482,8 +484,10 @@ static void run_test_on_pipe_planes(data_t *data, enum pipe pipe, igt_output_t *
{
igt_display_t *display = &data->display;
igt_plane_t *plane;
+ int first_plane = -1;
+ int last_plane = -1;
- for_each_plane_on_pipe(display, pipe, plane) {
+ for_each_plane_on_pipe(&data->display, pipe, plane) {
if (!igt_plane_has_prop(plane, IGT_PLANE_ALPHA))
continue;
@@ -496,6 +500,19 @@ static void run_test_on_pipe_planes(data_t *data, enum pipe pipe, igt_output_t *
if (must_multiply && !has_multiplied_alpha(data, plane))
continue;
+ if (first_plane < 0)
+ first_plane = j__;
+
+ last_plane = j__;
+ }
+
+ for_each_plane_on_pipe(&data->display, pipe, plane) {
+ if (igt_run_in_simulation() &&
+ j__ != first_plane && j__ != last_plane)
+ continue;
+
+ /* reset plane alpha properties between each plane */
+ reset_alpha(display, pipe);
igt_info("Testing plane %u\n", plane->index);
test(data, pipe, plane);
igt_plane_set_fb(plane, NULL);
@@ -615,12 +632,23 @@ static void run_subtests(data_t *data)
{
igt_output_t *output;
enum pipe pipe;
+ enum pipe active_pipes[IGT_MAX_PIPES];
+ uint32_t last_pipe = 0;
+
+ /* Get active pipes. */
+ for_each_pipe(&data->display, pipe)
+ active_pipes[last_pipe++] = pipe;
+ last_pipe--;
for (int i = 0; i < ARRAY_SIZE(subtests); i++) {
igt_describe_f("%s\n", subtests[i].desc);
igt_subtest_with_dynamic(subtests[i].name) {
for_each_pipe_with_single_output(&data->display, pipe, output) {
+ if (igt_run_in_simulation() && !extended &&
+ pipe != active_pipes[0] &&
+ pipe != active_pipes[last_pipe])
+ continue;
prepare_crtc(data, output, pipe);
if (!pipe_check(data, pipe, subtests[i].blend, subtests[i].must_multiply))
continue;
@@ -628,12 +656,31 @@ static void run_subtests(data_t *data)
igt_dynamic_f("pipe-%s-%s", kmstest_pipe_name(pipe), output->name)
run_test_on_pipe_planes(data, pipe, output, subtests[i].blend,
subtests[i].must_multiply, subtests[i].test);
+
+ if (igt_run_in_simulation())
+ break;
}
}
}
}
-igt_main
+static int opt_handler(int opt, int opt_index, void *_data)
+{
+ switch (opt) {
+ case 'e':
+ extended = true;
+ break;
+ default:
+ return IGT_OPT_HANDLER_ERROR;
+ }
+
+ return IGT_OPT_HANDLER_SUCCESS;
+}
+
+const char *help_str =
+ " -e \tExtended tests.\n";
+
+igt_main_args("e", NULL, help_str, opt_handler, NULL)
{
data_t data = {};
--
2.39.0
next prev parent reply other threads:[~2023-02-02 5:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 5:15 [igt-dev] [PATCH v4 0/7] Limit the execution to few pipes/planes Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 1/7] tests/i915/kms_draw_crc: Ignore RGB565 & XRGB2101010 formats on simulation Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 2/7] tests/kms_async_flips: Limit the execution to single pipe Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 3/7] tests/kms_pipe_crc_basic: Limit the execution to two pipes Nidhi Gupta
2023-02-02 10:33 ` Modem, Bhanuprakash
2023-02-03 2:15 ` [igt-dev] [PATCH v5 " Nidhi Gupta
2023-02-03 5:49 ` [igt-dev] [i-g-t V3 " Bhanuprakash Modem
2023-02-02 5:15 ` Nidhi Gupta [this message]
2023-02-02 6:01 ` [igt-dev] [PATCH v5 4/7] tests/kms_plane_alpha_blend: Limit the execution to single pipe & two planes Nidhi Gupta
2023-02-02 7:00 ` Nidhi Gupta
2023-02-02 15:00 ` Kamil Konieczny
2023-02-02 5:15 ` [igt-dev] [PATCH v4 5/7] tests/kms_plane_cursor: Limit the execution to two pipes Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 6/7] tests/kms_plane_scaling: Limit the execution to two pipes/planes Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 7/7] tests/i915/kms_frontbuffer_tracking: Reduce the execution time on simulation Nidhi Gupta
2023-02-02 5:51 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev2) Patchwork
2023-02-02 6:00 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Limit the execution to few pipes/planes (rev3) Patchwork
2023-02-02 6:00 ` [igt-dev] ✗ Fi.CI.BAT: failure for Limit the execution to few pipes/planes (rev2) Patchwork
2023-02-02 7:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev4) Patchwork
2023-02-02 7:26 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2023-02-02 15:45 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2023-02-03 2:40 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-03 7:16 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev6) Patchwork
2023-02-03 12:40 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-03 13:08 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev6) Patchwork
2023-02-03 17:48 ` [igt-dev] ✓ Fi.CI.IGT: success for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-04 0:12 ` [igt-dev] ✓ Fi.CI.IGT: success for Limit the execution to few pipes/planes (rev6) 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=20230202051509.28983-5-nidhi1.gupta@intel.com \
--to=nidhi1.gupta@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