Searched +full:system +full:- +full:reboot +full:- +full:controller (Results 1 – 25 of 334) sorted by relevance
12345678910>>...14
| /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-6.6/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-6.6/Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,sci.yaml | 1 # 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 <nm@ti.com>
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
25 The TI-SCI node describes the Texas Instrument's System Controller entity node.
29 relationship between the TI-SCI parent node to the child node.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | canaan,k210-sysctl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/canaan,k210-sysctl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Canaan Kendryte K210 System Controller
10 - Damien Le Moal <dlemoal@kernel.org>
13 Canaan Inc. Kendryte K210 SoC system controller which provides a
20 - const: canaan,k210-sysctl
21 - const: syscon
22 - const: simple-mfd
[all …]
|
| D | ti,nspire-misc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2022-2023 Texas Instruments Incorporated - https://www.ti.com/
4 ---
5 $id: http://devicetree.org/schemas/mfd/ti,nspire-misc.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Andrew Davis <afd@ti.com>
14 System controller node represents a register region containing a set
17 controller.
22 - enum:
23 - ti,nspire-misc
[all …]
|
| /kernel/linux/linux-5.10/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" for TI 66AK2G SoC
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | syscon-reboot.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/reset/syscon-reboot.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
16 mask defined in the reboot node. Default will be little endian mode, 32 bit
18 parental dt-node. So the SYSCON reboot node should be represented as a
19 sub-node of a "syscon", "simple-mfd" node. Though the regmap property
20 pointing to the system controller node is also supported.
24 const: syscon-reboot
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/reset/ |
| D | syscon-reboot.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/reset/syscon-reboot.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
16 mask defined in the reboot node. Default will be little endian mode, 32 bit
18 parental dt-node. So the SYSCON reboot node should be represented as a
19 sub-node of a "syscon", "simple-mfd" node. Though the regmap property
20 pointing to the system controller node is also supported.
24 const: syscon-reboot
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 2 -----------------------------------------------
3 Boards with Broadcom Brahma15 ARM-based BCMxxxx (generally BCM7xxx variants)
7 - compatible: "brcm,bcm<chip_id>", "brcm,brcmstb"
11 #address-cells = <2>;
12 #size-cells = <2>;
16 Further, syscon nodes that map platform-specific registers used for general
17 system control is required:
19 - compatible: "brcm,bcm<chip_id>-sun-top-ctrl", "syscon"
20 - compatible: "brcm,bcm<chip_id>-cpu-biu-ctrl",
21 "brcm,brcmstb-cpu-biu-ctrl",
[all …]
|
| D | brcm,bcm63138.txt | 1 Broadcom BCM63138 DSL System-on-a-Chip device tree bindings
2 -----------------------------------------------------------
4 Boards compatible with the BCM63138 DSL System-on-a-Chip should have the
12 initialization as well as a 'resets' phandle to the correct PMB controller as
13 defined in reset/brcm,bcm63138-pmb.txt for this secondary CPU, and an
14 'enable-method' property.
17 - compatible: should be "brcm,bcm63138-bootlut"
18 - reg: register base address and length for the Boot Lookup table
21 - enable-method: should be "brcm,bcm63138"
24 - enable-method: should be "brcm,bcm63138"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 2 -----------------------------------------------
3 Boards with Broadcom Brahma15 ARM-based BCMxxxx (generally BCM7xxx variants)
7 - compatible: "brcm,bcm<chip_id>", "brcm,brcmstb"
11 #address-cells = <2>;
12 #size-cells = <2>;
16 Further, syscon nodes that map platform-specific registers used for general
17 system control is required:
19 - compatible: "brcm,bcm<chip_id>-sun-top-ctrl", "syscon"
20 - compatible: "brcm,bcm<chip_id>-cpu-biu-ctrl",
21 "brcm,brcmstb-cpu-biu-ctrl",
[all …]
|
| D | brcm,bcm63138.txt | 1 Broadcom BCM63138 DSL System-on-a-Chip device tree bindings
2 -----------------------------------------------------------
4 Boards compatible with the BCM63138 DSL System-on-a-Chip should have the
12 initialization as well as a 'resets' phandle to the correct PMB controller as
13 defined in reset/brcm,bcm63138-pmb.txt for this secondary CPU, and an
14 'enable-method' property.
17 - compatible: should be "brcm,bcm63138-bootlut"
18 - reg: register base address and length for the Boot Lookup table
21 - enable-method: should be "brcm,bcm63138"
24 - enable-method: should be "brcm,bcm63138"
[all …]
|
| /kernel/linux/linux-6.6/drivers/power/reset/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 bool "ams AS3722 power-off driver"
16 This driver supports turning off board via a ams AS3722 power-off.
35 tristate "Atmel AT91 SAMA5D2-Compatible shutdown controller driver"
39 This driver supports the alternate shutdown controller for some Atmel
43 tristate "Actions Semi ATC260x PMIC power-off driver"
46 This driver provides power-off and restart support for a system
64 Say Y here if you have a Broadcom Kona-based board and you wish
79 bool "Cortina Gemini power-off driver"
88 bool "GPIO power-off driver"
[all …]
|
| /kernel/linux/linux-5.10/drivers/power/reset/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 bool "ams AS3722 power-off driver"
16 This driver supports turning off board via a ams AS3722 power-off.
35 tristate "Atmel AT91 SAMA5D2-Compatible shutdown controller driver"
39 This driver supports the alternate shutdown controller for some Atmel
57 Say Y here if you have a Broadcom Kona-based board and you wish
72 bool "Cortina Gemini power-off driver"
81 bool "GPIO power-off driver"
97 bool "Hisilicon power-off driver"
100 Reboot support for Hisilicon boards.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/x86_64/ |
| D | boot-options.rst | 1 .. SPDX-License-Identifier: GPL-2.0
39 Do not opt-in to Local MCE delivery. Use legacy method
47 in a reboot. On Intel systems it is enabled by default.
55 Don't overwrite the bios-set CMCI threshold. This boot option
62 Force-enable recoverable machine check code paths
73 Use IO-APIC. Default
76 Don't use the IO-APIC.
85 See Documentation/arch/x86/i386/IO-APIC.rst
91 Don't check the IO-APIC timer. This can work around
122 reboot=b[ios] | t[riple] | k[bd] | a[cpi] | e[fi] | p[ci] [, [w]arm | [c]old]
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/x86_64/ |
| D | boot-options.rst | 1 .. SPDX-License-Identifier: GPL-2.0
39 Do not opt-in to Local MCE delivery. Use legacy method
47 in a reboot. On Intel systems it is enabled by default.
62 Don't overwrite the bios-set CMCI threshold. This boot option
69 Force-enable recoverable machine check code paths
80 Use IO-APIC. Default
83 Don't use the IO-APIC.
92 See Documentation/x86/i386/IO-APIC.rst
98 Don't check the IO-APIC timer. This can work around
129 reboot=b[ios] | t[riple] | k[bd] | a[cpi] | e[fi] [, [w]arm | [c]old]
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/samsung/ |
| D | exynos-pmu.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/soc/samsung/exynos-pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
18 - samsung,exynos3250-pmu
19 - samsung,exynos4210-pmu
20 - samsung,exynos4212-pmu
21 - samsung,exynos4412-pmu
22 - samsung,exynos5250-pmu
[all …]
|
| /kernel/linux/linux-6.6/arch/powerpc/boot/dts/ |
| D | turris1x.dts | 1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright 2013 - 2022 CZ.NIC z.s.p.o. (http://www.nic.cz/)
8 * and available at: https://docs.turris.cz/hw/turris-1x/turris-1x/
11 #include <dt-bindings/gpio/gpio.h>
12 #include <dt-bindings/interrupt-controller/irq.h>
13 #include <dt-bindings/leds/common.h>
14 /include/ "fsl/p2020si-pre.dtsi"
40 /* PCA9557PW GPIO controller for boot config */
41 gpio-controller@18 {
45 #gpio-cells = <2>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/samsung/ |
| D | pmu.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
18 - samsung,exynos3250-pmu
19 - samsung,exynos4210-pmu
20 - samsung,exynos4412-pmu
21 - samsung,exynos5250-pmu
22 - samsung,exynos5260-pmu
23 - samsung,exynos5410-pmu
[all …]
|
| /kernel/linux/linux-6.6/drivers/watchdog/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 on-line as fast as possible after a lock-up. There's both a watchdog
18 reboot the machine) and a driver for hardware watchdog boards, which
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
25 <https://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon
26 can also monitor NFS connections and can reboot the machine when the
51 bool "Update boot-enabled watchdog until userspace takes over"
59 enough your device will reboot.
77 bool "Enable watchdog hrtimer-based pretimeouts"
130 the kernel log buffer and don't do any system changes.
[all …]
|
| /kernel/linux/linux-5.10/drivers/watchdog/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 on-line as fast as possible after a lock-up. There's both a watchdog
18 reboot the machine) and a driver for hardware watchdog boards, which
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
25 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
26 also monitor NFS connections and can reboot the machine when the process
51 bool "Update boot-enabled watchdog until userspace takes over"
59 enough your device will reboot.
122 the kernel log buffer and don't do any system changes.
130 a watchdog feeder is dead and reboot is unavoidable.
[all …]
|
| /kernel/linux/linux-6.6/arch/mips/boot/dts/mti/ |
| D | malta.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include <dt-bindings/interrupt-controller/irq.h>
5 #include <dt-bindings/interrupt-controller/mips-gic.h>
12 #address-cells = <1>;
13 #size-cells = <1>;
16 cpu_intc: interrupt-controller {
17 compatible = "mti,cpu-interrupt-controller";
19 interrupt-controller;
20 #interrupt-cells = <1>;
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/boot/dts/mti/ |
| D | malta.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include <dt-bindings/interrupt-controller/irq.h>
5 #include <dt-bindings/interrupt-controller/mips-gic.h>
12 #address-cells = <1>;
13 #size-cells = <1>;
16 cpu_intc: interrupt-controller {
17 compatible = "mti,cpu-interrupt-controller";
19 interrupt-controller;
20 #interrupt-cells = <1>;
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mips/lantiq/ |
| D | rcu.txt | 4 This binding describes the RCU (reset controller unit) multifunction device,
5 where each sub-device has its own set of registers.
14 -------------------------------------------------------------------------------
16 - compatible : The first and second values must be:
17 "lantiq,xrx200-rcu", "simple-mfd", "syscon"
18 - reg : The address and length of the system control registers
21 -------------------------------------------------------------------------------
24 compatible = "lantiq,xrx200-rcu", "simple-mfd", "syscon";
27 big-endian;
29 reset0: reset-controller@10 {
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mips/lantiq/ |
| D | rcu.txt | 4 This binding describes the RCU (reset controller unit) multifunction device,
5 where each sub-device has it's own set of registers.
14 -------------------------------------------------------------------------------
16 - compatible : The first and second values must be:
17 "lantiq,xrx200-rcu", "simple-mfd", "syscon"
18 - reg : The address and length of the system control registers
21 -------------------------------------------------------------------------------
24 compatible = "lantiq,xrx200-rcu", "simple-mfd", "syscon";
27 big-endian;
29 reset0: reset-controller@10 {
[all …]
|
12345678910>>...14