From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/2] tests/kms_frontbuffer_tracking: Rework to prevent modesets!
Date: Mon, 19 Mar 2018 16:04:09 +0100 [thread overview]
Message-ID: <20180319150411.4937-1-maarten.lankhorst@linux.intel.com> (raw)
Now that FBC can be toggled at runtime, I wanted to make sure that we try to prevent
modesets as much as we can.
Patch 1 kind of needs kernel support to work.
https://patchwork.freedesktop.org/series/39955/
Maarten Lankhorst (2):
tests/kms_frontbuffer_tracking: Add support for toggling edp psr
through debugfs, v2.
tests/kms_frontbuffer_tracking: Remove redundant modesets during
subtest start, v3.
tests/kms_frontbuffer_tracking.c | 93 +++++++++++++++++++++++++++++++++-------
1 file changed, 78 insertions(+), 15 deletions(-)
--
2.16.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-03-19 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 15:04 Maarten Lankhorst [this message]
2018-03-19 15:04 ` [igt-dev] [PATCH i-g-t 1/2] tests/kms_frontbuffer_tracking: Add support for toggling edp psr through debugfs, v2 Maarten Lankhorst
2018-03-19 15:04 ` [igt-dev] [PATCH i-g-t 2/2] tests/kms_frontbuffer_tracking: Remove redundant modesets during subtest start, v3 Maarten Lankhorst
2018-03-19 20:54 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_frontbuffer_tracking: Rework to prevent modesets! Patchwork
2018-03-20 9:54 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-03-20 11:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-04-05 19:56 ` Daniel Vetter
2018-04-05 20:36 ` Rodrigo Vivi
2018-04-06 5:47 ` Lofstedt, Marta
2018-04-06 7:12 ` Tomi Sarvela
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=20180319150411.4937-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).