Greg Kroah-Hartman | b244131 | 2017-11-01 15:07:57 +0100 | [diff] [blame] | 1 | # SPDX-License-Identifier: GPL-2.0 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 2 | menu "Generic Driver Options" |
| 3 | |
Michael Marineau | 86d5613 | 2014-04-10 14:09:31 -0700 | [diff] [blame] | 4 | config UEVENT_HELPER |
| 5 | bool "Support for uevent helper" |
| 6 | default y |
Kay Sievers | 6a8d8ab | 2007-08-15 15:38:28 +0200 | [diff] [blame] | 7 | help |
Michael Marineau | 86d5613 | 2014-04-10 14:09:31 -0700 | [diff] [blame] | 8 | The uevent helper program is forked by the kernel for |
Kay Sievers | 6a8d8ab | 2007-08-15 15:38:28 +0200 | [diff] [blame] | 9 | every uevent. |
Kay Sievers | 7934779 | 2010-01-14 22:49:39 +0100 | [diff] [blame] | 10 | Before the switch to the netlink-based uevent source, this was |
| 11 | used to hook hotplug scripts into kernel device events. It |
| 12 | usually pointed to a shell script at /sbin/hotplug. |
| 13 | This should not be used today, because usual systems create |
| 14 | many events at bootup or device discovery in a very short time |
| 15 | frame. One forked process per event can create so many processes |
| 16 | that it creates a high system load, or on smaller systems |
| 17 | it is known to create out-of-memory situations during bootup. |
Kay Sievers | 6a8d8ab | 2007-08-15 15:38:28 +0200 | [diff] [blame] | 18 | |
Michael Marineau | 86d5613 | 2014-04-10 14:09:31 -0700 | [diff] [blame] | 19 | config UEVENT_HELPER_PATH |
| 20 | string "path to uevent helper" |
| 21 | depends on UEVENT_HELPER |
| 22 | default "" |
| 23 | help |
| 24 | To disable user space helper program execution at by default |
| 25 | specify an empty string here. This setting can still be altered |
Márton Németh | 573c977 | 2011-06-19 22:30:16 +0200 | [diff] [blame] | 26 | via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper |
| 27 | later at runtime. |
| 28 | |
Kay Sievers | 2b2af54 | 2009-04-30 15:23:42 +0200 | [diff] [blame] | 29 | config DEVTMPFS |
Kay Sievers | 4237e5f | 2010-01-14 22:47:57 +0100 | [diff] [blame] | 30 | bool "Maintain a devtmpfs filesystem to mount at /dev" |
Kay Sievers | 2b2af54 | 2009-04-30 15:23:42 +0200 | [diff] [blame] | 31 | help |
Peter Korsgaard | da5e4ef | 2010-03-16 21:55:21 +0100 | [diff] [blame] | 32 | This creates a tmpfs/ramfs filesystem instance early at bootup. |
Kay Sievers | 4237e5f | 2010-01-14 22:47:57 +0100 | [diff] [blame] | 33 | In this filesystem, the kernel driver core maintains device |
| 34 | nodes with their default names and permissions for all |
| 35 | registered devices with an assigned major/minor number. |
| 36 | Userspace can modify the filesystem content as needed, add |
| 37 | symlinks, and apply needed permissions. |
| 38 | It provides a fully functional /dev directory, where usually |
| 39 | udev runs on top, managing permissions and adding meaningful |
| 40 | symlinks. |
| 41 | In very limited environments, it may provide a sufficient |
| 42 | functional /dev without any further help. It also allows simple |
| 43 | rescue systems, and reliably handles dynamic major/minor numbers. |
Kay Sievers | 2b2af54 | 2009-04-30 15:23:42 +0200 | [diff] [blame] | 44 | |
Peter Korsgaard | da5e4ef | 2010-03-16 21:55:21 +0100 | [diff] [blame] | 45 | Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs |
| 46 | file system will be used instead. |
| 47 | |
Kay Sievers | 2b2af54 | 2009-04-30 15:23:42 +0200 | [diff] [blame] | 48 | config DEVTMPFS_MOUNT |
Kay Sievers | 4237e5f | 2010-01-14 22:47:57 +0100 | [diff] [blame] | 49 | bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs" |
Kay Sievers | 2b2af54 | 2009-04-30 15:23:42 +0200 | [diff] [blame] | 50 | depends on DEVTMPFS |
| 51 | help |
Kay Sievers | 4237e5f | 2010-01-14 22:47:57 +0100 | [diff] [blame] | 52 | This will instruct the kernel to automatically mount the |
| 53 | devtmpfs filesystem at /dev, directly after the kernel has |
| 54 | mounted the root filesystem. The behavior can be overridden |
| 55 | with the commandline parameter: devtmpfs.mount=0|1. |
| 56 | This option does not affect initramfs based booting, here |
| 57 | the devtmpfs filesystem always needs to be mounted manually |
Emilio López | 0feb03a | 2013-12-02 10:59:39 -0300 | [diff] [blame] | 58 | after the rootfs is mounted. |
Kay Sievers | 4237e5f | 2010-01-14 22:47:57 +0100 | [diff] [blame] | 59 | With this option enabled, it allows to bring up a system in |
| 60 | rescue mode with init=/bin/sh, even when the /dev directory |
| 61 | on the rootfs is completely empty. |
Kay Sievers | 2b2af54 | 2009-04-30 15:23:42 +0200 | [diff] [blame] | 62 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 63 | config STANDALONE |
Kees Cook | 967857d | 2012-10-23 13:01:50 -0700 | [diff] [blame] | 64 | bool "Select only drivers that don't need compile-time external firmware" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 65 | default y |
| 66 | help |
| 67 | Select this option if you don't have magic firmware for drivers that |
| 68 | need it. |
| 69 | |
| 70 | If unsure, say Y. |
| 71 | |
| 72 | config PREVENT_FIRMWARE_BUILD |
| 73 | bool "Prevent firmware from being built" |
| 74 | default y |
| 75 | help |
| 76 | Say yes to avoid building firmware. Firmware is usually shipped |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 77 | with the driver and only when updating the firmware should a |
| 78 | rebuild be made. |
| 79 | If unsure, say Y here. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 80 | |
| 81 | config FW_LOADER |
David Rientjes | 6a108a1 | 2011-01-20 14:44:16 -0800 | [diff] [blame] | 82 | tristate "Userspace firmware loading support" if EXPERT |
Adrian Bunk | d9b1919 | 2008-06-10 19:04:08 +0300 | [diff] [blame] | 83 | default y |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 84 | ---help--- |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 85 | This option is provided for the case where none of the in-tree modules |
| 86 | require userspace firmware loading support, but a module built |
| 87 | out-of-tree does. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 88 | |
Benjamin Gilbert | 7f55c73 | 2018-01-23 18:06:31 -0800 | [diff] [blame] | 89 | config EXTRA_FIRMWARE |
| 90 | string "External firmware blobs to build into the kernel binary" |
David Woodhouse | d172e7f | 2008-06-25 13:56:07 +0100 | [diff] [blame] | 91 | depends on FW_LOADER |
David Woodhouse | d172e7f | 2008-06-25 13:56:07 +0100 | [diff] [blame] | 92 | help |
Robin H. Johnson | 0946b2f | 2017-11-16 14:36:12 -0800 | [diff] [blame] | 93 | Various drivers in the kernel source tree may require firmware, |
| 94 | which is generally available in your distribution's linux-firmware |
| 95 | package. |
| 96 | |
| 97 | The linux-firmware package should install firmware into |
| 98 | /lib/firmware/ on your system, so they can be loaded by userspace |
| 99 | helpers on request. |
David Woodhouse | d172e7f | 2008-06-25 13:56:07 +0100 | [diff] [blame] | 100 | |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 101 | This option allows firmware to be built into the kernel for the case |
| 102 | where the user either cannot or doesn't want to provide it from |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 103 | userspace at runtime (for example, when the firmware in question is |
| 104 | required for accessing the boot device, and the user doesn't want to |
| 105 | use an initrd). |
| 106 | |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 107 | This option is a string and takes the (space-separated) names of the |
| 108 | firmware files -- the same names that appear in MODULE_FIRMWARE() |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 109 | and request_firmware() in the source. These files should exist under |
| 110 | the directory specified by the EXTRA_FIRMWARE_DIR option, which is |
Benjamin Gilbert | 7f55c73 | 2018-01-23 18:06:31 -0800 | [diff] [blame] | 111 | /lib/firmware by default. |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 112 | |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 113 | For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy |
Benjamin Gilbert | 7f55c73 | 2018-01-23 18:06:31 -0800 | [diff] [blame] | 114 | the usb8388.bin file into /lib/firmware, and build the kernel. Then |
| 115 | any request_firmware("usb8388.bin") will be satisfied internally |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 116 | without needing to call out to userspace. |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 117 | |
| 118 | WARNING: If you include additional firmware files into your binary |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 119 | kernel image that are not available under the terms of the GPL, |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 120 | then it may be a violation of the GPL to distribute the resulting |
matt mooney | 113647a | 2011-06-12 11:17:30 -0700 | [diff] [blame] | 121 | image since it combines both GPL and non-GPL work. You should |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 122 | consult a lawyer of your own before distributing such an image. |
| 123 | |
| 124 | config EXTRA_FIRMWARE_DIR |
| 125 | string "Firmware blobs root directory" |
| 126 | depends on EXTRA_FIRMWARE != "" |
Markus Trippelsdorf | df85b2d | 2017-09-16 11:01:16 +0200 | [diff] [blame] | 127 | default "/lib/firmware" |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 128 | help |
| 129 | This option controls the directory in which the kernel build system |
| 130 | looks for the firmware files listed in the EXTRA_FIRMWARE option. |
David Woodhouse | 4d2acfb | 2008-05-23 13:58:12 +0100 | [diff] [blame] | 131 | |
Takashi Iwai | 7b1269f | 2013-01-31 11:13:55 +0100 | [diff] [blame] | 132 | config FW_LOADER_USER_HELPER |
Takashi Iwai | 5a1379e | 2014-06-04 17:48:15 +0200 | [diff] [blame] | 133 | bool |
| 134 | |
| 135 | config FW_LOADER_USER_HELPER_FALLBACK |
Takashi Iwai | 7b1269f | 2013-01-31 11:13:55 +0100 | [diff] [blame] | 136 | bool "Fallback user-helper invocation for firmware loading" |
| 137 | depends on FW_LOADER |
Takashi Iwai | 5a1379e | 2014-06-04 17:48:15 +0200 | [diff] [blame] | 138 | select FW_LOADER_USER_HELPER |
Takashi Iwai | 7b1269f | 2013-01-31 11:13:55 +0100 | [diff] [blame] | 139 | help |
| 140 | This option enables / disables the invocation of user-helper |
| 141 | (e.g. udev) for loading firmware files as a fallback after the |
| 142 | direct file loading in kernel fails. The user-mode helper is |
| 143 | no longer required unless you have a special firmware file that |
Takashi Iwai | 5a1379e | 2014-06-04 17:48:15 +0200 | [diff] [blame] | 144 | resides in a non-standard path. Moreover, the udev support has |
| 145 | been deprecated upstream. |
| 146 | |
| 147 | If you are unsure about this, say N here. |
Takashi Iwai | 7b1269f | 2013-01-31 11:13:55 +0100 | [diff] [blame] | 148 | |
Johannes Berg | 833c954 | 2014-09-12 09:01:56 +0200 | [diff] [blame] | 149 | config WANT_DEV_COREDUMP |
| 150 | bool |
| 151 | help |
| 152 | Drivers should "select" this option if they desire to use the |
| 153 | device coredump mechanism. |
| 154 | |
Johannes Berg | cd3d9ea | 2014-10-30 10:00:35 +0100 | [diff] [blame] | 155 | config ALLOW_DEV_COREDUMP |
| 156 | bool "Allow device coredump" if EXPERT |
Aristeu Rozanski | 9c60269 | 2014-10-16 11:49:49 -0400 | [diff] [blame] | 157 | default y |
Johannes Berg | 833c954 | 2014-09-12 09:01:56 +0200 | [diff] [blame] | 158 | help |
Aristeu Rozanski | 9c60269 | 2014-10-16 11:49:49 -0400 | [diff] [blame] | 159 | This option controls if the device coredump mechanism is available or |
| 160 | not; if disabled, the mechanism will be omitted even if drivers that |
| 161 | can use it are enabled. |
| 162 | Say 'N' for more sensitive systems or systems that don't want |
| 163 | to ever access the information to not have the code, nor keep any |
| 164 | data. |
Johannes Berg | 833c954 | 2014-09-12 09:01:56 +0200 | [diff] [blame] | 165 | |
Aristeu Rozanski | 9c60269 | 2014-10-16 11:49:49 -0400 | [diff] [blame] | 166 | If unsure, say Y. |
Johannes Berg | 833c954 | 2014-09-12 09:01:56 +0200 | [diff] [blame] | 167 | |
| 168 | config DEV_COREDUMP |
| 169 | bool |
| 170 | default y if WANT_DEV_COREDUMP |
Johannes Berg | cd3d9ea | 2014-10-30 10:00:35 +0100 | [diff] [blame] | 171 | depends on ALLOW_DEV_COREDUMP |
Johannes Berg | 833c954 | 2014-09-12 09:01:56 +0200 | [diff] [blame] | 172 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 173 | config DEBUG_DRIVER |
| 174 | bool "Driver Core verbose debug messages" |
| 175 | depends on DEBUG_KERNEL |
| 176 | help |
| 177 | Say Y here if you want the Driver core to produce a bunch of |
| 178 | debug messages to the system log. Select this if you are having a |
| 179 | problem with the driver core and want to see more of what is |
| 180 | going on. |
| 181 | |
| 182 | If you are unsure about this, say N here. |
| 183 | |
Tejun Heo | 9ac7849 | 2007-01-20 16:00:26 +0900 | [diff] [blame] | 184 | config DEBUG_DEVRES |
| 185 | bool "Managed device resources verbose debug messages" |
| 186 | depends on DEBUG_KERNEL |
| 187 | help |
| 188 | This option enables kernel parameter devres.log. If set to |
| 189 | non-zero, devres debug messages are printed. Select this if |
| 190 | you are having a problem with devres or want to debug |
| 191 | resource management for a managed device. devres.log can be |
| 192 | switched on and off from sysfs node. |
| 193 | |
| 194 | If you are unsure about this, Say N here. |
| 195 | |
Rob Herring | bea5b15 | 2016-08-11 10:20:58 -0500 | [diff] [blame] | 196 | config DEBUG_TEST_DRIVER_REMOVE |
Laura Abbott | 248ff02 | 2016-10-07 09:09:30 -0700 | [diff] [blame] | 197 | bool "Test driver remove calls during probe (UNSTABLE)" |
Rob Herring | bea5b15 | 2016-08-11 10:20:58 -0500 | [diff] [blame] | 198 | depends on DEBUG_KERNEL |
| 199 | help |
| 200 | Say Y here if you want the Driver core to test driver remove functions |
| 201 | by calling probe, remove, probe. This tests the remove path without |
| 202 | having to unbind the driver or unload the driver module. |
| 203 | |
Laura Abbott | 248ff02 | 2016-10-07 09:09:30 -0700 | [diff] [blame] | 204 | This option is expected to find errors and may render your system |
| 205 | unusable. You should say N here unless you are explicitly looking to |
| 206 | test this functionality. |
Rob Herring | bea5b15 | 2016-08-11 10:20:58 -0500 | [diff] [blame] | 207 | |
Dmitry Torokhov | 79543cf | 2016-09-29 17:13:14 +0200 | [diff] [blame] | 208 | source "drivers/base/test/Kconfig" |
| 209 | |
Michael Holzheu | 4039483 | 2006-05-09 12:53:49 +0200 | [diff] [blame] | 210 | config SYS_HYPERVISOR |
| 211 | bool |
| 212 | default n |
Randy Dunlap | eba6cd6 | 2006-10-28 10:38:55 -0700 | [diff] [blame] | 213 | |
Ben Hutchings | 9f13a1f | 2012-01-10 03:04:32 +0000 | [diff] [blame] | 214 | config GENERIC_CPU_DEVICES |
| 215 | bool |
| 216 | default n |
| 217 | |
Ard Biesheuvel | 67bad2f | 2014-02-08 13:34:09 +0100 | [diff] [blame] | 218 | config GENERIC_CPU_AUTOPROBE |
| 219 | bool |
Ard Biesheuvel | 67bad2f | 2014-02-08 13:34:09 +0100 | [diff] [blame] | 220 | |
Thomas Gleixner | 87590ce | 2018-01-07 22:48:00 +0100 | [diff] [blame] | 221 | config GENERIC_CPU_VULNERABILITIES |
| 222 | bool |
| 223 | |
Lee Jones | 74d1d82 | 2012-02-06 11:22:22 -0800 | [diff] [blame] | 224 | config SOC_BUS |
| 225 | bool |
Arnd Bergmann | c97db7c | 2016-09-21 14:57:19 +0800 | [diff] [blame] | 226 | select GLOB |
Lee Jones | 74d1d82 | 2012-02-06 11:22:22 -0800 | [diff] [blame] | 227 | |
Mark Brown | b83a313 | 2011-05-11 19:59:58 +0200 | [diff] [blame] | 228 | source "drivers/base/regmap/Kconfig" |
| 229 | |
Sumit Semwal | d15bd7e | 2011-12-26 14:53:15 +0530 | [diff] [blame] | 230 | config DMA_SHARED_BUFFER |
Dave Airlie | 3b32a59 | 2012-01-13 09:05:14 +0000 | [diff] [blame] | 231 | bool |
Sumit Semwal | d15bd7e | 2011-12-26 14:53:15 +0530 | [diff] [blame] | 232 | default n |
| 233 | select ANON_INODES |
Chris Wilson | 03e4e0a | 2017-11-14 16:27:19 +0000 | [diff] [blame] | 234 | select IRQ_WORK |
Sumit Semwal | d15bd7e | 2011-12-26 14:53:15 +0530 | [diff] [blame] | 235 | help |
| 236 | This option enables the framework for buffer-sharing between |
| 237 | multiple drivers. A buffer is associated with a file using driver |
| 238 | APIs extension; the file's descriptor can then be passed on to other |
| 239 | driver. |
| 240 | |
Chris Wilson | f54d186 | 2016-10-25 13:00:45 +0100 | [diff] [blame] | 241 | config DMA_FENCE_TRACE |
| 242 | bool "Enable verbose DMA_FENCE_TRACE messages" |
Maarten Lankhorst | e941759 | 2014-07-01 12:57:14 +0200 | [diff] [blame] | 243 | depends on DMA_SHARED_BUFFER |
| 244 | help |
Chris Wilson | f54d186 | 2016-10-25 13:00:45 +0100 | [diff] [blame] | 245 | Enable the DMA_FENCE_TRACE printks. This will add extra |
Maarten Lankhorst | e941759 | 2014-07-01 12:57:14 +0200 | [diff] [blame] | 246 | spam to the console log, but will make it easier to diagnose |
| 247 | lockup related problems for dma-buffers shared across multiple |
| 248 | devices. |
| 249 | |
Aneesh Kumar K.V | f825c73 | 2013-07-02 11:15:15 +0530 | [diff] [blame] | 250 | config DMA_CMA |
| 251 | bool "DMA Contiguous Memory Allocator" |
| 252 | depends on HAVE_DMA_CONTIGUOUS && CMA |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 253 | help |
| 254 | This enables the Contiguous Memory Allocator which allows drivers |
| 255 | to allocate big physically-contiguous blocks of memory for use with |
| 256 | hardware components that do not support I/O map nor scatter-gather. |
| 257 | |
Jean Delvare | f0d6d1f | 2014-10-09 15:29:41 -0700 | [diff] [blame] | 258 | You can disable CMA by specifying "cma=0" on the kernel's command |
| 259 | line. |
| 260 | |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 261 | For more information see <include/linux/dma-contiguous.h>. |
| 262 | If unsure, say "n". |
| 263 | |
Aneesh Kumar K.V | f825c73 | 2013-07-02 11:15:15 +0530 | [diff] [blame] | 264 | if DMA_CMA |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 265 | comment "Default contiguous memory area size:" |
| 266 | |
| 267 | config CMA_SIZE_MBYTES |
| 268 | int "Size in Mega Bytes" |
| 269 | depends on !CMA_SIZE_SEL_PERCENTAGE |
Akinobu Mita | d7be003 | 2014-12-10 15:43:14 -0800 | [diff] [blame] | 270 | default 0 if X86 |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 271 | default 16 |
| 272 | help |
| 273 | Defines the size (in MiB) of the default memory area for Contiguous |
Akinobu Mita | d7be003 | 2014-12-10 15:43:14 -0800 | [diff] [blame] | 274 | Memory Allocator. If the size of 0 is selected, CMA is disabled by |
| 275 | default, but it can be enabled by passing cma=size[MG] to the kernel. |
| 276 | |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 277 | |
| 278 | config CMA_SIZE_PERCENTAGE |
| 279 | int "Percentage of total memory" |
| 280 | depends on !CMA_SIZE_SEL_MBYTES |
Akinobu Mita | d7be003 | 2014-12-10 15:43:14 -0800 | [diff] [blame] | 281 | default 0 if X86 |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 282 | default 10 |
| 283 | help |
| 284 | Defines the size of the default memory area for Contiguous Memory |
| 285 | Allocator as a percentage of the total memory in the system. |
Akinobu Mita | d7be003 | 2014-12-10 15:43:14 -0800 | [diff] [blame] | 286 | If 0 percent is selected, CMA is disabled by default, but it can be |
| 287 | enabled by passing cma=size[MG] to the kernel. |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 288 | |
| 289 | choice |
| 290 | prompt "Selected region size" |
Laurent Pinchart | 5e97f3f | 2012-10-18 09:29:44 +0200 | [diff] [blame] | 291 | default CMA_SIZE_SEL_MBYTES |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 292 | |
| 293 | config CMA_SIZE_SEL_MBYTES |
| 294 | bool "Use mega bytes value only" |
| 295 | |
| 296 | config CMA_SIZE_SEL_PERCENTAGE |
| 297 | bool "Use percentage value only" |
| 298 | |
| 299 | config CMA_SIZE_SEL_MIN |
| 300 | bool "Use lower value (minimum)" |
| 301 | |
| 302 | config CMA_SIZE_SEL_MAX |
| 303 | bool "Use higher value (maximum)" |
| 304 | |
| 305 | endchoice |
| 306 | |
| 307 | config CMA_ALIGNMENT |
| 308 | int "Maximum PAGE_SIZE order of alignment for contiguous buffers" |
Marc Carino | fe54b1f | 2014-06-04 16:10:01 -0700 | [diff] [blame] | 309 | range 4 12 |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 310 | default 8 |
| 311 | help |
| 312 | DMA mapping framework by default aligns all buffers to the smallest |
| 313 | PAGE_SIZE order which is greater than or equal to the requested buffer |
| 314 | size. This works well for buffers up to a few hundreds kilobytes, but |
| 315 | for larger buffers it just a memory waste. With this parameter you can |
| 316 | specify the maximum PAGE_SIZE order for contiguous buffers. Larger |
| 317 | buffers will be aligned only to this specified order. The order is |
| 318 | expressed as a power of two multiplied by the PAGE_SIZE. |
| 319 | |
| 320 | For example, if your system defaults to 4KiB pages, the order value |
| 321 | of 8 means that the buffers will be aligned up to 1MiB only. |
| 322 | |
| 323 | If unsure, leave the default value "8". |
| 324 | |
Marek Szyprowski | c64be2b | 2011-12-29 13:09:51 +0100 | [diff] [blame] | 325 | endif |
| 326 | |
Juri Lelli | 2ef7a29 | 2017-05-31 17:59:28 +0100 | [diff] [blame] | 327 | config GENERIC_ARCH_TOPOLOGY |
| 328 | bool |
| 329 | help |
| 330 | Enable support for architectures common topology code: e.g., parsing |
| 331 | CPU capacity information from DT, usage of such information for |
| 332 | appropriate scaling, sysfs interface for changing capacity values at |
| 333 | runtime. |
| 334 | |
Randy Dunlap | eba6cd6 | 2006-10-28 10:38:55 -0700 | [diff] [blame] | 335 | endmenu |