| /freebsd-src/sys/contrib/device-tree/Bindings/arm/hisilicon/controller/ |
| H A 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 …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/arm/keystone/ |
| H A D | ti,sci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schema
[all...] |
| H A 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" for TI 66AK2G SoC
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/arm/hisilicon/ |
| H A D | hisilicon.txt | 2 ----------------------------------------------------
5 - compatible = "hisilicon,hi3660";
9 - compatible = "hisilicon,hi3660-hikey960", "hisilicon,hi3660";
13 - compatible = "hisilicon,hi3670";
17 - compatible = "hisilicon,hi3670-hikey970", "hisilicon,hi3670";
21 - compatible = "hisilicon,hi3798cv200";
25 - compatible = "hisilicon,hi3798cv200-poplar", "hisilicon,hi3798cv200";
29 - compatible = "hisilicon,hi3620-hi4511";
33 - compatible = "hisilicon,hi6220";
37 - compatible = "hisilicon,hi6220-hikey", "hisilicon,hi6220";
[all …]
|
| /freebsd-src/share/doc/smm/02.config/ |
| H A D | 5.t | 34 sample VAX-11/780 system on which the hardware can be
36 We then study the rules needed to configure a VAX-11/750
39 VAX-11/780 System
41 Our VAX-11/780 is configured with hardware
43 (this is one of the high-end configurations).
53 MASSBUS controller Emulex nexus ? mba0 hp(4)
56 MASSBUS controller Emulex nexus ? mba1
60 tape controller Emulex uba0 tm0 tm(4)
69 Table 1. VAX-11/780 Hardware support.
77 is ``vax''. We will assume this system will
[all …]
|
| H A D | 4.t | 40 configuration parameters global to all system images
44 system image to be generated, and
51 cpu types, options, timezone, system identifier, and maximum users.
55 The system is to run on the machine type specified. No more than
63 This system is to run on the cpu type specified.
76 Compile the listed optional code into the system.
80 \-DFUNNY \-DHAHA in the resultant makefile.
89 Other kernel options controlling system sizes and limits
97 Options that are used within the system makefile
108 Specifies the timezone used by the system. This is measured in the
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/arm/marvell/ |
| H A 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";
|
| H A D | ap80x-system-controller.txt | 1 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 …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A 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 …]
|
| /freebsd-src/usr.sbin/mlxcontrol/ |
| H A D | mlxcontrol.8 | 29 .Nd Mylex DAC-family RAID management utility
40 .Ar controller
41 .Op Ar controller ...
54 .Ar controller
67 Controller names are of the form "mlxN"
68 where N is the unit number of the controller.
72 .Bl -tag -width rebuild
74 Print the status of controllers and system drives.
78 about all controllers and drives in the system.
90 Rescan one or more controllers for non-attached system drives
[all …]
|
| /freebsd-src/share/man/man4/ |
| H A D | mlx.4 | 31 .Nd Mylex DAC-family RAID driver
36 .Bd -ragged -offset indent
44 .Bd -literal -offset indent
50 driver provides support for Mylex DAC-family PCI to SCSI RAID controllers,
57 .Bl -bullet -compact
79 RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-A
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/soc/microchip/ |
| H A D | microchip,mpfs-sys-controller.yaml | 1 # 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 <conor.dooley@microchip.com>
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 …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | ti,sci-inta.txt | 5 which handles the termination of system events to that they can
6 be coherently processed by the host(s) in the system. A maximum
11 +-----------------------------------------+
13 | +--------------+ +------------+ |
14 m ------>| | vint | bit | | 0 |.....|63| vint0 |
15 . | +--------------+ +------------+ | +------+
17 Globalevents ------>| . . |------>| IRQ |
19 . | . . | +------+
20 n ------>| +--------------+ +------------+ |
22 | +--------------+ +------------+ |
[all …]
|
| H A 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 …]
|
| H A D | ti,sci-intr.txt | 10 +----------------------+
12 +-------+ | +------+ +-----+ |
13 | GPIO |----------->| | irq0 | | 0 | | Host IRQ
14 +-------+ | +------+ +-----+ | controller
15 | . . | +-------+
16 +-------+ | . . |----->| IRQ |
17 | INTA |----------->| . . | +-------+
18 +-------+ | . +-----+ |
19 | +------+ | N | |
20 | | irqM | +-----+ |
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/reset/ |
| H A D | ti,sci-reset.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reset/ti,sci-rese
[all...] |
| H A 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 …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | ti,j721e-system-controller.yaml | 1 # 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/mfd/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 <kishon@ti.com>
[all …]
|
| H A D | syscon.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: System Controller Devices
10 System controlle
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/cache/ |
| H A 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/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 <yamada.masahiro@socionext.com>
19 const: socionext,uniphier-system-cache
[all …]
|
| /freebsd-src/sys/contrib/device-tree/Bindings/arm/socionext/ |
| H A 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 …]
|
| /freebsd-src/share/man/man4/man4.arm/ |
| H A D | aw_syscon.4 | 1 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
32 .Nd driver for the system controller in Allwinner SoC
36 device driver provides support for the Allwinner system controller.
37 This controller provide
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/sram/ |
| H A D | allwinner,sun4i-a10-system-control.yaml | 1 # SPDX-License-Identifier: GPL-2.0+
3 ---
4 $id: http://devicetree.org/schemas/sram/allwinner,sun4i-a10-system-contro
[all...] |
| /freebsd-src/sys/contrib/device-tree/Bindings/clock/ |
| H A D | ti,sci-clk.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/ti,sci-cl
[all...] |
| H A D | pistachio-clock.txt | 6 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 …]
|