summaryrefslogtreecommitdiff
path: root/tests/kms_color_chamelium.c
AgeCommit message (Collapse)Author
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_color_chamelium: Remove invalid LUT size testsVille Syrjälä
There is zero point in duplicating the invalid LUT size tests in the chamelium test. Get rid of them. Reviewed-by: Swati Sharma <swati2.sharma@intel.com> Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-09-16tests/kms_color_chamelium: Skip CTM test if property is not presentBhanuprakash Modem
CRTC property "CTM" is required for all CTM tests. Fixes: https://gitlab.freedesktop.org/drm/intel/-/issues/4133 Cc: Uma Shankar <uma.shankar@intel.com> Cc: Swati Sharma <swati2.sharma@intel.com> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Reviewed-by: Swati Sharma <swati2.sharma@intel.com>
2021-07-15Nuke local versions of DRM_FORMAT and DRM_MODELucas De Marchi
Use the definition from kernel headers. Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-06-08tests/kms_color_chamelium: Disable gamma in degamma testsVidya Srinivas
This patch disables gamma in degamma subtest which is missing. It compares CRC between (linear degamma + solid colors) and (max degamma + gradient colors). Patch also cleans up degamma before exiting degamma test and cleans up gamma before exiting gamma test. Signed-off-by: Vidya Srinivas <vidya.srinivas@intel.com> Reviewed-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
2021-02-21tests/kms_color_chamelium: Disabled fsm handling for kms_color_chameliumKunal Joshi
disabled fsm handling for kms_color_chamelium which operates on single mode through out. Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
2020-12-17tests/kms_color_chamelium: fix update successKunal Joshi
Made a silly mistake and didn't update bool success to true, fixing that with this patch. Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com> Reviewed-by: Karthik B S <karthik.b.s@intel.com>
2020-12-07tests/kms_color_chamelium: time optimizationKunal Joshi
Instead of going through all the delta even if we got success with one, now breaking when we pass, thus saving some time and decreasing load on chamelium for capturing the rest of the frames. Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com> Reviewed-by: Uma Shankar <uma.shankar@intel.com>
2020-07-21tests/kms: Skip kms test cases for disabled pipesMohammed Khajapasha
Skip the kms test cases for disabled pipes with non-contiguous pipe display. Signed-off-by: Mohammed Khajapasha <mohammed.khajapasha@intel.com> Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
2020-03-23lib/kms: Try to plug all Chamelium ports, abort if it failsArkadiusz Hiler
Using chamelium as a display for non-chamelium-aware test is challenging. The board can be left in multiple different states after kms_chamelium tests even though we have atexit() handlers and other measures which try to assure that all ports are plugged in. Sadly this is not 100% reliable. We also had a few boards hard hanging (happens very seldom) and requiring manual intervention. This leads to changes in the testing configuration - we may end up with any number of connectors plugged in which makes a lot of kms_ tests to flip between skip and pass depending on a run. In an attempt to make connectors state less random this patch makes igt_display_require() chamelium-aware. If chamelium is configured for given machine we try to reach it and make sure everything is plugged in. If we fail to do so we abort the execution because the testing configuration is an unknown. For machines without a configured chamelium this boils down to a nop. I have run a bunch of tests and measured how much time we spend in the Chamelium section of igt_display_require() (n = 1000) with chamelium configured: Min: 0.0030s Max: 0.0113s Avg: 0.0089s Median: 0.0089s With ~1000 of KMS subtests in a run it's only a mere 9s. This will however add a bit of extra execution time to test skips because of doing kmstest_set_vt_graphics_mode() and igt_display_require() before even checking whether Chamelium is configured. v2: do kmstest_set_vt_graphics_mode() before requiring display (Petri) Fixes: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/20 Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
2020-01-27tests/kms_color_chamelium: add subtests to validate colorKunal Joshi
To validate color subtests using chamelium, subtests modified to do frame dump comparison instead of crc comparison. Tests require chamelium and will validate color features at pipe level. (v2) Comparing framedump with framebuffer reference instead of comparing two framedump. (v3) Moved common functions with kms_color to lib/igt_color (v4) Added changes to skip the tests if there is no connected port with chamelium. Rearranged position of valid_output. Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com> Signed-off-by: Swati Sharma <swati2.sharma@intel.com> Suggested-by: Uma Shankar <uma.shankar@intel.com> Reviewed-by: Petri Latvala <petri.latvala@intel.com>