| /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/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/net/phy/mediatek/ |
| H A D | Kconfig | 7 Supports MediaTek SoC built-in 2.5Gb Ethernet PHYs.
17 Supports the MediaTek non-built-in Gigabit Ethernet PHYs.
19 Non-built-in Gigabit Ethernet PHYs include mt7530/mt7531.
21 common operations with MediaTek SoC built-in Gigabit
32 Supports MediaTek SoC built-in Gigabit Ethernet PHYs.
34 Include support for built-in Ethernet PHYs which are present in
|
| /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 | 10 will first look for built-in firmware, if it has any. Next, it will
23 You typically want this built-in (=y) but you can also enable this
24 as a module, in which case the firmware_class module will be built.
25 You also want to be sure to enable this built-in if you are going to
26 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
59 kernel firmware files. Built-in firmware searches are preceded
105 built-in. For details on how to work with the sysfs fallback mechanism
135 be if you have drivers which require firmware built-in and for
148 if firmware_class is built-in.
191 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 | 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/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/Documentation/ABI/testing/ |
| H A D | debugfs-scmi-raw | 11 Each write to the entry causes one command request to be built
29 Each write to the entry causes one command request to be built
45 Each write to the entry causes one command request to be built
65 Each write to the entry causes one command request to be built
116 Each write to the entry causes one command request to be built
143 Each write to the entry causes one command request to be built
169 Each write to the entry causes one command request to be built
198 Each write to the entry causes one command request to be built
|
| /linux/arch/loongarch/ |
| H A D | Kconfig | 372 string "Built-in kernel command line"
379 When that occurs, it is possible to define a built-in command
386 Choose how the kernel will handle the provided built-in command
393 Use the built-in command line as fallback in case we get nothing
397 bool "Use built-in to extend bootloader kernel arguments"
399 The built-in command line will be appended to the command-
405 bool "Always use the built-in kernel command string"
407 Always use the built-in command line, even if we get one during
415 bool "Enable built-in dtb in kernel"
423 Built-in DTBs are generic enough and can be used as references.
[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/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
109 The kernel module may be built after the fact on the running kernel to be
112 Say Y here if you want these performance tests built into the kernel.
|
| /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/drivers/gpio/ |
| H A D | Kconfig | 141 If built as a module its name will be gpio-idio-16.
166 If driver is built as a module it will be called gpio-altera.
613 When built as a module, the module will be called realtek_otto_gpio.
734 If built as a module its name will be gpio-tangier.
952 If built as a module its name will be gpio-i8255.
1184 controller. It requires the driver to be built in the kernel.
1307 This driver can also be built as a module. If so, the module
1319 This driver can also be built as a module. If so, the module
1330 This driver can also be built as a module. If so, the module
1340 This driver can also be built as a module. If so, the module will be
[all …]
|
| /linux/scripts/ |
| H A D | generate_builtin_ranges.awk | 69 # (1) Build a lookup map of built-in module names.
312 # (3) Collect offset ranges (relative to the section base address) for built-in
334 # If the current object does not belong to a built-in module, ignore it.
336 # If it does, we add a new built-in module offset range record.
348 # Determine which (if any) built-in modules the object belongs to.
351 # If we are processing a built-in module:
379 # If we encountered an object that is not part of a built-in module, we
384 # At this point, we encountered the start of a new built-in module.
402 # (3) Collect offset ranges (relative to the section base address) for built-in
446 # Determine which (if any) built
[all...] |
| /linux/Documentation/sound/cards/ |
| H A D | joystick.rst | 19 built-in gameport support. Hence, when the ALSA PCI driver is built
79 built-in gameport support.
81 As mentioned above, ALSA PCI drivers have the built-in gameport
89 ALSA ISA drivers don't have the built-in gameport support.
|
| /linux/lib/kunit/ |
| H A D | Makefile | 19 # KUnit 'hooks' are built-in even when KUnit is built as a module.
25 # string-stream-test compiles built-in only.
|
| /linux/drivers/firmware/arm_scmi/transports/ |
| H A D | Kconfig | 34 This driver can also be built as a module. If so, the module
48 This driver can also be built as a module. If so, the module
77 This driver can also be built as a module. If so, the module
90 This driver can also be built as a module. If so, the module
|
| /linux/drivers/pmdomain/arm/ |
| H A D | Kconfig | 11 This driver can also be built as a module. If so, the module will be
23 This driver can also be built as a module. If so, the module
36 This driver can also be built as a module. If so, the module will be
|