drm/exynos: move order to register vidi kms driver 88/43888/1 accepted/tizen/mobile/20150717.103244 accepted/tizen/tv/20150717.103406 accepted/tizen/wearable/20150717.103530 submit/tizen/20150717.090857
authorJoonyoung Shim <jy0922.shim@samsung.com>
Wed, 15 Jul 2015 01:48:06 +0000 (10:48 +0900)
committerJoonyoung Shim <jy0922.shim@samsung.com>
Wed, 15 Jul 2015 05:13:17 +0000 (14:13 +0900)
The vidi is virtual kms driver and now it is registered earlier than
actual hw kms drivers, so it will occupy crtc index 0. Some users
assume the condition yet that actual hw kms driver has crtc index 0.
It may or may not be matter but let's arrange register order.

Change-Id: Id3bbd0eeaf7ba2e584c21e39bb6971a483365ac9
Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
drivers/gpu/drm/exynos/exynos_drm_drv.c

index 1e4ab13dc13addf6c0c2040e1c3d4095d867bc44..fe60dd4b44d158eb535a53a3006bd17b3a109f08 100644 (file)
@@ -379,9 +379,6 @@ static struct platform_driver exynos_drm_platform_driver;
  * because connector requires pipe number of its crtc during initialization.
  */
 static struct platform_driver *const exynos_drm_kms_drivers[] = {
-#ifdef CONFIG_DRM_EXYNOS_VIDI
-       &vidi_driver,
-#endif
 #ifdef CONFIG_DRM_EXYNOS_FIMD
        &fimd_driver,
 #endif
@@ -401,6 +398,9 @@ static struct platform_driver *const exynos_drm_kms_drivers[] = {
        &mixer_driver,
        &hdmi_driver,
 #endif
+#ifdef CONFIG_DRM_EXYNOS_VIDI
+       &vidi_driver,
+#endif
 };
 
 static struct platform_driver *const exynos_drm_non_kms_drivers[] = {