From: Imre Deak <imre.deak@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] tests/kms_chamelium: Force reprobe after replugging the connector
Date: Wed, 3 Jun 2020 21:34:17 +0300 [thread overview]
Message-ID: <20200603183417.14626-1-imre.deak@intel.com> (raw)
After replugging a connector and the kernel reports the connector as
connected the cached modes returned by drmModeGetConnectorCurrent() (the
kernel's cached list of modes) may be stale. The modes will be only
updated by a full reprobe. Ensure this by setting output->force_reprobe
which will result in calling drmModeGetConnector().
This fixes sporadic test failures due to seeing no modes unexpectedly.
So far things happened to work, because some in-kernel user of the
output - like fbdev - does a full reprobe sometime after the hotplug
event.
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
tests/kms_chamelium.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/kms_chamelium.c b/tests/kms_chamelium.c
index dc1b8d1e3..7d3e06433 100644
--- a/tests/kms_chamelium.c
+++ b/tests/kms_chamelium.c
@@ -126,6 +126,7 @@ reprobe_connector(data_t *data, struct chamelium_port *port)
/* let's make sure that igt_display is up to date too */
output = igt_output_from_connector(&data->display, connector);
+ output->force_reprobe = true;
igt_output_refresh(output);
drmModeFreeConnector(connector);
--
2.23.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-06-03 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 18:34 Imre Deak [this message]
2020-06-03 19:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_chamelium: Force reprobe after replugging the connector Patchwork
2020-06-04 6:28 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2020-06-04 9:31 ` [igt-dev] [PATCH i-g-t] " Arkadiusz Hiler
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=20200603183417.14626-1-imre.deak@intel.com \
--to=imre.deak@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