1. 26 3月, 2014 14 次提交
  2. 24 3月, 2014 4 次提交
    • D
      drm/bridge/ptn3460: fix modular build · 63ac07cd
      Dave Airlie 提交于
      This failed to build =m, quick fix.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      63ac07cd
    • D
      Merge branch 'exynos-drm-next' of... · a5a2391e
      Dave Airlie 提交于
      Merge branch 'exynos-drm-next' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next
      
      Highlights
      ----------
      
      Re-factoring works over the exynos drm framework.
        - drm_crtc, drm_encoder/drm_connector are implemented by sub drivers
          directly.
        - Removing pm interfaces from each sub driver, and implementing them
          at top level of exynos drm.
      Add DisplayPort Transmitter driver.
        - Just moving existing driver from drivers/vides/exynos into
          drivers/gpu/drm/exynos.
      Add new LVDS bridge driver, PTN3460.
        - Placed in drivers/gpu/drm/bridge, and this device is used to transfer
          image signal from DP(DisplayPort) to LVDS Panel.
          So this driver will be used with DP driver moved into exynos drm.
      Add parallel panel support
        - With the re-factoring patch series, existing parallel panel support was
          broken by moving exynos_drm_display ops into each real connector driver,
          DP. So this patch series adds a new parallel panel module,
          exynos_drm_dpi, for supporting parallel panel, and also adds relevant
          bindings.
      Some fixups and cleanups.
      
      * 'exynos-drm-next' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos: (45 commits)
        drm/exynos: fimd: remove unused variable
        ARM: dts: exynos4210-universal: add exynos/fimd node
        drm/exynos: restore parallel output interface support
        exynos/fimd: add parallel output related bindings
        drm/exynos: correct timing porch conversion
        drm/exynos: init kms poll after creation of connectors
        drm/exynos: delay fbdev initialization until an output is connected
        drm/exynos: fix unnecessary resource cleanup
        drm/exynos: hdmi: use i2c_adapter instead of i2c_client
        drm/exynos: hdmi: consider APB PHY
        drm/exynos: Remove the exynos_drm_connector shim
        drm/exynos: Implement lvds bridge discovery to DP driver
        drm/bridge: Add PTN3460 bridge driver
        drm/exynos: Implement drm_connector directly in vidi driver
        drm/exynos: Implement drm_connector directly in dp driver
        drm/exynos: Implement drm_connector in hdmi directly
        drm/exynos: Add create_connector callback
        drm/exynos: Consolidate suspend/resume in drm_drv
        drm/exynos: Clean up FIMD power on/off routines
        drm/exynos: Implement dpms display callback in DP
        ...
      a5a2391e
    • D
      drm/gma500: add locking to fixed panel edid probing · c46145ae
      Daniel Vetter 提交于
      With the recent addition of locking checks in
      
      commit 62ff94a5
      Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
      AuthorDate: Thu Jan 23 22:18:47 2014 +0100
      
          drm/crtc-helper: remove LOCKING from kerneldoc
      
      drm_add_edid_modes started to WARN about the mode_config.mutex not
      being held in the lvds and dp initialization code.
      
      Now since this is init code locking is fairly redudant if it wouldn't
      be for the drm core registering sysfs files a bit early. And the
      locking WARNINGs nicely enforce that indeed all access to the mode
      lists are properly protected. And a full audit shows that only i915
      and gma500 touch the modes lists at init time.
      
      Hence I've opted to wrap up this entire mode detection sequence for
      fixed panels with the mode_config mutex for both lvds and edp outputs.
      
      Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Acked-by: NPatrik Jakobsson <patrik.r.jakobsson@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      c46145ae
    • D
      drm/i915: add locking to fixed panel edid probing · 060c8778
      Daniel Vetter 提交于
      With the recent addition of locking checks in
      
      commit 62ff94a5
      Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
      AuthorDate: Thu Jan 23 22:18:47 2014 +0100
      
          drm/crtc-helper: remove LOCKING from kerneldoc
      
      drm_add_edid_modes started to WARN about the mode_config.mutex not
      being held in the lvds and dp initialization code.
      
      Now since this is init code locking is fairly redudant if it wouldn't
      be for the drm core registering sysfs files a bit early. And the
      locking WARNINGs nicely enforce that indeed all access to the mode
      lists are properly protected. And a full audit shows that only i915
      and gma500 touch the modes lists at init time.
      
      Hence I've opted to wrap up this entire mode detection sequence for
      fixed panels with the mode_config mutex for both lvds and edp outputs.
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      060c8778
  3. 23 3月, 2014 22 次提交