Searched +full:controller +full:- +full:specific (Results 1 – 25 of 1102) sorted by relevance
12345678910>>...45
| /Linux-v5.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 …]
|
| /Linux-v5.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 …]
|
| D | ufs-qcom.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2013-2015, The Linux Foundation. All rights reserved.
8 #include <linux/reset-controller.h>
26 /* vendor specific pre-defined parameters */
43 /* QCOM UFS host controller vendor specific registers */
62 * QCOM UFS host controller vendor specific registers
68 /* QCOM UFS host controller vendor specific debug registers */
135 /* QUniPro Vendor specific attributes */
171 * Make sure de-assertion of ufs phy reset is written to in ufs_qcom_deassert_reset()
177 /* Host controller hardware version: major.minor.step */
[all …]
|
| /Linux-v5.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 …]
|
| D | k3-dw-mshc.txt | 1 * Hisilicon specific extensions to the Synopsys Designware Mobile
2 Storage Host Controller
4 Read synopsys-dw-mshc.txt for more details
6 The Synopsys designware mobile storage host controller is used to interface
8 differences between the core Synopsys dw mshc controller properties described
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
10 extensions to the Synopsys Designware Mobile Storage Host Controller.
15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
16 - "hisilicon,hi3670-dw-mshc", "hisilicon,hi3660-dw-mshc": for controllers
17 with hi3670 specific extensions.
[all …]
|
| D | bluefield-dw-mshc.txt | 1 * Mellanox Bluefield SoC specific extensions to the Synopsys Designware
2 Mobile Storage Host Controller
4 Read synopsys-dw-mshc.txt for more details
6 The Synopsys designware mobile storage host controller is used to interface
8 differences between the core Synopsys dw mshc controller properties described
9 by synopsys-dw-mshc.txt and the properties used by the Mellanox Bluefield SoC
10 specific extensions to the Synopsys Designware Mobile Storage Host Controller.
15 - "mellanox,bluefield-dw-mshc": for controllers with Mellanox Bluefield SoC
16 specific extensions.
22 compatible = "mellanox,bluefield-dw-mshc";
[all …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.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 …]
|
| D | building.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 distribution-specific source file or via the Kernel's main git tree\ [1]_.
12 - you're a braveheart and want to experiment with new stuff;
13 - if you want to report a bug;
14 - if you're developing new patches
23 https://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
50 Device Drivers --->
51 <M> Remote Controller support --->
54 [*] HDMI CEC drivers --->
55 <*> Multimedia support --->
[all …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.10/arch/x86/include/asm/ |
| D | x86_init.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
16 * struct x86_init_mpparse - platform specific mpparse ops
17 * @setup_ioapic_ids: platform specific ioapic id override
28 * struct x86_init_resources - platform specific resource related ops
32 * @memory_setup: platform specific memory setup
42 * struct x86_init_irqs - platform specific interrupt setup
59 * struct x86_init_oem - oem platform specific customizing functions
60 * @arch_setup: platform specific architecture setup
61 * @banner: print a platform specific banner
69 * struct x86_init_paging - platform specific paging functions
[all …]
|
| /Linux-v5.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 …]
|
| /Linux-v5.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 …]
|
| D | brcm,bcm-keypad.txt | 1 * Broadcom Keypad Controller device tree bindings
3 Broadcom 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 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
14 Required SoC Specific Properties:
15 - compatible: should be "brcm,bcm-keypad"
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
[all …]
|
| /Linux-v5.10/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| D | arcx,anybus-controller.txt | 1 * Arcx Anybus-S controller
8 --------------------
10 - compatible : The following chip-specific string:
11 "arcx,anybus-controller"
13 - reg : three areas:
15 index 1: bus memory area of the first host's dual-port ram.
16 index 2: bus memory area of the second host's dual-port ram.
18 - reset-gpios : the GPIO pin connected to the reset line of the controller.
20 - interrupts : two interrupts:
24 interrupt-controller/interrupts.txt
[all …]
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 12 use Universal Host Controller Interface (UHCI) or Open Host Controller
15 Instead, these embedded UDC rely on the USB On-the-Go (OTG)
18 Dual-Role Controller (MUSB HDRC) found in the Mentor Graphics Inventra™
21 As a self-taught exercise I have written an MUSB glue layer for the
28 .. _musb-basics:
33 To get started on the topic, please read USB On-the-Go Basics (see
37 albeit focused on some specific devices provided by these companies.
42 Linux USB stack is a layered architecture in which the MUSB controller
43 hardware sits at the lowest. The MUSB controller driver abstract the
44 MUSB controller hardware to the Linux USB stack::
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 55 Flash faults are re-read after strobing the flash. Possible
58 * led-over-voltage
59 flash controller voltage to the flash LED
60 has exceeded the limit specific to the flash controller
61 * flash-timeout-exceeded
65 * controller-over-temperature
66 the flash controller has
68 * controller-short-circuit
70 of the flash controller has been triggered
71 * led-power-supply-over-current
[all …]
|
| /Linux-v5.10/drivers/nvme/host/ |
| D | fabrics.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
4 * Copyright (c) 2015-2016 HGST, a Western Digital Company.
35 * enum nvmf_parsing_opts - used to define the sysfs parsing options used.
62 * struct nvmf_ctrl_options - Used to hold the options specified
65 * on adding a NVMe controller.
67 * better description) that will be used by an NVMe controller
71 * @traddr: The transport-specific TRADDR field for a port on the
72 * subsystem which is adding a controller.
73 * @trsvcid: The transport-specific TRSVCID field for a port on the
74 * subsystem which is adding a controller.
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | syscon.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: System Controller Registers R/W Device Tree Bindings
10 System controller node represents a register region containing a set
12 represent as any specific type of device. The typical use-case is
13 for some other node's driver, or platform-specific code, to acquire
15 search using a specific compatible value), interrogate the node (or
20 - Lee Jones <lee.jones@linaro.org>
27 - syscon
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/can/ |
| D | rcar_canfd.txt | 1 Renesas R-Car CAN FD controller Device Tree Bindings
2 ----------------------------------------------------
5 - compatible: Must contain one or more of the following:
6 - "renesas,rcar-gen3-canfd" for R-Car Gen3 and RZ/G2 compatible controllers.
7 - "renesas,r8a774a1-canfd" for R8A774A1 (RZ/G2M) compatible controller.
8 - "renesas,r8a774b1-canfd" for R8A774B1 (RZ/G2N) compatible controller.
9 - "renesas,r8a774c0-canfd" for R8A774C0 (RZ/G2E) compatible controller.
10 - "renesas,r8a774e1-canfd" for R8A774E1 (RZ/G2H) compatible controller.
11 - "renesas,r8a7795-canfd" for R8A7795 (R-Car H3) compatible controller.
12 - "renesas,r8a7796-canfd" for R8A7796 (R-Car M3-W) compatible controller.
[all …]
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/hisilicon/ |
| D | dw-dsi.txt | 1 Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver
3 A DSI Host Controller resides in the middle of display controller and external
7 - compatible: value should be "hisilicon,hi6220-dsi".
8 - reg: physical base address and length of dsi controller's registers.
9 - clocks: contains APB clock phandle + clock-specifier pair.
10 - clock-names: should be "pclk".
11 - ports: contains DSI controller input and output sub port.
17 A example of HiKey board hi6220 SoC and board specific DT entry:
20 SoC specific:
22 compatible = "hisilicon,hi6220-dsi";
[all …]
|
12345678910>>...45
