summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c
diff options
context:
space:
mode:
authorJyri Sarha <jsarha@ti.com>2018-04-26 11:06:59 +0300
committerThierry Reding <treding@nvidia.com>2018-05-18 11:22:06 +0200
commit38992c57c9c8425dc9cb75efe6f9b9255ea627a0 (patch)
tree6315380f51e94ee951fa3be75f5261302bf76864 /drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c
parent6553b123eae8dd117f6adb4a42e2e6ef8bff321d (diff)
drm/panel: Remove drm_panel_detach() calls from all panel drivers
Remove all drm_panel_detach() calls from all panel drivers and update the kerneldoc for drm_panel_detach(). Setting the connector and drm to NULL when the DRM panel device is going away hardly serves any purpose. Usually the whole memory structure is freed right after the remove call. However, calling the detach function from the master DRM device, and setting the connector pointer to NULL, has the logic of marking the panel again as available for another DRM master to attach. The usual situation would be the same DRM master device binding again. Signed-off-by: Jyri Sarha <jsarha@ti.com> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Thierry Reding <treding@nvidia.com> Link: https://patchwork.freedesktop.org/patch/msgid/464b8d330d6b4c94cfb5aad2ca9ea7eb2c52d934.1524727888.git.jsarha@ti.com
Diffstat (limited to 'drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c')
-rw-r--r--drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c b/drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c
index 494aa9b1628a..e5cae0050f52 100644
--- a/drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c
+++ b/drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c
@@ -327,7 +327,6 @@ static int sharp_nt_panel_remove(struct mipi_dsi_device *dsi)
if (ret < 0)
dev_err(&dsi->dev, "failed to detach from DSI host: %d\n", ret);
- drm_panel_detach(&sharp_nt->base);
sharp_nt_panel_del(sharp_nt);
return 0;