1. 18 5月, 2018 1 次提交
  2. 02 11月, 2017 2 次提交
  3. 17 2月, 2017 2 次提交
  4. 31 1月, 2017 1 次提交
  5. 07 11月, 2016 1 次提交
  6. 25 10月, 2016 1 次提交
    • C
      dma-buf: Rename struct fence to dma_fence · f54d1867
      Chris Wilson 提交于
      I plan to usurp the short name of struct fence for a core kernel struct,
      and so I need to rename the specialised fence/timeline for DMA
      operations to make room.
      
      A consensus was reached in
      https://lists.freedesktop.org/archives/dri-devel/2016-July/113083.html
      that making clear this fence applies to DMA operations was a good thing.
      Since then the patch has grown a bit as usage increases, so hopefully it
      remains a good thing!
      
      (v2...: rebase, rerun spatch)
      v3: Compile on msm, spotted a manual fixup that I broke.
      v4: Try again for msm, sorry Daniel
      
      coccinelle script:
      @@
      
      @@
      - struct fence
      + struct dma_fence
      @@
      
      @@
      - struct fence_ops
      + struct dma_fence_ops
      @@
      
      @@
      - struct fence_cb
      + struct dma_fence_cb
      @@
      
      @@
      - struct fence_array
      + struct dma_fence_array
      @@
      
      @@
      - enum fence_flag_bits
      + enum dma_fence_flag_bits
      @@
      
      @@
      (
      - fence_init
      + dma_fence_init
      |
      - fence_release
      + dma_fence_release
      |
      - fence_free
      + dma_fence_free
      |
      - fence_get
      + dma_fence_get
      |
      - fence_get_rcu
      + dma_fence_get_rcu
      |
      - fence_put
      + dma_fence_put
      |
      - fence_signal
      + dma_fence_signal
      |
      - fence_signal_locked
      + dma_fence_signal_locked
      |
      - fence_default_wait
      + dma_fence_default_wait
      |
      - fence_add_callback
      + dma_fence_add_callback
      |
      - fence_remove_callback
      + dma_fence_remove_callback
      |
      - fence_enable_sw_signaling
      + dma_fence_enable_sw_signaling
      |
      - fence_is_signaled_locked
      + dma_fence_is_signaled_locked
      |
      - fence_is_signaled
      + dma_fence_is_signaled
      |
      - fence_is_later
      + dma_fence_is_later
      |
      - fence_later
      + dma_fence_later
      |
      - fence_wait_timeout
      + dma_fence_wait_timeout
      |
      - fence_wait_any_timeout
      + dma_fence_wait_any_timeout
      |
      - fence_wait
      + dma_fence_wait
      |
      - fence_context_alloc
      + dma_fence_context_alloc
      |
      - fence_array_create
      + dma_fence_array_create
      |
      - to_fence_array
      + to_dma_fence_array
      |
      - fence_is_array
      + dma_fence_is_array
      |
      - trace_fence_emit
      + trace_dma_fence_emit
      |
      - FENCE_TRACE
      + DMA_FENCE_TRACE
      |
      - FENCE_WARN
      + DMA_FENCE_WARN
      |
      - FENCE_ERR
      + DMA_FENCE_ERR
      )
       (
       ...
       )
      Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
      Reviewed-by: NGustavo Padovan <gustavo.padovan@collabora.co.uk>
      Acked-by: NSumit Semwal <sumit.semwal@linaro.org>
      Acked-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Link: http://patchwork.freedesktop.org/patch/msgid/20161025120045.28839-1-chris@chris-wilson.co.uk
      f54d1867
  7. 20 5月, 2016 1 次提交
  8. 28 8月, 2015 3 次提交
  9. 14 4月, 2015 1 次提交
    • A
      make RAM device optional · eaecf032
      Alexandre Courbot 提交于
      Having a RAM device does not make sense for chips like GK20A which have
      no dedicated video memory. The dummy RAM device that we used so far
      works as a temporary band-aid, but in the longer term it is desirable
      for the driver to be able to work without any kind of VRAM.
      
      This patch adds a few conditionals in places where a RAM device was
      assumed to be present and allows some more objects to be allocated from
      the TT domain, allowing Nouveau to handle GPUs for which
      pfb->ram == NULL.
      Signed-off-by: NAlexandre Courbot <acourbot@nvidia.com>
      Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
      eaecf032
  10. 22 1月, 2015 2 次提交
    • B
      drm/nouveau: finalise nvkm namespace switch (no binary change) · be83cd4e
      Ben Skeggs 提交于
      The namespace of NVKM is being changed to nvkm_ instead of nouveau_,
      which will be used for the DRM part of the driver.  This is being
      done in order to make it very clear as to what part of the driver a
      given symbol belongs to, and as a minor step towards splitting the
      DRM driver out to be able to stand on its own (for virt).
      
      Because there's already a large amount of churn here anyway, this is
      as good a time as any to also switch to NVIDIA's device and chipset
      naming to ease collaboration with them.
      
      A comparison of objdump disassemblies proves no code changes.
      Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
      be83cd4e
    • B
      drm/nouveau/nvif: namespace of nvkm accessors (no binary change) · 989aa5b7
      Ben Skeggs 提交于
      NVKM is having it's namespace switched to nvkm_, which will conflict
      with these functions (which are workarounds for the fact that as of
      yet, we still aren't able to split DRM and NVKM completely).
      
      A comparison of objdump disassemblies proves no code changes.
      Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
      989aa5b7
  11. 02 12月, 2014 2 次提交
  12. 01 10月, 2014 1 次提交
  13. 30 9月, 2014 2 次提交
  14. 02 9月, 2014 1 次提交
  15. 10 8月, 2014 5 次提交
  16. 20 2月, 2013 5 次提交
  17. 29 11月, 2012 2 次提交
  18. 03 10月, 2012 7 次提交