| /linux/drivers/hwmon/ |
| H A D | Kconfig | 23 This support can also be built as a module. If so, the module
53 This driver can also be built as a module. If so, the module
67 This driver can also be built as a module. If so, the module
85 This driver can also be built as a module. If so, the module
95 This driver can also be built as a module. If so, the module
105 This driver can also be built as a module. If so, the module
116 This driver can also be built as a module. If so, the module
127 This driver can also be built as a module. If so, the module
138 This driver can also be built as a module. If so, the module
148 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/drivers/rtc/ |
| H A D | Kconfig | 158 This driver can also be built as a module. If so, the module
172 This driver can also be built as a module. If so, the module
182 This driver can also be built as a module. If so, the module
192 This driver can also be built as a module. If so, the module
202 This driver can also be built as a module. If so, the module
212 This driver can also be built as a module. If so, the module
223 This driver can also be built as a module. If so, the module
233 This driver can also be built as a module. If so, the module
244 This driver can also be built as a module. If so, the module will
254 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/drivers/i2c/busses/ |
| H A D | Kconfig | 28 This driver can also be built as a module. If so, the module
40 This driver can also be built as a module. If so, the module
50 This driver can also be built as a module. If so, the module
62 This driver can also be built as a module. If so, the module
72 This driver can also be built as a module. If so, the module
82 This driver can also be built as modules. If so, the modules will
92 built-in ASF functionality, allowing it to issue generic SMBus
109 This driver can also be built as a module. If so, the module
169 This driver can also be built as a module. If so, the module
188 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/drivers/iio/adc/ |
| H A D | Kconfig | 518 This driver can also be built as a module. If so, the module will be
529 This driver can also be built as a module. If so, the module will be
538 This driver can also be built as a module. If chosen, the module name
552 This driver can also be built as a module. If so, the module will be
598 This driver can also be built as a module. If so, the module will be
626 This driver can also be built as a module. If so, the module will be
647 This driver can also be built as a module. If so, the module will be
667 This driver can also be built as a module. If so, the module will be
688 This driver can also be built as a module. If so, the module will be
698 This driver can also be built as a module. If so, the module will be
[all …]
|
| /linux/drivers/net/ieee802154/ |
| H A D | Kconfig | 21 This driver can also be built as a module. To do so say M here.
33 This driver can also be built as a module. To do so, say M here.
45 This driver can also be built as a module. To do so, say M here.
56 This driver can also be built as a module. To do so, say M here.
66 This driver can also be built as a module. To do so say M here.
77 This driver can also be built as a module. To do so, say M here.
89 This driver can also be built as a module. To do so, say M here.
111 This driver can also be built as a module. To do so, say M here.
122 This driver can also be built as a module. To do so say M here.
|
| /linux/drivers/i2c/muxes/ |
| H A D | Kconfig | 19 This driver can also be built as a module. If so, the module
31 This driver can also be built as a module. If so, the module
44 This driver can also be built as a module. If so, the module
55 This driver can also be built as a module. If so, the module
64 This driver can also be built as a module. If so, the module
74 This driver can also be built as a module. If so, the module
87 This driver can also be built as a module. If so, the module will be
99 This driver can also be built as a module. If so, the module
119 This driver can also be built as a module. If so, the module
135 This driver can also be built as a module. If so, the module
|
| /linux/net/caif/ |
| H A D | Kconfig | 19 built as a module. You will also need to say Y (or M) to any CAIF
40 This can be either built-in or a loadable module.
41 If you select to build it as a built-in then the main CAIF device must
42 also be a built-in.
51 This can be either built-in or a loadable module.
52 If you select to build it as a built-in then the main CAIF device must
53 also be a built-in.
|
| /linux/drivers/misc/lkdtm/ |
| H A D | lkdtm.h | 14 pr_err("Unexpected! This %s was built with " #kconfig "=y\n", \
17 pr_warn("This is probably expected, since this %s was built *without* " #kconfig "=y\n", \
28 …pr_warn("This is probably expected, since this %s was built with " #kconfig "=y but booted with '"…
32 pr_err("Unexpected! This %s was built with " #kconfig "=y and booted with '" param "=Y'\n", \
36 …pr_err("Unexpected! This %s was built with " #kconfig "=y (and booted without '" param "' specifie…
42 …pr_warn("This is probably expected, as this %s was built *without* " #kconfig "=y and booted with …
46 … pr_err("Unexpected! This %s was built *without* " #kconfig "=y but booted with '" param "=Y'\n", \
50 …pr_err("This is probably expected, since this %s was built *without* " #kconfig "=y (and booted wi…
|
| /linux/drivers/base/firmware_loader/builtin/ |
| H A D | main.c | 38 * if the firmware was built-in and if so use it right away. This can be used
41 * This looks for the firmware in the built-in kernel. Only if the kernel was
42 * built-in with the firmware you are looking for will this return successfully.
70 * @buf: If set this lets you use a pre-allocated buffer so that the built-in
75 * If the built-in firmware does not fit into the pre-allocated @buf this
78 * This looks for the firmware in the built-in kernel. Only if the kernel was
79 * built-in with the firmware you are looking for will this call possibly
81 * built-in firmware fits into the pre-allocated buffer size specified in
|
| /linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 11 will first look for built-in firmware, if it has any. Next, it will
24 You typically want this built-in (=y) but you can also enable this
25 as a module, in which case the firmware_class module will be built.
26 You also want to be sure to enable this built-in if you are going to
27 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
61 kernel firmware files. Built-in firmware searches are preceded
107 built-in. For details on how to work with the sysfs fallback mechanism
137 be if you have drivers which require firmware built-in and for
150 if firmware_class is built-in.
193 that are built into the kernel image (CONFIG_EXTRA_FIRMWARE).
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | run_manual.rst | 26 tests can also be built by enabling their config options in our
28 ending in ``_KUNIT_TEST``. Most tests can either be built as a module,
29 or be built into the kernel.
38 Once we have built our kernel (and/or modules), it is simple to run
39 the tests. If the tests are built-in, they will run automatically on the
43 If the tests are built as modules, they will run when the module is
78 You can use the debugfs filesystem to trigger built-in tests to run after
|
| /linux/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 81 "user-defined function" in contrast to "built-in function" listed below).
93 Built-in functions
96 Like Make, Kconfig provides several built-in functions. Every function takes a
99 In Make, every built-in function takes at least one argument. Kconfig allows
100 zero argument for built-in functions, such as $(filename), $(lineno). You could
101 consider those as "built-in variable", but it is just a matter of how we call
102 it after all. Let's say "built-in function" here to refer to natively supported
105 Kconfig currently supports the following built-in functions.
172 In Make, a user-defined function is referenced by using a built-in function,
177 Kconfig invokes user-defined functions and built-in functions in the same way.
|
| H A D | kbuild.rst | 17 This file lists all modules that are built into the kernel. This is used
22 This file contains modinfo from all modules that are built into the kernel.
28 that are built into the kernel. Together with System.map, it can be used
42 Additional options to the assembler (for built-in and modules).
50 Additional assembler options for built-in.
54 Additional options to the C compiler (for built-in and modules).
58 Additional options to the Rust compiler (for built-in and modules).
63 code that is compiled as built-in.
72 code that is compiled as built-in.
138 building external modules against a pre-built kernel in a separate build
[all …]
|
| H A D | makefiles.rst | 34 any built-in or modular targets.
83 These lines define the files to be built, any special compilation
93 foo.o. foo.o will be built from foo.c or foo.S.
95 If foo.o shall be built as a module, the variable obj-m is used.
102 $(CONFIG_FOO) evaluates to either y (for built-in) or m (for module).
106 Built-in object goals - obj-y
114 ``$(AR) rcSTP`` to merge these files into one built-in.a file.
120 built-in.a and succeeding instances will be ignored.
139 $(obj-m) specifies object files which are built as loadable
142 A module may be built from one source file or several source
[all …]
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | nfs-rdma.rst | 139 and server will not be built
142 in this case the NFS/RDMA client and server will be built as modules
145 and server will be built into the kernel
148 the NFS/RDMA client and server will be built.
163 If you built the RDMA components as modules, load them at
247 If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
254 Regardless of how the server was built (module or built-in), start the
275 If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
282 Regardless of how the client was built (module or built-in), use this
|
| /linux/drivers/gpu/drm/panel/ |
| H A D | Kconfig | 68 the host and has a built-in LED backlight.
79 interface to the host and has a built-in LED backlight.
262 the host and has a built-in LED backlight.
314 the host, a built-in LED backlight and touch controller.
325 the host and has a built-in LED backlight.
336 the host and has a built-in LED backlight.
347 the host and has a built-in LED backlight.
387 built-in LED backlight.
408 has a resolution of 720x1440 pixels, a built in backlight and touch
434 Say Y here if you want to enable support for the panels built
[all …]
|
| /linux/drivers/pinctrl/sophgo/ |
| H A D | Kconfig | 20 each pin. This driver can also be built as a module called
31 each pin. This driver can also be built as a module called
42 each pin. This driver can also be built as a module called
53 each pin. This driver can also be built as a module called
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | built-in-fw.rst | 2 Built-in firmware
5 Firmware can be built-in to the kernel, this means building the firmware
8 directly. You can enable built-in firmware using the kernel configuration
22 able to make use of built-in firmware:
|
| /linux/kernel/rcu/ |
| H A D | Kconfig.debug | 33 tests on the RCU infrastructure. The kernel module may be built
36 Say Y here if you want RCU performance tests to be built into
48 on the RCU infrastructure. The kernel module may be built
51 Say Y here if you want RCU torture tests to be built into
64 The kernel module may be built after the fact on the running kernel to be
67 Say Y here if you want these performance tests built into the kernel.
|
| /linux/drivers/watchdog/ |
| H A D | Kconfig | 228 This driver can also be built as a module. If so, the module
239 This driver can be built as a module. The module name is da9063_wdt.
249 This driver can be built as a module. The module name is da9062_wdt.
279 This driver can also be built as a module. If so, the module
290 This driver can also be built as a module. If so the module
300 This driver can also be built as a module. If so the module
505 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
546 be built as a module by choosing M. The module will
572 The driver can be built as a module by choosing M, and will
624 This driver can be built as a module by choosing M. The module
[all …]
|
| /linux/drivers/iio/light/ |
| H A D | Kconfig | 32 This driver can also be built as a module. If so, the module
85 If built as a dynamically linked module, it will be called
114 This driver can also be built as a module. If so, the module
400 This driver can also be built as a module. If so, the module
414 This driver can also be built as a module. If so, the module
425 If built as a dynamically linked module, it will be called
480 If built as a dynamically linked module, it will be called
491 If built as a dynamically linked module, it will be called
502 This driver can also be built as a module. If so, the module
574 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/security/tomoyo/ |
| H A D | Kconfig | 45 Say Y here if you want to activate access control as soon as built-in
78 bool "Use insecure built-in settings for fuzzing tests."
83 Enabling this option forces minimal built-in policy and disables
85 this option only if this kernel is built for doing fuzzing tests.
|
| /linux/drivers/accessibility/speakup/ |
| H A D | Kconfig | 9 video console for blind people. If built in to the
24 Speakup can either be built in or compiled as a module
28 the synthesizer drivers below can only be built as
36 The Dectalk pc driver can only be built as a module, and
127 This driver must be built as a module, and can not be
175 it built-in to the kernel or loaded as a module.
|
| /linux/arch/mips/ |
| H A D | Kconfig.debug | 30 bool "Built-in kernel command line"
41 The built-in options will be concatenated to the default command
43 command line will be ignored and replaced by the built-in string.
64 bool "Built-in command line overrides firmware arguments"
69 Instead, the built-in command line will be used exclusively.
|
| /linux/scripts/ |
| H A D | generate_builtin_ranges.awk | 69 # (1) Build a lookup map of built-in module names.
307 # (3) Collect offset ranges (relative to the section base address) for built-in
329 # If the current object does not belong to a built-in module, ignore it.
331 # If it does, we add a new built-in module offset range record.
343 # Determine which (if any) built-in modules the object belongs to.
346 # If we are processing a built-in module:
374 # If we encountered an object that is not part of a built-in module, we
379 # At this point, we encountered the start of a new built-in module.
397 # (3) Collect offset ranges (relative to the section base address) for built-in
441 # Determine which (if any) built-in modules the object belongs to.
[all …]
|