Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Sean Paul <sean@poorly.run>, <igt-dev@lists.freedesktop.org>
Cc: Sean Paul <seanpaul@chromium.org>
Subject: Re: [igt-dev] [PATCH 3/6] tests/kms_vrr: Allow test rate to be altered from the command line
Date: Thu, 7 Sep 2023 00:37:59 +0530	[thread overview]
Message-ID: <4d4589ef-ee8c-4528-8f85-6412e1fc5932@intel.com> (raw)
In-Reply-To: <20230825183934.1271156-4-sean@poorly.run>


On Sat-26-08-2023 12:06 am, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
> 
> Instead of always using the midpoint, introduce optional argument
> --refresh-rate to allow callers to specify the target refresh rate for
> the test.
> 
> Cc: Mark Yacoub <markyacoub@chromium.org>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
>   tests/kms_vrr.c | 44 ++++++++++++++++++++++++++++++++++++--------
>   1 file changed, 36 insertions(+), 8 deletions(-)
> 
> diff --git a/tests/kms_vrr.c b/tests/kms_vrr.c
> index 8ef5972aa..d62ded180 100644
> --- a/tests/kms_vrr.c
> +++ b/tests/kms_vrr.c
> @@ -103,7 +103,7 @@ typedef struct range {
>   
>   typedef struct vtest_ns {
>   	uint64_t min;
> -	uint64_t mid;
> +	uint64_t rate_ns;
>   	uint64_t max;
>   } vtest_ns_t;
>   
> @@ -250,10 +250,18 @@ static void prepare_test(data_t *data, igt_output_t *output, enum pipe pipe)
>   	data->range = get_vrr_range(data, output);
>   
>   	data->vtest_ns.min = rate_from_refresh(data->range.min);
> -	data->vtest_ns.mid = rate_from_refresh(
> -				(data->range.min + data->range.max) / 2);
>   	data->vtest_ns.max = rate_from_refresh(data->range.max);
>   
> +	/* If unspecified on the command line, default rate to the midpoint */
> +	if (data->vtest_ns.rate_ns == 0) {
> +		range_t *range = &data->range;
> +		data->vtest_ns.rate_ns = rate_from_refresh(
> +						(range->min + range->max) / 2);
> +	}
> +	igt_assert_f(data->vtest_ns.rate_ns <= data->vtest_ns.min &&
> +		     data->vtest_ns.rate_ns >= data->vtest_ns.max,
> +		     "Invalid test rate specified!\n");
> +
>   	/* Override mode with max vrefresh.
>   	 *   - vrr_min range should be less than the override mode vrefresh.
>   	 *   - Limit the vrr_max range with the override mode vrefresh.
> @@ -406,7 +414,7 @@ test_basic(data_t *data, enum pipe pipe, igt_output_t *output, uint32_t flags)
>   	prepare_test(data, output, pipe);
>   	range = data->range;
>   	vtest_ns = data->vtest_ns;
> -	rate = vtest_ns.mid;
> +	rate = vtest_ns.rate_ns;
>   
>   	igt_info("VRR Test execution on %s, PIPE_%s with VRR range: (%u-%u) Hz\n",
>   		 output->name, kmstest_pipe_name(pipe), range.min, range.max);
> @@ -457,7 +465,7 @@ test_basic(data_t *data, enum pipe pipe, igt_output_t *output, uint32_t flags)
>   	}
>   
>   	if (flags & ~TEST_NEGATIVE) {
> -		rate = vtest_ns.mid;
> +		rate = vtest_ns.rate_ns;
>   		result = flip_and_measure(data, output, pipe, rate, TEST_DURATION_NS);
>   		igt_assert_f(result > 75,
>   			     "Refresh rate (%u Hz) %"PRIu64"ns: Target VRR on threshold not reached, result was %u%%\n",
> @@ -478,7 +486,7 @@ test_basic(data_t *data, enum pipe pipe, igt_output_t *output, uint32_t flags)
>   	 * a VRR capable panel.
>   	 */
>   	set_vrr_on_pipe(data, pipe, (flags & TEST_NEGATIVE)? true : false);
> -	rate = vtest_ns.mid;
> +	rate = vtest_ns.rate_ns;
>   	result = flip_and_measure(data, output, pipe, rate, TEST_DURATION_NS);
>   	igt_assert_f(result < 10,
>   		     "Refresh rate (%u Hz) %"PRIu64"ns: Target VRR %s threshold exceeded, result was %u%%\n",
> @@ -530,10 +538,30 @@ run_vrr_test(data_t *data, test_t test, uint32_t flags)
>   	}
>   }
>   
> -igt_main
> +static int opt_handler(int opt, int opt_index, void *_data)
>   {
> -	data_t data = {};
> +	data_t *data = _data;
> +
> +	switch (opt) {
> +	case 'r':
> +		data->vtest_ns.rate_ns = rate_from_refresh(atoi(optarg));
> +		break;
> +	}
> +	return IGT_OPT_HANDLER_SUCCESS;
> +}
>   
> +static const struct option long_opts[] = {
> +	{ .name = "refresh-rate", .has_arg = true, .val = 'r', },
> +	{}
> +};
> +
> +static const char help_str[] =
> +	"  --refresh-rate <refresh-hz>\t\tThe refresh rate to flip at\n";
> +
> +static data_t data;
> +
> +igt_main_args("", long_opts, help_str, opt_handler, &data)
-----------------^

Please mention the supported short opts. i.e "r:"

By fixing the above comment, this patch is
Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>

- Bhanu

> +{
>   	igt_fixture {
>   		data.drm_fd = drm_open_driver_master(DRIVER_ANY);
>   

  reply	other threads:[~2023-09-06 19:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 18:36 [igt-dev] [PATCH 0/6] tests/kms_vrr: Modify kms_vrr to allow flicker Sean Paul
2023-08-25 18:36 ` [igt-dev] [PATCH 1/6] tests/kms_vrr: Move fb0 and fb1 to an array Sean Paul
2023-09-06 19:07   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 2/6] tests/kms_vrr: Move vtest_ns into data_t Sean Paul
2023-09-06 19:07   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 3/6] tests/kms_vrr: Allow test rate to be altered from the command line Sean Paul
2023-09-06 19:07   ` Modem, Bhanuprakash [this message]
2023-08-25 18:36 ` [igt-dev] [PATCH 4/6] tests/kms_vrr: Allow test duration to be specified " Sean Paul
2023-09-06 19:08   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 5/6] tests/kms_vrr: Change the pattern displayed in the test Sean Paul
2023-09-06 19:08   ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 6/6] test/kms_vrr: Add ability to flip static image for flicker profiling Sean Paul
2023-08-25 19:30 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_vrr: Modify kms_vrr to allow flicker Patchwork
2023-08-25 19:46 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-08-25 19:55 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-08-26 13:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-31 17:15 ` [igt-dev] [PATCH 0/6] " Sean Paul
2023-09-06 19:08 ` Modem, Bhanuprakash

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=4d4589ef-ee8c-4528-8f85-6412e1fc5932@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sean@poorly.run \
    --cc=seanpaul@chromium.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