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 v1 0/3] kms_atomic_transition improvements
Date: Fri, 29 Mar 2019 13:28:58 +0200 [thread overview]
Message-ID: <20190329112901.27830-1-stanislav.lisovskiy@intel.com> (raw)
Simplified plane parameter initialization code, 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.
Stanislav Lisovskiy (3):
igt/tests/kms_atomic_transition: Skip transition, if no changes done
igt/tests: Remove redundant code in kms_atomic_transition
igt/tests: Tolerate if kernel can't have all planes
tests/kms_atomic_transition.c | 86 +++++++++++++++++++----------------
1 file changed, 48 insertions(+), 38 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-03-29 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 11:28 Stanislav Lisovskiy [this message]
2019-03-29 11:28 ` [igt-dev] [PATCH i-g-t v1 1/3] igt/tests/kms_atomic_transition: Skip transition, if no changes done Stanislav Lisovskiy
2019-03-29 11:29 ` [igt-dev] [PATCH i-g-t v1 2/3] igt/tests: Remove redundant code in kms_atomic_transition Stanislav Lisovskiy
2019-03-29 11:29 ` [igt-dev] [PATCH i-g-t v1 3/3] igt/tests: Tolerate if kernel can't have all planes Stanislav Lisovskiy
2019-04-01 7:28 ` Daniel Vetter
2019-04-01 7:30 ` Daniel Vetter
2019-04-01 7:40 ` Daniel Vetter
2019-03-29 12:18 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_atomic_transition improvements Patchwork
2019-03-29 14:58 ` [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=20190329112901.27830-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox