public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Martin Peres <martin.peres@free.fr>,
	Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] intel-ci: Sanitycheck CRC readback on the first pipe only
Date: Thu, 11 Apr 2019 18:00:10 +0200	[thread overview]
Message-ID: <1e189a5f-ca1c-5c1f-6c82-71a6748b0935@linux.intel.com> (raw)
In-Reply-To: <20190411105248.25149-1-chris@chris-wilson.co.uk>

Op 11-04-2019 om 12:52 schreef Chris Wilson:
> For fast-feedback, we need to sanitycheck that CRC reads work, otherwise
> the display validation tests are flawed. However, we don't need to
> extensively test each pipe as the HW is fundamentally the same. Instead,
> do the full suite of tests on one pipe, and just verify that the interface
> works for the other pipes. This should speed BAT up by reducing
> NUM_PIPES suspend and resume cycles to just 1.
>
> The shards should cover the extended test suite on all pipes for
> complete validation.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Martin Peres <martin.peres@free.fr>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
>  tests/intel-ci/fast-feedback.testlist | 13 +------------
>  1 file changed, 1 insertion(+), 12 deletions(-)
>
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index 8ae5e8a28..a3b917fd0 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -205,25 +205,14 @@ igt@kms_force_connector_basic@force-edid
>  igt@kms_force_connector_basic@force-load-detect
>  igt@kms_force_connector_basic@prune-stale-modes
>  igt@kms_frontbuffer_tracking@basic
> -igt@kms_pipe_crc_basic@bad-source
>  igt@kms_pipe_crc_basic@hang-read-crc-pipe-a
> -igt@kms_pipe_crc_basic@hang-read-crc-pipe-b
> -igt@kms_pipe_crc_basic@hang-read-crc-pipe-c
>  igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a
>  igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence
> -igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b
> -igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence
> -igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c
> -igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c-frame-sequence
>  igt@kms_pipe_crc_basic@read-crc-pipe-a
> -igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence
>  igt@kms_pipe_crc_basic@read-crc-pipe-b
> -igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence
>  igt@kms_pipe_crc_basic@read-crc-pipe-c
> -igt@kms_pipe_crc_basic@read-crc-pipe-c-frame-sequence
> +igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence
>  igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a
> -igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b
> -igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c
>  igt@kms_psr@primary_page_flip
>  igt@kms_psr@cursor_plane_move
>  igt@kms_psr@sprite_plane_onoff

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Makes sense, we might want to make fastset specific versions sometime in the future..

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-04-11 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 10:52 [igt-dev] [PATCH i-g-t] intel-ci: Sanitycheck CRC readback on the first pipe only Chris Wilson
2019-04-11 11:02 ` Martin Peres
2019-04-11 14:07 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-04-11 16:00 ` Maarten Lankhorst [this message]
2019-04-11 18:05 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=1e189a5f-ca1c-5c1f-6c82-71a6748b0935@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@free.fr \
    --cc=petri.latvala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox