Directory Files
.. 2
File Size
Kconfig 1.6 kB
Makefile 370 B
dma-buf.c 37 kB
dma-fence-array.c 5.9 kB
dma-fence-chain.c 6.7 kB
dma-fence.c 19 kB
dma-resv.c 16 kB
dmabuf_selftests.mod.c 0 B
selftest.c 3.1 kB
selftest.h 549 B
selftests.h 534 B
seqno-fence.c 1.8 kB
st-dma-fence.c 11 kB
sw_sync.c 9.7 kB
sync_debug.c 4.7 kB
sync_debug.h 1.9 kB
sync_file.c 11 kB
sync_trace.h 774 B
udmabuf.c 6.7 kB

Linux v5.4-rc3 - dma-buf

# SPDX-License-Identifier: GPL-2.0-only
menu "DMABUF options"

config SYNC_FILE
	bool "Explicit Synchronization Framework"
	default n
	select DMA_SHARED_BUFFER
	---help---
	  The Sync File Framework adds explicit syncronization via
	  userspace. It enables send/receive 'struct dma_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/driver-api/sync_file.rst.

config SW_SYNC
	bool "Sync File Validation Framework"
	default n
	depends on SYNC_FILE
	depends on DEBUG_FS
	---help---
	  A sync object driver that uses a 32bit counter to coordinate
	  synchronization.  Useful when there is no hardware primitive backing
	  the synchronization.

	  WARNING: improper use of this can result in deadlocking kernel
	  drivers from userspace. Intended for test and debug only.

config UDMABUF
	bool "userspace dmabuf misc driver"
	default n
	depends on DMA_SHARED_BUFFER
	depends on MEMFD_CREATE || COMPILE_TEST
	help
	  A driver to let userspace turn memfd regions into dma-bufs.
	  Qemu can use this to create host dmabufs for guest framebuffers.

config DMABUF_SELFTESTS
	tristate "Selftests for the dma-buf interfaces"
	default n
	depends on DMA_SHARED_BUFFER

endmenu