1menu "DMABUF options" 2 3config SYNC_FILE 4 bool "Explicit Synchronization Framework" 5 default n 6 select DMA_SHARED_BUFFER 7 ---help--- 8 The Sync File Framework adds explicit syncronization via 9 userspace. It enables send/receive 'struct dma_fence' objects to/from 10 userspace via Sync File fds for synchronization between drivers via 11 userspace components. It has been ported from Android. 12 13 The first and main user for this is graphics in which a fence is 14 associated with a buffer. When a job is submitted to the GPU a fence 15 is attached to the buffer and is transferred via userspace, using Sync 16 Files fds, to the DRM driver for example. More details at 17 Documentation/sync_file.txt. 18 19config SW_SYNC 20 bool "Sync File Validation Framework" 21 default n 22 depends on SYNC_FILE 23 depends on DEBUG_FS 24 ---help--- 25 A sync object driver that uses a 32bit counter to coordinate 26 synchronization. Useful when there is no hardware primitive backing 27 the synchronization. 28 29 WARNING: improper use of this can result in deadlocking kernel 30 drivers from userspace. Intended for test and debug only. 31 32config UDMABUF 33 bool "userspace dmabuf misc driver" 34 default n 35 depends on DMA_SHARED_BUFFER 36 depends on MEMFD_CREATE || COMPILE_TEST 37 help 38 A driver to let userspace turn memfd regions into dma-bufs. 39 Qemu can use this to create host dmabufs for guest framebuffers. 40 41endmenu 42