From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org
Cc: Charlton Lin <charlton.lin@intel.com>,
Khaled Almahallawy <khaled.almahallawy@intel.com>
Subject: Re: [PATCH] tests/kms_sysfs_edid_timing: increase thresholds
Date: Mon, 11 Dec 2023 14:49:22 +0200 [thread overview]
Message-ID: <87h6koykdp.fsf@intel.com> (raw)
In-Reply-To: <20231211124444.f62euqvbg7posuxn@kamilkon-desk.igk.intel.com>
On Mon, 11 Dec 2023, Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> On 2023-12-08 at 14:42:05 -0800, Charlton Lin wrote:
>> 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
>
> This is like increasing it ten times, add this to description.
> I am not KMS nor panel expert but is it really that long?
Would be worth investigating *why* this specific panel takes so long,
instead of allowing *all* panels to do so. We might add a regression
that slows down probing and nobody would notice.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-12-11 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 22:42 [PATCH] tests/kms_sysfs_edid_timing: increase thresholds Charlton Lin
2023-12-11 12:44 ` Kamil Konieczny
2023-12-11 12:49 ` Jani Nikula [this message]
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=87h6koykdp.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=charlton.lin@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.