From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Swati Sharma <swati2.sharma@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 3/3] tests/kms_feature_discovery: detect mst configuration
Date: Thu, 7 Sep 2023 22:17:13 +0530 [thread overview]
Message-ID: <a4c2cc23-6bfd-5e55-b863-e5379b3a324c@intel.com> (raw)
In-Reply-To: <20230907143214.1280453-4-swati2.sharma@intel.com>
Hi Swati,
On Thu-07-09-2023 08:02 pm, Swati Sharma wrote:
> Add test to detect if we have mst configuration.
>
> v2: -use for_each_connected_output() (Bhanu)
> -don't use helper (Bhanu)
> -add documentation
>
> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
> Reviewed-by: Kunal Joshi <kunal1.joshi@intel.com>
> ---
> tests/kms_feature_discovery.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/tests/kms_feature_discovery.c b/tests/kms_feature_discovery.c
> index 49958fd88..a178010d6 100644
> --- a/tests/kms_feature_discovery.c
> +++ b/tests/kms_feature_discovery.c
> @@ -71,6 +71,14 @@
> * Run type: FULL
> * Test category: functionality test
> *
> + * SUBTEST: dp-mst
> + * Description: Make sure that we have DP-MST configuration.
> + * Driver requirement: i915, xe
> + * Functionality: feature_discovery, mst
> + * Mega feature: General Display Features
> + * Run type: FULL
> + * Test category: functionality test
> + *
> * arg[1].values: 2, 3, 4
> */
>
> @@ -164,5 +172,23 @@ igt_main {
> igt_subtest("psr2") {
> igt_require(psr_sink_support(fd, debugfs_fd, PSR_MODE_2));
> }
> +
> + igt_describe("Make sure that we have DP-MST configuration.");
> + igt_subtest("dp-mst") {
> + struct kmstest_connector_config config;
> + igt_output_t *output;
> + const char *encoder;
> + int ret;
----------------------------^
Please initialize 'ret' with -1, otherwise test will send a false
positive on headless configs.
> +
> + for_each_connected_output(&display, output) {
> + kmstest_get_connector_config(fd, output->config.connector->connector_id, -1, &config);
> + encoder = kmstest_encoder_type_str(config.encoder->encoder_type);
> +
> + ret = strcmp(encoder, "DP MST");
> + if (ret == 0)
> + break;
> + }
> + igt_require(ret == 0);
Please add some meaningful message on skip.
- Bhanu
> + }
> }
> }
next prev parent reply other threads:[~2023-09-07 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 14:32 [igt-dev] [PATCH i-g-t 0/3] enable feature-discovery tests Swati Sharma
2023-09-07 14:32 ` [igt-dev] [PATCH i-g-t 1/3] tests: rename feature_discovery to kms_feature_discovery Swati Sharma
2023-09-07 16:38 ` Modem, Bhanuprakash
2023-09-07 17:33 ` Kamil Konieczny
2023-09-08 5:51 ` Sharma, Swati2
2023-09-07 14:32 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel-ci: remove feature_discovery from blocklist Swati Sharma
2023-09-07 17:33 ` Kamil Konieczny
2023-09-07 14:32 ` [igt-dev] [PATCH i-g-t 3/3] tests/kms_feature_discovery: detect mst configuration Swati Sharma
2023-09-07 16:47 ` Modem, Bhanuprakash [this message]
2023-09-07 16:09 ` [igt-dev] ✓ CI.xeBAT: success for enable feature-discovery tests Patchwork
2023-09-07 16:13 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-09-07 18:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=a4c2cc23-6bfd-5e55-b863-e5379b3a324c@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kunal1.joshi@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