1. 23 12月, 2014 9 次提交
  2. 03 12月, 2014 1 次提交
  3. 27 11月, 2014 6 次提交
  4. 13 11月, 2014 2 次提交
    • T
      drm/rcar: gem: dumb: pitch is an output · 7e295a36
      Thierry Reding 提交于
      When creating a dumb buffer object using the DRM_IOCTL_MODE_CREATE_DUMB
      IOCTL, only the width, height, bpp and flags fields are inputs. The
      caller is not guaranteed to zero out or set handle, pitch and size.
      Drivers must not treat these values as possible inputs, otherwise they
      may use uninitialized memory during the computation of the framebuffer
      size.
      
      The R-Car DU driver treats the pitch passed in from userspace as minimum
      and will only overwrite it when the driver-computed pitch is larger,
      allowing userspace to, intentionally or not, overallocate framebuffers.
      
      Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
      Reviewed-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: NThierry Reding <treding@nvidia.com>
      7e295a36
    • T
      drm/cma: Introduce drm_gem_cma_dumb_create_internal() · 6d178291
      Thierry Reding 提交于
      This function is similar to drm_gem_cma_dumb_create() but targetted at
      kernel internal users so that they can override the pitch and size
      requirements of the dumb buffer.
      
      It is important to make this difference because the IOCTL says that the
      pitch and size fields are to be considered outputs and therefore should
      not be used in computations of the framebuffer size. Internal users may
      still want to use this code to avoid duplication and at the same time
      pass on additional, driver-specific restrictions on the pitch and size.
      
      While at it, convert the R-Car DU driver, the single user that overrides
      the pitch, to use the new internal helper.
      Reviewed-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: NThierry Reding <treding@nvidia.com>
      6d178291
  5. 05 11月, 2014 1 次提交
  6. 20 10月, 2014 1 次提交
  7. 15 9月, 2014 3 次提交
  8. 10 9月, 2014 1 次提交
  9. 30 7月, 2014 1 次提交
  10. 22 7月, 2014 1 次提交
  11. 19 6月, 2014 1 次提交
  12. 27 5月, 2014 1 次提交
  13. 22 4月, 2014 1 次提交
    • A
      drm: make mode_valid callback optional · f9b0e251
      Andrzej Hajda 提交于
      Many drm connectors do not need mode validation.
      The patch makes this callback optional and removes dumb implementations.
      
      v2: Rebase:
      - imx move to a shared (but still dummy) ->mode_valid implementation.
      - probe helpers have been extracted to drm_probe_helper.c
      
      Signed-off-by: Andrzej Hajda <a.hajda@samsung.com> (v1)
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      f9b0e251
  14. 04 4月, 2014 1 次提交
  15. 02 4月, 2014 1 次提交
    • M
      drm: Replace crtc fb with primary plane fb (v3) · f4510a27
      Matt Roper 提交于
      Now that CRTC's have a primary plane, there's no need to track the
      framebuffer in the CRTC.  Replace all references to the CRTC fb with the
      primary plane's fb.
      
      This patch was generated by the Coccinelle semantic patching tool using
      the following rules:
      
              @@ struct drm_crtc C; @@
              -   (C).fb
              +   C.primary->fb
      
              @@ struct drm_crtc *C; @@
              -   (C)->fb
              +   C->primary->fb
      
      v3: Generate patch via coccinelle.  Actual removal of crtc->fb has been
          moved to a subsequent patch.
      
      v2: Fixup several lingering crtc->fb instances that were missed in the
          first patch iteration.  [Rob Clark]
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Reviewed-by: NRob Clark <robdclark@gmail.com>
      f4510a27
  16. 18 12月, 2013 2 次提交
  17. 02 12月, 2013 6 次提交
  18. 12 10月, 2013 1 次提交
    • D
      drm: Add separate Kconfig option for fbdev helpers · 92b6f89f
      Daniel Vetter 提交于
      For drivers which might want to disable fbdev legacy support.
      
      Select the new option in all drivers for now, so this shouldn't result
      in any change. Drivers need some work anyway to make fbdev support
      optional (if they have it implemented, that is), so the recommended
      way to expose this is by adding per-driver options. At least as long
      as most drivers don't support disabling the fbdev support.
      
      v2: Update for new drm drivers msm and rcar-du. Note that Rob's msm
      driver can already take advantage of this, which allows us to build
      msm without any fbdev depencies in the kernel!
      
      v3: Move the MODULE_* stuff from the fbdev helper file to
      drm_crtc_helper.c.
      
      Cc: David Herrmann <dh.herrmann@gmail.com>
      Cc: Rob Clark <robdclark@gmail.com>
      Reviewed-by: NRob Clark <robdclark@gmail.com>
      Acked-by: NDave Airlie <airlied@linux.ie>
      Reviewed-by: NChon Ming Lee <chon.ming.lee@intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      92b6f89f