|author||Gustavo Padovan <firstname.lastname@example.org>||2016-05-31 11:33:16 -0300|
|committer||Sumit Semwal <email@example.com>||2016-07-13 19:52:08 +0530|
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 <firstname.lastname@example.org> Signed-off-by: Gustavo Padovan <email@example.com> Signed-off-by: Sumit Semwal <firstname.lastname@example.org>
1 files changed, 12 insertions, 3 deletions
diff --git a/drivers/dma-buf/Kconfig b/drivers/dma-buf/Kconfig
index 9824bc4..25bcfa0 100644
@@ -1,11 +1,20 @@
menu "DMABUF options"
- bool "sync_file support for fences"
+ bool "Explicit Synchronization Framework"
- This option enables the fence framework synchronization to export
- sync_files to userspace that can represent one or more fences.
+ 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