summaryrefslogtreecommitdiff
path: root/tests/i915/kms_ccs.c
AgeCommit message (Collapse)Author
2022-06-07tests/i915/kms_ccs: Fix 4tiled rc ccs and color clear testsJuha-Pekka Heikkila
4tiled rc ccs and color clear tests were testing wrong things because wrong modifier was used for choosing test path. Signed-off-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com> Reviewed-by: Mika Kahola <mika.kahola@intel.com>
2022-05-25tests/kms_ccs: Add dg2 tiled-4 ccs modifiersJuha-Pekka Heikkilä
I915_FORMAT_MOD_4_TILED_DG2_RC_CCS I915_FORMAT_MOD_4_TILED_DG2_MC_CCS I915_FORMAT_MOD_4_TILED_DG2_RC_CCS_CC modifier added for testing and prevent impossible ccs test from flat ccs, fb generation for FB_HAS_PLANE will use linear modifier instead if Y-modifier as its no longer supported for latest platform. v2: Modified commit message. (Petri) Signed-off-by: Juha-Pekka Heikkilä <juha-pekka.heikkila@intel.com> Signed-off-by: Jeevan B <jeevan.b@intel.com> Reviewed-by: Mika Kahola <mika.kahola@intel.com>
2021-09-16tests/kms: Move Intel specific kms tests to i915 directoryBhanuprakash Modem
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>