From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: igt-dev@lists.freedesktop.org,
Tomi Sarvela <tomi.p.sarvela@intel.com>,
Martin Peres <martin.peres@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/psr: Add PSR tests to fast-feedback list.
Date: Mon, 16 Jul 2018 10:43:10 -0700 [thread overview]
Message-ID: <20180716174310.GM4262@intel.com> (raw)
In-Reply-To: <20180713233904.12917-1-dhinakaran.pandiyan@intel.com>
On Fri, Jul 13, 2018 at 04:39:04PM -0700, Dhinakaran Pandiyan wrote:
> We do not have PSR panels on shards machines, so this is the only way to
> test PSR in CI.
We definitely need this...
but we need to ckeck the overall time and ff limits here as well...
ditto on the kms_frontbuffer_tracking one...
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> ---
> tests/intel-ci/fast-feedback.testlist | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index aa861d39..e262d024 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -244,6 +244,26 @@ 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@basic
> +igt@kms_psr@no_drrs
> +igt@kms_psr@primary_page_flip
> +igt@kms_psr@primary_mmap_gtt
> +igt@kms_psr@primary_mmap_cpu
> +igt@kms_psr@primary_blt
> +igt@kms_psr@primary_render
> +igt@kms_psr@sprite_mmap_gtt
> +igt@kms_psr@sprite_mmap_cpu
> +igt@kms_psr@sprite_blt
> +igt@kms_psr@sprite_render
> +igt@kms_psr@sprite_plane_move
> +igt@kms_psr@sprite_plane_onoff
> +igt@kms_psr@cursor_mmap_gtt
> +igt@kms_psr@cursor_mmap_cpu
> +igt@kms_psr@cursor_blt
> +igt@kms_psr@cursor_render
> +igt@kms_psr@cursor_plane_move
> +igt@kms_psr@cursor_plane_onoff
> +igt@kms_psr@dpms
> +igt@kms_psr@suspend
> igt@kms_setmode@basic-clone-single-crtc
> igt@kms_sink_crc_basic
> igt@pm_backlight@basic-brightness
> --
> 2.17.1
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-07-16 17:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 23:39 [igt-dev] [PATCH i-g-t] tests/psr: Add PSR tests to fast-feedback list Dhinakaran Pandiyan
2018-07-14 0:13 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-07-14 0:28 ` [igt-dev] [PATCH i-g-t] " Rodrigo Vivi
2018-07-14 6:05 ` Dhinakaran Pandiyan
2018-07-14 1:08 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2018-07-14 6:37 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-07-14 8:03 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-07-16 17:43 ` Rodrigo Vivi [this message]
2018-07-16 18:29 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
2018-07-17 5:13 ` Rodrigo Vivi
2018-07-17 7:52 ` Martin Peres
2018-07-17 18:30 ` Dhinakaran Pandiyan
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=20180716174310.GM4262@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@linux.intel.com \
--cc=tomi.p.sarvela@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.