1. 19 8月, 2013 1 次提交
    • R
      drm/omap: use flip-work helper · 5833bd2f
      Rob Clark 提交于
      And simplify how we hold a ref+pin to what is being scanned out by using
      fb refcnt'ing.  The previous logic pre-dated fb refcnt, and as a result
      was less straightforward than it could have been.  By holding a ref to
      the fb, we don't have to care about how many plane's there are and
      holding a ref to each color plane's bo.
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      5833bd2f
  2. 17 2月, 2013 1 次提交
    • R
      drm/omap: move out of staging · 8bb0daff
      Rob Clark 提交于
      Now that the omapdss interface has been reworked so that omapdrm can use
      dispc directly, we have been able to fix the remaining functional kms
      issues with omapdrm.  And in the mean time the PM sequencing and many
      other of that open issues have been solved.  So I think it makes sense
      to finally move omapdrm out of staging.
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      8bb0daff
  3. 12 2月, 2013 1 次提交
  4. 20 1月, 2013 1 次提交
    • D
      drm/<drivers>: reorder framebuffer init sequence · c7d73f6a
      Daniel Vetter 提交于
      With more fine-grained locking we can no longer rely on the big
      mode_config lock to prevent concurrent access to mode resources
      like framebuffers. Instead a framebuffer becomes accessible to
      other threads as soon as it is added to the relevant lookup
      structures. Hence it needs to be fully set up by the time drivers
      call drm_framebuffer_init.
      
      This patch here is the drivers part of that reorg. Nothing really fancy
      going on safe for three special cases.
      
      - exynos needs to be careful to properly unref all handles.
      - nouveau gets a resource leak fixed for free: one of the error
        cases didn't cleanup the framebuffer, which is now moot since
        the framebuffer is only registered once it is fully set up.
      - vmwgfx requires a slight reordering of operations, I'm hoping I didn't
        break anything (but it's refcount management only, so should be safe).
      
      v2: Split out exynos, since it's a bit more hairy than expected.
      
      v3: Drop bogus cirrus hunk noticed by Richard Wilbur.
      
      v4: Split out vmwgfx since there's a small change in return values.
      
      Reviewed-by: Rob Clark <rob@ti.com> (core + omapdrm)
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      c7d73f6a
  5. 15 11月, 2012 1 次提交
  6. 23 10月, 2012 1 次提交
    • R
      drm/omap: fix issue w/ fb attached to multiple CRTCs · b74af83d
      Rob Clark 提交于
      When the fb is detached from one CRTC/plane, paddr was set back to
      zero.  But really we don't want to do this because the fb could still
      be attached to other CRTC/plane(s).  This originally worked like this
      to catch cases of freeing a pinned fb (but with the refcnt'ing this
      should no longer be needed).  Also, there is checking in the GEM code
      for freeing a pinned GEM object, so this extra level of checking is
      redundant.
      Signed-off-by: NRob Clark <rob@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b74af83d
  7. 16 8月, 2012 1 次提交
  8. 17 5月, 2012 1 次提交
  9. 11 4月, 2012 1 次提交
  10. 08 3月, 2012 4 次提交
  11. 09 2月, 2012 2 次提交
    • R
      staging: drm/omap: multiplanar and YUV support · 9a0774e0
      Rob Clark 提交于
      Add support in framebuffer objects for other color formats and multi-
      planar YUV (NV12).  Since this requires changing the API between the
      plane and fb for getting scanout information (paddr, etc), take
      advantage of the opportunity and put in place a way to allow fb's to
      be unpinned when they are not being scanned out.  Now, before start
      of scanout the plane calls omap_framebuffer_pin() which takes care
      to pin all the backing bo's, then omap_framebuffer_update_scanout()
      however many times to update the scanout address(es), etc, and then
      when finished omap_framebuffer_unpin().
      Signed-off-by: NRob Clark <rob@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      9a0774e0
    • R
      staging: drm/omap: drm API update: addfb2 · ae43d7ca
      Rob Clark 提交于
      Update to reflect changes in:
      "drm: add an fb creation ioctl that takes a pixel format v5"
      Signed-off-by: NRob Clark <rob@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      ae43d7ca
  12. 13 12月, 2011 2 次提交
  13. 09 12月, 2011 1 次提交
    • R
      drm/omap: add GEM support for tiled/dmm buffers · f7f9f453
      Rob Clark 提交于
      TILER/DMM provides two features for omapdrm GEM objects:
      1) providing a physically contiguous view to discontiguous memory
         for hw initiators that cannot otherwise support discontiguous
         buffers (DSS scanout, IVAHD video decode/encode, etc)
      2) providing untiling for 2d tiled buffers, which are used in some
         cases to provide rotation and reduce memory bandwidth for hw
         initiators that tend to access data in 2d block patterns.
      
      For 2d tiled buffers, there are some additional complications when
      it comes to userspace mmap'ings.  For non-tiled buffers, the original
      (potentially physically discontiguous) pages are used to back the
      mmap.  For tiled buffers, we need to mmap via the tiler/dmm region to
      provide an unswizzled view of the buffer.  But (a) the buffer is not
      necessarily pinned in TILER all the time (it can be unmapped when
      there is no DMA access to the buffer), and (b) when they are they
      are pinned, they not necessarily page aligned from the perspective of
      the CPU.  And non-page aligned userspace buffer mapping is evil.
      
      To solve this, we reserve one or more small regions in each of the 2d
      containers when the driver is loaded to use as a "user-GART" where we
      can create a second page-aligned mapping of parts of the buffer being
      accessed from userspace.  Page faulting is used to evict and remap
      different regions of whichever buffers are being accessed from user-
      space.
      Signed-off-by: NRob Clark <rob@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      f7f9f453
  14. 27 11月, 2011 1 次提交
    • R
      staging: add omapdrm DRM/KMS driver for TI OMAP platforms · cd5351f4
      Rob Clark 提交于
      A DRM display driver for TI OMAP platform.  Similar to omapfb (fbdev)
      and omap_vout (v4l2 display) drivers in the past, this driver uses the
      DSS2 driver to access the display hardware, including support for
      HDMI, DVI, and various types of LCD panels.  And it implements GEM
      support for buffer allocation (for KMS as well as offscreen buffers
      used by the xf86-video-omap userspace xorg driver).
      
      The driver maps CRTCs to overlays, encoders to overlay-managers, and
      connectors to dssdev's.  Note that this arrangement might change slightly
      when support for drm_plane overlays is added.
      
      For GEM support, non-scanout buffers are using the shmem backed pages
      provided by GEM core (In drm_gem_object_init()).  In the case of scanout
      buffers, which need to be physically contiguous, those are allocated
      with CMA and use drm_gem_private_object_init().
      
      See userspace xorg driver:
      git://github.com/robclark/xf86-video-omap.git
      
      Refer to this link for CMA (Continuous Memory Allocator):
      http://lkml.org/lkml/2011/8/19/302
      
      Links to previous versions of the patch:
      v1: http://lwn.net/Articles/458137/
      v2: http://patches.linaro.org/4156/
      v3: http://patches.linaro.org/4688/
      v4: http://patches.linaro.org/4791/
      
      History:
      
      v5: move headers from include/drm at Greg KH's request, minor rebasing
          on 3.2-rc1, pull in private copies of drm_gem_{get,put}_pages()
          because "drm/gem: add functions to get/put pages" patch is not
          merged yet
      v4: bit of rework of encoder/connector _dpms() code, modeset_init()
          rework to not use nested functions, update TODO.txt
      v3: minor cleanups, improved error handling for dev_load(), some minor
          API changes that will be needed later for tiled buffer support
      v2: replace omap_vram with CMA for scanout buffer allocation, remove
          unneeded functions, use dma_addr_t for physical addresses, error
          handling cleanup, refactor attach/detach pages into common drm
          functions, split non-userspace-facing API into omap_priv.h, remove
          plugin API
      
      v1: original
      Signed-off-by: NRob Clark <rob@ti.com>
      Acked-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      cd5351f4