Directory Files
.. 6
heaps 26
File Size
.built-in.a.cmd 340 B
.dma-buf-io.o.cmd 58 kB
.dma-buf-mapping.o.cmd 58 kB
.dma-buf.o.cmd 68 kB
.dma-fence-array.o.cmd 44 kB
.dma-fence-chain.o.cmd 44 kB
.dma-fence-unwrap.o.cmd 44 kB
.dma-fence.o.cmd 65 kB
.dma-heap.o.cmd 68 kB
.dma-resv.o.cmd 50 kB
.dmabuf_kunit.ko.cmd 303 B
.dmabuf_kunit.mod.cmd 219 B
.dmabuf_kunit.mod.o.cmd 50 kB
.dmabuf_kunit.o.cmd 477 B
.kunitconfig 42 B
.modules.order.cmd 163 B
.st-dma-fence-chain.o.cmd 53 kB
.st-dma-fence-unwrap.o.cmd 50 kB
.st-dma-fence.o.cmd 50 kB
.st-dma-resv.o.cmd 50 kB
.sw_sync.o.cmd 65 kB
.sync_debug.o.cmd 47 kB
.sync_file.o.cmd 47 kB
.udmabuf.o.cmd 67 kB
Kconfig 2.3 kB
Makefile 529 B
built-in.a 1.0 kB
dma-buf-io.c 6.3 kB
dma-buf-io.o 40 kB
dma-buf-mapping.c 7.0 kB
dma-buf-mapping.o 27 kB
dma-buf.c 53 kB
dma-buf.o 224 kB
dma-fence-array.c 9.7 kB
dma-fence-array.o 43 kB
dma-fence-chain.c 7.8 kB
dma-fence-chain.o 51 kB
dma-fence-unwrap.c 5.2 kB
dma-fence-unwrap.o 37 kB
dma-fence.c 40 kB
dma-fence.o 205 kB
dma-heap.c 8.0 kB
dma-heap.o 37 kB
dma-resv.c 23 kB
dma-resv.o 106 kB
dmabuf_kunit.ko 546 kB
dmabuf_kunit.mod 136 B
dmabuf_kunit.mod.c 376 B
dmabuf_kunit.mod.o 3.1 kB
dmabuf_kunit.o 561 kB
modules.order 100 B
st-dma-fence-chain.c 15 kB
st-dma-fence-chain.o 135 kB
st-dma-fence-unwrap.c 12 kB
st-dma-fence-unwrap.o 129 kB
st-dma-fence.c 10 kB
st-dma-fence.o 117 kB
st-dma-resv.c 6.8 kB
st-dma-resv.o 60 kB
sw_sync.c 11 kB
sw_sync.o 80 kB
sync_debug.c 3.0 kB
sync_debug.h 1.8 kB
sync_debug.o 25 kB
sync_file.c 9.3 kB
sync_file.o 53 kB
sync_trace.h 758 B
udmabuf.c 13 kB
udmabuf.o 55 kB

Linux v7.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 synchronization 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
	depends on MMU
	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_DEBUG
	bool "DMA-BUF debug checks"
	depends on DMA_SHARED_BUFFER
	default y if DEBUG
	help
	  This option enables additional checks for DMA-BUF importers and
	  exporters. Specifically it validates that importers do not peek at the
	  underlying struct page when they import a buffer.

config DMABUF_KUNIT_TEST
	tristate "KUnit tests for DMA-BUF" if !KUNIT_ALL_TESTS
	depends on KUNIT
	select DMA_SHARED_BUFFER
	default KUNIT_ALL_TESTS
	help
	   Enable kunit tests for DMA-BUF

menuconfig DMABUF_HEAPS
	bool "DMA-BUF Userland Memory Heaps"
	select DMA_SHARED_BUFFER
	help
	  Choose this option to enable the DMA-BUF userland memory heaps.
	  This options creates per heap chardevs in /dev/dma_heap/ which
	  allows userspace to allocate dma-bufs that can be shared
	  between drivers.

source "drivers/dma-buf/heaps/Kconfig"

endmenu