From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: <karthik.b.s@intel.com>, <kunal1.joshi@intel.com>
Subject: Re: [PATCH i-g-t v2] tests/kms_async_flips: Skip Async flips on joiner output
Date: Thu, 14 Nov 2024 11:52:16 +0530 [thread overview]
Message-ID: <1c085de7-2afc-4892-9f79-d9c471272c42@intel.com> (raw)
In-Reply-To: <20241024111105.2261777-1-santhosh.reddy.guddati@intel.com>
Hi Santhosh,
Sorry missed few comments.
Add bspec no. where this condition is mentioned.
On 24-10-2024 04:41 pm, Santhosh Reddy Guddati wrote:
> Async flips are disallowed with joiner, but the test commit still
> goes through and causes failures. Update the tests to skip on
> joiner outputs.
>
> V2: Skip tests only on joiner outputs (Kunal).
>
> Signed-off-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
> ---
> tests/kms_async_flips.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
> index 5dec71291..77f68b773 100644
> --- a/tests/kms_async_flips.c
> +++ b/tests/kms_async_flips.c
> @@ -638,6 +638,27 @@ static void test_crc(data_t *data)
> igt_assert_lt(data->frame_count * 2, data->flip_count);
> }
>
> +static bool is_joiner_mode(data_t *data)
> +{
> + bool is_joiner = false;
> + bool is_ultra_joiner = false;
> + int max_dotclock;
> + drmModeModeInfo mode;
> +
> + max_dotclock = igt_get_max_dotclock(data->drm_fd);
> + is_joiner = bigjoiner_mode_found(data->drm_fd,
> + data->output->config.connector,
> + max_dotclock, &mode);
> + is_ultra_joiner = ultrajoiner_mode_found(data->drm_fd,
> + data->output->config.connector,
> + max_dotclock, &mode);
> +
> + if (is_joiner || is_ultra_joiner)
> + return true;
> +
> + return false;
> +}
> +
> static void run_test(data_t *data, void (*test)(data_t *))
> {
> igt_display_t *display = &data->display;
> @@ -653,6 +674,8 @@ static void run_test(data_t *data, void (*test)(data_t *))
> data->allow_fail = false;
> data->modifier = default_modifier(data);
> igt_dynamic_f("pipe-%s-%s", kmstest_pipe_name(data->pipe), data->output->name) {
> + igt_skip_on_f(is_joiner_mode(data),
> + "Joiner mode found, skipping the test\n");
Can we make this more descriptive? Something like subject "skipping,
async flip not supported on joiner mode" ?
> test_init_fbs(data);
> test(data);
> }
> @@ -674,6 +697,8 @@ static void run_test_with_modifiers(data_t *data, void (*test)(data_t *))
> igt_dynamic_f("pipe-%s-%s-%s", kmstest_pipe_name(data->pipe),
> data->output->name,
> igt_fb_modifier_name(data->modifier)) {
> + igt_skip_on_f(is_joiner_mode(data),
> + "Joiner mode found, skipping the test\n");
> test_init_fbs(data);
> test(data);
> }
next prev parent reply other threads:[~2024-11-14 6:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 3:16 [PATCH i-g-t v1] tests/kms_async_flips: Skip Async flips on joiner output Santhosh Reddy Guddati
2024-10-23 4:00 ` ✓ CI.xeBAT: success for " Patchwork
2024-10-23 4:05 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-23 6:23 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-23 8:08 ` ✗ CI.xeFULL: " Patchwork
2024-10-24 9:34 ` [i-g-t,v1] " Joshi, Kunal1
2024-10-24 11:11 ` [PATCH i-g-t v2] " Santhosh Reddy Guddati
2024-10-30 6:34 ` [i-g-t,v2] " Joshi, Kunal1
2024-11-14 6:04 ` [PATCH i-g-t v2] " Sharma, Swati2
2024-11-14 6:22 ` Sharma, Swati2 [this message]
2024-10-24 12:18 ` ✓ Fi.CI.BAT: success for tests/kms_async_flips: Skip Async flips on joiner output (rev2) Patchwork
2024-10-24 12:51 ` ✓ CI.xeBAT: " Patchwork
2024-10-24 15:55 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-25 11:23 ` ✗ CI.xeFULL: " Patchwork
2024-11-13 12:20 ` [PATCH i-g-t v3 1/1] tests/kms_async_flips: Skip Async flips on joiner output Santhosh Reddy Guddati
2024-11-13 15:58 ` ✓ CI.xeBAT: success for tests/kms_async_flips: Skip Async flips on joiner output (rev3) Patchwork
2024-11-13 15:59 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-13 22:49 ` ✗ 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=1c085de7-2afc-4892-9f79-d9c471272c42@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--cc=kunal1.joshi@intel.com \
--cc=santhosh.reddy.guddati@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