diff options
| author | Imre Deak <imre.deak@intel.com> | 2016-09-30 17:28:53 +0300 |
|---|---|---|
| committer | Imre Deak <imre.deak@intel.com> | 2016-10-13 15:08:55 +0300 |
| commit | 022e6f8ae7c853e221eb9d8344cf1aa27c5fbe57 (patch) | |
| tree | ea9d7a00ee3e675c3ae5fbd5063572bc816dc352 /tests/kms_cursor_crc.c | |
| parent | e442481c9cf35a1c509b836cf076bae597296200 (diff) | |
lib/igt_aux: Add support for various system suspend/resume options
To have a more accurate idea about any suspend/resume issues we can
perform the s/r until various phases in the s/r sequence. This way we
can isolate the given problem as being a device driver, kernel core or
BIOS related issue. Actual subtests using these new s/r phases will be
added as follow-up.
While at it also add the freeze suspend target, it's something we also
would need to test.
Signed-off-by: Imre Deak <imre.deak@intel.com>
Diffstat (limited to 'tests/kms_cursor_crc.c')
| -rw-r--r-- | tests/kms_cursor_crc.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/kms_cursor_crc.c b/tests/kms_cursor_crc.c index d1de4501..926579d6 100644 --- a/tests/kms_cursor_crc.c +++ b/tests/kms_cursor_crc.c @@ -140,7 +140,8 @@ static void do_single_test(data_t *data, int x, int y) } if (data->flags & TEST_SUSPEND) - igt_system_suspend_autoresume(); + igt_system_suspend_autoresume(SUSPEND_STATE_MEM, + SUSPEND_TEST_NONE); igt_pipe_crc_collect_crc(pipe_crc, &crc_after); igt_assert_crc_equal(&crc, &crc_after); |