summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/omapdrm/omap_fbdev.c
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart@ideasonboard.com>2016-12-14 13:41:24 +0300
committerLaurent Pinchart <laurent.pinchart@ideasonboard.com>2016-12-19 12:25:05 +0300
commite57e17cc40d3297fbb279c6c0e9613bdc81ef893 (patch)
treea5173ccd8a251f85f80d2e652fd22e1c1691c7ef /drivers/gpu/drm/omapdrm/omap_fbdev.c
parentd501b12999eb9cdfc488127fabaf794171dd9bbf (diff)
downloadlinux-e57e17cc40d3297fbb279c6c0e9613bdc81ef893.tar.xz
drm: Move vblank cleanup from unregister to release
Calling drm_vblank_cleanup() in drm_dev_unregister() causes issues with drivers that have moved away from the .load() and .unload() midlayer. Those drivers call drm_dev_unregister() as the first operation at unbind time, before shutting down the device. This results in warnings due to drm_vblank_cleanup() being called with vblank interrupts still active, and then to vblank events being sent after cleanup. Fix the problem by moving vblank cleanup from drm_dev_unregister() to drm_dev_release() that is guaranteed to be called after drivers shut down the device. Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Tested-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
Diffstat (limited to 'drivers/gpu/drm/omapdrm/omap_fbdev.c')
0 files changed, 0 insertions, 0 deletions