Searched +full:system +full:- +full:controller (Results 1 – 25 of 1107) sorted by relevance
12345678910>>...45
| /kernel/linux/linux-4.19/drivers/eisa/ |
| D | eisa.ids | 6 # Marc Zyngier <maz@wild-wind.fr.eu.org>
10 ABP0510 "Advansys ABP-510 ISA SCSI Host Adapter"
11 ABP0540 "Advansys ABP-540/542 ISA SCSI Host Adapter"
12 ABP7401 "AdvanSys ABP-740/742 EISA Single Channel SCSI Host Adapter"
13 ABP7501 "AdvanSys ABP-750/752 EISA Dual Channel SCSI Host Adapter"
14 ACC1200 "ACCTON EtherCombo-32 Ethernet Adapter"
15 ACC120A "ACCTON EtherCombo-32 Ethernet Adapter"
18 ACE1010 "ACME Super Fast System Board"
22 ACE4010 "ACME Tape Controller"
24 ACE6010 "ACME Disk Controller"
[all …]
|
| /kernel/linux/linux-5.10/drivers/eisa/ |
| D | eisa.ids | 6 # Marc Zyngier <maz@wild-wind.fr.eu.org>
10 ABP0510 "Advansys ABP-510 ISA SCSI Host Adapter"
11 ABP0540 "Advansys ABP-540/542 ISA SCSI Host Adapter"
12 ABP7401 "AdvanSys ABP-740/742 EISA Single Channel SCSI Host Adapter"
13 ABP7501 "AdvanSys ABP-750/752 EISA Dual Channel SCSI Host Adapter"
14 ACC1200 "ACCTON EtherCombo-32 Ethernet Adapter"
15 ACC120A "ACCTON EtherCombo-32 Ethernet Adapter"
18 ACE1010 "ACME Super Fast System Board"
22 ACE4010 "ACME Tape Controller"
24 ACE6010 "ACME Disk Controller"
[all …]
|
| /kernel/linux/linux-4.19/drivers/soc/renesas/ |
| D | Kconfig | 29 bool "RZ/G1M System Controller support" if COMPILE_TEST
33 bool "RZ/G1E System Controller support" if COMPILE_TEST
37 bool "RZ/G1C System Controller support" if COMPILE_TEST
41 bool "R-Car H1 System Controller support" if COMPILE_TEST
45 bool "R-Car H2 System Controller support" if COMPILE_TEST
49 bool "R-Car M2-W/N System Controller support" if COMPILE_TEST
53 bool "R-Car V2H System Controller support" if COMPILE_TEST
57 bool "R-Car E2 System Controller support" if COMPILE_TEST
61 bool "R-Car H3 System Controller support" if COMPILE_TEST
65 bool "R-Car M3-W System Controller support" if COMPILE_TEST
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| D | sysctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/hisilicon/controller/sysctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Hisilicon system controller
10 - Wei Xu <xuwei5@hisilicon.com>
13 The Hisilicon system controller is used on many Hisilicon boards, it can be
14 used to assist the slave core startup, reboot the system, etc.
16 There are some variants of the Hisilicon system controller, such as HiP01,
17 Hi3519, Hi6220 system controller, each of them is mostly compatible with the
[all …]
|
| /kernel/linux/linux-5.10/drivers/soc/renesas/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
49 #comment "Renesas ARM SoCs System Type"
57 bool "ARM32 Platform support for R-Car E2"
63 bool "ARM32 Platform support for R-Car H1"
72 bool "ARM32 Platform support for R-Car H2"
80 bool "ARM32 Platform support for R-Car M1A"
85 bool "ARM32 Platform support for R-Car M2-N"
92 bool "ARM32 Platform support for R-Car M2-W"
99 bool "ARM32 Platform support for R-Car V2H"
105 bool "ARM32 Platform support for R-Mobile A1"
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/hisilicon/ |
| D | hisilicon.txt | 2 ----------------------------------------------------
5 - compatible = "hisilicon,hi3660";
9 - compatible = "hisilicon,hi3660-hikey960", "hisilicon,hi3660";
13 - compatible = "hisilicon,hi3798cv200";
17 - compatible = "hisilicon,hi3798cv200-poplar", "hisilicon,hi3798cv200";
21 - compatible = "hisilicon,hi3620-hi4511";
25 - compatible = "hisilicon,hi6220";
29 - compatible = "hisilicon,hi6220-hikey", "hisilicon,hi6220";
33 - compatible = "hisilicon,hip01-ca9x2";
37 - compatible = "hisilicon,hip04-d01";
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/misc/ |
| D | allwinner,syscon.txt | 1 * Allwinner sun8i system controller
3 This file describes the bindings for the system controller present in
8 Required properties for the system controller:
9 - reg: address and length of the register for the device.
10 - compatible: should be "syscon" and one of the following string:
11 "allwinner,sun8i-h3-system-controller"
12 "allwinner,sun8i-v3s-system-controller"
13 "allwinner,sun50i-a64-system-controller"
14 "allwinner,sun8i-a83t-system-controller"
18 compatible = "allwinner,sun8i-h3-system-controller", "syscon";
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/marvell/ |
| D | mvebu-system-controller.txt | 1 MVEBU System Controller
2 -----------------------
7 - compatible: one of:
8 - "marvell,orion-system-controller"
9 - "marvell,armada-370-xp-system-controller"
10 - "marvell,armada-375-system-controller"
11 - reg: Should contain system controller registers location and length.
15 system-controller@d0018200 {
16 compatible = "marvell,armada-370-xp-system-controller";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/marvell/ |
| D | mvebu-system-controller.txt | 1 MVEBU System Controller
2 -----------------------
7 - compatible: one of:
8 - "marvell,orion-system-controller"
9 - "marvell,armada-370-xp-system-controller"
10 - "marvell,armada-375-system-controller"
11 - reg: Should contain system controller registers location and length.
15 system-controller@d0018200 {
16 compatible = "marvell,armada-370-xp-system-controller";
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | berlin,pinctrl.txt | 1 * Pin-controller driver for the Marvell Berlin SoCs
3 Pin control registers are part of both chip controller and system
4 controller register sets. Pin controller nodes should be a sub-node of
5 either the chip controller or system controller node. The pins
9 A pin-controller node should contain subnodes representing the pin group
14 is called a 'function' in the pin-controller subsystem.
17 - compatible: should be one of:
18 "marvell,berlin2-soc-pinctrl",
19 "marvell,berlin2-system-pinctrl",
20 "marvell,berlin2cd-soc-pinctrl",
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | berlin,pinctrl.txt | 1 * Pin-controller driver for the Marvell Berlin SoCs
3 Pin control registers are part of both chip controller and system
4 controller register sets. Pin controller nodes should be a sub-node of
5 either the chip controller or system controller node. The pins
9 A pin-controller node should contain subnodes representing the pin group
14 is called a 'function' in the pin-controller subsystem.
17 - compatible: should be one of:
18 "marvell,berlin2-soc-pinctrl",
19 "marvell,berlin2-system-pinctrl",
20 "marvell,berlin2cd-soc-pinctrl",
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/clock/ |
| D | arm-syscon-icst.txt | 1 ARM System Controller ICST clocks
6 oscillators to their system controllers.
8 The various ARM system controllers contain logic to serialize and initialize
10 into the system controller. Furthermore, to even be able to alter one of
11 these frequencies, the system controller must first be unlocked by
12 writing a special token to another offset in the system controller.
23 integratorap-cm
26 integratorap-sys
29 integratorap-pci 14 1 14
32 integratorcp-cm-core
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/reset/ |
| D | ti,sci-reset.txt | 1 Texas Instruments System Control Interface (TI-SCI) Reset Controller
4 Some TI SoCs contain a system controller (like the Power Management Micro
5 Controller (PMMC) on Keystone 66AK2G SoC) that are responsible for controlling
7 between the host processor running an OS and the system controller happens
8 through a protocol called TI System Control Interface (TI-SCI protocol).
12 TI-SCI Reset Controller Node
14 This reset controller node uses the TI SCI protocol to perform the reset
16 node of the associated TI-SCI system controller node.
19 --------------------
20 - compatible : Should be "ti,sci-reset"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/reset/ |
| D | ti,sci-reset.txt | 1 Texas Instruments System Control Interface (TI-SCI) Reset Controller
4 Some TI SoCs contain a system controller (like the Power Management Micro
5 Controller (PMMC) on Keystone 66AK2G SoC) that are responsible for controlling
7 between the host processor running an OS and the system controller happens
8 through a protocol called TI System Control Interface (TI-SCI protocol).
12 TI-SCI Reset Controller Node
14 This reset controller node uses the TI SCI protocol to perform the reset
16 node of the associated TI-SCI system controller node.
19 --------------------
20 - compatible : Should be "ti,sci-reset"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/socionext/ |
| D | socionext,uniphier-system-cache.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/arm/socionext/socionext,uniphier-system-cache.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: UniPhier outer cache controller
10 UniPhier ARM 32-bit SoCs are integrated with a full-custom outer cache
11 controller system. All of them have a level 2 cache controller, and some
12 have a level 3 cache controller as well.
15 - Masahiro Yamada <yamada.masahiro@socionext.com>
19 const: socionext,uniphier-system-cache
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/sram/ |
| D | sunxi-sram.txt | 2 -----------------------------------------------------
4 The SRAM controller found on most Allwinner devices is represented by
5 a regular node for the SRAM controller itself, with sub-nodes
6 reprensenting the SRAM handled by the SRAM controller.
8 Controller Node
9 ---------------
12 - compatible : should be:
13 - "allwinner,sun4i-a10-sram-controller" (deprecated)
14 - "allwinner,sun4i-a10-system-control"
15 - "allwinner,sun5i-a13-system-control"
[all …]
|
| /kernel/linux/linux-4.19/drivers/reset/ |
| D | Kconfig | 5 bool "Reset Controller Support"
8 Generic Reset Controller support.
11 via GPIOs or SoC-internal reset controller modules.
18 tristate "Altera Arria10 System Resource Reset"
22 peripheral PHYs on the Altera Arria10 System Resource Chip.
28 This enables the ATH79 reset controller driver that supports the
29 AR71xx SoC reset controller.
35 This enables the reset controller driver for AXS10x.
41 This enables the reset controller driver for Marvell Berlin SoCs.
48 This enables the reset controller driver for HSDK board.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-edac | 1 What: /sys/devices/system/edac/mc/mc*/reset_counters
3 Contact: linux-edac@vger.kernel.org
4 Description: This write-only control file will zero all the statistical
5 counters for UE and CE errors on the given memory controller.
12 What: /sys/devices/system/edac/mc/mc*/seconds_since_reset
14 Contact: linux-edac@vger.kernel.org
19 What: /sys/devices/system/edac/mc/mc*/mc_name
21 Contact: linux-edac@vger.kernel.org
22 Description: This attribute file displays the type of memory controller
25 What: /sys/devices/system/edac/mc/mc*/size_mb
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-edac | 1 What: /sys/devices/system/edac/mc/mc*/reset_counters
3 Contact: linux-edac@vger.kernel.org
4 Description: This write-only control file will zero all the statistical
5 counters for UE and CE errors on the given memory controller.
12 What: /sys/devices/system/edac/mc/mc*/seconds_since_reset
14 Contact: linux-edac@vger.kernel.org
19 What: /sys/devices/system/edac/mc/mc*/mc_name
21 Contact: linux-edac@vger.kernel.org
22 Description: This attribute file displays the type of memory controller
25 What: /sys/devices/system/edac/mc/mc*/size_mb
[all …]
|
| /kernel/linux/linux-5.10/drivers/irqchip/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
75 The maximum number of VICs available in the system, for
91 bool "Amazon's Annapurna Labs Fabric Interrupt Controller"
96 Support Amazon's Annapurna Labs Fabric Interrupt Controller.
216 bool "J-Core integrated AIC" if COMPILE_TEST
220 Support for the J-Core integrated AIC.
230 Enable support for the Renesas Interrupt Controller for external
231 interrupt pins, as found on SH/R-Mobile and R-Car Gen1 SoCs.
234 bool "Renesas R-Mobile APE6, R-Car Gen{2,3} and RZ/G{1,2} IRQC support" if COMPILE_TEST
238 Enable support for the Renesas Interrupt Controller for external
[all …]
|
| /kernel/linux/linux-5.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
20 - Lee Jones <lee.jones@linaro.org>
27 - syscon
30 - compatible
[all …]
|
| /kernel/linux/linux-4.19/drivers/input/touchscreen/ |
| D | Kconfig | 23 support for the built-in touchscreen.
28 module will be called 88pm860x-ts.
36 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
37 and your board-specific setup code includes that in its
54 AD7877 controller, and your board-specific initialization
63 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
66 the AD7879-1/AD7889-1 controller.
78 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
81 module will be called ad7879-i2c.
88 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,sci.txt | 1 Texas Instruments System Control Interface (TI-SCI) Message Protocol
2 --------------------------------------------------------------------
6 management of the System on Chip (SoC) system. These include various system
9 An example of such an SoC is K2G, which contains the system control hardware
10 block called Power Management Micro Controller (PMMC). This hardware block is
16 TI-SCI controller Device Node:
19 The TI-SCI node describes the Texas Instrument's System Controller entity node.
23 relationship between the TI-SCI parent node to the child node.
26 -------------------
27 - compatible: should be "ti,k2g-sci"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,sci-inta.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/ti,sci-inta.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lokesh Vutla <lokeshvutla@ti.com>
13 - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
17 which handles the termination of system events to that they can
18 be coherently processed by the host(s) in the system. A maximum
22 +-----------------------------------------+
24 | +--------------+ +------------+ |
[all …]
|
| /kernel/linux/linux-5.10/drivers/input/touchscreen/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
24 support for the built-in touchscreen.
29 module will be called 88pm860x-ts.
37 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
38 and your board-specific setup code includes that in its
55 AD7877 controller, and your board-specific initialization
64 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
67 the AD7879-1/AD7889-1 controller.
79 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
82 module will be called ad7879-i2c.
[all …]
|
12345678910>>...45