From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Sean Paul <seanpaul@chromium.org>
Subject: [i-g-t v3 3/9] tests/kms_vrr: Allow test rate to be altered from the command line
Date: Mon, 18 Dec 2023 13:52:01 +0530 [thread overview]
Message-ID: <20231218082207.32719-4-bhanuprakash.modem@intel.com> (raw)
In-Reply-To: <20231218082207.32719-1-bhanuprakash.modem@intel.com>
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.
v2:
- Add short opt to the main callsite (Bhanu)
v3: (Bhanu)
- Rebase
Cc: Mark Yacoub <markyacoub@chromium.org>
Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
tests/kms_vrr.c | 46 +++++++++++++++++++++++++++++++++++++---------
1 file changed, 37 insertions(+), 9 deletions(-)
diff --git a/tests/kms_vrr.c b/tests/kms_vrr.c
index 505bad44b..014497bcd 100644
--- a/tests/kms_vrr.c
+++ b/tests/kms_vrr.c
@@ -102,7 +102,7 @@ typedef struct range {
typedef struct vtest_ns {
uint64_t min;
- uint64_t mid;
+ uint64_t rate_ns;
uint64_t max;
} vtest_ns_t;
@@ -266,10 +266,18 @@ static void prepare_test(data_t *data, igt_output_t *output, enum pipe pipe)
mode = *igt_output_get_mode(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");
+
/* Prepare resources */
igt_create_color_fb(data->drm_fd, mode.hdisplay, mode.vdisplay,
DRM_FORMAT_XRGB8888, DRM_FORMAT_MOD_LINEAR,
@@ -413,7 +421,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);
@@ -466,7 +474,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",
@@ -487,7 +495,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_FASTSET), (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",
@@ -535,7 +543,7 @@ test_seamless_rr_basic(data_t *data, enum pipe pipe, igt_output_t *output, uint3
igt_output_override_mode(output, &data->switch_modes[HIGH_RR_MODE]);
igt_assert(igt_display_try_commit_atomic(&data->display, 0, NULL) == 0);
- rate = vtest_ns.mid;
+ rate = vtest_ns.rate_ns;
result = flip_and_measure(data, output, pipe, rate, TEST_DURATION_NS);
igt_assert_f(vrr ? (result > 75) : (result < 10),
"Refresh rate (%u Hz) %"PRIu64"ns: Target VRR %s threshold %s, result was %u%%\n",
@@ -655,10 +663,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("r:", long_opts, help_str, opt_handler, &data)
+{
igt_fixture {
data.drm_fd = drm_open_driver_master(DRIVER_ANY);
--
2.40.0
next prev parent reply other threads:[~2023-12-18 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 8:21 [i-g-t v3 0/9] tests/kms_vrr: Modify kms_vrr to allow flicker profiling Bhanuprakash Modem
2023-12-18 8:21 ` [i-g-t v3 1/9] tests/kms_vrr: Move fb0 and fb1 to an array Bhanuprakash Modem
2023-12-18 8:22 ` [i-g-t v3 2/9] tests/kms_vrr: Move vtest_ns into data_t Bhanuprakash Modem
2023-12-18 8:22 ` Bhanuprakash Modem [this message]
2023-12-18 8:22 ` [i-g-t v3 4/9] tests/kms_vrr: Allow test duration to be specified from the command line Bhanuprakash Modem
2023-12-18 8:22 ` [i-g-t v3 5/9] tests/kms_vrr: Change the pattern displayed in the test Bhanuprakash Modem
2023-12-18 8:22 ` [i-g-t v3 6/9] tests/kms_vrr: Add ability to flip static image for flicker profiling Bhanuprakash Modem
2023-12-18 8:22 ` [i-g-t v3 7/9] tests/kms_vrr: Allow for multiple rates in a test Bhanuprakash Modem
2023-12-18 8:22 ` [i-g-t v3 8/9] tests/kms_vrr: Add a max/min test to oscillate between rates Bhanuprakash Modem
2023-12-18 8:22 ` [i-g-t v3 9/9] HAX/DO_NOT_MERGE: Test VRR only in BAT Bhanuprakash Modem
2023-12-18 20:24 ` ✗ Fi.CI.BAT: failure for tests/kms_vrr: Modify kms_vrr to allow flicker profiling (rev2) Patchwork
2023-12-18 21:12 ` ✗ CI.xeBAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 2:06 [i-g-t v3 0/9] tests/kms_vrr: Modify kms_vrr to allow flicker profiling Bhanuprakash Modem
2023-12-19 2:06 ` [i-g-t v3 3/9] tests/kms_vrr: Allow test rate to be altered from the command line Bhanuprakash Modem
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=20231218082207.32719-4-bhanuprakash.modem@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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