From: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: ville.syrjala@intel.com, martin.peres@intel.com,
stanislav.lisovskiy@intel.com
Subject: [igt-dev] [PATCH i-g-t v5 0/2] kms_atomic_transition improvements
Date: Thu, 4 Apr 2019 15:13:57 +0300 [thread overview]
Message-ID: <20190404121359.3339-1-stanislav.lisovskiy@intel.com> (raw)
Fixed run_transition_test issue, which might happen when no changes
are done and wait_transition is called and made setup_parms function
tolerate if kernel can't afford having all sprite planes enabled
depending on current mode. Remove redundant condition nesting and code.
Stanislav Lisovskiy (2):
igt/tests/kms_atomic_transition: Skip transition, if no changes done
igt/tests/kms_atomic_transition: Tolerate if can't have all planes
tests/kms_atomic_transition.c | 146 ++++++++++++++++++++--------------
1 file changed, 88 insertions(+), 58 deletions(-)
--
2.17.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-04-04 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 12:13 Stanislav Lisovskiy [this message]
2019-04-04 12:13 ` [igt-dev] [PATCH i-g-t v5 1/2] igt/tests/kms_atomic_transition: Skip transition, if no changes done Stanislav Lisovskiy
2019-04-04 22:55 ` Souza, Jose
2019-04-05 6:50 ` Lisovskiy, Stanislav
2019-04-05 23:45 ` Souza, Jose
2019-04-08 7:50 ` Lisovskiy, Stanislav
2019-04-04 12:13 ` [igt-dev] [PATCH i-g-t v5 2/2] igt/tests/kms_atomic_transition: Tolerate if can't have all planes Stanislav Lisovskiy
2019-04-05 0:59 ` Souza, Jose
2019-04-05 6:57 ` Lisovskiy, Stanislav
2019-04-04 14:08 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_atomic_transition improvements (rev9) Patchwork
2019-04-05 5:28 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-04-05 14:21 [igt-dev] [PATCH i-g-t v5 0/2] kms_atomic_transition improvements Stanislav Lisovskiy
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=20190404121359.3339-1-stanislav.lisovskiy@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@intel.com \
--cc=ville.syrjala@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.