| /linux/drivers/mfd/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 menu "Multifunction device drivers"
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
18 depends on !UML
27 depends on I2C
28 depends on OF
37 depends on ARCH_INTEL_SOCFPGA && SPI_MASTER=y && OF
48 depends on ARCH_INTEL_SOCFPGA && OF
57 tristate "Active-semi ACT8945A"
60 depends on I2C && OF
[all …]
|
| /linux/drivers/md/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 depends on BLOCK
10 Support multiple physical spindles through a single logical device.
20 # after relevant mdadm enhancements - to make "names=yes"
21 # the default - are widely available.
25 logical block device. This can be used to simply append one
27 into a RAID1/4/5 device so as to provide protection against hard
33 More information about Software RAID on Linux is contained in the
34 Software RAID mini-HOWTO, available from
[all …]
|
| /linux/include/linux/usb/ |
| H A D | otg-fsm.h | 1 // SPDX-License-Identifier: GPL-2.0+
18 * Table:6-4
23 * Table:6-5
49 * struct otg_fsm - OTG state machine according to the OTG spec
53 * Common inputs for A and B device
54 * @id: TRUE for B-device, FALSE for A-device.
56 * ADP measurement taken at n-2, differs by more than CADP_THR
57 * @power_up: TRUE when the OTG device first powers up its USB system and
60 * A-Device state inputs
61 * @a_srp_det: TRUE if the A-device detects SRP
[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
29 be called surface3-wmi.
[all …]
|
| /linux/sound/soc/mediatek/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
8 depends on ARCH_MEDIATEK
13 Select Y if you have such device.
18 depends on SND_SOC_MT2701 && I2C
24 Select Y if you have such device.
29 depends on SND_SOC_MT2701 && I2C
34 Select Y if you have such device.
39 depends on ARCH_MEDIATEK
44 Select Y if you have such device.
49 depends on SND_SOC_MT6797 && MTK_PMIC_WRAP
[all …]
|
| /linux/drivers/mtd/maps/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on MTD!=n
4 depends on HAS_IOMEM
7 bool "Support non-linear mappings of flash chips"
13 tristate "Flash device in physical memory map"
14 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_RAM || MTD_LPDDR
19 the physical address and size of the flash chips on your
21 with config options or at run-time.
28 depends on MTD_PHYSMAP
39 depends on MTD_PHYSMAP_COMPAT
[all …]
|
| /linux/drivers/usb/gadget/udc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # USB Gadget support on a system involves
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
22 # - integrated/SOC controllers first
23 # - licensed IP used in both SOC and discrete versions
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | device_link.rst | 4 Device links
8 that are borne out of a parent/child relationship within the device
10 are ordered based on this relationship, i.e. children are always suspended
13 Sometimes there is a need to represent device dependencies beyond the
18 dependencies, i.e. that one device must be bound to a driver before
21 Often these two dependency types come together, so a device depends on
25 Device links allow representation of such dependencies in the driver core.
27 In its standard or *managed* form, a device link combines *both* dependency
29 "supplier" device and its "consumer" devices, and it guarantees driver
30 presence on the supplier. The consumer devices are not probed before the
[all …]
|
| /linux/sound/soc/intel/boards/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on SND_SOC_INTEL_SST_TOPLEVEL || SND_SOC_SOF_INTEL_TOPLEVEL
51 depends on I2C
52 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
53 depends on X86_INTEL_LPSS || COMPILE_TEST
56 This adds support for the Lynxpoint Audio DSP on Intel(R) Haswell
58 Say Y or m if you have such a device.
67 depends on I2C
68 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
69 depends on X86_INTEL_LPSS || COMPILE_TEST
[all …]
|
| /linux/drivers/cdx/ |
| H A D | cdx.h | 1 /* SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2022-2023, Advanced Micro Devices, Inc.
14 * struct cdx_dev_params - CDX device parameters
15 * @cdx: CDX controller associated with the device
16 * @parent: Associated CDX Bus device
17 * @vendor: Vendor ID for CDX device
18 * @device: Device ID for CDX device
19 * @subsys_vendor: Sub vendor ID for CDX device
20 * @subsys_device: Sub device ID for CDX device
21 * @bus_num: Bus number for this CDX device
[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
10 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
12 These devices come in memory configurations from 32M - 1G. If you
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/Documentation/hid/ |
| H A D | hid-transport.rst | 8 Bluetooth, I2C and user-space I/O drivers.
14 devices and register them with the HID bus. HID core then loads generic device
15 drivers on top of it. The transport drivers are responsible for raw data
16 transport and device setup/management. HID core is responsible for
17 report-parsing, report interpretation and the user-space API. Device specifics
18 and quirks are handled by all layers depending on the quirk.
22 +-----------+ +-----------+ +-----------+ +-----------+
23 | Device #1 | | Device #i | | Device #j | | Device #k |
24 +-----------+ +-----------+ +-----------+ +-----------+
26 +------------+ +------------+
[all …]
|
| /linux/drivers/mtd/ |
| H A D | Kconfig | 2 tristate "Memory Technology Device (MTD) support"
6 used for solid state file systems on embedded devices. This option
9 to enumerate the devices which are present and obtain a handle on
17 depends on m
23 WARNING: some of the tests will ERASE entire MTD device which they
33 # MTD block device support is select'ed if needed
39 tristate "Caching block device access to MTD devices"
40 depends on BLOCK
45 on RAM chips in this manner. This block device is a user of MTD
49 It's possible to mount a rootfs using the MTD device on the "root="
[all …]
|
| /linux/sound/soc/intel/avs/boards/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 depends on SND_SOC_INTEL_AVS
9 depends on I2C
10 depends on MFD_INTEL_LPSS || COMPILE_TEST
14 Say Y or m if you have such a device. This is a recommended option.
22 Say Y or m if you have such a device. This is a recommended option.
27 depends on X86 && I2C
28 depends on MFD_INTEL_LPSS || COMPILE_TEST
32 Say Y or m if you have such a device. This is a recommended option.
36 tristate "HD-Audio generic board"
[all …]
|
| /linux/include/linux/surface_aggregator/ |
| H A D | device.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Surface System Aggregator Module (SSAM) bus and client-device subsystem.
5 * Main interface for the surface-aggregator bus, surface-aggregator client
6 * devices, and respective drivers building on top of the SSAM controller.
7 * Provides support for non-platform/non-ACPI SSAM clients via dedicated
10 * Copyright (C) 2019-2021 Maximilian Luz <luzmaximilian@gmail.com>
16 #include <linux/device.h>
24 /* -- Surface System Aggregator Module bus. --------------------------------- */
27 * enum ssam_device_domain - SAM device domain.
28 * @SSAM_DOMAIN_VIRTUAL: Virtual device.
[all …]
|
| /linux/include/linux/device/ |
| H A D | bus.h | 1 // SPDX-License-Identifier: GPL-2.0
3 * bus.h - the bus-specific portions of the driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
6 * Copyright (c) 2004-2009 Greg Kroah-Hartman <gregkh@suse.de>
7 * Copyright (c) 2008-2009 Novell Inc.
8 * Copyright (c) 2012-2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
9 * Copyright (c) 2012-2019 Linux Foundation
11 * See Documentation/driver-api/driver-model/ for more information.
25 * struct bus_type - The bus type of the device
28 * @dev_name: Used for subsystems to enumerate devices like ("foo%u", dev->id).
[all …]
|
| /linux/Documentation/driver-api/i3c/ |
| H A D | protocol.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 This chapter will focus on aspects that matter to software developers. For
11 everything hardware related (like how things are transmitted on the bus, how
17 https://resources.mipi.org/mipi-i3c-v1-download).
22 The I3C (pronounced 'eye-three-see') is a MIPI standardized protocol designed
25 while remaining power-efficient.
31 well, but let's focus on I3C devices for now.
33 An I3C device on the I3C bus can have one of the following roles:
35 * Master: the device is driving the bus. It's the one in charge of initiating
36 transactions or deciding who is allowed to talk on the bus (slave generated
[all …]
|
| /linux/drivers/iio/ |
| H A D | industrialio-backend.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * The typical architecture is to have one device as the frontend device which
8 * device which will callback into the backends when needed (to get/set some
11 * -------------------------------------------------------
12 * ------------------ | ------------ ------------ ------- FPGA|
13 * | ADC |------------------------| | ADC CORE |---------| DMA CORE |------| RAM | |
14 * | (Frontend/IIO) | Serial Data (eg: LVDS) | |(backend) |---------| |------| | |
15 * | |------------------------| ------------ ------------ ------- |
16 * ------------------ -------------------------------------------------------
19 * - Backends should register themselves with devm_iio_backend_register()
[all …]
|
| /linux/Documentation/virt/hyperv/ |
| H A D | vpci.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 PCI pass-thru devices
5 In a Hyper-V guest VM, PCI pass-thru devices (also called
8 Guest device drivers can interact directly with the hardware
10 provides higher bandwidth access to the device with lower
12 hypervisor. The device should appear to the guest just as it
13 would when running on bare metal, so no changes are required
14 to the Linux device drivers for the device.
16 Hyper-V terminology for vPCI devices is "Discrete Device
17 Assignment" (DDA). Public documentation for Hyper-V DDA is
[all …]
|
| /linux/drivers/usb/gadget/legacy/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # USB Gadget support on a system involves
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
19 # are a subset (implementing a USB device class specification).
23 # Gadget drivers are hardware-neutral, or "platform independent",
[all …]
|
| /linux/drivers/vdpa/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on NET
6 Enable this module to support vDPA device that uses a
13 tristate "vDPA device simulator core"
14 depends on RUNTIME_TESTING_MENU
18 Enable this module to support vDPA device simulators. These devices
22 tristate "vDPA simulator for networking device"
23 depends on VDPA_SIM
26 vDPA networking device simulator which loops TX traffic back to RX.
29 tristate "vDPA simulator for block device"
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts)
2 0 = reserved as null device number
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
8 3 = /dev/null Null device
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
12 7 = /dev/full Returns ENOSPC on write
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
[all …]
|
| /linux/drivers/video/fbdev/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 tristate "Support for frame buffer device drivers"
11 The frame buffer device provides an abstraction for the graphics
14 a well-defined interface, so the software doesn't need to know
15 anything about the low-level (hardware register) stuff.
20 server exists which uses the frame buffer device exclusively.
21 On several non-X86 architectures, the frame buffer device is the
24 The device is accessed through special device nodes, usually located
29 and the Framebuffer-HOWTO at
30 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
[all …]
|
| /linux/drivers/staging/greybus/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
6 depends on SOUND && SND_SOC
8 Select this option if you have a device that follows the
12 will be called gb-audio.ko
16 depends on SND_SOC && GREYBUS_AUDIO
18 Select this option if you have a Toshiba APB device that has I2S
19 ports and acts as a Greybus "Dummy codec". This device is a
20 bridge from an APB-I2S port to a Unipro network.
23 will be called gb-audio-codec.ko
29 Select this option if you have a device that follows the
[all …]
|
| /linux/Documentation/networking/ |
| H A D | switchdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Ethernet switch device driver model (switchdev)
11 Copyright |copy| 2014-2015 Scott Feldman <sfeldma@gmail.com>
14 The Ethernet switch device driver model (switchdev) is an in-kernel driver
19 an example setup using a data-center-class switch ASIC chip. Other setups
20 with SR-IOV or soft switches, such as OVS, are possible.
25 User-space tools
28 +-------------------------------------------------------------------+
31 +--------------+-------------------------------+
35 +----------------------------------------------+
[all …]
|