| Gustavo Padovan | 62304fb | 2016-04-28 10:46:58 -0300 | [diff] [blame] | 1 | menu "DMABUF options" |
| 2 | |
| 3 | config SYNC_FILE |
| Gustavo Padovan | 3195466 | 2016-05-31 11:33:16 -0300 | [diff] [blame] | 4 | bool "Explicit Synchronization Framework" |
| Gustavo Padovan | 62304fb | 2016-04-28 10:46:58 -0300 | [diff] [blame] | 5 | default n |
| 6 | select ANON_INODES |
| 7 | select DMA_SHARED_BUFFER |
| 8 | ---help--- |
| Gustavo Padovan | 3195466 | 2016-05-31 11:33:16 -0300 | [diff] [blame] | 9 | The Sync File Framework adds explicit syncronization via |
| 10 | userspace. It enables send/receive 'struct fence' objects to/from |
| 11 | 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 Padovan | 62304fb | 2016-04-28 10:46:58 -0300 | [diff] [blame] | 20 | endmenu |