Blame view
drivers/dma-buf/Kconfig
1.11 KB
62304fb1f dma-buf/sync_file... |
1 2 3 |
menu "DMABUF options" config SYNC_FILE |
31954660a dma-buf/sync_file... |
4 |
bool "Explicit Synchronization Framework" |
62304fb1f dma-buf/sync_file... |
5 6 7 8 |
default n select ANON_INODES select DMA_SHARED_BUFFER ---help--- |
31954660a dma-buf/sync_file... |
9 10 11 12 13 14 15 16 17 18 |
The Sync File Framework adds explicit syncronization via userspace. It enables send/receive 'struct 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. |
35538d782 dma-buf/sw_sync: ... |
19 20 21 22 23 24 25 26 27 28 29 30 |
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. |
62304fb1f dma-buf/sync_file... |
31 |
endmenu |