Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | menu "Generic Driver Options" |
2 | ||
86d56134 MM |
3 | config UEVENT_HELPER |
4 | bool "Support for uevent helper" | |
5 | default y | |
6a8d8abb | 6 | help |
86d56134 | 7 | The uevent helper program is forked by the kernel for |
6a8d8abb | 8 | every uevent. |
7934779a KS |
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. | |
6a8d8abb | 17 | |
86d56134 MM |
18 | config UEVENT_HELPER_PATH |
19 | string "path to uevent helper" | |
20 | depends on UEVENT_HELPER | |
21 | default "" | |
22 | help | |
23 | To disable user space helper program execution at by default | |
24 | specify an empty string here. This setting can still be altered | |
573c9774 MN |
25 | via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper |
26 | later at runtime. | |
27 | ||
2b2af54a | 28 | config DEVTMPFS |
4237e5fd | 29 | bool "Maintain a devtmpfs filesystem to mount at /dev" |
2b2af54a | 30 | help |
da5e4ef7 | 31 | This creates a tmpfs/ramfs filesystem instance early at bootup. |
4237e5fd KS |
32 | In this filesystem, the kernel driver core maintains device |
33 | nodes with their default names and permissions for all | |
34 | registered devices with an assigned major/minor number. | |
35 | Userspace can modify the filesystem content as needed, add | |
36 | symlinks, and apply needed permissions. | |
37 | It provides a fully functional /dev directory, where usually | |
38 | udev runs on top, managing permissions and adding meaningful | |
39 | symlinks. | |
40 | In very limited environments, it may provide a sufficient | |
41 | functional /dev without any further help. It also allows simple | |
42 | rescue systems, and reliably handles dynamic major/minor numbers. | |
2b2af54a | 43 | |
da5e4ef7 PK |
44 | Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs |
45 | file system will be used instead. | |
46 | ||
2b2af54a | 47 | config DEVTMPFS_MOUNT |
4237e5fd | 48 | bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs" |
2b2af54a KS |
49 | depends on DEVTMPFS |
50 | help | |
4237e5fd KS |
51 | This will instruct the kernel to automatically mount the |
52 | devtmpfs filesystem at /dev, directly after the kernel has | |
53 | mounted the root filesystem. The behavior can be overridden | |
54 | with the commandline parameter: devtmpfs.mount=0|1. | |
55 | This option does not affect initramfs based booting, here | |
56 | the devtmpfs filesystem always needs to be mounted manually | |
0feb03af | 57 | after the rootfs is mounted. |
4237e5fd KS |
58 | With this option enabled, it allows to bring up a system in |
59 | rescue mode with init=/bin/sh, even when the /dev directory | |
60 | on the rootfs is completely empty. | |
2b2af54a | 61 | |
1da177e4 | 62 | config STANDALONE |
967857df | 63 | bool "Select only drivers that don't need compile-time external firmware" |
1da177e4 LT |
64 | default y |
65 | help | |
66 | Select this option if you don't have magic firmware for drivers that | |
67 | need it. | |
68 | ||
69 | If unsure, say Y. | |
70 | ||
71 | config PREVENT_FIRMWARE_BUILD | |
72 | bool "Prevent firmware from being built" | |
73 | default y | |
74 | help | |
75 | Say yes to avoid building firmware. Firmware is usually shipped | |
113647a2 | 76 | with the driver and only when updating the firmware should a |
77 | rebuild be made. | |
78 | If unsure, say Y here. | |
1da177e4 LT |
79 | |
80 | config FW_LOADER | |
6a108a14 | 81 | tristate "Userspace firmware loading support" if EXPERT |
d9b19199 | 82 | default y |
1da177e4 | 83 | ---help--- |
113647a2 | 84 | This option is provided for the case where none of the in-tree modules |
85 | require userspace firmware loading support, but a module built | |
86 | out-of-tree does. | |
1da177e4 | 87 | |
d172e7f5 DW |
88 | config FIRMWARE_IN_KERNEL |
89 | bool "Include in-kernel firmware blobs in kernel binary" | |
90 | depends on FW_LOADER | |
91 | default y | |
92 | help | |
93 | The kernel source tree includes a number of firmware 'blobs' | |
113647a2 | 94 | that are used by various drivers. The recommended way to |
156faf90 | 95 | use these is to run "make firmware_install", which, after |
96 | converting ihex files to binary, copies all of the needed | |
97 | binary files in firmware/ to /lib/firmware/ on your system so | |
d172e7f5 DW |
98 | that they can be loaded by userspace helpers on request. |
99 | ||
100 | Enabling this option will build each required firmware blob | |
101 | into the kernel directly, where request_firmware() will find | |
102 | them without having to call out to userspace. This may be | |
113647a2 | 103 | useful if your root file system requires a device that uses |
104 | such firmware and do not wish to use an initrd. | |
d172e7f5 DW |
105 | |
106 | This single option controls the inclusion of firmware for | |
113647a2 | 107 | every driver that uses request_firmware() and ships its |
108 | firmware in the kernel source tree, which avoids a | |
109 | proliferation of 'Include firmware for xxx device' options. | |
d172e7f5 DW |
110 | |
111 | Say 'N' and let firmware be loaded from userspace. | |
112 | ||
4d2acfbf DW |
113 | config EXTRA_FIRMWARE |
114 | string "External firmware blobs to build into the kernel binary" | |
115 | depends on FW_LOADER | |
116 | help | |
113647a2 | 117 | This option allows firmware to be built into the kernel for the case |
118 | where the user either cannot or doesn't want to provide it from | |
4d2acfbf DW |
119 | userspace at runtime (for example, when the firmware in question is |
120 | required for accessing the boot device, and the user doesn't want to | |
121 | use an initrd). | |
122 | ||
113647a2 | 123 | This option is a string and takes the (space-separated) names of the |
124 | firmware files -- the same names that appear in MODULE_FIRMWARE() | |
4d2acfbf DW |
125 | and request_firmware() in the source. These files should exist under |
126 | the directory specified by the EXTRA_FIRMWARE_DIR option, which is | |
113647a2 | 127 | by default the firmware subdirectory of the kernel source tree. |
4d2acfbf | 128 | |
113647a2 | 129 | For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy |
130 | the usb8388.bin file into the firmware directory, and build the kernel. | |
131 | Then any request_firmware("usb8388.bin") will be satisfied internally | |
132 | without needing to call out to userspace. | |
4d2acfbf DW |
133 | |
134 | WARNING: If you include additional firmware files into your binary | |
113647a2 | 135 | kernel image that are not available under the terms of the GPL, |
4d2acfbf | 136 | then it may be a violation of the GPL to distribute the resulting |
113647a2 | 137 | image since it combines both GPL and non-GPL work. You should |
4d2acfbf DW |
138 | consult a lawyer of your own before distributing such an image. |
139 | ||
140 | config EXTRA_FIRMWARE_DIR | |
141 | string "Firmware blobs root directory" | |
142 | depends on EXTRA_FIRMWARE != "" | |
df85b2d7 | 143 | default "/lib/firmware" |
4d2acfbf DW |
144 | help |
145 | This option controls the directory in which the kernel build system | |
146 | looks for the firmware files listed in the EXTRA_FIRMWARE option. | |
4d2acfbf | 147 | |
7b1269f7 | 148 | config FW_LOADER_USER_HELPER |
5a1379e8 TI |
149 | bool |
150 | ||
151 | config FW_LOADER_USER_HELPER_FALLBACK | |
7b1269f7 TI |
152 | bool "Fallback user-helper invocation for firmware loading" |
153 | depends on FW_LOADER | |
5a1379e8 | 154 | select FW_LOADER_USER_HELPER |
7b1269f7 TI |
155 | help |
156 | This option enables / disables the invocation of user-helper | |
157 | (e.g. udev) for loading firmware files as a fallback after the | |
158 | direct file loading in kernel fails. The user-mode helper is | |
159 | no longer required unless you have a special firmware file that | |
5a1379e8 TI |
160 | resides in a non-standard path. Moreover, the udev support has |
161 | been deprecated upstream. | |
162 | ||
163 | If you are unsure about this, say N here. | |
7b1269f7 | 164 | |
833c9545 JB |
165 | config WANT_DEV_COREDUMP |
166 | bool | |
167 | help | |
168 | Drivers should "select" this option if they desire to use the | |
169 | device coredump mechanism. | |
170 | ||
cd3d9ea1 JB |
171 | config ALLOW_DEV_COREDUMP |
172 | bool "Allow device coredump" if EXPERT | |
9c602699 | 173 | default y |
833c9545 | 174 | help |
9c602699 AR |
175 | This option controls if the device coredump mechanism is available or |
176 | not; if disabled, the mechanism will be omitted even if drivers that | |
177 | can use it are enabled. | |
178 | Say 'N' for more sensitive systems or systems that don't want | |
179 | to ever access the information to not have the code, nor keep any | |
180 | data. | |
833c9545 | 181 | |
9c602699 | 182 | If unsure, say Y. |
833c9545 JB |
183 | |
184 | config DEV_COREDUMP | |
185 | bool | |
186 | default y if WANT_DEV_COREDUMP | |
cd3d9ea1 | 187 | depends on ALLOW_DEV_COREDUMP |
833c9545 | 188 | |
1da177e4 LT |
189 | config DEBUG_DRIVER |
190 | bool "Driver Core verbose debug messages" | |
191 | depends on DEBUG_KERNEL | |
192 | help | |
193 | Say Y here if you want the Driver core to produce a bunch of | |
194 | debug messages to the system log. Select this if you are having a | |
195 | problem with the driver core and want to see more of what is | |
196 | going on. | |
197 | ||
198 | If you are unsure about this, say N here. | |
199 | ||
9ac7849e TH |
200 | config DEBUG_DEVRES |
201 | bool "Managed device resources verbose debug messages" | |
202 | depends on DEBUG_KERNEL | |
203 | help | |
204 | This option enables kernel parameter devres.log. If set to | |
205 | non-zero, devres debug messages are printed. Select this if | |
206 | you are having a problem with devres or want to debug | |
207 | resource management for a managed device. devres.log can be | |
208 | switched on and off from sysfs node. | |
209 | ||
210 | If you are unsure about this, Say N here. | |
211 | ||
bea5b158 | 212 | config DEBUG_TEST_DRIVER_REMOVE |
248ff021 | 213 | bool "Test driver remove calls during probe (UNSTABLE)" |
bea5b158 RH |
214 | depends on DEBUG_KERNEL |
215 | help | |
216 | Say Y here if you want the Driver core to test driver remove functions | |
217 | by calling probe, remove, probe. This tests the remove path without | |
218 | having to unbind the driver or unload the driver module. | |
219 | ||
248ff021 LA |
220 | This option is expected to find errors and may render your system |
221 | unusable. You should say N here unless you are explicitly looking to | |
222 | test this functionality. | |
bea5b158 | 223 | |
79543cf2 DT |
224 | source "drivers/base/test/Kconfig" |
225 | ||
4039483f MH |
226 | config SYS_HYPERVISOR |
227 | bool | |
228 | default n | |
eba6cd67 | 229 | |
9f13a1fd BH |
230 | config GENERIC_CPU_DEVICES |
231 | bool | |
232 | default n | |
233 | ||
67bad2fd AB |
234 | config GENERIC_CPU_AUTOPROBE |
235 | bool | |
67bad2fd | 236 | |
74d1d82c LJ |
237 | config SOC_BUS |
238 | bool | |
c97db7cc | 239 | select GLOB |
74d1d82c | 240 | |
b83a313b MB |
241 | source "drivers/base/regmap/Kconfig" |
242 | ||
d15bd7ee | 243 | config DMA_SHARED_BUFFER |
3b32a592 | 244 | bool |
d15bd7ee SS |
245 | default n |
246 | select ANON_INODES | |
247 | help | |
248 | This option enables the framework for buffer-sharing between | |
249 | multiple drivers. A buffer is associated with a file using driver | |
250 | APIs extension; the file's descriptor can then be passed on to other | |
251 | driver. | |
252 | ||
f54d1867 CW |
253 | config DMA_FENCE_TRACE |
254 | bool "Enable verbose DMA_FENCE_TRACE messages" | |
e941759c ML |
255 | depends on DMA_SHARED_BUFFER |
256 | help | |
f54d1867 | 257 | Enable the DMA_FENCE_TRACE printks. This will add extra |
e941759c ML |
258 | spam to the console log, but will make it easier to diagnose |
259 | lockup related problems for dma-buffers shared across multiple | |
260 | devices. | |
261 | ||
f825c736 AK |
262 | config DMA_CMA |
263 | bool "DMA Contiguous Memory Allocator" | |
264 | depends on HAVE_DMA_CONTIGUOUS && CMA | |
c64be2bb MS |
265 | help |
266 | This enables the Contiguous Memory Allocator which allows drivers | |
267 | to allocate big physically-contiguous blocks of memory for use with | |
268 | hardware components that do not support I/O map nor scatter-gather. | |
269 | ||
f0d6d1f6 JD |
270 | You can disable CMA by specifying "cma=0" on the kernel's command |
271 | line. | |
272 | ||
c64be2bb MS |
273 | For more information see <include/linux/dma-contiguous.h>. |
274 | If unsure, say "n". | |
275 | ||
f825c736 | 276 | if DMA_CMA |
c64be2bb MS |
277 | comment "Default contiguous memory area size:" |
278 | ||
279 | config CMA_SIZE_MBYTES | |
280 | int "Size in Mega Bytes" | |
281 | depends on !CMA_SIZE_SEL_PERCENTAGE | |
d7be003a | 282 | default 0 if X86 |
c64be2bb MS |
283 | default 16 |
284 | help | |
285 | Defines the size (in MiB) of the default memory area for Contiguous | |
d7be003a AM |
286 | Memory Allocator. If the size of 0 is selected, CMA is disabled by |
287 | default, but it can be enabled by passing cma=size[MG] to the kernel. | |
288 | ||
c64be2bb MS |
289 | |
290 | config CMA_SIZE_PERCENTAGE | |
291 | int "Percentage of total memory" | |
292 | depends on !CMA_SIZE_SEL_MBYTES | |
d7be003a | 293 | default 0 if X86 |
c64be2bb MS |
294 | default 10 |
295 | help | |
296 | Defines the size of the default memory area for Contiguous Memory | |
297 | Allocator as a percentage of the total memory in the system. | |
d7be003a AM |
298 | If 0 percent is selected, CMA is disabled by default, but it can be |
299 | enabled by passing cma=size[MG] to the kernel. | |
c64be2bb MS |
300 | |
301 | choice | |
302 | prompt "Selected region size" | |
5e97f3f9 | 303 | default CMA_SIZE_SEL_MBYTES |
c64be2bb MS |
304 | |
305 | config CMA_SIZE_SEL_MBYTES | |
306 | bool "Use mega bytes value only" | |
307 | ||
308 | config CMA_SIZE_SEL_PERCENTAGE | |
309 | bool "Use percentage value only" | |
310 | ||
311 | config CMA_SIZE_SEL_MIN | |
312 | bool "Use lower value (minimum)" | |
313 | ||
314 | config CMA_SIZE_SEL_MAX | |
315 | bool "Use higher value (maximum)" | |
316 | ||
317 | endchoice | |
318 | ||
319 | config CMA_ALIGNMENT | |
320 | int "Maximum PAGE_SIZE order of alignment for contiguous buffers" | |
fe54b1fd | 321 | range 4 12 |
c64be2bb MS |
322 | default 8 |
323 | help | |
324 | DMA mapping framework by default aligns all buffers to the smallest | |
325 | PAGE_SIZE order which is greater than or equal to the requested buffer | |
326 | size. This works well for buffers up to a few hundreds kilobytes, but | |
327 | for larger buffers it just a memory waste. With this parameter you can | |
328 | specify the maximum PAGE_SIZE order for contiguous buffers. Larger | |
329 | buffers will be aligned only to this specified order. The order is | |
330 | expressed as a power of two multiplied by the PAGE_SIZE. | |
331 | ||
332 | For example, if your system defaults to 4KiB pages, the order value | |
333 | of 8 means that the buffers will be aligned up to 1MiB only. | |
334 | ||
335 | If unsure, leave the default value "8". | |
336 | ||
c64be2bb MS |
337 | endif |
338 | ||
2ef7a295 JL |
339 | config GENERIC_ARCH_TOPOLOGY |
340 | bool | |
341 | help | |
342 | Enable support for architectures common topology code: e.g., parsing | |
343 | CPU capacity information from DT, usage of such information for | |
344 | appropriate scaling, sysfs interface for changing capacity values at | |
345 | runtime. | |
346 | ||
eba6cd67 | 347 | endmenu |