1 menu "Generic Driver Options"
3 config UEVENT_HELPER_PATH
4 string "path to uevent helper"
8 Path to uevent helper program forked by the kernel for
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.
19 To disable user space helper program execution at early boot
20 time specify an empty string here. This setting can be altered
21 via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
25 bool "Maintain a devtmpfs filesystem to mount at /dev"
28 This creates a tmpfs/ramfs filesystem instance early at bootup.
29 In this filesystem, the kernel driver core maintains device
30 nodes with their default names and permissions for all
31 registered devices with an assigned major/minor number.
32 Userspace can modify the filesystem content as needed, add
33 symlinks, and apply needed permissions.
34 It provides a fully functional /dev directory, where usually
35 udev runs on top, managing permissions and adding meaningful
37 In very limited environments, it may provide a sufficient
38 functional /dev without any further help. It also allows simple
39 rescue systems, and reliably handles dynamic major/minor numbers.
41 Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs
42 file system will be used instead.
45 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
49 This will instruct the kernel to automatically mount the
50 devtmpfs filesystem at /dev, directly after the kernel has
51 mounted the root filesystem. The behavior can be overridden
52 with the commandline parameter: devtmpfs.mount=0|1.
53 This option does not affect initramfs based booting, here
54 the devtmpfs filesystem always needs to be mounted manually
55 after the roots is mounted.
56 With this option enabled, it allows to bring up a system in
57 rescue mode with init=/bin/sh, even when the /dev directory
58 on the rootfs is completely empty.
61 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
64 Select this option if you don't have magic firmware for drivers that
69 config PREVENT_FIRMWARE_BUILD
70 bool "Prevent firmware from being built"
73 Say yes to avoid building firmware. Firmware is usually shipped
74 with the driver and only when updating the firmware should a
76 If unsure, say Y here.
79 tristate "Userspace firmware loading support" if EXPERT
82 This option is provided for the case where none of the in-tree modules
83 require userspace firmware loading support, but a module built
86 config FIRMWARE_IN_KERNEL
87 bool "Include in-kernel firmware blobs in kernel binary"
91 The kernel source tree includes a number of firmware 'blobs'
92 that are used by various drivers. The recommended way to
93 use these is to run "make firmware_install", which, after
94 converting ihex files to binary, copies all of the needed
95 binary files in firmware/ to /lib/firmware/ on your system so
96 that they can be loaded by userspace helpers on request.
98 Enabling this option will build each required firmware blob
99 into the kernel directly, where request_firmware() will find
100 them without having to call out to userspace. This may be
101 useful if your root file system requires a device that uses
102 such firmware and do not wish to use an initrd.
104 This single option controls the inclusion of firmware for
105 every driver that uses request_firmware() and ships its
106 firmware in the kernel source tree, which avoids a
107 proliferation of 'Include firmware for xxx device' options.
109 Say 'N' and let firmware be loaded from userspace.
111 config EXTRA_FIRMWARE
112 string "External firmware blobs to build into the kernel binary"
115 This option allows firmware to be built into the kernel for the case
116 where the user either cannot or doesn't want to provide it from
117 userspace at runtime (for example, when the firmware in question is
118 required for accessing the boot device, and the user doesn't want to
121 This option is a string and takes the (space-separated) names of the
122 firmware files -- the same names that appear in MODULE_FIRMWARE()
123 and request_firmware() in the source. These files should exist under
124 the directory specified by the EXTRA_FIRMWARE_DIR option, which is
125 by default the firmware subdirectory of the kernel source tree.
127 For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy
128 the usb8388.bin file into the firmware directory, and build the kernel.
129 Then any request_firmware("usb8388.bin") will be satisfied internally
130 without needing to call out to userspace.
132 WARNING: If you include additional firmware files into your binary
133 kernel image that are not available under the terms of the GPL,
134 then it may be a violation of the GPL to distribute the resulting
135 image since it combines both GPL and non-GPL work. You should
136 consult a lawyer of your own before distributing such an image.
138 config EXTRA_FIRMWARE_DIR
139 string "Firmware blobs root directory"
140 depends on EXTRA_FIRMWARE != ""
143 This option controls the directory in which the kernel build system
144 looks for the firmware files listed in the EXTRA_FIRMWARE option.
145 The default is firmware/ in the kernel source tree, but by changing
146 this option you can point it elsewhere, such as /lib/firmware/ or
147 some other directory containing the firmware files.
150 bool "Driver Core verbose debug messages"
151 depends on DEBUG_KERNEL
153 Say Y here if you want the Driver core to produce a bunch of
154 debug messages to the system log. Select this if you are having a
155 problem with the driver core and want to see more of what is
158 If you are unsure about this, say N here.
161 bool "Managed device resources verbose debug messages"
162 depends on DEBUG_KERNEL
164 This option enables kernel parameter devres.log. If set to
165 non-zero, devres debug messages are printed. Select this if
166 you are having a problem with devres or want to debug
167 resource management for a managed device. devres.log can be
168 switched on and off from sysfs node.
170 If you are unsure about this, Say N here.
172 config SYS_HYPERVISOR
176 source "drivers/base/regmap/Kconfig"