summaryrefslogtreecommitdiff
path: root/tests/kms_chamelium.c
diff options
context:
space:
mode:
authorImre Deak <imre.deak@intel.com>2020-06-03 21:34:17 +0300
committerArkadiusz Hiler <arkadiusz.hiler@intel.com>2020-06-04 12:55:29 +0300
commit53e8c878a6fb5708e63c99403691e8960b86ea9c (patch)
tree5e07178f7b1eaaad31f5619f1cb3f96385bdee80 /tests/kms_chamelium.c
parent1af067a15b3000c559c93d6a8dd5a5079c4f8af0 (diff)
tests/kms_chamelium: Force reprobe after replugging the connector
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> Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Diffstat (limited to 'tests/kms_chamelium.c')
-rw-r--r--tests/kms_chamelium.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/kms_chamelium.c b/tests/kms_chamelium.c
index dc1b8d1e..7d3e0643 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);