dma-buf/sync_file: improve Kconfig description for Sync Files
We've got a complaint saying that the description was quite obtuse and indeed it was. This patch tries to improve it. Cc: Dave Jones <davej@codemonkey.org.uk> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk> Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
This commit is contained in:
parent
c483e06506
commit
31954660a7
|
@ -1,11 +1,20 @@
|
||||||
menu "DMABUF options"
|
menu "DMABUF options"
|
||||||
|
|
||||||
config SYNC_FILE
|
config SYNC_FILE
|
||||||
bool "sync_file support for fences"
|
bool "Explicit Synchronization Framework"
|
||||||
default n
|
default n
|
||||||
select ANON_INODES
|
select ANON_INODES
|
||||||
select DMA_SHARED_BUFFER
|
select DMA_SHARED_BUFFER
|
||||||
---help---
|
---help---
|
||||||
This option enables the fence framework synchronization to export
|
The Sync File Framework adds explicit syncronization via
|
||||||
sync_files to userspace that can represent one or more fences.
|
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.
|
||||||
|
|
||||||
endmenu
|
endmenu
|
||||||
|
|
Loading…
Reference in New Issue