On Fri, Aug 04, 2017 at 11:23:18AM -0700, clinton.a.taylor@xxxxxxxxx wrote:
> From: Clint Taylor <clinton.a.taylor@xxxxxxxxx>
>
> Current 50ms max threshold timing for an EDID read is very close to the
> actual time for a 2 block HDMI EDID read of 48ms. Any delay like a clock
> stretch by the EDID eeprom will cause this test to fail. A 4 block HDMI
> EDID read takes approximately 88ms under nominal conditions, making the max
> threshold 95ms will allow this test to pass regardless of monitor attached.
>
> Signed-off-by: Clint Taylor <clinton.a.taylor@xxxxxxxxx>
Per internal mail, this needs to be runtime adjusted to fit the EDID we're
reading. Maybe 30ms per edid block.
Thanks, Daniel
> ---
> tests/kms_sysfs_edid_timing.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/kms_sysfs_edid_timing.c b/tests/kms_sysfs_edid_timing.c
> index 1201388..b45e080 100644
> --- a/tests/kms_sysfs_edid_timing.c
> +++ b/tests/kms_sysfs_edid_timing.c
> @@ -27,14 +27,14 @@
> #include <sys/stat.h>
>
> #define THRESHOLD_PER_CONNECTOR 10
> -#define THRESHOLD_TOTAL 50
> +#define THRESHOLD_TOTAL 95
> #define CHECK_TIMES 15
>
> IGT_TEST_DESCRIPTION("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");
> + "we sometimes take a *really* long time. So let's just "
> + "check an approximate HDMI 4 block edid read timing here");
>
>
> igt_simple_main
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
