Searched +full:controller +full:- +full:specific (Results 1 – 25 of 1140) sorted by relevance
12345678910>>...46
| /kernel/linux/linux-5.10/drivers/pci/controller/dwc/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
23 bool "TI DRA7xx PCIe controller Host Mode"
31 Enables support for the PCIe controller in the DRA7xx SoC to work in
32 host mode. There are two instances of PCIe controller in DRA7xx.
33 This controller can work either as EP or RC. In order to enable
34 host-specific features PCI_DRA7XX_HOST must be selected and in order
35 to enable device-specific features PCI_DRA7XX_EP must be selected.
39 bool "TI DRA7xx PCIe controller Endpoint Mode"
46 Enables support for the PCIe controller in the DRA7xx SoC to work in
47 endpoint mode. There are two instances of PCIe controller in DRA7xx.
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/ufs/ |
| D | Kconfig | 2 # Kernel configuration file for the UFS Host Controller
5 # Copyright (C) 2011-2013 Samsung India Software Operations
15 # See the COPYING file in the top-level directory or visit
16 # <http://www.gnu.org/licenses/gpl-2.0.html>
36 tristate "Universal Flash Storage Controller Driver Core"
45 called UFS Host Controller), because you will be asked for it.
54 tristate "PCI bus based UFS Controller support"
57 This selects the PCI UFS Host Controller Interface. Select this if
58 you have UFS Host Controller with PCI Interface.
60 If you have a controller with this interface, say Y or M here.
[all …]
|
| /kernel/linux/linux-4.19/drivers/pci/controller/dwc/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
23 bool "TI DRA7xx PCIe controller Host Mode"
31 Enables support for the PCIe controller in the DRA7xx SoC to work in
32 host mode. There are two instances of PCIe controller in DRA7xx.
33 This controller can work either as EP or RC. In order to enable
34 host-specific features PCI_DRA7XX_HOST must be selected and in order
35 to enable device-specific features PCI_DRA7XX_EP must be selected.
39 bool "TI DRA7xx PCIe controller Endpoint Mode"
46 Enables support for the PCIe controller in the DRA7xx SoC to work in
47 endpoint mode. There are two instances of PCIe controller in DRA7xx.
[all …]
|
| /kernel/linux/linux-4.19/drivers/scsi/ufs/ |
| D | Kconfig | 2 # Kernel configuration file for the UFS Host Controller
5 # Copyright (C) 2011-2013 Samsung India Software Operations
15 # See the COPYING file in the top-level directory or visit
16 # <http://www.gnu.org/licenses/gpl-2.0.html>
36 tristate "Universal Flash Storage Controller Driver Core"
41 ---help---
45 called UFS Host Controller), because you will be asked for it.
54 tristate "PCI bus based UFS Controller support"
56 ---help---
57 This selects the PCI UFS Host Controller Interface. Select this if
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mmc/ |
| D | samsung-sdhci.txt | 1 * Samsung's SDHCI Controller device tree bindings
3 Samsung's SDHCI controller is used as a connectivity interface with external
6 Samsung implementation of the SDHCI controller.
8 Required SoC Specific Properties:
9 - compatible: should be one of the following
10 - "samsung,s3c6410-sdhci": For controllers compatible with s3c6410 sdhci
11 controller.
12 - "samsung,exynos4210-sdhci": For controllers compatible with Exynos4 sdhci
13 controller.
15 Required Board Specific Properties:
[all …]
|
| D | exynos-dw-mshc.txt | 1 * Samsung Exynos specific extensions to the Synopsys Designware Mobile
2 Storage Host Controller
4 The Synopsys designware mobile storage host controller is used to interface
6 differences between the core Synopsys dw mshc controller properties described
7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
8 extensions to the Synopsys Designware Mobile Storage Host Controller.
13 - "samsung,exynos4210-dw-mshc": for controllers with Samsung Exynos4210
14 specific extensions.
15 - "samsung,exynos4412-dw-mshc": for controllers with Samsung Exynos4412
16 specific extensions.
[all …]
|
| D | synopsys-dw-mshc.txt | 1 * Synopsys Designware Mobile Storage Host Controller
3 The Synopsys designware mobile storage host controller is used to interface
6 properties used by the Synopsys Designware Mobile Storage Host Controller.
11 - snps,dw-mshc: for controllers compliant with synopsys dw-mshc.
12 * #address-cells: should be 1.
13 * #size-cells: should be 0.
15 # Slots (DEPRECATED): The slot specific information are contained within
16 child-nodes with each child-node representing a supported slot. There should
19 of the slot connected to the controller. The following are optional properties
23 property is 0 to (num-slots -1), where num-slots is the value
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | samsung-sdhci.txt | 1 * Samsung's SDHCI Controller device tree bindings
3 Samsung's SDHCI controller is used as a connectivity interface with external
6 Samsung implementation of the SDHCI controller.
8 Required SoC Specific Properties:
9 - compatible: should be one of the following
10 - "samsung,s3c6410-sdhci": For controllers compatible with s3c6410 sdhci
11 controller.
12 - "samsung,exynos4210-sdhci": For controllers compatible with Exynos4 sdhci
13 controller.
15 Required Board Specific Properties:
[all …]
|
| D | exynos-dw-mshc.txt | 1 * Samsung Exynos specific extensions to the Synopsys Designware Mobile
2 Storage Host Controller
4 The Synopsys designware mobile storage host controller is used to interface
6 differences between the core Synopsys dw mshc controller properties described
7 by synopsys-dw-mshc.txt and the properties used by the Samsung Exynos specific
8 extensions to the Synopsys Designware Mobile Storage Host Controller.
13 - "samsung,exynos4210-dw-mshc": for controllers with Samsung Exynos4210
14 specific extensions.
15 - "samsung,exynos4412-dw-mshc": for controllers with Samsung Exynos4412
16 specific extensions.
[all …]
|
| /kernel/linux/linux-5.10/drivers/pinctrl/samsung/ |
| D | pinctrl-samsung.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * pin-controller/pin-mux/pin-config/gpio-driver for Samsung's SoC's.
25 * enum pincfg_type - possible pin configuration types supported.
46 * packed together into a 16-bits. The upper 8-bits represent the configuration
47 * type and the lower 8-bits hold the value of the configuration type.
57 * enum eint_type - possible external interrupt types.
63 * Samsung GPIO controller groups all the available pins into banks. The pins
77 /* maximum length of a pin in pin descriptor (example: "gpa0-0") */
108 * struct samsung_pin_bank_data: represent a controller pin-bank (init data).
110 * @pctl_offset: starting offset of the pin-bank registers.
[all …]
|
| /kernel/linux/linux-4.19/drivers/pinctrl/samsung/ |
| D | pinctrl-samsung.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * pin-controller/pin-mux/pin-config/gpio-driver for Samsung's SoC's.
25 * enum pincfg_type - possible pin configuration types supported.
46 * packed together into a 16-bits. The upper 8-bits represent the configuration
47 * type and the lower 8-bits hold the value of the configuration type.
57 * enum eint_type - possible external interrupt types.
63 * Samsung GPIO controller groups all the available pins into banks. The pins
77 /* maximum length of a pin in pin descriptor (example: "gpa0-0") */
108 * struct samsung_pin_bank_data: represent a controller pin-bank (init data).
110 * @pctl_offset: starting offset of the pin-bank registers.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/spi/ |
| D | spi-samsung.txt | 1 * Samsung SPI Controller
3 The Samsung SPI controller is used to interface with various devices such as flash
6 Required SoC Specific Properties:
8 - compatible: should be one of the following.
9 - samsung,s3c2443-spi: for s3c2443, s3c2416 and s3c2450 platforms
10 - samsung,s3c6410-spi: for s3c6410 platforms
11 - samsung,s5pv210-spi: for s5pv210 and s5pc110 platforms
12 - samsung,exynos5433-spi: for exynos5433 compatible controllers
13 - samsung,exynos7-spi: for exynos7 platforms <DEPRECATED>
15 - reg: physical base address of the controller and length of memory mapped
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| D | spi-samsung.txt | 1 * Samsung SPI Controller
3 The Samsung SPI controller is used to interface with various devices such as flash
6 Required SoC Specific Properties:
8 - compatible: should be one of the following.
9 - samsung,s3c2443-spi: for s3c2443, s3c2416 and s3c2450 platforms
10 - samsung,s3c6410-spi: for s3c6410 platforms
11 - samsung,s5pv210-spi: for s5pv210 and s5pc110 platforms
12 - samsung,exynos5433-spi: for exynos5433 compatible controllers
13 - samsung,exynos7-spi: for exynos7 platforms <DEPRECATED>
15 - reg: physical base address of the controller and length of memory mapped
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/dma/ |
| D | dma.txt | 1 * Generic DMA Controller and DMA request bindings
5 controller.
8 * DMA controller
11 - #dma-cells: Must be at least 1. Used to provide DMA controller
12 specific information. See DMA client binding below for
16 - dma-channels: Number of DMA channels supported by the controller.
17 - dma-requests: Number of DMA request signals supported by the
18 controller.
23 compatible = "ti,omap-sdma";
29 #dma-cells = <1>;
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/v4l-drivers/ |
| D | davinci-vpbe.rst | 5 -----------------
11 VPBE display controller
26 -----------------------
35 2. Display controller
41 controller port is done at init time based on default output and standard
45 When connected to an external encoder, vpbe controller is also responsible
47 board specific settings (specified in board-xxx-evm.c). This allows
50 API to set timings in VENC for a specific display resolution. As of this
56 setting timings at LCD controller port when external encoders are connected
58 is connected, the timings for a specific standard/preset is retrieved from
[all …]
|
| /kernel/linux/linux-4.19/drivers/mmc/host/ |
| D | Kconfig | 2 # MMC/SD host controller drivers
5 comment "MMC/SD/SDIO Host Controller Drivers"
27 bool "Qualcomm Data Mover for SD Card Controller"
31 This selects the Qualcomm Data Mover lite/local on SD Card controller.
48 tristate "Secure Digital Host Controller Interface support"
51 This selects the generic Secure Digital Host Controller Interface.
55 If you have a controller with this interface, say Y or M here. You
73 and performing I/O to a SDHCI controller through a bus that
74 implements a hardware byte swapper using a 32-bit datum.
86 This selects the PCI Secure Digital Host Controller Interface.
[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"
34 This selects the platform specific bus support for the stmmac driver.
38 If you have a controller with this interface, say Y or M here.
45 tristate "Support for snps,dwc-qos-ethernet.txt DT binding."
50 Support for chips using the snps,dwc-qos-ethernet.txt DT binding.
57 platform specific code to function or is using platform
65 Support for Adaptrum Anarion GMAC Ethernet controller.
80 will behave like standard non-accelerated ethernet interfaces.
94 Support for MediaTek GMAC Ethernet controller.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -----------------------
16 2. Display controller
23 controller port is done at init time based on default output and standard
27 When connected to an external encoder, vpbe controller is also responsible
29 board specific settings (specified in board-xxx-evm.c). This allows
32 API to set timings in VENC for a specific display resolution. As of this
39 setting timings at LCD controller port when external encoders are connected
41 is connected, the timings for a specific standard/preset is retrieved from
42 the board specific table and the values are used to set the timings in
[all …]
|
| /kernel/linux/linux-4.19/arch/x86/include/asm/ |
| D | x86_init.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
13 * struct x86_init_mpparse - platform specific mpparse ops
14 * @mpc_record: platform specific mpc record accounting
15 * @setup_ioapic_ids: platform specific ioapic id override
16 * @mpc_apic_id: platform specific mpc apic id assignment
17 * @smp_read_mpc_oem: platform specific oem mpc table setup
18 * @mpc_oem_pci_bus: platform specific pci bus setup (default NULL)
19 * @mpc_oem_bus_info: platform specific mpc bus info
35 * struct x86_init_resources - platform specific resource related ops
39 * @memory_setup: platform specific memory setup
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic.txt | 2 Freescale MPIC Interrupt Controller Node
6 The Freescale MPIC interrupt controller is found on all PowerQUICC
14 - compatible
22 - reg
24 Value type: <prop-encoded-array>
29 - interrupt-controller
33 controller
35 - #interrupt-cells
39 specifiers do not contain the interrupt-type or type-specific
42 - #address-cells
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic.txt | 2 Freescale MPIC Interrupt Controller Node
6 The Freescale MPIC interrupt controller is found on all PowerQUICC
14 - compatible
22 - reg
24 Value type: <prop-encoded-array>
29 - interrupt-controller
33 controller
35 - #interrupt-cells
39 specifiers do not contain the interrupt-type or type-specific
42 - #address-cells
[all …]
|
| /kernel/linux/linux-5.10/drivers/mmc/host/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # MMC/SD host controller drivers
6 comment "MMC/SD/SDIO Host Controller Drivers"
28 bool "Qualcomm Data Mover for SD Card Controller"
32 This selects the Qualcomm Data Mover lite/local on SD Card controller.
39 bool "STMicroelectronics STM32 SDMMC Controller"
43 This selects the STMicroelectronics STM32 SDMMC host controller.
59 tristate "Secure Digital Host Controller Interface support"
62 This selects the generic Secure Digital Host Controller Interface.
66 If you have a controller with this interface, say Y or M here. You
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-mt8183.txt | 1 * Mediatek MT8183 Pin Controller
3 The Mediatek's Pin controller is used to control SoC pins.
6 - compatible: value should be one of the following.
7 "mediatek,mt8183-pinctrl", compatible with mt8183 pinctrl.
8 - gpio-controller : Marks the device node as a gpio controller.
9 - #gpio-cells: number of cells in GPIO specifier. Since the generic GPIO
12 - gpio-ranges : gpio valid number range.
13 - reg: physical address base for gpio base registers. There are 10 GPIO
17 - reg-names: gpio base register names. There are 10 gpio base register
20 - interrupt-controller: Marks the device node as an interrupt controller
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/ |
| D | samsung-keypad.txt | 1 * Samsung's Keypad Controller device tree bindings
3 Samsung's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 Required SoC Specific Properties:
10 - compatible: should be one of the following
11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
12 controller.
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
14 controller.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/input/ |
| D | samsung-keypad.txt | 1 * Samsung's Keypad Controller device tree bindings
3 Samsung's Keypad controller is used to interface a SoC with a matrix-type
4 keypad device. The keypad controller supports multiple row and column lines.
6 The keypad controller can sense a key-press and key-release and report the
9 Required SoC Specific Properties:
10 - compatible: should be one of the following
11 - "samsung,s3c6410-keypad": For controllers compatible with s3c6410 keypad
12 controller.
13 - "samsung,s5pv210-keypad": For controllers compatible with s5pv210 keypad
14 controller.
[all …]
|
12345678910>>...46