Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> writes: > For in-flight-suspend, we need to wait for the GPU hang within > i915_gem_suspend(). This will take 10-20s, which means that the standard > wakeup delay of around 15s may occur before we complete the suspend. > This causes a pm_system_wakeup(), causing dpm_suspend() to return > -EBUSY. > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Mika Kuoppala <mika.kuoppala@xxxxxxxxxxxxxxx> > --- > tests/gem_eio.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/tests/gem_eio.c b/tests/gem_eio.c > index 7a6be393..2ac9f0a9 100644 > --- a/tests/gem_eio.c > +++ b/tests/gem_eio.c > @@ -258,8 +258,8 @@ static void test_inflight_suspend(int fd) > igt_assert(fence[n] != -1); > } > > - igt_system_suspend_autoresume(SUSPEND_STATE_MEM, > - SUSPEND_TEST_NONE); > + igt_set_autoresume_delay(30); > + igt_system_suspend_autoresume(SUSPEND_STATE_MEM, SUSPEND_TEST_NONE); > > igt_post_hang_ring(fd, hang); post_hang_cleanup(?) ... -Mika > > -- > 2.15.1 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
