public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: sumit kishore <sumit.kishore@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: pranay.samala@intel.com, Sumit Kishore <sumit.kishore@intel.com>
Subject: [PATCH i-g-t v3] tests/kms_invalid_mode: Add igt_info when test skips
Date: Wed,  1 Apr 2026 15:44:11 +0530	[thread overview]
Message-ID: <20260401101411.408817-1-sumit.kishore@intel.com> (raw)

From: Sumit Kishore <sumit.kishore@intel.com>

Add igt_info to print the reason for test skip,
when an invalid mode is requested on eDP display.

v2: Update commit title and description.
    Add igt_info message.

Signed-off-by: Sumit Kishore <sumit.kishore@intel.com>
---
 tests/kms_invalid_mode.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/kms_invalid_mode.c b/tests/kms_invalid_mode.c
index 5edffb649..1a4563153 100644
--- a/tests/kms_invalid_mode.c
+++ b/tests/kms_invalid_mode.c
@@ -136,8 +136,10 @@ adjust_mode_clock_too_high(data_t *data, drmModeModeInfoPtr mode)
 	 * roughly match the user will get. For now skip the
 	 * test on  any connector with a fixed mode.
 	 */
-	if (has_scaling_mode_prop(data))
+	if (has_scaling_mode_prop(data)) {
+		igt_info("Skipping as %s has scaling properties\n", data->output->name);
 		return false;
+	}
 
 	/*
 	 * Newer platforms can support modes higher than the maximum dot clock
-- 
2.43.0


             reply	other threads:[~2026-04-01 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 10:14 sumit kishore [this message]
2026-04-01 17:43 ` ✓ Xe.CI.BAT: success for tests/kms_invalid_mode: Add igt_info when test skips Patchwork
2026-04-01 17:53 ` ✓ i915.CI.BAT: " Patchwork
2026-04-01 22:26 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-02 12:22 ` ✓ i915.CI.Full: " 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=20260401101411.408817-1-sumit.kishore@intel.com \
    --to=sumit.kishore@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=pranay.samala@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