From: Karthik B S <karthik.b.s@intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: Nidhi Gupta <nidhi1.gupta@intel.com>
Subject: Re: [igt-dev] [i-g-t 2/2] tests/kms_cursor_edge_walk: Limit the execution to two pipes
Date: Fri, 10 Feb 2023 13:48:58 +0530 [thread overview]
Message-ID: <c10f5522-64e4-b4b8-6fbe-72fac1b33f9e@intel.com> (raw)
In-Reply-To: <20230210042419.1744563-2-bhanuprakash.modem@intel.com>
On 2/10/2023 9:54 AM, Bhanuprakash Modem wrote:
> To optimize the test execution time, limit the execution to
> two (first & last) pipes. This patch will also provide an
> option (command line flag '--extended') to execute on all
> pipes.
>
> Example:
> ./kms_cursor_edge_walk --extended --run-subtest 64x64-left-edge
>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
> ---
> tests/kms_cursor_edge_walk.c | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_cursor_edge_walk.c b/tests/kms_cursor_edge_walk.c
> index 96812776c..304c0ea8f 100644
> --- a/tests/kms_cursor_edge_walk.c
> +++ b/tests/kms_cursor_edge_walk.c
> @@ -60,6 +60,10 @@ enum {
> EDGE_BOTTOM = 0x8,
> };
>
> +static bool extended;
> +static enum pipe active_pipes[IGT_MAX_PIPES];
> +static uint32_t last_pipe;
> +
> static void create_cursor_fb(data_t *data, int cur_w, int cur_h)
> {
> cairo_t *cr;
> @@ -284,6 +288,9 @@ static int opt_handler(int opt, int opt_index, void *_data)
> case 'd':
> data->disable = true;
> break;
> + case 'e':
> + extended = true;
> + break;
> case 'j':
> data->jump = true;
> break;
> @@ -300,12 +307,14 @@ static const struct option long_opts[] = {
> { .name = "colored", .val = 'c' },
> { .name = "disable", .val = 'd'},
> { .name = "jump", .val = 'j' },
> + { .name = "extended", .val = 'e'},
> {}
> };
> static const char *help_str =
> " --colored\t\tUse a colored cursor (disables CRC checks)\n"
> " --disable\t\tDisable the cursor between each step\n"
> - " --jump\t\tJump the cursor to middle of the screen between each step)\n";
> + " --jump\t\tJump the cursor to middle of the screen between each step)\n"
> + " --extended\t\tRun on all pipes.(Default it will Run only two pipes)\n";
>
> igt_main_args("", long_opts, help_str, opt_handler, &data)
> {
> @@ -322,6 +331,7 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>
> igt_fixture {
> int ret;
> + enum pipe pipe;
>
> data.drm_fd = drm_open_driver_master(DRIVER_ANY);
>
> @@ -340,6 +350,12 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
>
> igt_display_require(&data.display, data.drm_fd);
> igt_display_require_output(&data.display);
> +
> + /* Get active pipes. */
> + last_pipe = 0;
> + for_each_pipe(&data.display, pipe)
> + active_pipes[last_pipe++] = pipe;
> + last_pipe--;
> }
>
> for (i = 0; i < ARRAY_SIZE(tests); i++) {
> @@ -353,6 +369,10 @@ igt_main_args("", long_opts, help_str, opt_handler, &data)
> igt_subtest_with_dynamic_f("%dx%d-%s", data.curw,
> data.curh, tests[i].name) {
> for_each_pipe_with_single_output(&data.display, data.pipe, data.output) {
> + if (!extended && data.pipe != active_pipes[0] &&
> + data.pipe != active_pipes[last_pipe])
> + continue;
> +
> igt_dynamic_f("pipe-%s-%s",
> kmstest_pipe_name(data.pipe),
> data.output->name)
next prev parent reply other threads:[~2023-02-10 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 4:24 [igt-dev] [i-g-t 1/2] tests/kms_cursor_edge_walk: Re-org dynamic subtests Bhanuprakash Modem
2023-02-10 4:24 ` [igt-dev] [i-g-t 2/2] tests/kms_cursor_edge_walk: Limit the execution to two pipes Bhanuprakash Modem
2023-02-10 8:18 ` Karthik B S [this message]
2023-02-10 8:10 ` [igt-dev] [i-g-t 1/2] tests/kms_cursor_edge_walk: Re-org dynamic subtests Karthik B S
2023-02-10 15:22 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] " Patchwork
2023-02-10 22:22 ` [igt-dev] ✓ Fi.CI.IGT: " 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=c10f5522-64e4-b4b8-6fbe-72fac1b33f9e@intel.com \
--to=karthik.b.s@intel.com \
--cc=bhanuprakash.modem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox