Searched +full:built +full:- +full:in (Results 1 – 25 of 1049) sorted by relevance
12345678910>>...42
| /kernel/linux/linux-6.6/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
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 …]
|
| /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-6.6/drivers/i2c/busses/ |
| 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 …]
|
| /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-6.6/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
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 …]
|
| /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-6.6/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-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-6.6/drivers/base/firmware_loader/builtin/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/nvmem/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
37 calibration data required for the PCIe or the USB-C PHY.
39 This driver can also be built as a module. If so, the module will
40 be called nvmem-apple-efuses.
43 tristate "Broadcom On-Chip OTP Controller support"
51 This driver can also be built as a module. If so, the module
52 will be called nvmem-bcm-ocotp.
71 This driver can also be built as a module. If so, the module
72 will be called nvmem-imx-iim.
75 tristate "i.MX 6/7/8 On-Chip OTP Controller support"
[all …]
|
| /kernel/linux/linux-6.6/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"
33 Say yes here to build support for Analog Devices AD4130-8 SPI analog
44 Say yes here to build support for Analog Devices AD7091R-5 ADC.
47 tristate "Analog Devices AD7124 and similar sigma-delta ADCs driver"
51 Say yes here to build support for Analog Devices AD7124-4 and AD7124-8
126 tristate "Analog Devices AD7476 1-channel ADCs driver and other similar devices from AD and TI"
152 ad7605-4, ad7606, ad7606-6, ad7606-4 analog to digital converters (ADC).
163 ad7605-4, ad7606, ad7606-6, ad7606-4 analog to digital converters (ADC).
[all …]
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/kunit/ |
| 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 …]
|
| /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/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-6.6/drivers/base/firmware_loader/ |
| 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).
54 kernel firmware files. Built-in firmware searches are preceded
59 in boot and cannot rely on the firmware being placed in an initrd or
[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 …]
|
| D | makefiles.rst | 12 --- 3.1 Goal definitions
13 --- 3.2 Built-in object goals - obj-y
14 --- 3.3 Loadable module goals - obj-m
15 --- 3.4 Objects which export symbols
16 --- 3.5 Library file goals - lib-y
17 --- 3.6 Descending down in directories
18 --- 3.7 Compilation flags
19 --- 3.8 <deleted>
20 --- 3.9 Dependency tracking
21 --- 3.10 Special Rules
[all …]
|
| /kernel/linux/linux-6.6/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-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/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-6.6/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-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-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-6.6/drivers/gpu/drm/panel/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/firmware/ |
| 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
|
12345678910>>...42