| Age | Commit message (Collapse) | Author |
|---|
|
Currently we are seeing failures in ICL platforms due to
missing support for IGT_PLANE_FB_DAMAGE_CLIPS. Use
IGT_PLANE_FB_DAMAGE_CLIPS only if it is supported
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4148
Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
|
|
Igt_fixture is in a loop for different operations. This is causing
display_fini being called at the end of each iteration and
triggering SIGSEGV. Fix this by removing igt_fixture out from
the loop.
Fixes: 6be8feeb148e ("tests/kms_psr2_su: add biplanar selective update tests")
Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
|
|
Add biplanar formats (NV12, p010) into selective update test.
v2: Add back skipping of frontbuffer rendering tests
v3: Use hyphen instead of underscore in testnames
v4: Split offset change to own patch
Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
|
|
Adding offset to drawn rectangle reveals better problems offset
configuration.
Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
|
|
DRM_FORMAT_MOD_LINEAR is the more sensible name for
DRM_FORMAT_MOD_NONE. Use the better name.
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
|
|
The whole test needs to skip in display 13 platforms as
PSR2_SU_STATUS is not being updated anymore by HW.
It was not reliable in older display versions and now it is 100% dead.
For display 12 and newer platforms now we have PSR2 selective fetch
enabled default, so software is doing all the tracking of the areas
that needs updates but we still can't do that for frontbuffer
rendering so we are doing full frame fetches for now what will cause
this test to fail, so also skipping it for the frontbuffer subtest.
Cc: Jeevan B <jeevan.b@intel.com>
Cc: Swati Sharma <swati2.sharma@intel.com>
Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
|
|
As KMS tests on IGT are officially supported on multiple SoCs
and there is an active development on it. So, KMS tests are
meant to be generic and if we need to test few things specific
to Intel, we can use igt_require_intel(). But if the whole test
is Intel specific, then the best place for the test would be
tests/i915.
This patch will
* Move all Intel specific kms tests to tests/i915 directory.
* Update the tests those are generic but still open the driver
as 'drm_open_driver_master(DRIVER_INTEL);'.
V2:
* Few more tests
V3:
* Remove cleanups (will submit separate patch later)
* Move few more tests to i915 dir (Karthik)
V4:
* Move kms_big_joiner.c to i915 dir (Karthik)
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Mark Yacoub <markyacoub@chromium.org>
Cc: Petri Latvala <petri.latvala@intel.com>
Cc: Vidya Srinivas <vidya.srinivas@intel.com>
Cc: Karthik B S <karthik.b.s@intel.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Reviewed-by: Mark Yacoub <markyacoub@chromium.org>
Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
|
