Searched +full:on +full:- +full:device (Results 1 – 25 of 1169) sorted by relevance
12345678910>>...47
| /Linux-v6.1/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_INTEL_SOCFPGA && SPI_MASTER=y && OF
35 depends on ARCH_INTEL_SOCFPGA && 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 …]
|
| /Linux-v6.1/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
45 depends on I2C
46 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
47 depends on X86_INTEL_LPSS || COMPILE_TEST
50 This adds support for the Lynxpoint Audio DSP on Intel(R) Haswell
52 Say Y or m if you have such a device.
61 depends on I2C
62 depends on I2C_DESIGNWARE_PLATFORM || COMPILE_TEST
63 depends on X86_INTEL_LPSS || COMPILE_TEST
[all …]
|
| /Linux-v6.1/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.
21 logical block device. This can be used to simply append one
23 into a RAID1/4/5 device so as to provide protection against hard
29 More information about Software RAID on Linux is contained in the
30 Software RAID mini-HOWTO, available from
38 depends on BLK_DEV_MD=y
45 a several-second delay in the boot time due to various
[all …]
|
| /Linux-v6.1/include/linux/usb/ |
| 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-v6.1/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 …]
|
| /Linux-v6.1/drivers/platform/surface/ |
| 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-v6.1/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 …]
|
| /Linux-v6.1/sound/soc/mediatek/ |
| 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-v6.1/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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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 It's possible to mount a rootfs using the MTD device on the "root="
[all …]
|
| /Linux-v6.1/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 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-v6.1/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
23 depends on ARCH_MAY_HAVE_PC_FDC
28 <file:Documentation/admin-guide/blockdev/floppy.rst>.
38 depends on BLK_DEV_FD
41 special low-level hardware accesses to them (access and use
42 non-standard formats, for example), then enable this.
54 depends on AMIGA
[all …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/include/linux/surface_aggregator/ |
| 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-v6.1/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 …]
|
| /Linux-v6.1/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
28 #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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/drivers/virtio/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 Modern PCI device implementation. This module implements the
17 basic probe and control for devices which are based on modern
18 PCI device with possible vendor specific extensions. Any
19 module that selects this module must depend on PCI.
24 Legacy PCI device (Virtio PCI Card 0.9.x Draft and older device)
27 which are based on legacy PCI device. Any module that selects this
28 module must depend on PCI.
38 depends on BROKEN
40 Enable this to harden the device notifications and suppress
[all …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/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
45 depends on TLS || TLS_DEVICE=n
63 This is essentially a bit-bucket device (i.e. traffic you send to
64 this device is consigned into oblivion) with a configurable IP
[all …]
|
| /Linux-v6.1/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.
25 tristate "X-Power AXP288 EXTCON support"
26 depends on MFD_AXP20X && USB_SUPPORT && X86 && ACPI && IOSF_MBI
30 and USB MUX switching by X-Power AXP288 PMIC.
34 depends on INPUT && I2C
[all …]
|
| /Linux-v6.1/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 …]
|
12345678910>>...47
