From: Michael Williamson <michael.william...@criticallink.com>

The logic to configure polling (vs async/irq notification) of hot-plug
events was not correct.  If the connected bridge requires polling,
then inform the upstream bridge we also require polling.

Signed-off-by: Michael Williamson <michael.william...@criticallink.com>
Signed-off-by: Jonathan Cormier <jcorm...@criticallink.com>
---
 drivers/gpu/drm/bridge/ti-tfp410.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/bridge/ti-tfp410.c 
b/drivers/gpu/drm/bridge/ti-tfp410.c
index 323a6d9ed188..837e1f81a0ff 100644
--- a/drivers/gpu/drm/bridge/ti-tfp410.c
+++ b/drivers/gpu/drm/bridge/ti-tfp410.c
@@ -155,7 +155,7 @@ static int tfp410_attach(struct drm_bridge *bridge,
                return -ENODEV;
        }
 
-       if (dvi->next_bridge->ops & DRM_BRIDGE_OP_DETECT)
+       if (dvi->next_bridge->ops & DRM_BRIDGE_OP_HPD)
                dvi->connector.polled = DRM_CONNECTOR_POLL_HPD;
        else
                dvi->connector.polled = DRM_CONNECTOR_POLL_CONNECT | 
DRM_CONNECTOR_POLL_DISCONNECT;

-- 
2.25.1

Reply via email to