Doesn't protect anything at all, and probably just here because a long
time ago dev->struct_mutex was required to allocate gem objects.

With this patch exynos is completely struct_mutex free!

Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>
---
 drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 22 ++++++++--------------
 1 file changed, 8 insertions(+), 14 deletions(-)

diff --git a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c 
b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
index a221f753ad9c..4e2166d4a964 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
+++ b/drivers/gpu/drm/exynos/exynos_drm_fbdev.c
@@ -137,8 +137,6 @@ static int exynos_drm_fbdev_create(struct drm_fb_helper 
*helper,
        mode_cmd.pixel_format = drm_mode_legacy_fb_format(sizes->surface_bpp,
                                                          sizes->surface_depth);

-       mutex_lock(&dev->struct_mutex);
-
        size = mode_cmd.pitches[0] * mode_cmd.height;

        obj = exynos_drm_gem_create(dev, EXYNOS_BO_CONTIG, size);
@@ -152,10 +150,8 @@ static int exynos_drm_fbdev_create(struct drm_fb_helper 
*helper,
                obj = exynos_drm_gem_create(dev, EXYNOS_BO_NONCONTIG, size);
        }

-       if (IS_ERR(obj)) {
-               ret = PTR_ERR(obj);
-               goto out;
-       }
+       if (IS_ERR(obj))
+               return PTR_ERR(obj);

        exynos_fbdev->obj = obj;

@@ -170,7 +166,6 @@ static int exynos_drm_fbdev_create(struct drm_fb_helper 
*helper,
        if (ret < 0)
                goto err_destroy_framebuffer;

-       mutex_unlock(&dev->struct_mutex);
        return ret;

 err_destroy_framebuffer:
@@ -178,13 +173,12 @@ err_destroy_framebuffer:
 err_destroy_gem:
        exynos_drm_gem_destroy(obj);

-/*
- * if failed, all resources allocated above would be released by
- * drm_mode_config_cleanup() when drm_load() had been called prior
- * to any specific driver such as fimd or hdmi driver.
- */
-out:
-       mutex_unlock(&dev->struct_mutex);
+       /*
+        * if failed, all resources allocated above would be released by
+        * drm_mode_config_cleanup() when drm_load() had been called prior
+        * to any specific driver such as fimd or hdmi driver.
+        */
+
        return ret;
 }

-- 
2.5.1

Reply via email to