From: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lyude <lyude@redhat.com>
Subject: Re: [PATCH i-g-t] tests/chamelium: Require HPD storm control for basic hotplug test
Date: Tue, 13 Jun 2017 15:46:08 +0300 [thread overview]
Message-ID: <1497357968.25733.8.camel@linux.intel.com> (raw)
In-Reply-To: <20170613124433.5818-1-paul.kocialkowski@linux.intel.com>
On Tue, 2017-06-13 at 15:44 +0300, Paul Kocialkowski wrote:
> The basic hotplug test (test_basic_hotplug) makes calls to
> igt_hpd_storm_set_threshold, which requires HPD storm control.
>
> This adds a check for that control, since it was missing.
This is a resend of yesterday's patch with the right subject prefix so that
patchwork can pick it up.
> Signed-off-by: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
> ---
> tests/chamelium.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/chamelium.c b/tests/chamelium.c
> index 2e14ccb9..bd7772f8 100644
> --- a/tests/chamelium.c
> +++ b/tests/chamelium.c
> @@ -153,6 +153,8 @@ test_basic_hotplug(data_t *data, struct chamelium_port
> *port)
> struct udev_monitor *mon = igt_watch_hotplug();
> int i;
>
> + igt_require_hpd_storm_ctl(data->drm_fd);
> +
> reset_state(data, port);
> igt_hpd_storm_set_threshold(data->drm_fd, 0);
>
--
Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-13 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 12:44 [PATCH i-g-t] tests/chamelium: Require HPD storm control for basic hotplug test Paul Kocialkowski
2017-06-13 12:46 ` Paul Kocialkowski [this message]
2017-06-13 18:20 ` Lyude Paul
2017-06-14 7:47 ` Paul Kocialkowski
2017-06-14 7:51 ` Paul Kocialkowski
2017-06-14 10:38 ` Paul Kocialkowski
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=1497357968.25733.8.camel@linux.intel.com \
--to=paul.kocialkowski@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lyude@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).