flywithu/ntel-gpu-tools
1
0
Fork 0
mirror of https://github.com/tiagovignatti/intel-gpu-tools.git synced 2025-06-12 02:16:17 +00:00
Code Issues Releases Wiki Activity

tests: add a test for checking edid reading delays

Browse Source 
With base on EDID timing testing, when we take more than 1s to run
xrandr command, something is wrong.. So add this test for testing the time
we take to read the status of all the connectors from sysfs. It should do
us an average picture of how long we'd take to run xrandr (roughtly 2x
that value).

Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
This commit is contained in:
Eugeni Dodonov 2011-11-10 11:27:27 -02:00
parent 48186febf1
commit faf413d875
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
tests/Makefile.am
View File

@ -57,6 +57,7 @@ TESTS_progs = \
TESTS_scripts = \
debugfs_reader \
debugfs_emon_crash \
sysfs_edid_timing \
$(NULL)
kernel_tests = \

20
tests/sysfs_edid_timing Executable file
View File

@ -0,0 +1,20 @@
#!/bin/sh
#
# This check the time we take to read the content of all the possible connectors.
# Without the edid -ENXIO patch (http://permalink.gmane.org/gmane.comp.video.dri.devel/62083),
# we sometimes take a *really* long time. So let's just check for some reasonable timing here
#
TIME1=$(date +%s%N)
cat $(find /sys/devices/|grep drm | grep /status) > /dev/null
TIME2=$(date +%s%N)
# time in ms
RES=$[(TIME2 - TIME1) / 1000000]
if [ $RES -gt 600 ]; then
echo "Talking to outputs took ${RES}ms, something is wrong"
exit 1
fi
exit 0