| /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/base/firmware_loader/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
10 This enables the firmware loading facility in the kernel. The kernel
11 will first look for built-in firmware, if it has any. Next, it will
12 look for the requested firmware in a series of filesystem paths:
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
66 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 …]
|
| /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 …]
|
| H A D | faq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 test a single unit of code in isolation and hence the name *unit test*. A unit
15 code paths to be tested in the code under test. This is only possible if the
20 require installing the kernel on a test machine or in a virtual machine. All
21 testing frameworks require tests to be written in userspace and run on the
32 kernel and runs when the kernel boots, or when built as a module, when the
35 (see :ref:`kunit-on-qemu`).
37 In short, yes, you can run KUnit on other architectures, but it might require
40 For more information, see :ref:`kunit-on-non-uml`.
42 .. _kinds-of-tests:
[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/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
57 tristate "Scalability tests for read-side synchronization (RCU and others)"
63 useful comparing RCU with various read-side synchronization mechanisms.
64 The kernel module may be built after the fact on the running kernel to be
[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/Documentation/admin-guide/ |
| H A D | verify-bugs-and-bisect-regressions.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
8 This document describes how to check if some Linux kernel problem occurs in code
9 currently supported by developers -- to then explain how to locate the change
22 read and navigate this document -- especially when you want to look something
23 up in the reference section, then jump back to where you left off.
26 https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
33 the same commands as this section while describing them in brief fashion. The
35 in a reference section mention many alternatives, pitfalls, and additional
36 aspects, all of which might be essential in your present case.]*
[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/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/security/tomoyo/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 This selects TOMOYO Linux, pathname-based access control.
25 useful for kernels built by Linux distributors where TOMOYO is
40 such programs in "learning mode" dulls the system response
60 Say Y here if you want to activate access control as soon as built-in
[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 …]
|
| /linux/drivers/power/supply/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
57 Say Y here to enable support for the battery charger in the Maxim
65 in the Wolfson Microelectronics WM831x PMICs.
100 This driver can be built as a module. If so, the module will be
104 tristate "Active-semi ACT8945A charger driver"
108 Active-semi ActivePath ACT8945A charger.
124 battery fuel gauge (used in the Pinebook Pro & others)
126 This driver can also be built as a module. If so, the module will be
151 The battery monitor chip is used in many batteries/devices
158 tristate "DS2782/DS2786 standalone gas-gauge"
[all …]
|
| /linux/drivers/spmi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 SPMI (System Power Management Interface) is a two-wire
20 built-in SPMI PMIC Arbiter interface on Hisilicon 3670
31 built-in SPMI PMIC Arbiter interface on Qualcomm MSM family
42 built-in SPMI PMIC Arbiter interface on Mediatek family
|
| /linux/lib/kunit/ |
| H A D | Makefile | 1 obj-$(CONFIG_KUNIT) += kunit.o
3 kunit-objs += test.o \
7 string-stream.o \
9 try-catch.o \
16 kunit-objs += debugfs.o
19 # KUnit 'hooks' are built-in even when KUnit is built as a module.
20 obj-
[all...] |
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-module | 5 The name of the module that is in the kernel. This
7 dynamic module. If it is built directly into the kernel, it
11 Note: The conditions of creation in the built-in case are not
12 by design and may be removed in the future.
24 placed in this location within sysfs. See the
33 Note: If the module is built into the kernel, or if the
|
| /linux/lib/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
31 converting bitfields between a CPU-usable representation and a
33 - Is little endian (bytes are reversed within a 32-bit group)
34 - The least-significant 32-bit word comes first (within a 64-bit
36 - The most significant bit of a byte is at its right (bit 0 of a
39 in the data sheets of the peripherals they are in control of.
41 When in doubt, say N.
50 This option enables the use of hardware bit-reversal instructions on
90 bool "Access I/O in non-MMIO mode"
95 hosts which can not be accessed in MMIO mode. Using the logical PIO
[all …]
|
| /linux/drivers/iio/gyro/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 # When adding new entries keep the list in alphabetical order
41 This driver can also be built as a module. If so, the module
45 tristate "Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver"
53 This driver can also be built as a module. If so, the module will be
63 This driver can also be built as a module. If so, the module
74 Say yes here to build support for BOSCH BMG160 Tri-axis Gyro Sensor
78 This driver can also be built as a module. If so, the module
97 Say yes here to build support for NXP FXAS21002C Tri-axis Gyro
100 This driver can also be built as a module. If so, the module
[all …]
|