From: Karthik B S <karthik.b.s@intel.com>
To: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: <swati2.sharma@intel.com>
Subject: Re: [PATCH i-g-t v3 1/1] tests/intel/kms_joiner: switch modeset from uj to bj and vice-versa
Date: Thu, 3 Oct 2024 09:53:56 +0530 [thread overview]
Message-ID: <86709185-c52d-400d-937c-93d6ddc2e322@intel.com> (raw)
In-Reply-To: <20241001073448.2252300-2-santhosh.reddy.guddati@intel.com>
Hi Santhosh,
On 10/1/2024 1:04 PM, Santhosh Reddy Guddati wrote:
> Add a subtest to validate switching from ultra joiner to big joiner
> and vice-versa.
>
> v2: Add new subtests for switching without force joiner (Karthik)
> v3: start with uj to bj switch, if not available switch to force mode
>
> Signed-off-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
> ---
> tests/intel/kms_joiner.c | 53 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 53 insertions(+)
>
> diff --git a/tests/intel/kms_joiner.c b/tests/intel/kms_joiner.c
> index 508e82ce3..7c7436b9a 100644
> --- a/tests/intel/kms_joiner.c
> +++ b/tests/intel/kms_joiner.c
> @@ -71,6 +71,9 @@
> * SUBTEST: invalid-modeset-force-ultra-joiner
> * Description: Verify if the modeset on the other pipes are rejected when
> * the pipe A is active with force ultra joiner modeset.
> + *
> + * SUBTEST: switch-modeset-big-joiner-ultra-joiner
> + * Description: Verify modeset switch between ultra joiner and big joiner.
> */
> IGT_TEST_DESCRIPTION("Test joiner / force joiner");
>
> @@ -507,6 +510,56 @@ igt_main
> test_ultra_joiner(&data, false, false, false);
> }
>
> + igt_describe("Verify modeset switch between joiner and ultra joiner");
> + igt_subtest_with_dynamic("switch-modeset-big-joiner-ultra-joiner") {
> + igt_require_f(data.n_pipes > 1,
> + "Minimum 2 pipes required\n");
We need four pipes to support ultra joiner. So we can skip the test if
we don't have 4 pipes.
Also, I would suggest to add the checks to verify if we're able to
support both big and ultra joiner before the start of the dynamic
subtests. If either one is not supported, then just skip the subtest
from here itself rather than starting the dynamic subtest and skipping
from there.
Thanks,
Karthik.B.S
> +
> + igt_dynamic_f("ultra_joiner_to_big_joiner") {
> + if (data.ultra_joiner_output_count > 0) {
> + test_ultra_joiner(&data, false, false, false);
> + } else {
> + igt_require_f(force_joiner_supported &&
> + data.non_ultra_joiner_output_count > 0,
> + "Force joiner not supported on this platform or none of the connected output supports it\n");
> + enable_force_joiner_on_all_non_ultra_joiner_outputs(&data);
> + test_ultra_joiner(&data, false, false, true);
> + }
> + if (data.big_joiner_output_count > 0) {
> + test_single_joiner(&data, data.big_joiner_output_count, false);
> + } else {
> + igt_require_f(force_joiner_supported &&
> + data.non_big_joiner_output_count > 0,
> + "Force joiner not supported on this platform or none of the connected outputs support it\n");
> + enable_force_joiner_on_all_non_big_joiner_outputs(&data);
> + test_single_joiner(&data, data.non_big_joiner_output_count, true);
> + }
> + igt_reset_connectors();
> + }
> +
> + igt_dynamic_f("big_joiner_to_ultra_joiner") {
> + if (data.big_joiner_output_count > 0) {
> + test_single_joiner(&data, data.big_joiner_output_count, false);
> + } else {
> + igt_require_f(force_joiner_supported &&
> + data.non_big_joiner_output_count > 0,
> + "Force joiner not supported on this platform or none of the connected output supports it\n");
> + enable_force_joiner_on_all_non_big_joiner_outputs(&data);
> + test_single_joiner(&data, data.non_big_joiner_output_count, true);
> + }
> + if (data.ultra_joiner_output_count > 0) {
> + test_ultra_joiner(&data, false, false, false);
> + } else {
> + igt_require_f(force_joiner_supported &&
> + data.non_ultra_joiner_output_count > 0,
> + "Force joiner not supported on this platform or none of the connected output supports it\n");
> + enable_force_joiner_on_all_non_ultra_joiner_outputs(&data);
> + test_ultra_joiner(&data, false, false, true);
> + }
> + igt_reset_connectors();
> + }
> + }
> +
> igt_describe("Verify if the modeset on the adjoining pipe is rejected "
> "when the pipe is active with a big joiner modeset");
> igt_subtest_with_dynamic("invalid-modeset-big-joiner") {
next prev parent reply other threads:[~2024-10-03 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 7:34 [PATCH i-g-t v3 0/1] tests/intel/kms_joiner: switch modeset from uj to bj and vice-versa Santhosh Reddy Guddati
2024-10-01 7:34 ` [PATCH i-g-t v3 1/1] " Santhosh Reddy Guddati
2024-10-03 4:23 ` Karthik B S [this message]
2024-10-01 10:37 ` ✓ CI.xeBAT: success for tests/intel/kms_joiner: switch modeset from uj to bj and vice-versa (rev3) Patchwork
2024-10-01 10:44 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-01 18:14 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-02 5:43 ` ✗ Fi.CI.IGT: " 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=86709185-c52d-400d-937c-93d6ddc2e322@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=santhosh.reddy.guddati@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