Home
last modified time | relevance | path

Searched +full:system +full:- +full:controller (Results 1 – 25 of 1041) sorted by relevance

12345678910>>...42

/linux-6.14.4/drivers/pmdomain/renesas/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
5 bool "System Controller support for R-Car" if COMPILE_TEST
8 bool "System Controller support for R-Car Gen4" if COMPILE_TEST
11 bool "System Controller support for R-Car D3" if COMPILE_TEST
15 bool "System Controller support for R-Car E2" if COMPILE_TEST
19 bool "System Controller support for R-Car E3" if COMPILE_TEST
23 bool "System Controller support for R-Car H1" if COMPILE_TEST
27 bool "System Controller support for R-Car H2" if COMPILE_TEST
31 bool "System Controller support for R-Car H3" if COMPILE_TEST
35 bool "System Controller support for R-Car M2-W/N" if COMPILE_TEST
[all …]
/linux-6.14.4/drivers/eisa/
Deisa.ids6 # 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/arm/hisilicon/controller/
Dsysctrl.yaml1 # 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 <[email protected]>
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 …]
/linux-6.14.4/Documentation/devicetree/bindings/arm/keystone/
Dti,sci.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI controller
10 - Nishanth Menon <[email protected]>
15 management of the System on Chip (SoC) system. These include various system
18 An example of such an SoC is K2G, which contains the system control hardware
19 block called Power Management Micro Controller (PMMC). This hardware block is
23 See https://software-dl.ti.com/tisci/esd/latest/index.html for protocol definition.
25 The TI-SCI node describes the Texas Instrument's System Controller entity node.
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/arm/marvell/
Dmvebu-system-controller.txt1 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";
Dap80x-system-controller.txt1 Marvell Armada AP80x System Controller
5 7K/8K/931x SoCs. It contains system controllers, which provide several
6 registers giving access to numerous features: clocks, pin-muxing and
8 these system controllers.
11 - compatible: must be: "syscon", "simple-mfd";
12 - reg: register area of the AP80x system controller
14 SYSTEM CONTROLLER 0
18 -------
21 The Device Tree node representing the AP806/AP807 system controller
24 - 0: reference clock of CPU cluster 0
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/pinctrl/
Dberlin,pinctrl.txt1 * 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/soc/microchip/
Dmicrochip,mpfs-sys-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/microchip/microchip,mpfs-sys-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip PolarFire SoC (MPFS) MSS (microprocessor subsystem) system controller
10 - Conor Dooley <[email protected]>
13 PolarFire SoC devices include a microcontroller acting as the system controller,
17 https://onlinedocs.microchip.com/pr/GUID-1409CF11-8EF9-4C24-A94E-70979A688632-en-US-1/index.html
19 Communication with the system controller is done via a mailbox, of which the client
27 const: microchip,mpfs-sys-controller
[all …]
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-devices-edac1 What: /sys/devices/system/edac/mc/mc*/reset_counters
3 Contact: linux-[email protected]
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-[email protected]
19 What: /sys/devices/system/edac/mc/mc*/mc_name
21 Contact: linux-[email protected]
22 Description: This attribute file displays the type of memory controller
25 What: /sys/devices/system/edac/mc/mc*/size_mb
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/reset/
Dti,sci-reset.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reset/ti,sci-reset.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI reset controller
10 - Nishanth Menon <[email protected]>
13 Some TI SoCs contain a system controller (like the Power Management Micro
14 Controller (PMMC) on Keystone 66AK2G SoC) that are responsible for controlling
16 between the host processor running an OS and the system controller happens
17 through a protocol called TI System Control Interface (TI-SCI protocol).
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/mfd/
Dsyscon.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: System Controller Devices
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 <[email protected]>
30 - al,alpine-sysfabric-service
31 - allwinner,sun8i-a83t-system-controller
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/cache/
Dsocionext,uniphier-system-cache.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/cache/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 <[email protected]>
19 const: socionext,uniphier-system-cache
[all …]
/linux-6.14.4/drivers/input/touchscreen/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
20 support for the built-in touchscreen.
25 module will be called 88pm860x-ts.
33 ADS7846/TSC2046/AD7873 or ADS7843/AD7843 controller,
34 and your board-specific setup code includes that in its
51 AD7877 controller, and your board-specific initialization
60 tristate "Analog Devices AD7879-1/AD7889-1 touchscreen interface"
63 the AD7879-1/AD7889-1 controller.
75 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
78 module will be called ad7879-i2c.
[all …]
/linux-6.14.4/drivers/pci/hotplug/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
11 Say Y here if you have a motherboard with a PCI Hotplug controller.
26 controller.
38 controller. This will allow the PCI Hotplug driver to store the PCI
39 system configuration options in NVRAM.
48 controller.
59 Say Y here if you have a system that supports PCI Hotplug using
69 Say Y here if you have an Ampere Altra system.
80 Say Y here if you have an IBM system that supports PCI Hotplug using
91 Say Y here if you have a CompactPCI system card with CompactPCI
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/soc/ti/
Dti,j721e-system-controller.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2020 Texas Instruments Incorporated - http://www.ti.com/
4 ---
5 $id: http://devicetree.org/schemas/soc/ti/ti,j721e-system-controller.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: TI J721e System Controller Registers R/W
12 System controller node represents a register region containing a set
14 represent as any specific type of device. The typical use-case is
15 for some other node's driver, or platform-specific code, to acquire
22 - Kishon Vijay Abraham I <[email protected]>
[all …]
/linux-6.14.4/drivers/usb/typec/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
8 be Type-A plug on one end of the cable and Type-B plug on the other.
9 Determination of the host-to-device relationship happens through a
10 specific Configuration Channel (CC) which goes through the USB Type-C
12 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
22 USB Type-C connector, however it is mostly used together with USB
23 Type-C connectors.
25 USB Type-C and USB Power Delivery Specifications define a set of state
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/
Dti,sci-inta.yaml1 # 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 <[email protected]>
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 …]
/linux-6.14.4/arch/mips/boot/dts/mobileye/
Deyeq6h.dtsi1 // SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
6 #include <dt-bindings/interrupt-controller/mips-gic.h>
8 #include <dt-bindings/clock/mobileye,eyeq5-clk.h>
11 #address-cells = <2>;
12 #size-cells = <2>;
14 #address-cells = <1>;
15 #size-cells = <0>;
28 cpu_intc: interrupt-controller {
29 compatible = "mti,cpu-interrupt-controller";
30 interrupt-controller;
[all …]
/linux-6.14.4/drivers/staging/media/atomisp/pci/
Dsystem_local.c1 // SPDX-License-Identifier: GPL-2.0
86 /*GP TIMER , all timer registers are inter-twined,
130 /* IBUF_CTRL, part of the Input System 2401 */
132 0x00000000000C1800ULL, /* ibuf controller A */
133 0x00000000000C3800ULL, /* ibuf controller B */
134 0x00000000000C5800ULL /* ibuf controller C */
137 /* ISYS IRQ Controllers, part of the Input System 2401 */
144 /* CSI FE, part of the Input System 2401 */
146 0x00000000000C0400ULL, /* csi fe controller A */
147 0x00000000000C2400ULL, /* csi fe controller B */
[all …]
/linux-6.14.4/Documentation/arch/x86/
Dearlyprintk.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Mini-HOWTO for using the earlyprintk=dbgp boot option with a
13 [host/target] <-------> [USB debug key] <-------> [client/console]
18 a) Host/target system needs to have USB debug port capability.
21 the lspci -vvv output::
23 # lspci -vvv
25 …00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (p…
27 …Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisIN…
28 …Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- I…
31 Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K]
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/sram/
Dallwinner,sun4i-a10-system-control.yaml1 # SPDX-License-Identifier: GPL-2.0+
3 ---
4 $id: http://devicetree.org/schemas/sram/allwinner,sun4i-a10-system-control.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Allwinner A10 System Control
10 - Chen-Yu Tsai <[email protected]>
11 - Maxime Ripard <[email protected]>
14 The SRAM controller found on most Allwinner devices is represented
15 by a regular node for the SRAM controller itself, with sub-nodes
16 representing the SRAM handled by the SRAM controller.
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/clock/
Dti,sci-clk.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/ti,sci-clk.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI clock controller
10 - Nishanth Menon <[email protected]>
13 Some TI SoCs contain a system controller (like the Power Management Micro
14 Controller (PMMC) on Keystone 66AK2G SoC) that are responsible for controlling
16 between the host processor running an OS and the system controller happens
17 through a protocol called TI System Control Interface (TI-SCI protocol).
[all …]
Dpistachio-clock.txt6 from the device-tree.
9 ----------------
12 defined with the following clock-output-names:
13 - "xtal": External 52Mhz oscillator (required)
14 - "audio_clk_in": Alternate audio reference clock (optional)
15 - "enet_clk_in": Alternate ethernet PHY clock (optional)
17 Core clock controller:
18 ----------------------
20 The core clock controller generates clocks for the CPU, RPU (WiFi + BT
21 co-processor), audio, and several peripherals.
[all …]
/linux-6.14.4/drivers/clk/starfive/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
12 Say yes here to support the clock controller on the StarFive JH7100
29 Say yes here to support the PLL clock controller on the
33 bool "StarFive JH7110 system clock support"
41 Say yes here to support the system clock controller on the
45 tristate "StarFive JH7110 always-on clock support"
49 Say yes here to support the always-on clock controller on the
53 tristate "StarFive JH7110 System-Top-Group clock support"
57 Say yes here to support the System-Top-Group clock controller
61 tristate "StarFive JH7110 Image-Signal-Process clock support"
[all …]
/linux-6.14.4/drivers/reset/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
6 bool "Reset Controller Support"
9 Generic Reset Controller support.
12 via GPIOs or SoC-internal reset controller modules.
19 tristate "Altera Arria10 System Resource Reset"
23 peripheral PHYs on the Altera Arria10 System Resource Chip.
29 This enables the ATH79 reset controller driver that supports the
30 AR71xx SoC reset controller.
36 This enables the reset controller driver for AXS10x.
39 bool "BCM6345 Reset Controller"
[all …]

12345678910>>...42