summaryrefslogtreecommitdiff
path: root/tests/i915/kms_frontbuffer_tracking.c
AgeCommit message (Collapse)Author
2022-03-24tests/kms_frontbuffer_tracking: Add support for 4 tilingMika Kahola
GEN12 uses 4 tiling instead of Y tiling. Let's add support for tiling 4. Signed-off-by: Mika Kahola <mika.kahola@intel.com> Signed-off-by: Jeevan B <jeevan.b@intel.com> Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
2022-03-07tests/i915/kms_frontbuffer_tracking: ignore case when checking DRRS supportJames Xiong
commit caab25dc9e36 ("drm/i915/display: Fix DRRS debugfs") switched to macro yesno and changed i915_drrs_status from "DRRS Supported: Yes" to "yes". ignore case when checking if drrs is supported to avoid false result. Signed-off-by: James Xiong <james.xiong@intel.com> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
2022-02-25tests/kms_frontbuffer_tracking: Extend to test FBC on multiple pipesNidhi Gupta
In future more platforms will support FBC on multiple pipes, so to validate the same extending the kms_frontbuffer_tracking test. In kernel code now FBC debugfs files are exposed for each crtc so added debugfs_read_crtc function to get the per pipe fbc status. Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-11-25tests/kms_frontbuffer_tracking: Accept missing FBC debugfs filesVille Syrjälä
With multiple FBC instances becoming a thing at some point the current plan is to go with separate debugfs files for each FBC instance. Which also means that if there is no FBC there will be no debugfs files either. Adapt the test to tolerate such conditions. Reviewed-by: Petri Latvala <petri.latvala@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-18tests/i915/kms_frontbuffer_tracking: Use preferred modes's vrefreshVille Syrjälä
i915 will reject custom modes that don't match the laptop panel's fixed mode refresh rate. Thus we must generate our override modes with a matching refresh rate. Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4283 Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-18lib/kms: Have igt_std_1024_mode_get() return a mode with specific refreshVille Syrjälä
Pass the desired refresh rate to igt_std_1024_mode_get(), and have it return a mode that will have said refresh rate. Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-18lib/kms: Have igt_std_1024_mode_get() return a copy of the modeVille Syrjälä
We want to provide override modes with different refresh rates. Start by making igt_std_1024_mode_get() return a copy rather than a pointer to the static const mode directly. And sprinkle the necessary free() calls, and some igt_memdups() into parallel codepaths, so we are consistnetly allocating and freeing everything. Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-18tests/i915/kms_frontbuffer_tracking: Get rid of the funny mode_copyVille Syrjälä
For some reason we make a copy of the mode into 'mode_copy', and then point the 'mode' pointer at that copy. Get rid of the pointer and just use the struct directly. Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-11igt: s/DRM_FORMAT_MOD_NONE/DRM_FORMAT_MOD_LINEAR/Ville Syrjälä
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>
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>