1# SPDX-License-Identifier: GPL-2.0-only 2 3config NO_DMA 4 bool 5 6config HAS_DMA 7 bool 8 depends on !NO_DMA 9 default y 10 11config DMA_OPS 12 depends on HAS_DMA 13 bool 14 15# 16# IOMMU drivers that can bypass the IOMMU code and optionally use the direct 17# mapping fast path should select this option and set the dma_ops_bypass 18# flag in struct device where applicable 19# 20config DMA_OPS_BYPASS 21 bool 22 23config NEED_SG_DMA_LENGTH 24 bool 25 26config NEED_DMA_MAP_STATE 27 bool 28 29config ARCH_DMA_ADDR_T_64BIT 30 def_bool 64BIT || PHYS_ADDR_T_64BIT 31 32config ARCH_HAS_DMA_COHERENCE_H 33 bool 34 35config ARCH_HAS_DMA_SET_MASK 36 bool 37 38# 39# Select this option if the architecture needs special handling for 40# DMA_ATTR_WRITE_COMBINE. Normally the "uncached" mapping should be what 41# people thing of when saying write combine, so very few platforms should 42# need to enable this. 43# 44config ARCH_HAS_DMA_WRITE_COMBINE 45 bool 46 47# 48# Select if the architectures provides the arch_dma_mark_clean hook 49# 50config ARCH_HAS_DMA_MARK_CLEAN 51 bool 52 53config DMA_DECLARE_COHERENT 54 bool 55 56config ARCH_HAS_SETUP_DMA_OPS 57 bool 58 59config ARCH_HAS_TEARDOWN_DMA_OPS 60 bool 61 62config ARCH_HAS_SYNC_DMA_FOR_DEVICE 63 bool 64 65config ARCH_HAS_SYNC_DMA_FOR_CPU 66 bool 67 select NEED_DMA_MAP_STATE 68 69config ARCH_HAS_SYNC_DMA_FOR_CPU_ALL 70 bool 71 72config ARCH_HAS_DMA_PREP_COHERENT 73 bool 74 75config ARCH_HAS_FORCE_DMA_UNENCRYPTED 76 bool 77 78config DMA_VIRT_OPS 79 bool 80 depends on HAS_DMA 81 select DMA_OPS 82 83config SWIOTLB 84 bool 85 select NEED_DMA_MAP_STATE 86 87config DMA_RESTRICTED_POOL 88 bool "DMA Restricted Pool" 89 depends on OF && OF_RESERVED_MEM && SWIOTLB 90 help 91 This enables support for restricted DMA pools which provide a level of 92 DMA memory protection on systems with limited hardware protection 93 capabilities, such as those lacking an IOMMU. 94 95 For more information see 96 <Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt> 97 and <kernel/dma/swiotlb.c>. 98 If unsure, say "n". 99 100# 101# Should be selected if we can mmap non-coherent mappings to userspace. 102# The only thing that is really required is a way to set an uncached bit 103# in the pagetables 104# 105config DMA_NONCOHERENT_MMAP 106 default y if !MMU 107 bool 108 109config DMA_COHERENT_POOL 110 select GENERIC_ALLOCATOR 111 bool 112 113config DMA_REMAP 114 bool 115 depends on MMU 116 select DMA_NONCOHERENT_MMAP 117 118config DMA_DIRECT_REMAP 119 bool 120 select DMA_REMAP 121 select DMA_COHERENT_POOL 122 123config DMA_CMA 124 bool "DMA Contiguous Memory Allocator" 125 depends on HAVE_DMA_CONTIGUOUS && CMA 126 help 127 This enables the Contiguous Memory Allocator which allows drivers 128 to allocate big physically-contiguous blocks of memory for use with 129 hardware components that do not support I/O map nor scatter-gather. 130 131 You can disable CMA by specifying "cma=0" on the kernel's command 132 line. 133 134 For more information see <kernel/dma/contiguous.c>. 135 If unsure, say "n". 136 137if DMA_CMA 138 139config DMA_PERNUMA_CMA 140 bool "Enable separate DMA Contiguous Memory Area for each NUMA Node" 141 default NUMA && ARM64 142 help 143 Enable this option to get pernuma CMA areas so that devices like 144 ARM64 SMMU can get local memory by DMA coherent APIs. 145 146 You can set the size of pernuma CMA by specifying "cma_pernuma=size" 147 on the kernel's command line. 148 149comment "Default contiguous memory area size:" 150 151config CMA_SIZE_MBYTES 152 int "Size in Mega Bytes" 153 depends on !CMA_SIZE_SEL_PERCENTAGE 154 default 0 if X86 155 default 16 156 help 157 Defines the size (in MiB) of the default memory area for Contiguous 158 Memory Allocator. If the size of 0 is selected, CMA is disabled by 159 default, but it can be enabled by passing cma=size[MG] to the kernel. 160 161 162config CMA_SIZE_PERCENTAGE 163 int "Percentage of total memory" 164 depends on !CMA_SIZE_SEL_MBYTES 165 default 0 if X86 166 default 10 167 help 168 Defines the size of the default memory area for Contiguous Memory 169 Allocator as a percentage of the total memory in the system. 170 If 0 percent is selected, CMA is disabled by default, but it can be 171 enabled by passing cma=size[MG] to the kernel. 172 173choice 174 prompt "Selected region size" 175 default CMA_SIZE_SEL_MBYTES 176 177config CMA_SIZE_SEL_MBYTES 178 bool "Use mega bytes value only" 179 180config CMA_SIZE_SEL_PERCENTAGE 181 bool "Use percentage value only" 182 183config CMA_SIZE_SEL_MIN 184 bool "Use lower value (minimum)" 185 186config CMA_SIZE_SEL_MAX 187 bool "Use higher value (maximum)" 188 189endchoice 190 191config CMA_ALIGNMENT 192 int "Maximum PAGE_SIZE order of alignment for contiguous buffers" 193 range 2 12 194 default 8 195 help 196 DMA mapping framework by default aligns all buffers to the smallest 197 PAGE_SIZE order which is greater than or equal to the requested buffer 198 size. This works well for buffers up to a few hundreds kilobytes, but 199 for larger buffers it just a memory waste. With this parameter you can 200 specify the maximum PAGE_SIZE order for contiguous buffers. Larger 201 buffers will be aligned only to this specified order. The order is 202 expressed as a power of two multiplied by the PAGE_SIZE. 203 204 For example, if your system defaults to 4KiB pages, the order value 205 of 8 means that the buffers will be aligned up to 1MiB only. 206 207 If unsure, leave the default value "8". 208 209endif 210 211config DMA_API_DEBUG 212 bool "Enable debugging of DMA-API usage" 213 select NEED_DMA_MAP_STATE 214 help 215 Enable this option to debug the use of the DMA API by device drivers. 216 With this option you will be able to detect common bugs in device 217 drivers like double-freeing of DMA mappings or freeing mappings that 218 were never allocated. 219 220 This option causes a performance degradation. Use only if you want to 221 debug device drivers and dma interactions. 222 223 If unsure, say N. 224 225config DMA_API_DEBUG_SG 226 bool "Debug DMA scatter-gather usage" 227 default y 228 depends on DMA_API_DEBUG 229 help 230 Perform extra checking that callers of dma_map_sg() have respected the 231 appropriate segment length/boundary limits for the given device when 232 preparing DMA scatterlists. 233 234 This is particularly likely to have been overlooked in cases where the 235 dma_map_sg() API is used for general bulk mapping of pages rather than 236 preparing literal scatter-gather descriptors, where there is a risk of 237 unexpected behaviour from DMA API implementations if the scatterlist 238 is technically out-of-spec. 239 240 If unsure, say N. 241