Searched +full:in +full:- +full:built (Results 1 – 25 of 1022) sorted by relevance
12345678910>>...41
| /kernel/linux/linux-4.19/drivers/rtc/ |
| D | Kconfig | 40 device should record time in UTC, since the kernel won't do
46 This clock should be battery-backed, so that it reads the correct
47 time when the system boots from a power-off state. Otherwise, your
60 in the RTC specified by RTC_HCTOSYS_DEVICE approximately every 11
71 one can sleep when setting time, because it runs in the workqueue
77 Say yes here to enable debugging support in the RTC framework
134 once-per-second update interrupts, used for synchronization.
151 This driver can also be built as a module. If so, the module
152 will be called rtc-test.
162 If you say yes here you get support for RTC function in Marvell
[all …]
|
| /kernel/linux/linux-5.10/drivers/rtc/ |
| 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
132 once-per-second update interrupts, used for synchronization.
149 This driver can also be built as a module. If so, the module
150 will be called rtc-test.
[all …]
|
| /kernel/linux/linux-5.10/drivers/i2c/busses/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
18 controller is part of the 7101 device, which is an ACPI-compliant
21 This driver can also be built as a module. If so, the module
22 will be called i2c-ali1535.
30 controller is part of the 7101 device, which is an ACPI-compliant
33 This driver can also be built as a module. If so, the module
34 will be called i2c-ali1563.
43 This driver can also be built as a module. If so, the module
44 will be called i2c-ali15x3.
55 This driver can also be built as a module. If so, the module
[all …]
|
| /kernel/linux/linux-4.19/drivers/i2c/busses/ |
| D | Kconfig | 17 controller is part of the 7101 device, which is an ACPI-compliant
20 This driver can also be built as a module. If so, the module
21 will be called i2c-ali1535.
29 controller is part of the 7101 device, which is an ACPI-compliant
32 This driver can also be built as a module. If so, the module
33 will be called i2c-ali1563.
42 This driver can also be built as a module. If so, the module
43 will be called i2c-ali15x3.
54 This driver can also be built as a module. If so, the module
55 will be called i2c-amd756.
[all …]
|
| /kernel/linux/linux-5.10/drivers/hwmon/ |
| 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
51 This driver can also be built as a module. If so, the module
52 will be called abx500-temp.
66 This driver can also be built as a module. If so, the module
80 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
100 This driver can also be built as a module. If so, the module
[all …]
|
| /kernel/linux/linux-4.19/drivers/hwmon/ |
| D | Kconfig | 19 sensors-detect script from the lm_sensors package. Read
20 <file:Documentation/hwmon/userspace-tools> for details.
22 This support can also be built as a module. If so, the module
49 This driver can also be built as a module. If so, the module
50 will be called abx500-temp.
64 This driver can also be built as a module. If so, the module
78 This driver can also be built as a module. If so, the module
88 This driver can also be built as a module. If so, the module
98 This driver can also be built as a module. If so, the module
108 This driver can also be built as a module. If so, the module
[all …]
|
| /kernel/linux/linux-4.19/net/caif/ |
| D | Kconfig | 9 ---help---
11 based connection-oriented MUX protocol developed by ST-Ericsson for use
18 built as modules. You will also need to say yes to any CAIF physical
28 ---help---
29 Enable the inclusion of debug code in the CAIF stack.
37 ---help---
39 This can be either built-in or a loadable module,
40 If you select to build it as a built-in then the main CAIF device must
41 also be a built-in.
48 ---help---
[all …]
|
| /kernel/linux/linux-5.10/net/caif/ |
| 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.
|
| /kernel/linux/linux-4.19/arch/riscv/ |
| D | Kconfig.debug | 3 bool "Built-in kernel command line"
12 For that, choose 'Y' here and fill in the extra boot parameters
13 in CONFIG_CMDLINE.
15 The built-in options will be concatenated to the default command
17 command line will be ignored and replaced by the built-in string.
20 string "Built-in kernel command string"
24 Supply command-line options at build time by entering them here.
27 bool "Built-in command line overrides bootloader arguments"
31 or firmware command line. Instead, the built-in command line
|
| /kernel/linux/linux-4.19/drivers/iio/adc/ |
| D | Kconfig | 4 # When adding new entries keep the list in alphabetical order
49 tristate "Analog Devices AD7476 and similar 1-channel ADCs driver"
67 Say yes here to build support for Analog Devices AD7766, AD7766-1,
68 AD7766-2, AD7767, AD7767-1, AD7767-2 SPI analog to digital converters.
138 If you say yes here you get support for the ADC included in Aspeed
167 called at91-sama5d2_adc.
170 tristate "X-Powers AXP20X and AXP22X ADC driver"
173 Say yes here to have support for X-Powers power management IC (PMIC)
180 tristate "X-Powers AXP288 ADC driver"
183 Say yes here to have support for X-Powers power management IC (PMIC) ADC
[all …]
|
| /kernel/linux/linux-4.19/drivers/nvmem/ |
| D | Kconfig | 9 This driver can also be built as a module. If so, the module
24 This driver can also be built as a module. If so, the module
25 will be called nvmem-imx-iim.
28 tristate "i.MX6 On-Chip OTP Controller support"
32 This is a driver for the On-Chip OTP Controller (OCOTP) available on
33 i.MX6 SoCs, providing access to 4 Kbits of one-time programmable
36 This driver can also be built as a module. If so, the module
37 will be called nvmem-imx-ocotp.
44 Say Y here to include support for NXP LPC18xx EEPROM memory found in
60 tristate "Freescale MXS On-Chip OTP Memory Support"
[all …]
|
| /kernel/linux/linux-4.19/drivers/base/firmware_loader/ |
| D | Kconfig | 7 This enables the firmware loading facility in the kernel. The kernel
8 will first look for built-in firmware, if it has any. Next, it will
9 look for the requested firmware in a series of filesystem paths:
21 You typically want this built-in (=y) but you can also enable this
22 as a module, in which case the firmware_class module will be built.
23 You also want to be sure to enable this built-in if you are going to
24 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
34 kernel firmware files. Built-in firmware searches are preceded
39 in boot and cannot rely on the firmware being placed in an initrd or
42 This option is a string and takes the (space-separated) names of the
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/adc/ |
| 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"
29 Say yes here to build support for Analog Devices AD7091R-5 ADC.
32 tristate "Analog Devices AD7124 and similar sigma-delta ADCs driver"
36 Say yes here to build support for Analog Devices AD7124-4 and AD7124-8
100 tristate "Analog Devices AD7476 1-channel ADCs driver and other similar devices from AD an TI"
126 ad7605-4, ad7606, ad7606-6, ad7606-4 analog to digital converters (ADC).
137 ad7605-4, ad7606, ad7606-6, ad7606-4 analog to digital converters (ADC).
148 Say yes here to build support for Analog Devices AD7766, AD7766-1,
[all …]
|
| /kernel/linux/linux-4.19/scripts/ |
| D | link-vmlinux.sh | 2 # SPDX-License-Identifier: GPL-2.0
7 # $(KBUILD_VMLINUX_MAIN) and $(KBUILD_VMLINUX_LIBS). Most are built-in.a files
8 # from top-level directories in the kernel tree, others are specified in
11 # which are linked conditionally (not within --whole-archive), and do not
17 # +-< $(KBUILD_VMLINUX_INIT)
18 # | +--< init/version.o + more
20 # +--< $(KBUILD_VMLINUX_MAIN)
21 # | +--< drivers/built-in.a mm/built-in.a + more
23 # +--< $(KBUILD_VMLINUX_LIBS)
24 # | +--< lib/lib.a + more
[all …]
|
| /kernel/linux/linux-5.10/drivers/base/firmware_loader/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
8 This enables the firmware loading facility in the kernel. The kernel
9 will first look for built-in firmware, if it has any. Next, it will
10 look for the requested firmware in a series of filesystem paths:
22 You typically want this built-in (=y) but you can also enable this
23 as a module, in which case the firmware_class module will be built.
24 You also want to be sure to enable this built-in if you are going to
25 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
38 kernel firmware files. Built-in firmware searches are preceded
43 in boot and cannot rely on the firmware being placed in an initrd or
[all …]
|
| /kernel/linux/linux-5.10/drivers/nvmem/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
32 This driver can also be built as a module. If so, the module
33 will be called nvmem-imx-iim.
36 tristate "i.MX 6/7/8 On-Chip OTP Controller support"
40 This is a driver for the On-Chip OTP Controller (OCOTP) available on
41 i.MX6 SoCs, providing access to 4 Kbits of one-time programmable
44 This driver can also be built as a module. If so, the module
45 will be called nvmem-imx-ocotp.
48 tristate "i.MX8 SCU On-Chip OTP Controller support"
52 This is a driver for the SCU On-Chip OTP Controller (OCOTP)
[all …]
|
| /kernel/linux/linux-4.19/Documentation/kbuild/ |
| D | kconfig-macro-language.txt | 2 -------
5 two languages in one. One language describes dependency graphs consisting of
17 $(CC) -o $(APP) $(SRC)
23 gcc -o foo foo.c
28 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
34 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
36 The macro language in Kconfig processes the source file into the following
42 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
43 dependency as explained in kconfig-language.txt.
47 ---------
[all …]
|
| D | makefiles.txt | 10 --- 3.1 Goal definitions
11 --- 3.2 Built-in object goals - obj-y
12 --- 3.3 Loadable module goals - obj-m
13 --- 3.4 Objects which export symbols
14 --- 3.5 Library file goals - lib-y
15 --- 3.6 Descending down in directories
16 --- 3.7 Compilation flags
17 --- 3.8 Command line dependency
18 --- 3.9 Dependency tracking
19 --- 3.10 Special Rules
[all …]
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| 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 …]
|
| /kernel/linux/linux-4.19/arch/mips/netlogic/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
6 bool "Built-in device tree for XLP EVP boards"
11 This DTB will be used if the firmware does not pass in a DTB
16 bool "Built-in device tree for XLP SVP boards"
21 This DTB will be used if the firmware does not pass in a DTB
26 bool "Built-in device tree for XLP FVP boards"
31 This DTB will be used if the firmware does not pass in a DTB
36 bool "Built-in device tree for XLP GVP boards"
41 This DTB will be used if the firmware does not pass in a DTB
46 bool "Built-in device tree for XLP RVP boards"
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/netlogic/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
6 bool "Built-in device tree for XLP EVP boards"
11 This DTB will be used if the firmware does not pass in a DTB
16 bool "Built-in device tree for XLP SVP boards"
21 This DTB will be used if the firmware does not pass in a DTB
26 bool "Built-in device tree for XLP FVP boards"
31 This DTB will be used if the firmware does not pass in a DTB
36 bool "Built-in device tree for XLP GVP boards"
41 This DTB will be used if the firmware does not pass in a DTB
46 bool "Built-in device tree for XLP RVP boards"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/nfs/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/filesystems/nfs/ |
| D | nfs-rdma.txt | 12 - Overview
13 - Getting Help
14 - Installation
15 - Check RDMA and NFS Setup
16 - NFS/RDMA Setup
24 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
25 was first included in the following release, Linux 2.6.25.
27 In our testing, we have obtained excellent performance results (full 10Gbit
37 nfs-rdma-devel@lists.sourceforge.net
47 - Install an RDMA device
[all …]
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| 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
37 tests on the RCU infrastructure. The kernel module may be built
40 Say Y here if you want RCU performance tests to be built into
56 on the RCU infrastructure. The kernel module may be built
59 Say Y here if you want RCU torture tests to be built into
65 tristate "Scalability tests for read-side synchronization (RCU and others)"
75 useful comparing RCU with various read-side synchronization mechanisms.
76 The kernel module may be built after the fact on the running kernel to be
[all …]
|
| /kernel/linux/linux-4.19/drivers/watchdog/ |
| D | Kconfig | 8 ---help---
13 longer than 1 minute will result in rebooting the machine. This
15 on-line as fast as possible after a lock-up. There's both a watchdog
16 implementation entirely in software (which can sometimes fail to
20 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
34 ---help---
50 bool "Update boot-enabled watchdog until userspace takes over"
98 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
113 This driver can also be built as a module. If so, the module
121 Support for the watchdog in the DA9063 PMIC.
[all …]
|
12345678910>>...41