[igt-dev] [PATCH i-g-t] tests/kms_chamelium: Fix waiting for hotplug uevents
Arkadiusz Hiler
arkadiusz.hiler at intel.com
Mon Mar 23 09:15:20 UTC 2020
On Mon, Mar 23, 2020 at 10:48:28AM +0200, Imre Deak wrote:
> The driver can emit multiple hotplug events in response to a hotplug
> interrupt, which may cause tests fail receiving a spurious early hotplug
> event and concluding that an expected state didn't get set. Let's use
> Arek's idea and wait for multiple hotplug events - with the current 20s
> timeout - rechecking if the expected state got set after each hotplug.
>
> The reasons for multiple hotplug events I noticed are:
> - Both a get connector IOCTL and an HPD interrupt can generate a hotplug
> event.
> - Resetting chamelium results in an intermittent state where HPD gets
> asserted, generating a hotplug connect uevent, then HPD gets
> deasserted generating the expected hotplug disconnect uevent.
>
> Suggested-by: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
> Signed-off-by: Imre Deak <imre.deak at intel.com>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler at intel.com>
More information about the igt-dev
mailing list