| /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/drivers/i2c/busses/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 for Cypress CCGx Type-C controller. Individual bus drivers
25 controller is part of the 7101 device, which is an ACPI-compliant
28 This driver can also be built as a module. If so, the module
29 will be called i2c-ali1535.
37 controller is part of the 7101 device, which is an ACPI-compliant
40 This driver can also be built as a module. If so, the module
41 will be called i2c-ali1563.
50 This driver can also be built as a module. If so, the module
51 will be called i2c-ali15x3.
[all …]
|
| /linux/drivers/hwmon/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
20 sensors-detect script from the lm_sensors package. Read
21 <file:Documentation/hwmon/userspace-tools.rst> for details.
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
76 with SMpro co-processor.
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
[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/iio/adc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 # When adding new entries keep the list in alphabetical order
10 bool "ST-Ericsson AB8500 GPADC driver"
45 Say yes here to build support for Analog Devices AD4130-8 SPI analog
73 Say yes here to build support for Analog Devices AD7091R-5 ADC.
81 Say yes here to build support for Analog Devices AD7091R-2, AD7091R-4,
82 and AD7091R-8 ADC.
88 tristate "Analog Devices AD7124 and similar sigma-delta ADCs driver"
92 Say yes here to build support for Analog Devices AD7124-4 and AD7124-8
107 - AD7172-2
[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 …]
|
| H A D | kbuild.rst | 10 -------------
11 This file records the order in which modules appear in Makefiles. This
16 ---------------
17 This file lists all modules that are built into the kernel. This is used
21 -----------------------
22 This file contains modinfo from all modules that are built into the kernel.
26 ----------------------
28 that are built into the kernel. Together with System.map, it can be used
35 ---------
37 will be used in all cases where kbuild does preprocessing including
[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/drivers/gpu/drm/panel/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 Y030XX067A 320x480 3.0" panel as found in the YLM RG-280M, RG-300
18 and RG-99 handheld gaming consoles.
28 in the Versatile family syscon registers.
37 NT35596 1080x1920 video mode panel as found in some Asus
46 as found in the YLM RS-97 handheld gaming console.
49 tristate "Boe BF060Y8M-AJ0 panel"
54 Say Y here if you want to enable support for Boe BF060Y8M-AJ0
66 TFT-LCD modules. The panel has a 1200x1920 resolution and uses
68 the host and has a built-in LED backlight.
[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/drivers/watchdog/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 longer than 1 minute will result in rebooting the machine. This
16 on-line as fast as possible after a lock-up. There's both a watchdog
17 implementation entirely in software (which can sometimes fail to
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
51 bool "Update boot-enabled watchdog until userspace takes over"
65 The maximum time, in seconds, for which the watchdog framework takes
77 bool "Enable watchdog hrtimer-based pretimeouts"
82 be able to fire before the actual watchdog fires in some situations.
176 Support for the watchdog in the ROHM BD9576 and BD9573 PMICs.
[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
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/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/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 section 'osect'.
65 entries[idx] = sprintf("%s %08x-%08x %s", sect, soff, eoff, mod);
69 # (1) Build a lookup map of built-in module names.
[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 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.
|