Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshi, Kunal1" <kunal1.joshi@intel.com>
To: Pranay Samala <pranay.samala@intel.com>, igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, swati2.sharma@intel.com,
	sameer.lattannavar@intel.com
Subject: Re: [PATCH i-g-t v3 1/3] tests/chamelium/kms_chamelium_edid: Use extended flag to reduce the number of edid
Date: Thu, 24 Oct 2024 15:13:19 +0530	[thread overview]
Message-ID: <a52e5482-5b8c-41ab-88e3-8dfa478e4b22@intel.com> (raw)
In-Reply-To: <20241024082704.1746746-2-pranay.samala@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]

Hello Pranay,

On 24-10-2024 13:57, Pranay Samala wrote:
> This test iterates on all the available edids of HDMI.
> Due to CI test timeut limitation, we are reducing the
> number of edids to execute to avoid result as timeout.
>
> Using extended flag to achieve this. The test will execute
> only 25 edids when this flag is not used as CI doesnt uses
> this flag.
> In local execution to execute on all edids, we have to give
> this flag at the runtime.
>
> Signed-off-by: Pranay Samala<pranay.samala@intel.com>
> ---
>   tests/chamelium/kms_chamelium_edid.c | 20 +++++++++++++++++++-
>   1 file changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/tests/chamelium/kms_chamelium_edid.c b/tests/chamelium/kms_chamelium_edid.c
> index 8438f5f15..1bdde1768 100644
> --- a/tests/chamelium/kms_chamelium_edid.c
> +++ b/tests/chamelium/kms_chamelium_edid.c
> @@ -122,6 +122,7 @@
>    */
>   
>   #define MODE_CLOCK_ACCURACY 0.05 /* 5% */
> +static bool extended;
>   
>   static void get_connectors_link_status_failed(chamelium_data_t *data,
>   					      bool *link_status_failed)
> @@ -273,6 +274,9 @@ static void edid_stress_resolution(chamelium_data_t *data,
>   			      data->ports, data->port_count);
>   
>   
> +	if (!extended)
> +		edids_list_len = 25;
> +

Is there any environment variable that can be checked here instead of 
using extended?
If we can somehow know that this is a CI execution with some environment 
variable we can use that instead.
It will allow executing test without extended flag.

If we don't have any such env variable I am ok with this approach just 
add a info message to notify
user we are shortening the list also add a intel platform check.


Thanks and Regards Kunal Joshi

>   	for (i = 0; i < edids_list_len; ++i) {
>   		struct chamelium_edid *chamelium_edid;
>   		drmModeModeInfo mode;
> @@ -504,8 +508,22 @@ static void test_mode_timings(chamelium_data_t *data,
>   	} while (++i < count_modes);
>   }
>   
> +static int opt_handler(int opt, int opt_index, void *_data)
> +{
> +	switch (opt) {
> +	case 'e':
> +		extended = true;
> +		break;
> +	}
> +
> +	return IGT_OPT_HANDLER_SUCCESS;
> +}
> +
> +const char *help_str =
> +	"  -e \tExtended tests.\n";
> +
>   IGT_TEST_DESCRIPTION("Testing EDID with a Chamelium board");
> -igt_main
> +igt_main_args("e", NULL, help_str, opt_handler, NULL)
>   {
>   	chamelium_data_t data;
>   	struct chamelium_port *port;

[-- Attachment #2: Type: text/html, Size: 3125 bytes --]

  reply	other threads:[~2024-10-24  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  8:27 [PATCH i-g-t v3 0/3] tests/chamelium: Reduce edid count to avoid timeout Pranay Samala
2024-10-24  8:27 ` [PATCH i-g-t v3 1/3] tests/chamelium/kms_chamelium_edid: Use extended flag to reduce the number of edid Pranay Samala
2024-10-24  9:43   ` Joshi, Kunal1 [this message]
2024-10-24  8:27 ` [PATCH i-g-t v3 2/3] HAX: Do not merge Pranay Samala
2024-10-24  8:27 ` [PATCH i-g-t v3 3/3] lib/monitor_edids/hdmi_edids: Shuffle edid with the redundant one Pranay Samala
2024-10-24 10:28 ` ✗ Fi.CI.BAT: failure for tests/chamelium: Reduce edid count to avoid timeout Patchwork
2024-10-24 11:05 ` ✓ CI.xeBAT: success " Patchwork
2024-10-25  2:38 ` ✓ CI.xeFULL: " 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=a52e5482-5b8c-41ab-88e3-8dfa478e4b22@intel.com \
    --to=kunal1.joshi@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=karthik.b.s@intel.com \
    --cc=pranay.samala@intel.com \
    --cc=sameer.lattannavar@intel.com \
    --cc=swati2.sharma@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