summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/bridge/adv7511/Makefile
diff options
context:
space:
mode:
authorArchit Taneja <architt@codeaurora.org>2016-06-15 16:20:45 +0530
committerArchit Taneja <architt@codeaurora.org>2016-07-13 14:24:36 +0530
commitf0bfcc22d9822947b0ad3095e8363eab5261864c (patch)
tree2ab24e01aa051c3f481c043c8bca6de26507ae94 /drivers/gpu/drm/bridge/adv7511/Makefile
parentc582778900425d0cf2a5687a84b0125fee797d32 (diff)
downloadtalos-op-linux-f0bfcc22d9822947b0ad3095e8363eab5261864c.tar.gz
talos-op-linux-f0bfcc22d9822947b0ad3095e8363eab5261864c.zip
drm/bridge: adv7511: Fix mutex deadlock when interrupts are disabled
When the adv7511 i2c client doesn't have an interrupt line, we observe a deadlock on caused by trying to lock drm device's mode_config.mutex twice in the same context. Here is the sequence that causes it: ioctl DRM_IOCTL_MODE_GETCONNECTOR from userspace drm_mode_getconnector (acquires mode_config mutex) connector->fill_modes() drm_helper_probe_single_connector_modes connector_funcs->get_modes adv7511_encoder_get_modes adv7511_get_edid_block adv7511_irq_process drm_helper_hpd_irq_event (acquires mode_config mutex again) In adv7511_irq_process, don't call drm_helper_hpd_irq_event when not called from the interrupt handler. It doesn't serve any purpose there anyway. Signed-off-by: Archit Taneja <architt@codeaurora.org>
Diffstat (limited to 'drivers/gpu/drm/bridge/adv7511/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud