Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kunal Joshi <kunal1.joshi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: [igt-dev] [PATCH 2/2] tests/chamelium/kms_chamelium_hpd: issue disabling modeset when for very plug/unplug cycle
Date: Wed, 15 Mar 2023 15:36:57 +0530	[thread overview]
Message-ID: <20230315100657.3385384-3-kunal1.joshi@intel.com> (raw)
In-Reply-To: <20230315100657.3385384-1-kunal1.joshi@intel.com>

It is known issue that we don't get hotplug with enabled
mode on TypeC connector, issue a disabling modeset for
every plug/unplug cycle

Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
---
 tests/chamelium/kms_chamelium_hpd.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/chamelium/kms_chamelium_hpd.c b/tests/chamelium/kms_chamelium_hpd.c
index d9718d76..2b17ce29 100644
--- a/tests/chamelium/kms_chamelium_hpd.c
+++ b/tests/chamelium/kms_chamelium_hpd.c
@@ -190,6 +190,7 @@ static void test_hotplug_for_each_pipe(chamelium_data_t *data,
 						   DRM_MODE_DISCONNECTED);
 
 	for_each_pipe(&data->display, pipe) {
+		igt_modeset_disable_all_outputs(&data->display);
 		igt_flush_uevents(mon);
 		/* Check if we get a sysfs hotplug event */
 		chamelium_plug(data->chamelium, port);
-- 
2.25.1

  parent reply	other threads:[~2023-03-15 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 10:06 [igt-dev] [PATCH 0/2] fix minor chamelium issues Kunal Joshi
2023-03-15 10:06 ` [igt-dev] [PATCH 1/2] tests/chamelium/kms_chamelium_edid: reset state before starting subtest Kunal Joshi
2023-03-23 14:31   ` Karthik B S
2023-03-15 10:06 ` Kunal Joshi [this message]
2023-03-23 14:32   ` [igt-dev] [PATCH 2/2] tests/chamelium/kms_chamelium_hpd: issue disabling modeset when for very plug/unplug cycle Karthik B S
2023-03-15 10:46 ` [igt-dev] ✓ Fi.CI.BAT: success for fix minor chamelium issues Patchwork
2023-03-16  1:07 ` [igt-dev] ✓ 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=20230315100657.3385384-3-kunal1.joshi@intel.com \
    --to=kunal1.joshi@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