From: Lyude Paul <lyude@redhat.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/2] tests/chamelium: Don't sleep so much in basic hpd tests
Date: Thu, 23 Feb 2017 15:31:09 -0500 [thread overview]
Message-ID: <1487881869.20062.4.camel@redhat.com> (raw)
In-Reply-To: <20170223072627.GL10557@nuc-i3427.alporthouse.com>
On Thu, 2017-02-23 at 07:26 +0000, Chris Wilson wrote:
> On Wed, Feb 22, 2017 at 10:18:33PM -0500, Lyude wrote:
> > 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);
>
> You will want to check that you have the debugfs interface first and
> skip the test otherwise. Or was there a fallback? Or is it already
> checkd?
>
> -Chris
If the debugfs interface isn't there, the function just doesn't do
anything and returns immediately
>
--
Cheers,
Lyude
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-23 20:31 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 ` [PATCH i-g-t 2/2] tests/chamelium: Don't sleep so much in basic hpd tests Lyude
2017-02-23 7:26 ` Chris Wilson
2017-02-23 20:31 ` Lyude Paul [this message]
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=1487881869.20062.4.camel@redhat.com \
--to=lyude@redhat.com \
--cc=chris@chris-wilson.co.uk \
--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