Searched +full:on +full:- +full:device (Results 1 – 25 of 1156) sorted by relevance
12345678910>>...47
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 menu "Multifunction device drivers"
17 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
24 depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
35 depends on (ARCH_SOCFPGA || ARCH_STRATIX10) && OF
44 tristate "Active-semi ACT8945A"
47 depends on I2C && OF
49 Support for the ACT8945A PMIC from Active-semi. This device
50 features three step-down DC/DC converters and four low-dropout
59 depends on ARCH_SUNXI || COMPILE_TEST
[all …]
|
| /kernel/linux/linux-5.10/include/linux/usb/ |
| D | otg-fsm.h | 1 // SPDX-License-Identifier: GPL-2.0+
31 * Table:6-4
36 * Table:6-5
62 * struct otg_fsm - OTG state machine according to the OTG spec
66 * Common inputs for A and B device
67 * @id: TRUE for B-device, FALSE for A-device.
69 * ADP measurement taken at n-2, differs by more than CADP_THR
70 * @power_up: TRUE when the OTG device first powers up its USB system and
73 * A-Device state inputs
74 * @a_srp_det: TRUE if the A-device detects SRP
[all …]
|
| /kernel/linux/linux-5.10/drivers/md/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 depends on BLOCK
11 Support multiple physical spindles through a single logical device.
20 logical block device. This can be used to simply append one
22 into a RAID1/4/5 device so as to provide protection against hard
28 More information about Software RAID on Linux is contained in the
29 Software RAID mini-HOWTO, available from
37 depends on BLK_DEV_MD=y
44 a several-second delay in the boot time due to various
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| 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 …]
|
| /kernel/linux/linux-5.10/sound/soc/intel/boards/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 depends on SND_SOC_INTEL_SST_TOPLEVEL || SND_SOC_SOF_INTEL_TOPLEVEL
33 depends on I2C
34 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
35 depends on X86_INTEL_LPSS || COMPILE_TEST
38 This adds support for the Lynxpoint Audio DSP on Intel(R) Haswell
40 Say Y or m if you have such a device.
49 depends on I2C
50 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
51 depends on X86_INTEL_LPSS || COMPILE_TEST
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/gadget/udc/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/mtd/devices/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/mtd/ |
| 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 System(s) to obtain a handle on the MTD device when it's mounted
[all …]
|
| /kernel/linux/linux-5.10/drivers/block/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # Block device driver configuration
8 depends on BLOCK
11 Say Y here to get to see options for various different block device
25 depends on BLK_DEV_NULL_BLK && FAULT_INJECTION
29 depends on ARCH_MAY_HAVE_PC_FDC
34 <file:Documentation/admin-guide/blockdev/floppy.rst>.
44 depends on BLK_DEV_FD
47 special low-level hardware accesses to them (access and use
48 non-standard formats, for example), then enable this.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hid/ |
| 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 of raw data
16 transport and device setup/management. HID core is responsible of
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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/i3c/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/usb/gadget/legacy/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/greybus/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
7 This target is read-only.
21 This is the type of the on-disk hash format.
32 This is the device containing data, the integrity of which needs to be
33 checked. It may be specified as a path, like /dev/sdaX, or a device number,
37 This is the device that supplies the hash tree data. It may be
38 specified similarly to the device path and may be the same device. If the
39 same device is used, the hash_start should be outside the configured
40 dm-verity device.
[all …]
|
| /kernel/linux/linux-5.10/drivers/fpga/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 depends on ARCH_SOCFPGA || COMPILE_TEST
23 depends on ARCH_SOCFPGA || COMPILE_TEST
35 depends on ALTERA_PR_IP_CORE && OF && HAS_IOMEM
42 depends on SPI
50 depends on PCI
52 FPGA manager driver support for Arria-V, Cyclone-V, Stratix-V,
57 depends on ARCH_ZYNQ || COMPILE_TEST
63 depends on (ARCH_STRATIX10 && INTEL_STRATIX10_SERVICE)
69 depends on SPI
[all …]
|
| /kernel/linux/linux-5.10/drivers/devfreq/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 A device may have a list of frequencies and voltages available.
8 devfreq, a generic DVFS framework can be registered for a device
10 operating frequency based on the device driver's policy.
12 Each device may have its own governor and policy. Devfreq can
13 reevaluate the device state periodically and/or based on the
16 Like some CPUs with CPUfreq, a device may have multiple clocks.
17 However, because the clock frequencies of a single device are
18 determined by the single device's state, an instance of devfreq
19 is attached to a single device and returns a "representative"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Sub-device Interface
13 components as software blocks called sub-devices.
15 V4L2 sub-devices are usually kernel-only objects. If the V4L2 driver
16 implements the media device API, they will automatically inherit from
17 media entities. Applications will be able to enumerate the sub-devices
21 In addition to make sub-devices discoverable, drivers can also choose to
23 sub-device driver and the V4L2 device driver support this, sub-devices
24 will feature a character device node on which ioctls can be called to
26 - query, read and write sub-devices controls
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Network device configuration
8 depends on NET
9 bool "Network device support"
25 # All the following symbols are dependent on NETDEVICES - do not repeat
43 depends on INET
44 depends on IPV6 || IPV6=n
62 This is essentially a bit-bucket device (i.e. traffic you send to
63 this device is consigned into oblivion) with a configurable IP
76 depends on NET && INET
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/stmicro/stmmac/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "STMicroelectronics Multi-Gigabit Ethernet driver"
4 depends on HAS_IOMEM && HAS_DMA
20 depends on INET
21 depends on STMMAC_ETH
30 depends on STMMAC_ETH
35 This is the driver used on several SoCs:
45 tristate "Support for snps,dwc-qos-ethernet.txt DT binding."
48 depends on OF && HAS_DMA
50 Support for chips using the snps,dwc-qos-ethernet.txt DT binding.
[all …]
|
| /kernel/linux/linux-5.10/drivers/thermal/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
22 depends on NET
26 trip point crossed, cooling device update or governor
37 int "Emergency poweroff delay in milli-seconds"
47 time for orderly_poweroff() to finish on regular execution.
54 prompt "Expose thermal sensors as hwmon device"
55 depends on HWMON=y || HWMON=THERMAL
68 prompt "APIs to parse thermal data out of device tree"
69 depends on OF
74 device tree blob.
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_mipi_dsi.c | 4 * Copyright (C) 2012-2013, Samsung Electronics, Co., Ltd.
21 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
30 #include <linux/device.h>
50 static int mipi_dsi_device_match(struct device *dev, struct device_driver *drv) in mipi_dsi_device_match()
58 /* compare DSI device and driver names */ in mipi_dsi_device_match()
59 if (!strcmp(dsi->name, drv->name)) in mipi_dsi_device_match()
65 static int mipi_dsi_uevent(struct device *dev, struct kobj_uevent_env *env) in mipi_dsi_uevent()
71 if (err != -ENODEV) in mipi_dsi_uevent()
75 dsi->name); in mipi_dsi_uevent()
92 .name = "mipi-dsi",
[all …]
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | instantiating-devices.rst | 6 level. Instead, the software must know which devices are connected on each
9 several ways to achieve this, depending on the context and requirements.
13 --------------------------------------------
16 for many embedded systems. On such systems, each I2C bus has a number which
17 is known in advance. It is thus possible to pre-declare the I2C devices
18 which live on this bus.
20 This information is provided to the kernel in a different way on different
21 architectures: device tree, ACPI or board files.
24 instantiated automatically by i2c-core. The devices will be automatically
25 unbound and destroyed when the I2C bus they sit on goes away (if ever).
[all …]
|
| /kernel/linux/linux-5.10/drivers/extcon/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
9 cables attached. For example, an external connector of a device
11 host USB ports. Many of 30-pin connectors including PDMI are
16 comment "Extcon Device Drivers"
20 depends on IIO
22 Say Y here to enable extcon device driver based on ADC values.
26 depends on MFD_ARIZONA && INPUT && SND_SOC
33 tristate "X-Power AXP288 EXTCON support"
34 depends on MFD_AXP20X && USB_SUPPORT && X86 && ACPI
38 and USB MUX switching by X-Power AXP288 PMIC.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | amd-iommu.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (C) 2007-2010 Advanced Micro Devices, Inc.
14 * This is mainly used to communicate information back-and-forth
36 * amd_iommu_enable_device_erratum() - Enable erratum workaround for device
38 * @pdev: The PCI device the workaround is necessary for
43 * - AMD_PRI_DEV_ERRATUM_ENABLE_RESET - Reset PRI capability when PRI
45 * - AMD_PRI_DEV_ERRATUM_LIMIT_REQ_ONE - Limit number of outstanding PRI
54 * amd_iommu_init_device() - Init device for use with IOMMUv2 driver
55 * @pdev: The PCI device to initialize
56 * @pasids: Number of PASIDs to support for this device
[all …]
|
12345678910>>...47