Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340
  1. menu "Generic Driver Options"
  2. config UEVENT_HELPER_PATH
  3. string "path to uevent helper"
  4. depends on HOTPLUG
  5. default ""
  6. help
  7. Path to uevent helper program forked by the kernel for
  8. every uevent.
  9. Before the switch to the netlink-based uevent source, this was
  10. used to hook hotplug scripts into kernel device events. It
  11. usually pointed to a shell script at /sbin/hotplug.
  12. This should not be used today, because usual systems create
  13. many events at bootup or device discovery in a very short time
  14. frame. One forked process per event can create so many processes
  15. that it creates a high system load, or on smaller systems
  16. it is known to create out-of-memory situations during bootup.
  17. To disable user space helper program execution at early boot
  18. time specify an empty string here. This setting can be altered
  19. via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
  20. later at runtime.
  21. config DEVTMPFS
  22. bool "Maintain a devtmpfs filesystem to mount at /dev"
  23. depends on HOTPLUG
  24. help
  25. This creates a tmpfs/ramfs filesystem instance early at bootup.
  26. In this filesystem, the kernel driver core maintains device
  27. nodes with their default names and permissions for all
  28. registered devices with an assigned major/minor number.
  29. Userspace can modify the filesystem content as needed, add
  30. symlinks, and apply needed permissions.
  31. It provides a fully functional /dev directory, where usually
  32. udev runs on top, managing permissions and adding meaningful
  33. symlinks.
  34. In very limited environments, it may provide a sufficient
  35. functional /dev without any further help. It also allows simple
  36. rescue systems, and reliably handles dynamic major/minor numbers.
  37. Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs
  38. file system will be used instead.
  39. config DEVTMPFS_MOUNT
  40. bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
  41. depends on DEVTMPFS
  42. help
  43. This will instruct the kernel to automatically mount the
  44. devtmpfs filesystem at /dev, directly after the kernel has
  45. mounted the root filesystem. The behavior can be overridden
  46. with the commandline parameter: devtmpfs.mount=0|1.
  47. This option does not affect initramfs based booting, here
  48. the devtmpfs filesystem always needs to be mounted manually
  49. after the roots is mounted.
  50. With this option enabled, it allows to bring up a system in
  51. rescue mode with init=/bin/sh, even when the /dev directory
  52. on the rootfs is completely empty.
  53. config STANDALONE
  54. bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
  55. default y
  56. help
  57. Select this option if you don't have magic firmware for drivers that
  58. need it.
  59. If unsure, say Y.
  60. config PREVENT_FIRMWARE_BUILD
  61. bool "Prevent firmware from being built"
  62. default y
  63. help
  64. Say yes to avoid building firmware. Firmware is usually shipped
  65. with the driver and only when updating the firmware should a
  66. rebuild be made.
  67. If unsure, say Y here.
  68. config FW_LOADER
  69. tristate "Userspace firmware loading support" if EXPERT
  70. default y
  71. ---help---
  72. This option is provided for the case where none of the in-tree modules
  73. require userspace firmware loading support, but a module built
  74. out-of-tree does.
  75. config FIRMWARE_IN_KERNEL
  76. bool "Include in-kernel firmware blobs in kernel binary"
  77. depends on FW_LOADER
  78. default y
  79. help
  80. The kernel source tree includes a number of firmware 'blobs'
  81. that are used by various drivers. The recommended way to
  82. use these is to run "make firmware_install", which, after
  83. converting ihex files to binary, copies all of the needed
  84. binary files in firmware/ to /lib/firmware/ on your system so
  85. that they can be loaded by userspace helpers on request.
  86. Enabling this option will build each required firmware blob
  87. into the kernel directly, where request_firmware() will find
  88. them without having to call out to userspace. This may be
  89. useful if your root file system requires a device that uses
  90. such firmware and do not wish to use an initrd.
  91. This single option controls the inclusion of firmware for
  92. every driver that uses request_firmware() and ships its
  93. firmware in the kernel source tree, which avoids a
  94. proliferation of 'Include firmware for xxx device' options.
  95. Say 'N' and let firmware be loaded from userspace.
  96. config EXTRA_FIRMWARE
  97. string "External firmware blobs to build into the kernel binary"
  98. depends on FW_LOADER
  99. help
  100. This option allows firmware to be built into the kernel for the case
  101. where the user either cannot or doesn't want to provide it from
  102. userspace at runtime (for example, when the firmware in question is
  103. required for accessing the boot device, and the user doesn't want to
  104. use an initrd).
  105. This option is a string and takes the (space-separated) names of the
  106. firmware files -- the same names that appear in MODULE_FIRMWARE()
  107. and request_firmware() in the source. These files should exist under
  108. the directory specified by the EXTRA_FIRMWARE_DIR option, which is
  109. by default the firmware subdirectory of the kernel source tree.
  110. For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy
  111. the usb8388.bin file into the firmware directory, and build the kernel.
  112. Then any request_firmware("usb8388.bin") will be satisfied internally
  113. without needing to call out to userspace.
  114. WARNING: If you include additional firmware files into your binary
  115. kernel image that are not available under the terms of the GPL,
  116. then it may be a violation of the GPL to distribute the resulting
  117. image since it combines both GPL and non-GPL work. You should
  118. consult a lawyer of your own before distributing such an image.
  119. config EXTRA_FIRMWARE_DIR
  120. string "Firmware blobs root directory"
  121. depends on EXTRA_FIRMWARE != ""
  122. default "firmware"
  123. help
  124. This option controls the directory in which the kernel build system
  125. looks for the firmware files listed in the EXTRA_FIRMWARE option.
  126. The default is firmware/ in the kernel source tree, but by changing
  127. this option you can point it elsewhere, such as /lib/firmware/ or
  128. some other directory containing the firmware files.
  129. config DEBUG_DRIVER
  130. bool "Driver Core verbose debug messages"
  131. depends on DEBUG_KERNEL
  132. help
  133. Say Y here if you want the Driver core to produce a bunch of
  134. debug messages to the system log. Select this if you are having a
  135. problem with the driver core and want to see more of what is
  136. going on.
  137. If you are unsure about this, say N here.
  138. config DEBUG_DEVRES
  139. bool "Managed device resources verbose debug messages"
  140. depends on DEBUG_KERNEL
  141. help
  142. This option enables kernel parameter devres.log. If set to
  143. non-zero, devres debug messages are printed. Select this if
  144. you are having a problem with devres or want to debug
  145. resource management for a managed device. devres.log can be
  146. switched on and off from sysfs node.
  147. If you are unsure about this, Say N here.
  148. config SYS_HYPERVISOR
  149. bool
  150. default n
  151. config GENERIC_CPU_DEVICES
  152. bool
  153. default n
  154. config SOC_BUS
  155. bool
  156. source "drivers/base/regmap/Kconfig"
  157. config DMA_SHARED_BUFFER
  158. bool
  159. default n
  160. select ANON_INODES
  161. depends on EXPERIMENTAL
  162. help
  163. This option enables the framework for buffer-sharing between
  164. multiple drivers. A buffer is associated with a file using driver
  165. APIs extension; the file's descriptor can then be passed on to other
  166. driver.
  167. config GENLOCK
  168. bool "Enable a generic cross-process locking mechanism"
  169. depends on ANON_INODES
  170. help
  171. Enable a generic cross-process locking API to provide protection
  172. for shared memory objects such as graphics buffers.
  173. config GENLOCK_MISCDEVICE
  174. bool "Enable a misc-device for userspace to access the genlock engine"
  175. depends on GENLOCK
  176. help
  177. Create a miscdevice for the purposes of allowing userspace to create
  178. and interact with locks created using genlock.
  179. config SYNC
  180. bool "Synchronization framework"
  181. default n
  182. select ANON_INODES
  183. help
  184. This option enables the framework for synchronization between multiple
  185. drivers. Sync implementations can take advantage of hardware
  186. synchronization built into devices like GPUs.
  187. config SW_SYNC
  188. bool "Software synchronization objects"
  189. default n
  190. depends on SYNC
  191. help
  192. A sync object driver that uses a 32bit counter to coordinate
  193. syncrhronization. Useful when there is no hardware primitive backing
  194. the synchronization.
  195. config SW_SYNC_USER
  196. bool "Userspace API for SW_SYNC"
  197. default n
  198. depends on SW_SYNC
  199. help
  200. Provides a user space API to the sw sync object.
  201. *WARNING* improper use of this can result in deadlocking kernel
  202. drivers from userspace.
  203. config CMA
  204. bool "Contiguous Memory Allocator (EXPERIMENTAL)"
  205. depends on HAVE_DMA_CONTIGUOUS && HAVE_MEMBLOCK && EXPERIMENTAL
  206. select MIGRATION
  207. help
  208. This enables the Contiguous Memory Allocator which allows drivers
  209. to allocate big physically-contiguous blocks of memory for use with
  210. hardware components that do not support I/O map nor scatter-gather.
  211. For more information see <include/linux/dma-contiguous.h>.
  212. If unsure, say "n".
  213. if CMA
  214. config CMA_PAGE_COUNTING
  215. bool "CMA page counting"
  216. default n
  217. help
  218. Counting cma pages in the anonymous & file active/inactive lists
  219. to subtract cma pages when calculating a lmk other_file threshold.
  220. config CMA_DEBUG
  221. bool "CMA debug messages (DEVELOPMENT)"
  222. depends on DEBUG_KERNEL
  223. help
  224. Turns on debug messages in CMA. This produces KERN_DEBUG
  225. messages for every CMA call as well as various messages while
  226. processing calls such as dma_alloc_from_contiguous().
  227. This option does not affect warning and error messages.
  228. config CMA_PINPAGE_MIGRATION
  229. bool "CMA pinned page migration (EXPERIMENTAL)"
  230. depends on CMA
  231. default n
  232. help
  233. Turns on cma page migration for pinned page.
  234. comment "Default contiguous memory area size:"
  235. config CMA_SIZE_MBYTES
  236. int "Size in Mega Bytes"
  237. depends on !CMA_SIZE_SEL_PERCENTAGE
  238. default 16
  239. help
  240. Defines the size (in MiB) of the default memory area for Contiguous
  241. Memory Allocator.
  242. config CMA_SIZE_PERCENTAGE
  243. int "Percentage of total memory"
  244. depends on !CMA_SIZE_SEL_MBYTES
  245. default 10
  246. help
  247. Defines the size of the default memory area for Contiguous Memory
  248. Allocator as a percentage of the total memory in the system.
  249. choice
  250. prompt "Selected region size"
  251. default CMA_SIZE_SEL_ABSOLUTE
  252. config CMA_SIZE_SEL_MBYTES
  253. bool "Use mega bytes value only"
  254. config CMA_SIZE_SEL_PERCENTAGE
  255. bool "Use percentage value only"
  256. config CMA_SIZE_SEL_MIN
  257. bool "Use lower value (minimum)"
  258. config CMA_SIZE_SEL_MAX
  259. bool "Use higher value (maximum)"
  260. endchoice
  261. config CMA_ALIGNMENT
  262. int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
  263. range 4 9
  264. default 8
  265. help
  266. DMA mapping framework by default aligns all buffers to the smallest
  267. PAGE_SIZE order which is greater than or equal to the requested buffer
  268. size. This works well for buffers up to a few hundreds kilobytes, but
  269. for larger buffers it just a memory waste. With this parameter you can
  270. specify the maximum PAGE_SIZE order for contiguous buffers. Larger
  271. buffers will be aligned only to this specified order. The order is
  272. expressed as a power of two multiplied by the PAGE_SIZE.
  273. For example, if your system defaults to 4KiB pages, the order value
  274. of 8 means that the buffers will be aligned up to 1MiB only.
  275. If unsure, leave the default value "8".
  276. config CMA_AREAS
  277. int "Maximum count of the CMA device-private areas"
  278. default 7
  279. help
  280. CMA allows to create CMA areas for particular devices. This parameter
  281. sets the maximum number of such device private CMA areas in the
  282. system.
  283. If unsure, leave the default value "7".
  284. endif
  285. endmenu