blob: e373671652b0914c10f3237ada35998be9de7fcf [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "Generic Driver Options"
2
Kay Sievers6a8d8ab2007-08-15 15:38:28 +02003config UEVENT_HELPER_PATH
4 string "path to uevent helper"
Kay Sievers79347792010-01-14 22:49:39 +01005 default ""
Kay Sievers6a8d8ab2007-08-15 15:38:28 +02006 help
7 Path to uevent helper program forked by the kernel for
8 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
Márton Németh573c9772011-06-19 22:30:16 +020018 To disable user space helper program execution at early boot
19 time specify an empty string here. This setting can be altered
20 via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
21 later at runtime.
22
Kay Sievers2b2af542009-04-30 15:23:42 +020023config DEVTMPFS
Kay Sievers4237e5f2010-01-14 22:47:57 +010024 bool "Maintain a devtmpfs filesystem to mount at /dev"
Kay Sievers2b2af542009-04-30 15:23:42 +020025 help
Peter Korsgaardda5e4ef2010-03-16 21:55:21 +010026 This creates a tmpfs/ramfs filesystem instance early at bootup.
Kay Sievers4237e5f2010-01-14 22:47:57 +010027 In this filesystem, the kernel driver core maintains device
28 nodes with their default names and permissions for all
29 registered devices with an assigned major/minor number.
30 Userspace can modify the filesystem content as needed, add
31 symlinks, and apply needed permissions.
32 It provides a fully functional /dev directory, where usually
33 udev runs on top, managing permissions and adding meaningful
34 symlinks.
35 In very limited environments, it may provide a sufficient
36 functional /dev without any further help. It also allows simple
37 rescue systems, and reliably handles dynamic major/minor numbers.
Kay Sievers2b2af542009-04-30 15:23:42 +020038
Peter Korsgaardda5e4ef2010-03-16 21:55:21 +010039 Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs
40 file system will be used instead.
41
Kay Sievers2b2af542009-04-30 15:23:42 +020042config DEVTMPFS_MOUNT
Kay Sievers4237e5f2010-01-14 22:47:57 +010043 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
Kay Sievers2b2af542009-04-30 15:23:42 +020044 depends on DEVTMPFS
45 help
Kay Sievers4237e5f2010-01-14 22:47:57 +010046 This will instruct the kernel to automatically mount the
47 devtmpfs filesystem at /dev, directly after the kernel has
48 mounted the root filesystem. The behavior can be overridden
49 with the commandline parameter: devtmpfs.mount=0|1.
50 This option does not affect initramfs based booting, here
51 the devtmpfs filesystem always needs to be mounted manually
52 after the roots is mounted.
53 With this option enabled, it allows to bring up a system in
54 rescue mode with init=/bin/sh, even when the /dev directory
55 on the rootfs is completely empty.
Kay Sievers2b2af542009-04-30 15:23:42 +020056
Linus Torvalds1da177e2005-04-16 15:20:36 -070057config STANDALONE
Kees Cook967857d2012-10-23 13:01:50 -070058 bool "Select only drivers that don't need compile-time external firmware"
Linus Torvalds1da177e2005-04-16 15:20:36 -070059 default y
60 help
61 Select this option if you don't have magic firmware for drivers that
62 need it.
63
64 If unsure, say Y.
65
66config PREVENT_FIRMWARE_BUILD
67 bool "Prevent firmware from being built"
68 default y
69 help
70 Say yes to avoid building firmware. Firmware is usually shipped
matt mooney113647a2011-06-12 11:17:30 -070071 with the driver and only when updating the firmware should a
72 rebuild be made.
73 If unsure, say Y here.
Linus Torvalds1da177e2005-04-16 15:20:36 -070074
75config FW_LOADER
David Rientjes6a108a12011-01-20 14:44:16 -080076 tristate "Userspace firmware loading support" if EXPERT
Adrian Bunkd9b19192008-06-10 19:04:08 +030077 default y
Linus Torvalds1da177e2005-04-16 15:20:36 -070078 ---help---
matt mooney113647a2011-06-12 11:17:30 -070079 This option is provided for the case where none of the in-tree modules
80 require userspace firmware loading support, but a module built
81 out-of-tree does.
Linus Torvalds1da177e2005-04-16 15:20:36 -070082
David Woodhoused172e7f2008-06-25 13:56:07 +010083config FIRMWARE_IN_KERNEL
84 bool "Include in-kernel firmware blobs in kernel binary"
85 depends on FW_LOADER
86 default y
87 help
88 The kernel source tree includes a number of firmware 'blobs'
matt mooney113647a2011-06-12 11:17:30 -070089 that are used by various drivers. The recommended way to
matt mooney156faf92011-06-12 11:17:31 -070090 use these is to run "make firmware_install", which, after
91 converting ihex files to binary, copies all of the needed
92 binary files in firmware/ to /lib/firmware/ on your system so
David Woodhoused172e7f2008-06-25 13:56:07 +010093 that they can be loaded by userspace helpers on request.
94
95 Enabling this option will build each required firmware blob
96 into the kernel directly, where request_firmware() will find
97 them without having to call out to userspace. This may be
matt mooney113647a2011-06-12 11:17:30 -070098 useful if your root file system requires a device that uses
99 such firmware and do not wish to use an initrd.
David Woodhoused172e7f2008-06-25 13:56:07 +0100100
101 This single option controls the inclusion of firmware for
matt mooney113647a2011-06-12 11:17:30 -0700102 every driver that uses request_firmware() and ships its
103 firmware in the kernel source tree, which avoids a
104 proliferation of 'Include firmware for xxx device' options.
David Woodhoused172e7f2008-06-25 13:56:07 +0100105
106 Say 'N' and let firmware be loaded from userspace.
107
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100108config EXTRA_FIRMWARE
109 string "External firmware blobs to build into the kernel binary"
110 depends on FW_LOADER
111 help
matt mooney113647a2011-06-12 11:17:30 -0700112 This option allows firmware to be built into the kernel for the case
113 where the user either cannot or doesn't want to provide it from
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100114 userspace at runtime (for example, when the firmware in question is
115 required for accessing the boot device, and the user doesn't want to
116 use an initrd).
117
matt mooney113647a2011-06-12 11:17:30 -0700118 This option is a string and takes the (space-separated) names of the
119 firmware files -- the same names that appear in MODULE_FIRMWARE()
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100120 and request_firmware() in the source. These files should exist under
121 the directory specified by the EXTRA_FIRMWARE_DIR option, which is
matt mooney113647a2011-06-12 11:17:30 -0700122 by default the firmware subdirectory of the kernel source tree.
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100123
matt mooney113647a2011-06-12 11:17:30 -0700124 For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy
125 the usb8388.bin file into the firmware directory, and build the kernel.
126 Then any request_firmware("usb8388.bin") will be satisfied internally
127 without needing to call out to userspace.
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100128
129 WARNING: If you include additional firmware files into your binary
matt mooney113647a2011-06-12 11:17:30 -0700130 kernel image that are not available under the terms of the GPL,
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100131 then it may be a violation of the GPL to distribute the resulting
matt mooney113647a2011-06-12 11:17:30 -0700132 image since it combines both GPL and non-GPL work. You should
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100133 consult a lawyer of your own before distributing such an image.
134
135config EXTRA_FIRMWARE_DIR
136 string "Firmware blobs root directory"
137 depends on EXTRA_FIRMWARE != ""
138 default "firmware"
139 help
140 This option controls the directory in which the kernel build system
141 looks for the firmware files listed in the EXTRA_FIRMWARE option.
matt mooney113647a2011-06-12 11:17:30 -0700142 The default is firmware/ in the kernel source tree, but by changing
143 this option you can point it elsewhere, such as /lib/firmware/ or
144 some other directory containing the firmware files.
David Woodhouse4d2acfb2008-05-23 13:58:12 +0100145
Takashi Iwai7b1269f2013-01-31 11:13:55 +0100146config FW_LOADER_USER_HELPER
147 bool "Fallback user-helper invocation for firmware loading"
148 depends on FW_LOADER
149 default y
150 help
151 This option enables / disables the invocation of user-helper
152 (e.g. udev) for loading firmware files as a fallback after the
153 direct file loading in kernel fails. The user-mode helper is
154 no longer required unless you have a special firmware file that
155 resides in a non-standard path.
156
Linus Torvalds1da177e2005-04-16 15:20:36 -0700157config DEBUG_DRIVER
158 bool "Driver Core verbose debug messages"
159 depends on DEBUG_KERNEL
160 help
161 Say Y here if you want the Driver core to produce a bunch of
162 debug messages to the system log. Select this if you are having a
163 problem with the driver core and want to see more of what is
164 going on.
165
166 If you are unsure about this, say N here.
167
Tejun Heo9ac78492007-01-20 16:00:26 +0900168config DEBUG_DEVRES
169 bool "Managed device resources verbose debug messages"
170 depends on DEBUG_KERNEL
171 help
172 This option enables kernel parameter devres.log. If set to
173 non-zero, devres debug messages are printed. Select this if
174 you are having a problem with devres or want to debug
175 resource management for a managed device. devres.log can be
176 switched on and off from sysfs node.
177
178 If you are unsure about this, Say N here.
179
Michael Holzheu40394832006-05-09 12:53:49 +0200180config SYS_HYPERVISOR
181 bool
182 default n
Randy Dunlapeba6cd62006-10-28 10:38:55 -0700183
Ben Hutchings9f13a1f2012-01-10 03:04:32 +0000184config GENERIC_CPU_DEVICES
185 bool
186 default n
187
Lee Jones74d1d822012-02-06 11:22:22 -0800188config SOC_BUS
189 bool
190
Mark Brownb83a3132011-05-11 19:59:58 +0200191source "drivers/base/regmap/Kconfig"
192
Sumit Semwald15bd7e2011-12-26 14:53:15 +0530193config DMA_SHARED_BUFFER
Dave Airlie3b32a592012-01-13 09:05:14 +0000194 bool
Sumit Semwald15bd7e2011-12-26 14:53:15 +0530195 default n
196 select ANON_INODES
197 help
198 This option enables the framework for buffer-sharing between
199 multiple drivers. A buffer is associated with a file using driver
200 APIs extension; the file's descriptor can then be passed on to other
201 driver.
202
Aneesh Kumar K.Vf825c732013-07-02 11:15:15 +0530203config DMA_CMA
204 bool "DMA Contiguous Memory Allocator"
205 depends on HAVE_DMA_CONTIGUOUS && CMA
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100206 help
207 This enables the Contiguous Memory Allocator which allows drivers
208 to allocate big physically-contiguous blocks of memory for use with
209 hardware components that do not support I/O map nor scatter-gather.
210
211 For more information see <include/linux/dma-contiguous.h>.
212 If unsure, say "n".
213
Aneesh Kumar K.Vf825c732013-07-02 11:15:15 +0530214if DMA_CMA
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100215comment "Default contiguous memory area size:"
216
217config CMA_SIZE_MBYTES
218 int "Size in Mega Bytes"
219 depends on !CMA_SIZE_SEL_PERCENTAGE
220 default 16
221 help
222 Defines the size (in MiB) of the default memory area for Contiguous
223 Memory Allocator.
224
225config CMA_SIZE_PERCENTAGE
226 int "Percentage of total memory"
227 depends on !CMA_SIZE_SEL_MBYTES
228 default 10
229 help
230 Defines the size of the default memory area for Contiguous Memory
231 Allocator as a percentage of the total memory in the system.
232
233choice
234 prompt "Selected region size"
Laurent Pinchart5e97f3f2012-10-18 09:29:44 +0200235 default CMA_SIZE_SEL_MBYTES
Marek Szyprowskic64be2b2011-12-29 13:09:51 +0100236
237config CMA_SIZE_SEL_MBYTES
238 bool "Use mega bytes value only"
239
240config CMA_SIZE_SEL_PERCENTAGE
241 bool "Use percentage value only"
242
243config CMA_SIZE_SEL_MIN
244 bool "Use lower value (minimum)"
245
246config CMA_SIZE_SEL_MAX
247 bool "Use higher value (maximum)"
248
249endchoice
250
251config CMA_ALIGNMENT
252 int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
253 range 4 9
254 default 8
255 help
256 DMA mapping framework by default aligns all buffers to the smallest
257 PAGE_SIZE order which is greater than or equal to the requested buffer
258 size. This works well for buffers up to a few hundreds kilobytes, but
259 for larger buffers it just a memory waste. With this parameter you can
260 specify the maximum PAGE_SIZE order for contiguous buffers. Larger
261 buffers will be aligned only to this specified order. The order is
262 expressed as a power of two multiplied by the PAGE_SIZE.
263
264 For example, if your system defaults to 4KiB pages, the order value
265 of 8 means that the buffers will be aligned up to 1MiB only.
266
267 If unsure, leave the default value "8".
268
269config CMA_AREAS
270 int "Maximum count of the CMA device-private areas"
271 default 7
272 help
273 CMA allows to create CMA areas for particular devices. This parameter
274 sets the maximum number of such device private CMA areas in the
275 system.
276
277 If unsure, leave the default value "7".
278
279endif
280
Randy Dunlapeba6cd62006-10-28 10:38:55 -0700281endmenu