Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Charlton Lin <charlton.lin@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Charlton Lin <charlton.lin@intel.com>,
	Sharma@freedesktop.org,
	Khaled Almahallawy <khaled.almahallawy@intel.com>
Subject: [PATCH] tests/kms_sysfs_edid_timing: increase thresholds
Date: Fri,  8 Dec 2023 14:42:05 -0800	[thread overview]
Message-ID: <20231208224205.3428717-1-charlton.lin@intel.com> (raw)

A customer panel consistently exceeds 150ms. Additionally, the
timing may be impacted by certain power states.

Increase all thresholds to accommodate.

Cc: Sharma, Swati2 <swati2.sharma@intel.com>
Cc: Khaled Almahallawy <khaled.almahallawy@intel.com>
Cc: Mark Yacoub <markyacoub@chromium.org>
Signed-off-by: Charlton Lin <charlton.lin@intel.com>
---
 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 775211089f81..582133ea002e 100644
--- a/tests/kms_sysfs_edid_timing.c
+++ b/tests/kms_sysfs_edid_timing.c
@@ -26,9 +26,9 @@
 #include <fcntl.h>
 #include <sys/stat.h>
 
-#define THRESHOLD_PER_CONNECTOR		150
-#define THRESHOLD_PER_CONNECTOR_MEAN	140
-#define THRESHOLD_ALL_CONNECTORS_MEAN	100
+#define THRESHOLD_PER_CONNECTOR		1500
+#define THRESHOLD_PER_CONNECTOR_MEAN	1400
+#define THRESHOLD_ALL_CONNECTORS_MEAN	1000
 #define CHECK_TIMES			15
 
 IGT_TEST_DESCRIPTION("This test checks the time it takes to reprobe each "
-- 
2.25.1

             reply	other threads:[~2023-12-08 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 22:42 Charlton Lin [this message]
2023-12-11 12:44 ` [PATCH] tests/kms_sysfs_edid_timing: increase thresholds Kamil Konieczny
2023-12-11 12:49   ` Jani Nikula
2023-12-11 19:29 ` ✗ Fi.CI.BUILD: failure for " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231208224205.3428717-1-charlton.lin@intel.com \
    --to=charlton.lin@intel.com \
    --cc=Sharma@freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=khaled.almahallawy@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox