summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/drm_atomic_helper.c
diff options
context:
space:
mode:
authorAndrea Merello <andrea.merello@gmail.com>2016-08-25 12:04:32 +0300
committerArchit Taneja <architt@codeaurora.org>2016-08-29 06:43:00 +0300
commitcf3bef95e1014233cb1ce89da8cfa5cd22e7412c (patch)
treeaa79bd6123a9669499178ee470ec3bd333b486bd /drivers/gpu/drm/drm_atomic_helper.c
parent6dcf0de7ef10244b17442f47956a1d9fabe2abe1 (diff)
downloadlinux-cf3bef95e1014233cb1ce89da8cfa5cd22e7412c.tar.xz
drm/bridge: introduce bridge detaching mechanism
Up to now, once a bridge has been attached to a DRM device, it cannot be undone. In particular you couldn't rmmod/insmod a DRM driver that uses a bridge, because the bridge would remain bound to the first (dead) driver instance. This patch fixes this by introducing drm_encoder_detach() and a ->detach callback in drm_bridge_funcs for the bridge to be notified about detaches. It's DRM/KMS driver responsibility to call drm_encoder_detach(). While adding the bridge detach callback, with its kerneldoc, I also added kerneldoc for attach callback. Few other kerneldocs fixes around there are included. Suggested-by: Daniel Vetter <daniel@ffwll.ch> Suggested-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Andrea Merello <andrea.merello@gmail.com> Cc: Archit Taneja <architt@codeaurora.org> Cc: David Airlie <airlied@linux.ie> Cc: Daniel Vetter <daniel@ffwll.ch> Cc: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Archit Taneja <architt@codeaurora.org> Link: http://patchwork.freedesktop.org/patch/msgid/1472115874-6219-1-git-send-email-andrea.merello@gmail.com
Diffstat (limited to 'drivers/gpu/drm/drm_atomic_helper.c')
0 files changed, 0 insertions, 0 deletions