blob: 4e7f0ff83ae7b162c43355b6727019c7edfbe897 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "Generic Driver Options"
2
Michael Marineau86d56132014-04-10 14:09:31 -07003config UEVENT_HELPER
4 bool "Support for uevent helper"
5 default y
Kay Sievers6a8d8ab2007-08-15 15:38:28 +02006 help
Michael Marineau86d56132014-04-10 14:09:31 -07007 The uevent helper program is forked by the kernel for
Kay Sievers6a8d8ab2007-08-15 15:38:28 +02008 every uevent.
Kay Sievers79347792010-01-14 22:49:39 +01009 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.
Kay Sievers6a8d8ab2007-08-15 15:38:28 +020017
Michael Marineau86d56132014-04-10 14:09:31 -070018config 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
Márton Németh573c9772011-06-19 22:30:16 +020025 via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
26 later at runtime.
27
Kay Sievers2b2af542009-04-30 15:23:42 +020028config DEVTMPFS
Kay Sievers4237e5f2010-01-14 22:47:57 +010029 bool "Maintain a devtmpfs filesystem to mount at /dev"
Kay Sievers2b2af542009-04-30 15:23:42 +020030 help
Peter Korsgaardda5e4ef2010-03-16 21:55:21 +010031 This creates a tmpfs/ramfs filesystem instance early at bootup.
Kay Sievers4237e5f2010-01-14 22:47:57 +010032 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.
Kay Sievers2b2af542009-04-30 15:23:42 +020043
Peter Korsgaardda5e4ef2010-03-16 21:55:21 +010044 Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs
45 file system will be used instead.
46
Kay Sievers2b2af542009-04-30 15:23:42 +020047config DEVTMPFS_MOUNT
Kay Sievers4237e5f2010-01-14 22:47:57 +010048 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
Kay Sievers2b2af542009-04-30 15:23:42 +020049 depends on DEVTMPFS
50 help
Kay Sievers4237e5f2010-01-14 22:47:57 +010051 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
Emilio López0feb03a2013-12-02 10:59:39 -030057 after the rootfs is mounted.
Kay Sievers4237e5f2010-01-14 22:47:57 +010058 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.
Kay Sievers2b2af542009-04-30 15:23:42 +020061
Linus Torvalds1da177e2005-04-16 15:20:36 -070062config STANDALONE
Kees Cook967857d2012-10-23 13:01:50 -070063 bool "Select only drivers that don't need compile-time external firmware"
Linus Torvalds1da177e2005-04-16 15:20:36 -070064 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
71config 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
matt mooney113647a2011-06-12 11:17:30 -070076 with the driver and only when updating the firmware should a
77 rebuild be made.
78 If unsure, say Y here.
Linus Torvalds1da177e2005-04-16 15:20:36 -070079
80config FW_LOADER
David Rientjes6a108a12011-01-20 14:44:16 -080081 tristate "Userspace firmware loading support" if EXPERT
Adrian Bunkd9b19192008-06-10 19:04:08 +030082 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -070083 ---help---
matt mooney113647a2011-06-12 11:17:30 -070084 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.
Linus Torvalds1da177e2005-04-16 15:20:36 -070087
David Woodhoused172e7f2008-06-25 13:56:07 +010088config 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'
matt mooney113647a2011-06-12 11:17:30 -070094 that are used by various drivers. The recommended way to
matt mooney156faf92011-06-12 11:17:31 -070095 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
David Woodhoused172e7f2008-06-25 13:56:07 +010098 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
matt mooney113647a2011-06-12 11:17:30 -0700103 useful if your root file system requires a device that uses
104 such firmware and do not wish to use an initrd.
David Woodhoused172e7f2008-06-25 13:56:07 +0100105
106 This single option controls the inclusion of firmware for
matt mooney113647a2011-06-12 11:17:30 -0700107 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.
David Woodhoused172e7f2008-06-25 13:56:07 +0100110
111 Say 'N' and let firmware be loaded from userspace.
112
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100113config EXTRA_FIRMWARE
114 string "External firmware blobs to build into the kernel binary"
115 depends on FW_LOADER
116 help
matt mooney113647a2011-06-12 11:17:30 -0700117 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
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100119 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
matt mooney113647a2011-06-12 11:17:30 -0700123 This option is a string and takes the (space-separated) names of the
124 firmware files -- the same names that appear in MODULE_FIRMWARE()
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100125 and request_firmware() in the source. These files should exist under
126 the directory specified by the EXTRA_FIRMWARE_DIR option, which is
matt mooney113647a2011-06-12 11:17:30 -0700127 by default the firmware subdirectory of the kernel source tree.
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100128
matt mooney113647a2011-06-12 11:17:30 -0700129 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.
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100133
134 WARNING: If you include additional firmware files into your binary
matt mooney113647a2011-06-12 11:17:30 -0700135 kernel image that are not available under the terms of the GPL,
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100136 then it may be a violation of the GPL to distribute the resulting
matt mooney113647a2011-06-12 11:17:30 -0700137 image since it combines both GPL and non-GPL work. You should
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100138 consult a lawyer of your own before distributing such an image.
139
140config EXTRA_FIRMWARE_DIR
141 string "Firmware blobs root directory"
142 depends on EXTRA_FIRMWARE != ""
143 default "firmware"
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.
matt mooney113647a2011-06-12 11:17:30 -0700147 The default is firmware/ in the kernel source tree, but by changing
148 this option you can point it elsewhere, such as /lib/firmware/ or
149 some other directory containing the firmware files.
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100150
Takashi Iwai7b1269f2013-01-31 11:13:55 +0100151config FW_LOADER_USER_HELPER
Takashi Iwai5a1379e2014-06-04 17:48:15 +0200152 bool
153
154config FW_LOADER_USER_HELPER_FALLBACK
Takashi Iwai7b1269f2013-01-31 11:13:55 +0100155 bool "Fallback user-helper invocation for firmware loading"
156 depends on FW_LOADER
Takashi Iwai5a1379e2014-06-04 17:48:15 +0200157 select FW_LOADER_USER_HELPER
Takashi Iwai7b1269f2013-01-31 11:13:55 +0100158 help
159 This option enables / disables the invocation of user-helper
160 (e.g. udev) for loading firmware files as a fallback after the
161 direct file loading in kernel fails. The user-mode helper is
162 no longer required unless you have a special firmware file that
Takashi Iwai5a1379e2014-06-04 17:48:15 +0200163 resides in a non-standard path. Moreover, the udev support has
164 been deprecated upstream.
165
166 If you are unsure about this, say N here.
Takashi Iwai7b1269f2013-01-31 11:13:55 +0100167
Linus Torvalds1da177e2005-04-16 15:20:36 -0700168config DEBUG_DRIVER
169 bool "Driver Core verbose debug messages"
170 depends on DEBUG_KERNEL
171 help
172 Say Y here if you want the Driver core to produce a bunch of
173 debug messages to the system log. Select this if you are having a
174 problem with the driver core and want to see more of what is
175 going on.
176
177 If you are unsure about this, say N here.
178
Tejun Heo9ac78492007-01-20 16:00:26 +0900179config DEBUG_DEVRES
180 bool "Managed device resources verbose debug messages"
181 depends on DEBUG_KERNEL
182 help
183 This option enables kernel parameter devres.log. If set to
184 non-zero, devres debug messages are printed. Select this if
185 you are having a problem with devres or want to debug
186 resource management for a managed device. devres.log can be
187 switched on and off from sysfs node.
188
189 If you are unsure about this, Say N here.
190
Michael Holzheu40394832006-05-09 12:53:49 +0200191config SYS_HYPERVISOR
192 bool
193 default n
Randy Dunlapeba6cd62006-10-28 10:38:55 -0700194
Ben Hutchings9f13a1f2012-01-10 03:04:32 +0000195config GENERIC_CPU_DEVICES
196 bool
197 default n
198
Ard Biesheuvel67bad2f2014-02-08 13:34:09 +0100199config GENERIC_CPU_AUTOPROBE
200 bool
Ard Biesheuvel67bad2f2014-02-08 13:34:09 +0100201
Lee Jones74d1d822012-02-06 11:22:22 -0800202config SOC_BUS
203 bool
204
Mark Brownb83a3132011-05-11 19:59:58 +0200205source "drivers/base/regmap/Kconfig"
206
Sumit Semwald15bd7e2011-12-26 14:53:15 +0530207config DMA_SHARED_BUFFER
Dave Airlie3b32a592012-01-13 09:05:14 +0000208 bool
Sumit Semwald15bd7e2011-12-26 14:53:15 +0530209 default n
210 select ANON_INODES
211 help
212 This option enables the framework for buffer-sharing between
213 multiple drivers. A buffer is associated with a file using driver
214 APIs extension; the file's descriptor can then be passed on to other
215 driver.
216
Maarten Lankhorste9417592014-07-01 12:57:14 +0200217config FENCE_TRACE
218 bool "Enable verbose FENCE_TRACE messages"
219 depends on DMA_SHARED_BUFFER
220 help
221 Enable the FENCE_TRACE printks. This will add extra
222 spam to the console log, but will make it easier to diagnose
223 lockup related problems for dma-buffers shared across multiple
224 devices.
225
Aneesh Kumar K.Vf825c732013-07-02 11:15:15 +0530226config DMA_CMA
227 bool "DMA Contiguous Memory Allocator"
228 depends on HAVE_DMA_CONTIGUOUS && CMA
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100229 help
230 This enables the Contiguous Memory Allocator which allows drivers
231 to allocate big physically-contiguous blocks of memory for use with
232 hardware components that do not support I/O map nor scatter-gather.
233
234 For more information see <include/linux/dma-contiguous.h>.
235 If unsure, say "n".
236
Aneesh Kumar K.Vf825c732013-07-02 11:15:15 +0530237if DMA_CMA
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100238comment "Default contiguous memory area size:"
239
240config CMA_SIZE_MBYTES
241 int "Size in Mega Bytes"
242 depends on !CMA_SIZE_SEL_PERCENTAGE
243 default 16
244 help
245 Defines the size (in MiB) of the default memory area for Contiguous
246 Memory Allocator.
247
248config CMA_SIZE_PERCENTAGE
249 int "Percentage of total memory"
250 depends on !CMA_SIZE_SEL_MBYTES
251 default 10
252 help
253 Defines the size of the default memory area for Contiguous Memory
254 Allocator as a percentage of the total memory in the system.
255
256choice
257 prompt "Selected region size"
Laurent Pinchart5e97f3f2012-10-18 09:29:44 +0200258 default CMA_SIZE_SEL_MBYTES
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100259
260config CMA_SIZE_SEL_MBYTES
261 bool "Use mega bytes value only"
262
263config CMA_SIZE_SEL_PERCENTAGE
264 bool "Use percentage value only"
265
266config CMA_SIZE_SEL_MIN
267 bool "Use lower value (minimum)"
268
269config CMA_SIZE_SEL_MAX
270 bool "Use higher value (maximum)"
271
272endchoice
273
274config CMA_ALIGNMENT
275 int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
Marc Carinofe54b1f2014-06-04 16:10:01 -0700276 range 4 12
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100277 default 8
278 help
279 DMA mapping framework by default aligns all buffers to the smallest
280 PAGE_SIZE order which is greater than or equal to the requested buffer
281 size. This works well for buffers up to a few hundreds kilobytes, but
282 for larger buffers it just a memory waste. With this parameter you can
283 specify the maximum PAGE_SIZE order for contiguous buffers. Larger
284 buffers will be aligned only to this specified order. The order is
285 expressed as a power of two multiplied by the PAGE_SIZE.
286
287 For example, if your system defaults to 4KiB pages, the order value
288 of 8 means that the buffers will be aligned up to 1MiB only.
289
290 If unsure, leave the default value "8".
291
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100292endif
293
Randy Dunlapeba6cd62006-10-28 10:38:55 -0700294endmenu