Searched +full:on +full:- +full:device (Results 1 – 25 of 1095) sorted by relevance
12345678910>>...44
| /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-4.19/drivers/mfd/ |
| D | Kconfig | 6 menu "Multifunction device drivers"
16 depends on PCI && (X86_32 || (X86 && COMPILE_TEST))
17 ---help---
23 depends on ARCH_SOCFPGA && SPI_MASTER=y && OF
33 tristate "Active-semi ACT8945A"
36 depends on I2C && OF
38 Support for the ACT8945A PMIC from Active-semi. This device
39 features three step-down DC/DC converters and four low-dropout
48 depends on ARCH_SUNXI || COMPILE_TEST
49 depends on !TOUCHSCREEN_SUN4I
[all …]
|
| /kernel/linux/linux-4.19/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/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-4.19/arch/arm/plat-samsung/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 depends on PLAT_S3C24XX || ARCH_S3C64XX || ARCH_EXYNOS || ARCH_S5PV210
16 depends on PM && (PLAT_S3C24XX || ARCH_S3C64XX)
29 int "S3C UART to use for low-level messages"
30 depends on ARCH_S3C64XX
33 Choice of which UART port to use for the low-level messages,
36 must have been initialised by the boot-loader before use.
40 depends on ATAGS
70 depends on !ARCH_MULTIPLATFORM
76 # device definitions to compile in
[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-4.19/drivers/mtd/maps/ |
| D | Kconfig | 2 depends on MTD!=n
3 depends on HAS_IOMEM
6 bool "Support non-linear mappings of flash chips"
12 tristate "Flash device in physical memory map"
13 depends on MTD_CFI || MTD_JEDECPROBE || MTD_ROM || MTD_LPDDR
18 the physical address and size of the flash chips on your
20 with config options or at run-time.
27 depends on MTD_PHYSMAP
38 depends on MTD_PHYSMAP_COMPAT
42 are mapped on your particular target board. Refer to the
[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/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-4.19/Documentation/driver-api/ |
| D | device_link.rst | 5 Device links
9 that are borne out of a parent/child relationship within the device
11 are ordered based on this relationship, i.e. children are always suspended
14 Sometimes there is a need to represent device dependencies beyond the
19 dependencies, i.e. that one device must be bound to a driver before
22 Often these two dependency types come together, so a device depends on
26 Device links allow representation of such dependencies in the driver core.
28 In its standard or *managed* form, a device link combines *both* dependency
30 "supplier" device and its "consumer" devices, and it guarantees driver
31 presence on the supplier. The consumer devices are not probed before the
[all …]
|
| /kernel/linux/linux-4.19/drivers/mtd/devices/ |
| D | Kconfig | 1 menu "Self-contained MTD device drivers"
2 depends on MTD!=n
3 depends on HAS_IOMEM
7 depends on PCI
9 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
11 These devices come in memory configurations from 32M - 1G. If you
17 will use a 1G memory map as its view of the device. As a module,
20 particularly useful on the 2.2 kernels on PPC architectures as there
25 depends on MTD_PMC551
33 depends on MTD_PMC551
[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-4.19/drivers/block/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # Block device driver configuration
8 depends on BLOCK
10 ---help---
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
30 ---help---
44 depends on AMIGA
48 depends on ATARI
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/gadget/udc/ |
| D | Kconfig | 2 # USB Gadget support on a system involves
6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
8 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
9 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
10 # - Some systems have both kinds of controllers.
12 # With help from a special transceiver and a "Mini-AB" jack, systems with
13 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
21 # - integrated/SOC controllers first
22 # - licensed IP used in both SOC and discrete versions
23 # - discrete ones (including all PCI-only controllers)
[all …]
|
| /kernel/linux/linux-4.19/drivers/md/ |
| D | Kconfig | 2 # Block device driver configuration
7 depends on BLOCK
10 Support multiple physical spindles through a single logical device.
17 ---help---
19 logical block device. This can be used to simply append one
21 into a RAID1/4/5 device so as to provide protection against hard
27 More information about Software RAID on Linux is contained in the
28 Software RAID mini-HOWTO, available from
36 depends on BLK_DEV_MD=y
38 ---help---
[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-4.19/drivers/mtd/ |
| D | Kconfig | 2 tristate "Memory Technology Device (MTD) support"
5 used for solid state file systems on embedded devices. This option
8 to enumerate the devices which are present and obtain a handle on
16 depends on m
22 WARNING: some of the tests will ERASE entire MTD device which they
30 blocks on the device, similar to a partition table, which gives
39 for your particular device. It won't happen automatically. The
47 default "-1"
56 sectors before the end of the device.
58 For example "2" means block number 2, "-1" means the last
[all …]
|
| /kernel/linux/linux-4.19/Documentation/hid/ |
| D | hid-transport.txt | 7 Bluetooth, I2C and user-space I/O drivers.
13 devices and register them with the HID bus. HID core then loads generic device
14 drivers on top of it. The transport drivers are responsible of raw data
15 transport and device setup/management. HID core is responsible of
16 report-parsing, report interpretation and the user-space API. Device specifics
17 and quirks are handled by all layers depending on the quirk.
19 +-----------+ +-----------+ +-----------+ +-----------+
20 | Device #1 | | Device #i | | Device #j | | Device #k |
21 +-----------+ +-----------+ +-----------+ +-----------+
23 +------------+ +------------+
[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-4.19/drivers/net/ |
| D | Kconfig | 2 # Network device configuration
7 depends on NET
8 bool "Network device support"
9 ---help---
24 # All the following symbols are dependent on NETDEVICES - do not repeat
34 ---help---
42 depends on INET
43 depends on IPV6 || IPV6=n
44 ---help---
60 ---help---
[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 …]
|
12345678910>>...44