public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: aemad <aemad@igalia.com>
To: igt-dev@lists.freedesktop.org
Cc: petri.latvala@intel.com
Subject: Re: [igt-dev] [PATCH RFC i-g-t 0/8] tests/kms_universal_plane: divide `functional_test_pipe` to mini-subtests
Date: Fri, 11 Nov 2022 09:31:11 +0100	[thread overview]
Message-ID: <35b8b7adb1e5671c2c1ae43ba7ce4774@igalia.com> (raw)
In-Reply-To: <cover.1668154709.git.aemad@igalia.com>

Please, let me know your thoughts.

On 2022-11-11 09:29, Alaa Emad wrote:
> Divide the `functional_test_pipe` test into seven subtests based on CRC
> comparisons because this will make it easier to debug the test and help
> in detecting the failure.
> 
> First 7 patches decouple each subtest and run it individually keeping
> `functional_test_pipe' test as it is. After making sure that each
> subtest can run individually with the expected result on both vkms and i915
> drivers, improve the test by creating `run_functional_test_pipe` and
> call all subtests from it and call `run_functional_test_pipe` in
> `igt_main`.
> 
> 
> Alaa Emad (8):
>   tests/kms_universal_plane: decouple verification of legacy and atomic
>     api
>   tests/kms_universal_plane: decouple verification of disabling primary
>     plane
>   tests/kms_universal_plane: decouple verification of re-enabling
>     primary plane
>   tests/kms_universal_plane: decouple verification of setup plane FB's
>     while CRTC is disabled
>   tests/kms_universal_plane: decouple verification of ablity to modeset
>     with the primary plane off
>   tests/kms_universal_plane: decouple verification of ablity to move the
>     primary plane completely offscreen
>   tests/kms_universal_plane: decouple verification of ablity to
>     explicitly disable an already implicitly-disabled primary plane
>   tests/kms_universal_plane: create the run_functional_test_pipe and
>     call all tests from it
> 
>  tests/kms_universal_plane.c | 416 ++++++++++++++++++++++--------------
>  1 file changed, 261 insertions(+), 155 deletions(-)

  parent reply	other threads:[~2022-11-11  9:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  8:29 [igt-dev] [PATCH RFC i-g-t 0/8] tests/kms_universal_plane: divide `functional_test_pipe` to mini-subtests Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 1/8] tests/kms_universal_plane: decouple verification of legacy and atomic api Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 2/8] tests/kms_universal_plane: decouple verification of disabling primary plane Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 3/8] tests/kms_universal_plane: decouple verification of re-enabling " Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 4/8] tests/kms_universal_plane: decouple verification of setup plane FB's while CRTC is disabled Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 5/8] tests/kms_universal_plane: decouple verification of ablity to modeset with the primary plane off Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 6/8] tests/kms_universal_plane: decouple verification of ablity to move the primary plane completely offscreen Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 7/8] tests/kms_universal_plane: decouple verification of ablity to explicitly disable an already implicitly-disabled primary plane Alaa Emad
2022-11-11  8:29 ` [igt-dev] [PATCH RFC i-g-t 8/8] tests/kms_universal_plane: create the run_functional_test_pipe and call all tests from it Alaa Emad
2022-11-11  8:31 ` aemad [this message]
2022-11-17 21:35   ` [igt-dev] [PATCH RFC i-g-t 0/8] tests/kms_universal_plane: divide `functional_test_pipe` to mini-subtests Alex Hung
2022-11-29 12:16     ` aemad
2022-11-11  9:59 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-11-12  4:08 ` [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=35b8b7adb1e5671c2c1ae43ba7ce4774@igalia.com \
    --to=aemad@igalia.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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