[igt-dev] [PATCH i-g-t 0/9] Handling mmap_gtt

Ramalingam C
2020-01-31T17:31:07Z

When platform doesn't support mappable aperture, we use device coherent
mapping instead of mmap_gtt.

And in such scenarios we are skipping the tiling based tests and fence
related tests along with GTT mmap specific tests.

Ramalingam C (9):
tests/prime_vgem: Skip fence and gtt specific tests
tests/intel_dp_compliance: Skip tests as tiling is not supported
tests/prime_mmap_coherency: use device coherent mapping instead of
mmap_gtt
tests/prime_mmap: use device coherent mapping instead of mmap_gtt
tests/kms_psr: Skip tests on mmap_gtt, if no mappable aperture
tests/kms_available_modes_crc: Skip test if mappable aperture not
supported
tests/i915_pm_rpm: use device coherent mapping instead of mmap_gtt
tests/i915_suspend: skip fence related tests, if no mmap_gtt
tests/gem_tiling_max_stride: Skip if set tiling is not supported

tests/i915/gem_tiling_max_stride.c | 1 +
tests/i915/i915_pm_rpm.c | 24 +++++++++++++++---------
tests/i915/i915_suspend.c | 16 ++++++++++++----
tests/kms_available_modes_crc.c | 1 +
tests/kms_psr.c | 1 +
tests/prime_mmap.c | 4 ++--
tests/prime_mmap_coherency.c | 2 +-
tests/prime_vgem.c | 12 +++++++++---
tools/intel_dp_compliance.c | 2 ++
9 files changed, 44 insertions(+), 19 deletions(-)

--
2.20.1