From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH] tests/kms_setmode: Add info as comment for valid scenario
Date: Wed, 20 Sep 2023 16:01:28 +0530 [thread overview]
Message-ID: <20230920103128.1016220-1-jeevan.b@intel.com> (raw)
Describe the valid scenario for 'basic-clone-single-crtc' and
'basic-clone-single-crtc' tests, as these tests are skipped if
a valid scenario is not found, which can cause confusion during
bug analysis.
Signed-off-by: Jeevan B <jeevan.b@intel.com>
cc: Swati Sharma <swati2.sharma@intel.com>
---
tests/kms_setmode.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tests/kms_setmode.c b/tests/kms_setmode.c
index 32a6fb690..14bc91198 100644
--- a/tests/kms_setmode.c
+++ b/tests/kms_setmode.c
@@ -979,6 +979,13 @@ const char *help_str =
" -t <test id>\tRun only the test with this id\n"
" -e \t\tExtend to run on all pipes. (By default tests will run on two pipes only)\n";
+/*
+ * basic-clone-single-crtc allows the use of a single CRTC for two connectors, for instance,
+ * in the case of a VGA and an HDMI connector. Similarly, for invalid-clone-exclusive-crtc
+ * when each connector uses its own CRTC, for instance, when a connector uses a CRTC that is
+ * not compatible with the connector.
+ */
+
igt_main_args("det:", NULL, help_str, opt_handler, NULL)
{
const struct {
--
2.25.1
next reply other threads:[~2023-09-20 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 10:31 Jeevan B [this message]
2023-09-20 11:26 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_setmode: Add info as comment for valid scenario (rev2) Patchwork
2023-09-20 11:47 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-09-20 15:32 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 15:19 [igt-dev] [PATCH] tests/kms_setmode: Add info as comment for valid scenario Jeevan B
2023-09-26 5:58 ` Sharma, Swati2
2023-09-20 6:08 Jeevan B
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=20230920103128.1016220-1-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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