drm/bridge: tfp410: fix use of cancel_delayed_work_sync
authorTomi Valkeinen <tomi.valkeinen@ti.com>
Mon, 10 Jun 2019 13:57:39 +0000 (16:57 +0300)
committerAndrzej Hajda <a.hajda@samsung.com>
Fri, 14 Jun 2019 07:46:14 +0000 (09:46 +0200)
We use delayed_work in HPD handling, and cancel any scheduled work in
tfp410_fini using cancel_delayed_work_sync(). However, we have only
initialized the delayed work if we actually have a HPD interrupt
configured in the DT, but in the tfp410_fini, we always cancel the work,
possibly causing a WARN().

Fix this by doing the cancel only if we actually had the delayed work
set up.

Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190610135739.6077-2-tomi.valkeinen@ti.com
drivers/gpu/drm/bridge/ti-tfp410.c

index 9f0836cc712bde0f8b29c554edecd8886eb83ebf..07b695172db25c2750294430773dacaeb3aa51fe 100644 (file)
@@ -381,7 +381,8 @@ static int tfp410_fini(struct device *dev)
 {
        struct tfp410 *dvi = dev_get_drvdata(dev);
 
-       cancel_delayed_work_sync(&dvi->hpd_work);
+       if (dvi->hpd_irq >= 0)
+               cancel_delayed_work_sync(&dvi->hpd_work);
 
        drm_bridge_remove(&dvi->bridge);