summaryrefslogtreecommitdiff
path: root/tests/kms_frontbuffer_tracking.c
diff options
context:
space:
mode:
authorPaulo Zanoni <paulo.r.zanoni@intel.com>2015-11-05 17:54:31 -0200
committerPaulo Zanoni <paulo.r.zanoni@intel.com>2015-11-27 09:57:35 -0200
commit98bb8428b2939311015b45ca59d7d9c65949c9bf (patch)
treefe19d53f942702af85c7db5d01201129d5989e4f /tests/kms_frontbuffer_tracking.c
parentf23ea58f1fbb7075d08bdbd85523d12270ce46a2 (diff)
kms_frontbuffer_tracking: assert the stride changes at stridechange()
We use igt_create_fb(), which decides the stride by itself: there's no guarantee that making a buffer 512 pixels bigger is going to make its stride change. I had a fix for this problem that was supposed to be applied before this patch, but due to a rework request I'm changing the order of the patches, so we should expect to hit this assertion for now. At least the root cause of the problem is clear now. v2: Update the commit message due to the patch order changing. Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Diffstat (limited to 'tests/kms_frontbuffer_tracking.c')
-rw-r--r--tests/kms_frontbuffer_tracking.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
index b4f4b22c6..d90bb25e9 100644
--- a/tests/kms_frontbuffer_tracking.c
+++ b/tests/kms_frontbuffer_tracking.c
@@ -2959,6 +2959,8 @@ static void stridechange_subtest(const struct test_mode *t)
LOCAL_I915_FORMAT_MOD_X_TILED, t->plane, &new_fb);
fill_fb(&new_fb, COLOR_PRIM_BG);
+ igt_assert(old_fb->stride != new_fb.stride);
+
/* We can't assert that FBC will be enabled since there may not be
* enough space for the CFB, but we can check the CRC. */
params->fb.fb = &new_fb;