| /linux/drivers/rtc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
41 device should record time in UTC, since the kernel won't do
44 This clock should be battery-backed, so that it reads the correct
45 time when the system boots from a power-off state. Otherwise, your
58 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
69 one can sleep when setting time, because it runs in the workqueue
75 Say yes here to enable debugging support in the RTC framework
141 once-per-second update interrupts, used for synchronization.
158 This driver can also be built as a module. If so, the module
159 will be called rtc-test.
[all …]
|
| /linux/net/caif/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
12 based connection-oriented MUX protocol developed by ST-Ericsson for use
19 built as a module. You will also need to say Y (or M) to any CAIF
30 Enable the inclusion of debug code in the CAIF stack.
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/base/firmware_loader/builtin/ |
| H A D | main.c | 1 // SPDX-License-Identifier: GPL-2.0
24 if (size < fw->size) in fw_copy_to_prealloc_buf()
26 memcpy(buf, fw->data, fw->size); in fw_copy_to_prealloc_buf()
31 * firmware_request_builtin() - load builtin firmware
35 * Some use cases in the kernel have a requirement so that no memory allocator
36 * is involved as these calls take place early in boot process. An example is
37 * the x86 CPU microcode loader. In these cases all the caller wants is to see
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.
[all …]
|
| /linux/drivers/net/phy/mediatek/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 Supports MediaTek SoC built-in 2.5Gb Ethernet PHYs.
11 bus. Certain link-up issues will also be fixed here.
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
36 present in the SoCs efuse and will dynamically calibrate VCM
37 (common-mode voltage) during startup.
|
| /linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
9 This enables the firmware loading facility in the kernel. The kernel
10 will first look for built-in firmware, if it has any. Next, it will
11 look for the requested firmware in a series of filesystem paths:
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
64 in boot and cannot rely on the firmware being placed in an initrd or
[all …]
|
| /linux/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 6 -------
9 two languages in one. One language describes dependency graphs consisting of
21 $(CC) -o $(APP) $(SRC)
27 gcc -o foo foo.c
32 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
38 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
40 The macro language in Kconfig processes the source file into the following
46 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
47 dependency as explained in kconfig-language.rst.
51 ---------
[all …]
|
| H A D | makefiles.rst | 16 kbuild Makefiles exist in every subdirectory
29 architecture-specific information to the top Makefile.
34 any built-in or modular targets.
51 working on. In order to do this effectively, they need some overall
69 kbuild infrastructure. This chapter introduces the syntax used in the
80 ----------------
83 These lines define the files to be built, any special compilation
90 obj-y += foo.o
92 This tells kbuild that there is one object in that directory, named
93 foo.o. foo.o will be built from foo.c or foo.S.
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | run_manual.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 include KUnit in any kernel, read out results, and parse manually.
11 .. note:: KUnit is not designed for use in a production system. It is
20 - We have an existing kernel configuration to test.
21 - Need to run on real hardware (or using an emulator/VM kunit_tool
23 - Wish to integrate with some existing testing systems.
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
[all …]
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | nfs-rdma.rst | 17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
18 was first included in the following release, Linux 2.6.25.
20 In our testing, we have obtained excellent performance results (full 10Gbit
29 nfs-rdma-devel@lists.sourceforge.net mailing list.
37 - Install an RDMA device
39 Any device supported by the drivers in drivers/infiniband/hw is acceptable.
41 Testing has been performed using several Mellanox-based IB cards, the
44 - Install a Linux distribution and tools
50 The procedures described in this document have been tested with
53 - Install nfs-utils-1.1.2 or greater on the client
[all …]
|
| /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:
24 * Legalese - firmware is non-GPL compatible
28 * Some firmware files may be really large in size. The remote-proc subsystem
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured
11 Each write to the entry causes one command request to be built
22 in little-endian binary format to have it sent to the configured
29 Each write to the entry causes one command request to be built
39 write a complete SCMI command message (header included) in
40 little-endian binary format to have it sent to the configured
45 Each write to the entry causes one command request to be built
55 polling-mode; write a complete SCMI asynchronous command message
56 (header included) in little-endian binary format to have it sent
58 polling-mode on the reception path of the immediate part of the
[all …]
|
| /linux/arch/loongarch/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
250 # MIPS Loongson code, to preserve Loongson-specific code paths in drivers that
281 def_bool $(as-instr,x:pcalau12i \$t0$(comma)%pc_hi20(x))
284 def_bool $(as-instr,movfcsr2gr \$t0$(comma)\$fcsr0)
287 def_bool $(cc-option,-Wa$(comma)-mthin-add-sub) || AS_IS_LLVM
290 def_bool $(as-instr,vld \$vr0$(comma)\$a0$(comma)0)
293 def_bool $(as-instr,xvld \$xr0$(comma)\$a0$(comma)0)
296 def_bool $(as-instr,movscr2gr \$a0$(comma)\$scr0)
299 def_bool $(as-instr,hvcl 0)
302 def_bool $(cc-option,-mannotate-tablejump)
[all …]
|
| /linux/drivers/misc/lkdtm/ |
| H A D | lkdtm.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
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…
97 /* Special declaration for function-in-rodata. */
|
| /linux/drivers/net/ieee802154/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 Say Y here to get to see options for IEEE 802.15.4 Low-Rate
11 If you say N, all options in this submenu will be skipped and
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.
[all …]
|
| /linux/arch/mips/ |
| H A D | Kconfig.debug | 1 # SPDX-License-Identifier: GPL-2.0
9 to print messages very early in the bootup process.
30 bool "Built-in kernel command line"
38 should choose 'Y' here, and fill in the extra boot arguments
39 in CONFIG_CMDLINE.
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.
46 the command line from the firmware or the second-stage bootloader.
55 the default command line, you can supply some command-line options at
56 build time by entering them here. In other cases you can specify
[all …]
|
| /linux/scripts/ |
| H A D | generate_builtin_ranges.awk | 1 #!/usr/bin/gawk -f
2 # SPDX-License-Identifier: GPL-2.0
16 if (fn in omod)
27 mod = substr(s, RSTART + 16, RLENGTH - 16);
30 mod = substr(s, RSTART + 13, RLENGTH - 13);
39 if (!(mod in mods))
44 gsub(/-/, "_", mod);
53 # Update the ranges entry for the given module 'mod' in sectio
[all...] |
| /linux/drivers/i2c/muxes/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 tristate "GPIO-based I2C arbitration"
19 This driver can also be built as a module. If so, the module
20 will be called i2c-arb-gpio-challenge.
23 tristate "GPIO-based I2C multiplexer"
31 This driver can also be built as a module. If so, the module
32 will be called i2c-mux-gpio.
41 I2C busses connected through a MUX, which in turn is controlled
42 by a MUX-controller from the MUX subsystem.
44 This driver can also be built as a module. If so, the module
[all …]
|
| /linux/kernel/rcu/ |
| H A D | Kconfig.debug | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # RCU-related debugging configuration options
19 false-positive splats, we keep it default disabled but once all
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
63 Note that PREEMPT_COUNT must be enabled if the preempt-disabled
64 and bh-disabled checks are to take effect, and that PREEMPT_RCU
65 must be enabled for the RCU-nesting checks to take effect.
[all …]
|
| /linux/Documentation/sound/cards/ |
| H A D | joystick.rst | 10 -------
17 cards. In the case of ISA (PnP) cards, it's usually handled by the
19 built-in gameport support. Hence, when the ALSA PCI driver is built
20 in the kernel, CONFIG_GAMEPORT must be 'y', too. Otherwise, the
24 the load time. It'd be safer to plug in the joystick device before
29 ---------
33 joystick support is always enabled. In the former ALSA version, there
43 als4000 joystick_port 0 = disable (default), 1 = auto-detect,
46 azf3328 joystick 0 = disable, 1 = enable, -1 = auto (default)
48 ens1371 joystick_port 0 = disable (default), 1 = auto-detect,
[all …]
|
| /linux/drivers/accessibility/speakup/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
9 video console for blind people. If built in to the
12 point your browser at <http://www.linux-speakup.org/>.
24 Speakup can either be built in or compiled as a module
28 the synthesizer drivers below can only be built as
32 used in conjunction with Speakup. Think of them as
36 The Dectalk pc driver can only be built as a module, and
37 requires software to be pre-loaded on to the card before
122 In order to use the DecTalk PC driver, you must download
123 the dec_pc.tgz file from linux-speakup.org. It is in
[all …]
|
| /linux/drivers/gpio/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
50 this symbol, but new drivers should use the generic gpio-regmap
60 non-sleeping contexts. They can make bitbanged serial protocols
81 numberspace-based functionalities of the sysfs interface.
125 # put drivers in the right section, in alphabetical order
137 Enables support for the idio-16 library functions. The idio-16 library
139 ACCES IDIO-16 family such as the 104-IDIO-16 and the PCI-IDIO-16.
141 If built as a module its name will be gpio-idio-16.
147 tristate "GPIO driver for 74xx-ICs with MMIO access"
151 Say yes here to support GPIO functionality for 74xx-compatible ICs
[all …]
|
| /linux/security/tomoyo/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 This selects TOMOYO Linux, pathname-based access control.
25 such programs in "learning mode" dulls the system response
45 Say Y here if you want to activate access control as soon as built-in
58 default "/sbin/tomoyo-init"
78 bool "Use insecure built-in settings for fuzzing tests."
83 Enabling this option forces minimal built-in policy and disables
84 domain/program checks for run-time policy modifications. Please enable
85 this option only if this kernel is built for doing fuzzing tests.
|
| /linux/drivers/firmware/arm_scmi/transports/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
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
57 If you want the SCMI SMC based transport to operate in atomic
62 in atomic context too, at the price of using a number of busy-waiting
66 tristate "SCMI transport based on OP-TEE service"
73 This enables the OP-TEE service based transport for SCMI.
76 transport based on OP-TEE SCMI service, answer Y.
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
[all …]
|
| /linux/drivers/net/can/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 to 8Mbit/s for the more recent CAN with Flexible Data-Rate
11 (CAN-FD). The CAN bus was originally mainly for automotive, but is now
12 widely used in marine (NMEA2000), industrial, and medical
14 PF_CAN is contained in <Documentation/networking/can.rst>.
16 This section contains all the CAN(-FD) device drivers including the
21 can-dev.
31 This driver can also be built as a module. If so, the module
43 In opposite to vcan loopback devices the vxcan only forwards CAN
45 CAN frames. To disable a potential echo in af_can.c the vxcan driver
[all …]
|
| /linux/certs/ |
| H A D | system_keyring.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
16 #include <keys/asymmetric-type.h>
36 * restrict_link_by_builtin_trusted - Restrict keyring addition by built-in CA
42 * Restrict the addition of keys into a keyring based on the key-to-be-added
43 * being vouched for by a key in the built in system keyring.
55 * restrict_link_by_digsig_builtin - Restrict digitalSignature key additions by the built-in keyring
61 * Restrict the addition of keys into a keyring based on the key-to-be-added
62 * being vouched for by a key in the built in system keyring. The new key
76 * restrict_link_by_builtin_and_secondary_trusted - Restrict keyring
77 * addition by both built-in and secondary keyrings.
[all …]
|