Blame view
drivers/dma-buf/Kconfig
2.3 KB
ec8f24b7f treewide: Add SPD... |
1 |
# SPDX-License-Identifier: GPL-2.0-only |
62304fb1f dma-buf/sync_file... |
2 3 4 |
menu "DMABUF options" config SYNC_FILE |
31954660a dma-buf/sync_file... |
5 |
bool "Explicit Synchronization Framework" |
62304fb1f dma-buf/sync_file... |
6 |
default n |
62304fb1f dma-buf/sync_file... |
7 |
select DMA_SHARED_BUFFER |
a7f7f6248 treewide: replace... |
8 |
help |
3e8a3844f dma-buf: Fix a ty... |
9 |
The Sync File Framework adds explicit synchronization via |
f54d18670 dma-buf: Rename s... |
10 |
userspace. It enables send/receive 'struct dma_fence' objects to/from |
31954660a dma-buf/sync_file... |
11 12 13 14 15 16 17 |
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 |
baa293e95 docs: driver-api:... |
18 |
Documentation/driver-api/sync_file.rst. |
31954660a dma-buf/sync_file... |
19 |
|
35538d782 dma-buf/sw_sync: ... |
20 21 22 23 24 |
config SW_SYNC bool "Sync File Validation Framework" default n depends on SYNC_FILE depends on DEBUG_FS |
a7f7f6248 treewide: replace... |
25 |
help |
35538d782 dma-buf/sw_sync: ... |
26 27 28 29 30 31 |
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. |
fbb0de795 Add udmabuf misc ... |
32 33 34 35 |
config UDMABUF bool "userspace dmabuf misc driver" default n depends on DMA_SHARED_BUFFER |
68d2f70ef udmabuf: add MEMF... |
36 |
depends on MEMFD_CREATE || COMPILE_TEST |
fbb0de795 Add udmabuf misc ... |
37 38 39 |
help A driver to let userspace turn memfd regions into dma-bufs. Qemu can use this to create host dmabufs for guest framebuffers. |
bb42df466 dma-buf: add dyna... |
40 41 42 43 |
config DMABUF_MOVE_NOTIFY bool "Move notify between drivers (EXPERIMENTAL)" default n help |
518110cd0 dma-buf: Improve ... |
44 45 46 47 48 49 |
Don't pin buffers if the dynamic DMA-buf interface is available on both the exporter as well as the importer. This fixes a security problem where userspace is able to pin unrestricted amounts of memory through DMA-buf. This is marked experimental because we don't yet have a consistent execution context and memory management between drivers. |
bb42df466 dma-buf: add dyna... |
50 |
|
9536b64ac dma-buf: Introduc... |
51 52 53 54 |
config DMABUF_SELFTESTS tristate "Selftests for the dma-buf interfaces" default n depends on DMA_SHARED_BUFFER |
c02a81fba dma-buf: Add dma-... |
55 56 57 58 59 60 61 62 |
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. |
efa04fefe dma-buf: heaps: A... |
63 |
source "drivers/dma-buf/heaps/Kconfig" |
62304fb1f dma-buf/sync_file... |
64 |
endmenu |