| /linux/drivers/input/touchscreen/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 depends on MFD_88PM860X
20 support for the built-in touchscreen.
24 To compile this driver as a module, choose M here: the
25 module will be called 88pm860x-ts.
29 depends on SPI_MASTER
30 depends on HWMON = n || HWMON
34 and your board-specific setup code includes that in its
38 on your board, you will also get hwmon interfaces for the voltage
39 (and on ads7846/tsc2046/ad7873, temperature) sensors of this chip.
[all …]
|
| /linux/drivers/char/ipmi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 tristate 'IPMI top-level message handler'
8 depends on HAS_IOMEM
15 voltage, etc.) in a system.
17 See <file:Documentation/driver-api/ipmi.rst> for more details on the driver.
31 bool 'Generate a panic event to all BMCs on a panic'
36 available, the module parameter for ipmi_msghandler named
42 depends on IPMI_PANIC_EVENT
52 the module parameter for ipmi_msghandler named panic_op can
63 tristate 'IPMI System Interface handler'
[all …]
|
| /linux/drivers/platform/surface/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Microsoft Surface Platform-Specific Drivers
7 bool "Microsoft Surface Platform-Specific Device Drivers"
8 depends on ARM64 || X86 || COMPILE_TEST
11 Say Y here to get to see options for platform-specific device drivers
21 depends on ACPI_WMI
22 depends on DMI
23 depends on INPUT
24 depends on SPI
28 To compile this driver as a module, choose M here: the module will
[all …]
|
| /linux/drivers/acpi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
11 depends on ARCH_SUPPORTS_ACPI
20 Linux requires an ACPI-compliant platform (hardware/firmware),
21 and assumes the presence of OS-directed configuration and power
27 the Plug-and-Play BIOS specification (PnP BIOS), the
32 Linux support for ACPI is based on Intel Corporation's ACPI
33 Component Architecture (ACPI CA). For more information on the
37 ACPI is an open industry specification originally co-developed by
38 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
66 depends on THERMAL
[all …]
|
| /linux/drivers/usb/typec/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
7 only one type of plug is supported on both ends, i.e. there will not
8 be Type-A plug on one end of the cable and Type-B plug on the other.
9 Determination of the host-to-device relationship happens through a
10 specific Configuration Channel (CC) which goes through the USB Type-C
12 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
21 Modes when they are supported. USB Power Delivery does not depend on
22 USB Type-C connector, however it is mostly used together with USB
[all …]
|
| /linux/drivers/platform/surface/aggregator/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+
2 # Copyright (C) 2019-2022 Maximilian Luz <luzmaximilian@gmail.com>
5 tristate "Microsoft Surface System Aggregator Module Subsystem and Drivers"
6 depends on SERIAL_DEV_BUS
7 depends on ACPI && !RISCV
10 The Surface System Aggregator Module (Surface SAM or SSAM) is an
11 embedded controller (EC) found on 5th- and later-generation Microsoft
15 Depending on the device in question, this EC provides varying
17 - EC access from ACPI via Surface ACPI Notify (5th- and 6th-generation)
18 - battery status information (all devices)
[all …]
|
| /linux/drivers/usb/typec/ucsi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Connector System Software Interface driver"
5 depends on !CPU_BIG_ENDIAN
6 depends on USB_ROLE_SWITCH || !USB_ROLE_SWITCH
9 USB Type-C Connector System Software Interface (UCSI) is a
10 specification for an interface that allows the operating system to
11 control the USB Type-C ports. On UCSI system the USB Type-C ports
14 is required. UCSI is available on most of the new Intel based systems
15 that are equipped with Embedded Controller and USB Type-C ports.
18 on the platform, ACPI, PCI, I2C, etc. may be used. Therefore this
[all …]
|
| /linux/drivers/firmware/arm_scmi/vendors/imx/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
6 depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF)
9 This enables i.MX System BBM control logic which supports RTC
12 To compile this driver as a module, choose M here: the
13 module will be called imx-sm-bbm.
17 depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF)
18 depends on IMX_SCMI_CPU_DRV
21 This enables i.MX System CPU Protocol to manage cpu
24 To compile this driver as a module, choose M here: the
25 module will be called imx-sm-cpu.
[all …]
|
| /linux/fs/minix/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Minix file system support"
4 depends on BLOCK
7 Minix is a simple operating system used in many classes about OS's.
8 The minix file system (method to organize files on a hard disk
9 partition or a floppy disk) was the original file system for Linux,
10 but has been superseded by the second extended file system ext2fs.
11 You don't want to use the minix file system on your hard disk
12 because of certain built-in restrictions, but it is sometimes found
13 on older Linux floppy disks. This option will enlarge your kernel
[all …]
|
| /linux/drivers/firmware/imx/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on IMX_MBOX
7 and the firmware running on DSP.
8 DSP exists on some i.MX8 processors (e.g i.MX8QM, i.MX8QXP).
15 depends on IMX_MBOX
18 The System Controller Firmware (SCFW) is a low-level system function
19 which runs on a dedicated Cortex-M core to provide power, clock, and
20 resource management. It exists on some i.MX8 processors. e.g. i.MX8QM
24 SCU firmware running on M4.
28 depends on ARCH_MXC || COMPILE_TEST
[all …]
|
| /linux/drivers/platform/x86/amd/hsmp/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 depends on AMD_NODE || COMPILE_TEST
14 depends on ACPI
15 depends on HWMON || !HWMON
18 Host System Management Port (HSMP) interface is a mailbox interface
19 between the x86 core and the System Management Unit (SMU) firmware.
21 system management functionality on EPYC and MI300A server CPUs
28 If you choose to compile this driver as a module the module will be
33 depends on HWMON || !HWMON
36 Host System Management Port (HSMP) interface is a mailbox interface
[all …]
|
| /linux/drivers/rtc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 depends on !S390
20 be allowed to plug one or more RTCs to your system. You will
26 bool "Set system time from RTC on startup and resume"
29 If you say yes here, the system time (wall clock) will be set using
34 string "RTC used to set the system time"
35 depends on RTC_HCTOSYS
38 The RTC device that will be used to (re)initialize the system
39 clock, usually rtc0. Initialization is done when the system
44 This clock should be battery-backed, so that it reads the correct
[all …]
|
| /linux/drivers/input/joystick/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 depends on !UML
10 weapon control system or something like that you can say Y here
33 To compile this driver as a module, choose M here: the
34 module will be called analog.
43 To compile this driver as a module, choose M here: the
44 module will be called a3d.
48 depends on IIO
54 To compile this driver as a module, choose M here: the
55 module will be called adc-joystick.
[all …]
|
| /linux/samples/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 depends on CC_CAN_LINK
14 tristate "Build trace_events examples -- loadable modules only"
15 depends on EVENT_TRACING && m
17 This builds the trace event example module.
20 tristate "Build custom trace event example -
[all...] |
| /linux/Documentation/arch/x86/ |
| H A D | intel_txt.rst | 6 Technology (Intel(R) TXT), defines platform-level enhancements that
13 - Provides dynamic root of trust for measurement (DRTM)
14 - Data protection in case of improper shutdown
15 - Measurement and verification of launched environment
18 non-vPro systems. It is currently available on desktop systems
19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell
20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45,
30 - LinuxTAG 2008:
31 http://www.linuxtag.org/2008/en/conf/events/vp-donnerstag.html
33 - TRUST2008:
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | ipmi.rst | 8 standard for controlling intelligent devices that monitor a system.
9 It provides for dynamic discovery of sensors in the system and the
12 standardized database for field-replaceable units (FRUs) and a watchdog
16 system (called a Baseboard Management Controller, or BMC) and
17 management software that can use the IPMI system.
25 -------------
28 things to have it work right depending on your hardware. Most of
32 No matter what, you must pick 'IPMI top-level message handler' to use
33 IPMI. What you do beyond that depends on your needs and hardware.
35 The message handler does not provide any user-level interfaces.
[all …]
|
| /linux/drivers/i2c/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
15 or System Management Bus is a subset of the I2C protocol. More
25 This I2C support can also be built as a module. If so, the module
26 will be called i2c-core.
30 depends on I2C=y && ACPI
46 Say Y here to use i2c-* device files, usually found in the /dev
47 directory on your system. They make it possible to have user-space
48 programs use the I2C bus. Information on how to do this is
49 contained in the file <file:Documentation/i2c/dev-interface.rst>.
[all …]
|
| /linux/drivers/hid/surface-hid/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+
2 menu "Surface System Aggregator Module HID support"
3 depends on SURFACE_AGGREGATOR
6 tristate "HID transport driver for Surface System Aggregator Module"
7 depends on SURFACE_AGGREGATOR_REGISTRY
10 Driver to support integrated HID devices on newer Microsoft Surface
14 by the Surface Aggregator Module (i.e. the embedded controller) on
15 7th-generation Microsoft Surface devices, i.e. Surface Book 3 and
16 Surface Laptop 3. On those models, it is mainly used to connect the
20 integrated touchpad and keyboard, on 7th generation Microsoft Surface
[all …]
|
| /linux/fs/romfs/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "ROM file system support"
4 depends on BLOCK || MTD
6 This is a very small read-only file system mainly intended for
8 other read-only media as well. Read
11 To compile this file system support as a module, choose M here: the
12 module will be called romfs. Note that the file system of your
14 module.
24 depends on ROMFS_FS
30 bool "Block device-backed ROM file system support"
[all …]
|
| /linux/drivers/mfd/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 depends on !UML
27 depends on I2C
28 depends on OF
36 bool "Altera Arria10 DevKit System Resource chip"
37 depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF
41 Support for the Altera Arria10 DevKit MAX5 System Resource chip
47 bool "Altera SOCFPGA System Manager"
48 depends on ARCH_INTEL_SOCFPGA || COMPILE_TEST
[all …]
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 15 There are many situations where users are reluctant to reboot a system. It may
16 be because their system is performing complex scientific computations or under
18 users want to also have a stable and secure system. Livepatching gives users
20 functions without a system reboot.
30 - The kernel probes are the most generic. The code can be redirected by
33 - The function tracer calls the code from a predefined location that is
35 compiler using the '-pg' gcc option.
37 - Livepatching typically needs to redirect the code at the very beginning
61 the same way to the rest of the system. In this case, the functions might
74 The aim is to define a so-called consistency model. It attempts to define
[all …]
|
| /linux/drivers/s390/char/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 depends on S390
8 depends on CCW && TTY
14 prompt "Support for fullscreen applications on 3270 terminals"
15 depends on TN3270
17 Include support for fullscreen applications on an IBM 3270 terminal.
21 prompt "Support for console on 3270 terminal"
22 depends on TN3270=y
24 Include support for using an IBM 3270 terminal as a Linux system
30 depends on CCW && TTY
[all …]
|
| /linux/drivers/mtd/devices/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
3 depends on MTD!=n
4 depends on HAS_IOMEM
8 depends on PCI
12 These devices come in memory configurations from 32M - 1G. If you
15 If this driver is compiled as a module you get the ability to select
18 will use a 1G memory map as its view of the device. As a module,
21 particularly useful on the 2.2 kernels on PPC architectures as there
26 depends on MTD_PMC551
[all …]
|
| /linux/fs/nfs/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on INET && FILE_LOCKING && MULTIUSER
11 Choose Y here if you want to access files residing on other
12 computers using Sun's Network File System protocol. To compile
13 this file system support as a module, choose M here: the module
18 the Linux nfs-utils package, available from http://linux-nfs.org/.
27 To configure a system which mounts its root file system via NFS
30 system on NFS" below. You cannot compile this file system as a
31 module in this case.
37 depends on NFS_FS
[all …]
|
| /linux/arch/m68k/ |
| H A D | Kconfig.devices | 1 # SPDX-License-Identifier: GPL-2.0
6 depends on BROKEN && (Q40 || SUN3X)
15 Use the power-on LED on your machine as a load meter. The exact
16 behavior is platform-dependent, but normally the flash frequency is
17 a hyperbolic function of the 5-minute load average.
19 # We have a dedicated heartbeat LED. :-)
22 depends on PROC_FS
25 access to information about the machine you're running on,
31 depends on ATARI
38 depends on BLOCK && NATFEAT
[all …]
|