[PATCH 00/10] drm/exynos: prepare multiple display controllers

[Seung-Woo Kim]

This patch is preparing multiple display controllers, FIMD and HDMI.
- added padding into ioctl structure to be 64 bit align
- added kms poll to handle hpd event
- fixed converting between display mode and timing
- fixed connector and crtc callbacks to call proper display driver
- code clean

based git repository is below:
git://people.freedesktop.org/~airlied/linux.git
branch name: drm-core-next
base commit-id: 1717c0e23f411147490c7a3312b894f0ea9a5fb1

Inki Dae (3):
  drm/exynos: added padding to be 64-bit align.
  drm/exynos: added manager object to connector
  drm/exynos: changed exynos_drm_display to exynos_drm_display_ops

Joonyoung Shim (1):
  drm/exynos: restored kernel_fb_list when reiniting fb_helper

Seung-Woo Kim (6):
  drm/exynos: added kms poll for handling hpd event
  drm/exynos: fixed connector flag with hpd and interlace scan for hdmi
  drm/exynos: fixed converting between display mode and timing
  drm/exynos: removed meaningless parameter from fbdev update
  drm/exynos: added crtc dpms for disable crtc
  drm/exynos: checked for null pointer

 drivers/gpu/drm/exynos/exynos_drm_connector.c |   78 ++++++++++++++++++-------
 drivers/gpu/drm/exynos/exynos_drm_crtc.c      |   16 ++++-
 drivers/gpu/drm/exynos/exynos_drm_drv.c       |    5 ++
 drivers/gpu/drm/exynos/exynos_drm_drv.h       |    4 +-
 drivers/gpu/drm/exynos/exynos_drm_encoder.c   |   64 +++++++++++++++++----
 drivers/gpu/drm/exynos/exynos_drm_encoder.h   |    1 +
 drivers/gpu/drm/exynos/exynos_drm_fb.c        |   12 ++++
 drivers/gpu/drm/exynos/exynos_drm_fbdev.c     |   29 ++++++---
 drivers/gpu/drm/exynos/exynos_drm_fimd.c      |    4 +-
 include/drm/exynos_drm.h                      |    2 +
 10 files changed, 165 insertions(+), 50 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/