f54d186700
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: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk> Acked-by: Sumit Semwal <sumit.semwal@linaro.org> Acked-by: Christian König <christian.koenig@amd.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/20161025120045.28839-1-chris@chris-wilson.co.uk
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
menu "DMABUF options"
|
|
|
|
config SYNC_FILE
|
|
bool "Explicit Synchronization Framework"
|
|
default n
|
|
select ANON_INODES
|
|
select DMA_SHARED_BUFFER
|
|
---help---
|
|
The Sync File Framework adds explicit syncronization via
|
|
userspace. It enables send/receive 'struct dma_fence' objects to/from
|
|
userspace via Sync File fds for synchronization between drivers via
|
|
userspace components. It has been ported from Android.
|
|
|
|
The first and main user for this is graphics in which a fence is
|
|
associated with a buffer. When a job is submitted to the GPU a fence
|
|
is attached to the buffer and is transferred via userspace, using Sync
|
|
Files fds, to the DRM driver for example. More details at
|
|
Documentation/sync_file.txt.
|
|
|
|
config SW_SYNC
|
|
bool "Sync File Validation Framework"
|
|
default n
|
|
depends on SYNC_FILE
|
|
depends on DEBUG_FS
|
|
---help---
|
|
A sync object driver that uses a 32bit counter to coordinate
|
|
synchronization. Useful when there is no hardware primitive backing
|
|
the synchronization.
|
|
|
|
WARNING: improper use of this can result in deadlocking kernel
|
|
drivers from userspace. Intended for test and debug only.
|
|
|
|
endmenu
|