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>

diff --git a/drivers/dma-buf/Kconfig b/drivers/dma-buf/Kconfig
index 9824bc4addf856d4b674b47d15058a74fa0f74e7..7e2d2c49f8ef74b0bdd895c5dd976543b80b8034 100644 (file)
--- a/drivers/dma-buf/Kconfig
+++ b/drivers/dma-buf/Kconfig
@@ -1,11 +1,20 @@
 menu "DMABUF options"
 
 config SYNC_FILE
-       bool "sync_file support for fences"
+       bool "Explicit Synchronization Framework"
        default n
        select ANON_INODES
        select DMA_SHARED_BUFFER
        ---help---
-         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 transfered via userspace, using Sync
+         Files fds, to the DRM driver for example. More details at
+         Documentation/sync_file.txt.
+
 endmenu