summaryrefslogtreecommitdiff
path: root/tests/kms_frontbuffer_tracking.c
diff options
context:
space:
mode:
authorImre Deak <imre.deak@intel.com>2016-09-30 17:28:53 +0300
committerImre Deak <imre.deak@intel.com>2016-10-13 15:08:55 +0300
commit022e6f8ae7c853e221eb9d8344cf1aa27c5fbe57 (patch)
treeea9d7a00ee3e675c3ae5fbd5063572bc816dc352 /tests/kms_frontbuffer_tracking.c
parente442481c9cf35a1c509b836cf076bae597296200 (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_frontbuffer_tracking.c')
-rw-r--r--tests/kms_frontbuffer_tracking.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
index 02ccbeb4..3a8b4583 100644
--- a/tests/kms_frontbuffer_tracking.c
+++ b/tests/kms_frontbuffer_tracking.c
@@ -2865,13 +2865,13 @@ static void suspend_subtest(const struct test_mode *t)
prepare_subtest(t, NULL);
sleep(5);
- igt_system_suspend_autoresume();
+ igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE);
sleep(5);
do_assertions(0);
unset_all_crtcs();
sleep(5);
- igt_system_suspend_autoresume();
+ igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE);
sleep(5);
do_assertions(ASSERT_FBC_DISABLED | ASSERT_PSR_DISABLED |
DONT_ASSERT_CRC);