blob: ed3b785bae37e1cd589697f04d1b868dc2fccd9b [file] [log] [blame]
Gustavo Padovan62304fb2016-04-28 10:46:58 -03001menu "DMABUF options"
2
3config SYNC_FILE
Gustavo Padovan31954662016-05-31 11:33:16 -03004 bool "Explicit Synchronization Framework"
Gustavo Padovan62304fb2016-04-28 10:46:58 -03005 default n
6 select ANON_INODES
7 select DMA_SHARED_BUFFER
8 ---help---
Gustavo Padovan31954662016-05-31 11:33:16 -03009 The Sync File Framework adds explicit syncronization via
Chris Wilsonf54d1862016-10-25 13:00:45 +010010 userspace. It enables send/receive 'struct dma_fence' objects to/from
Gustavo Padovan31954662016-05-31 11:33:16 -030011 userspace via Sync File fds for synchronization between drivers via
12 userspace components. It has been ported from Android.
13
14 The first and main user for this is graphics in which a fence is
15 associated with a buffer. When a job is submitted to the GPU a fence
16 is attached to the buffer and is transferred via userspace, using Sync
17 Files fds, to the DRM driver for example. More details at
18 Documentation/sync_file.txt.
19
Gustavo Padovan35538d72016-08-11 12:26:44 -030020config SW_SYNC
21 bool "Sync File Validation Framework"
22 default n
23 depends on SYNC_FILE
24 depends on DEBUG_FS
25 ---help---
26 A sync object driver that uses a 32bit counter to coordinate
27 synchronization. Useful when there is no hardware primitive backing
28 the synchronization.
29
30 WARNING: improper use of this can result in deadlocking kernel
31 drivers from userspace. Intended for test and debug only.
32
Gustavo Padovan62304fb2016-04-28 10:46:58 -030033endmenu