This check is not really needed: there is no reason the detaching client can be different from the attached one. Should this happen, that would be a bug elsewhere.
Signed-off-by: Luca Ceresoli <[email protected]> --- **NOTE**: I'm not 100% sure this is correct, but it appears so, and other drivers have no such check. And anyway it appears that such a check should belong to the core, not to individual drivers. Comments welcome! To: Kevin Hilman <[email protected]> To: Jerome Brunet <[email protected]> To: Martin Blumenstingl <[email protected]> Cc: [email protected] --- drivers/gpu/drm/meson/meson_dw_mipi_dsi.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/drivers/gpu/drm/meson/meson_dw_mipi_dsi.c b/drivers/gpu/drm/meson/meson_dw_mipi_dsi.c index 66c73c512b0e68ff0e9dbbfaba5f8bf2d347e6b1..4dc726cef5455075def7927a469ae23020ebfec7 100644 --- a/drivers/gpu/drm/meson/meson_dw_mipi_dsi.c +++ b/drivers/gpu/drm/meson/meson_dw_mipi_dsi.c @@ -252,11 +252,6 @@ static int meson_dw_mipi_dsi_host_detach(void *priv_data, { struct meson_dw_mipi_dsi *mipi_dsi = priv_data; - if (device == mipi_dsi->dsi_device) - mipi_dsi->dsi_device = NULL; - else - return -EINVAL; - return phy_exit(mipi_dsi->phy); } -- 2.49.0
