From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 1/2] kms_pipe_crc_basic: Only test one pipe in the basic set
Date: Mon, 25 Apr 2016 10:00:20 +0300 [thread overview]
Message-ID: <8760v6mauz.fsf@intel.com> (raw)
In-Reply-To: <1461336116-17408-1-git-send-email-tvrtko.ursulin@linux.intel.com>
On Fri, 22 Apr 2016, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> I would argue it is enough to test one pipe in the BAT set.
FWIW BYT/CHV DSI may be fixed to port C which is fixed to pipe B,
skipping the test for pipe A.
BR,
Jani.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> tests/kms_pipe_crc_basic.c | 23 +++++++++++++----------
> 1 file changed, 13 insertions(+), 10 deletions(-)
>
> diff --git a/tests/kms_pipe_crc_basic.c b/tests/kms_pipe_crc_basic.c
> index 4de53bc77a3a..291775934758 100644
> --- a/tests/kms_pipe_crc_basic.c
> +++ b/tests/kms_pipe_crc_basic.c
> @@ -180,6 +180,9 @@ static void test_read_crc(data_t *data, int pipe, unsigned flags)
>
> data_t data = {0, };
>
> +#define test_prefix(i) ((i) == 0 ? "basic-" : "")
> +#define pipe_name(i) ((i) + 'A')
> +
> igt_main
> {
> igt_skip_on_simulation();
> @@ -196,39 +199,39 @@ igt_main
> igt_display_init(&data.display, data.drm_fd);
> }
>
> - igt_subtest("bad-pipe")
> + igt_subtest("basic-bad-pipe")
> test_bad_command(&data, "pipe D none");
>
> - igt_subtest("bad-source")
> + igt_subtest("basic-bad-source")
> test_bad_command(&data, "pipe A foo");
>
> - igt_subtest("bad-nb-words-1")
> + igt_subtest("basic-bad-nb-words-1")
> test_bad_command(&data, "pipe foo");
>
> - igt_subtest("bad-nb-words-3")
> + igt_subtest("basic-bad-nb-words-3")
> test_bad_command(&data, "pipe A none option");
>
> for (int i = 0; i < 3; i++) {
> - igt_subtest_f("read-crc-pipe-%c", 'A'+i)
> + igt_subtest_f("%sread-crc-pipe-%c", test_prefix(i), pipe_name(i))
> test_read_crc(&data, i, 0);
>
> - igt_subtest_f("read-crc-pipe-%c-frame-sequence", 'A'+i)
> + igt_subtest_f("%sread-crc-pipe-%c-frame-sequence", test_prefix(i), pipe_name(i))
> test_read_crc(&data, i, TEST_SEQUENCE);
>
> - igt_subtest_f("nonblocking-crc-pipe-%c", 'A'+i)
> + igt_subtest_f("%snonblocking-crc-pipe-%c", test_prefix(i), pipe_name(i))
> test_read_crc(&data, i, TEST_NONBLOCK);
>
> - igt_subtest_f("nonblocking-crc-pipe-%c-frame-sequence", 'A'+i)
> + igt_subtest_f("%snonblocking-crc-pipe-%c-frame-sequence", test_prefix(i), pipe_name(i))
> test_read_crc(&data, i, TEST_SEQUENCE | TEST_NONBLOCK);
>
> - igt_subtest_f("suspend-read-crc-pipe-%c", 'A'+i) {
> + igt_subtest_f("%ssuspend-read-crc-pipe-%c", test_prefix(i), pipe_name(i)) {
> igt_skip_on(i >= data.display.n_pipes);
> igt_system_suspend_autoresume();
>
> test_read_crc(&data, i, 0);
> }
>
> - igt_subtest_f("hang-read-crc-pipe-%c", 'A'+i) {
> + igt_subtest_f("%shang-read-crc-pipe-%c", test_prefix(i), pipe_name(i)) {
> igt_hang_ring_t hang =
> igt_hang_ring(data.drm_fd, I915_EXEC_RENDER);
> test_read_crc(&data, i, 0);
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-04-25 7:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:41 [PATCH i-g-t 1/2] kms_pipe_crc_basic: Only test one pipe in the basic set Tvrtko Ursulin
2016-04-22 14:41 ` [PATCH i-g-t 2/2] kms_pipe_crc_basic: Rename test to kms_pipe_crc Tvrtko Ursulin
2016-04-22 15:11 ` [PATCH i-g-t 1/2] kms_pipe_crc_basic: Only test one pipe in the basic set Chris Wilson
2016-04-25 8:51 ` Daniel Vetter
2016-04-25 9:45 ` Tvrtko Ursulin
2016-04-25 20:12 ` Zanoni, Paulo R
2016-04-26 13:54 ` Daniel Vetter
2016-04-25 7:00 ` Jani Nikula [this message]
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=8760v6mauz.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.