public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lyude <lyude@redhat.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lyude <lyude@redhat.com>
Subject: [PATCH i-g-t 2/2] tests/chamelium: Don't sleep so much in basic hpd tests
Date: Wed, 22 Feb 2017 22:18:33 -0500	[thread overview]
Message-ID: <20170223031833.13442-2-lyude@redhat.com> (raw)
In-Reply-To: <20170223031833.13442-1-lyude@redhat.com>

Now that we can just disable HPD storm detection, there's no need to
sleep between each hotplug cycle.

Signed-off-by: Lyude <lyude@redhat.com>
---
 tests/chamelium.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/tests/chamelium.c b/tests/chamelium.c
index 849e1ac..810c955 100644
--- a/tests/chamelium.c
+++ b/tests/chamelium.c
@@ -154,6 +154,7 @@ test_basic_hotplug(data_t *data, struct chamelium_port *port)
 	int i;
 
 	reset_state(data, port);
+	igt_hpd_storm_set_threshold(0);
 
 	for (i = 0; i < 15; i++) {
 		igt_flush_hotplugs(mon);
@@ -171,12 +172,10 @@ test_basic_hotplug(data_t *data, struct chamelium_port *port)
 		igt_assert(igt_hotplug_detected(mon, HOTPLUG_TIMEOUT));
 		igt_assert_eq(reprobe_connector(data, port),
 			      DRM_MODE_DISCONNECTED);
-
-		/* Sleep so we don't accidentally cause an hpd storm */
-		usleep(500 * 1000);
 	}
 
 	igt_cleanup_hotplug(mon);
+	igt_hpd_storm_reset();
 }
 
 static void
-- 
2.9.3

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-02-23  3:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  3:18 [PATCH i-g-t 1/2] lib/igt_debugfs: Add functions/tests for controlling/testing HPD storm logic Lyude
2017-02-23  3:18 ` Lyude [this message]
2017-02-23  7:26   ` [PATCH i-g-t 2/2] tests/chamelium: Don't sleep so much in basic hpd tests Chris Wilson
2017-02-23 20:31     ` Lyude Paul
2017-02-23 22:53       ` Chris Wilson

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=20170223031833.13442-2-lyude@redhat.com \
    --to=lyude@redhat.com \
    --cc=intel-gfx@lists.freedesktop.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