Searched +full:reboot +full:- +full:mode (Results 1 – 25 of 64) sorted by relevance
123
| /Documentation/devicetree/bindings/power/reset/ |
| D | nvmem-reboot-mode.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/nvmem-reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic NVMEM reboot mode
10 - Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
13 This driver gets the reboot mode magic value from the reboot-mode driver
14 and stores it in the NVMEM cell named "reboot-mode". The bootloader can
19 const: nvmem-reboot-mode
21 nvmem-cells:
[all …]
|
| D | syscon-reboot-mode.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/power/reset/syscon-reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic SYSCON reboot mode driver
10 - Sebastian Reichel <sre@kernel.org>
13 This driver gets reboot mode magic value from reboot-mode driver
17 parental dt-node plus the offset. So the SYSCON reboot-mode node
18 should be represented as a sub-node of a "syscon", "simple-mfd" node.
22 const: syscon-reboot-mode
[all …]
|
| D | reboot-mode.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic reboot mode core map
10 - Andy Yan <andy.yan@rock-chips.com>
13 This driver get reboot mode arguments and call the write
18 All mode properties are vendor specific, it is a indication to tell
20 as mode-xxx = <magic> (xxx is mode name, magic should be a non-zero value).
23 - normal: Normal reboot mode, system reboot with command "reboot".
[all …]
|
| 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
24 const: syscon-reboot
32 description: Offset in the register map for the reboot register (in bytes).
[all …]
|
| D | qcom,pon.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinod Koul <vkoul@kernel.org>
14 and resin along with the Android reboot-mode.
21 - qcom,pm8916-pon
22 - qcom,pm8941-pon
23 - qcom,pms405-pon
24 - qcom,pm8998-pon
25 - qcom,pmk8350-pon
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-reboot | 1 What: /sys/kernel/reboot
5 Description: Interface to set the kernel reboot behavior, similarly to
6 what can be done via the reboot= cmdline option.
7 (see Documentation/admin-guide/kernel-parameters.txt)
9 What: /sys/kernel/reboot/mode
13 Description: Reboot mode. Valid values are: cold warm hard soft gpio
15 What: /sys/kernel/reboot/type
19 Description: Reboot type. Valid values are: bios acpi kbd triple efi pci
21 What: /sys/kernel/reboot/cpu
25 Description: CPU number to use to reboot.
[all …]
|
| D | sysfs-driver-toshiba_acpi | 5 Description: This file controls the keyboard backlight operation mode, valid
8 * 0x1 -> FN-Z
9 * 0x2 -> AUTO (also called TIMER)
10 * 0x8 -> ON
11 * 0x10 -> OFF
14 parameters, kernel 3.15 only accepts the first two (FN-Z and
17 a reboot for changes to take effect.
25 whenever the operation mode is set to AUTO (or TIMER),
26 valid values range from 0-60.
29 type and the range accepted for type 2 is 1-60.
[all …]
|
| D | sysfs-platform-asus-wmi | 6 Change CPU clock configuration (write-only).
9 * 0 -> Super Performance Mode
10 * 1 -> High Performance Mode
11 * 2 -> Power Saving Mode
46 Fan boost mode:
47 * 0 - normal,
48 * 1 - overboost,
49 * 2 - silent
56 Throttle thermal policy mode:
57 * 0 - default,
[all …]
|
| D | sysfs-power | 15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
28 The /sys/power/mem_sleep file controls the operating mode of
31 supported). The mode that will be used on subsequent attempts
35 Writing one of the above strings to this file causes the mode
39 See Documentation/admin-guide/pm/sleep-states.rst for more
46 The /sys/power/disk file controls the operating mode of the
47 suspend-to-disk mechanism. Reading from this file returns
51 'firmware' - means that the memory image will be saved to disk
[all …]
|
| /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 …]
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 10 To check if hibernation works, you can try to hibernate in the "reboot" mode::
12 # echo reboot > /sys/power/disk
15 and the system should create a hibernation image, reboot, resume and get back to
20 resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
21 modes causes the PM core to skip some platform-related callbacks which on ACPI
23 fails to hibernate or resume in the "reboot" mode, you should try the
24 "platform" mode::
29 which is the default and recommended mode of hibernation.
31 Unfortunately, the "platform" mode of hibernation does not work on some systems
32 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
[all …]
|
| /Documentation/devicetree/bindings/sram/ |
| D | qcom,imem.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
19 - enum:
20 - qcom,apq8064-imem
21 - qcom,msm8226-imem
22 - qcom,msm8974-imem
23 - qcom,qcs404-imem
24 - qcom,qdu1000-imem
[all …]
|
| /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 …]
|
| /Documentation/arch/s390/ |
| D | 3270.rst | 17 Linux/390. A 3270 device is a block-mode rows-and-columns terminal of
21 You may have 3270s in-house and not know it. If you're using the
22 VM-ESA operating system, define a 3270 to your virtual machine by using
23 the command "DEF GRAF <hex-address>" This paper presumes you will be
26 - DEF GRAF 620
27 - DEF GRAF 621
28 - DEF GRAF 622
29 - DEF GRAF 623
31 Your network connection from VM-ESA allows you to use x3270, tn3270, or
34 and this Linux-390 3270 driver, you have another way of talking to your
[all …]
|
| /Documentation/watchdog/ |
| D | watchdog-api.rst | 9 Copyright 2002 Christer Weingel <wingel@nano-system.com>
30 system (causing a reboot) after the timeout occurs.
32 The Linux watchdog API is a rather ad-hoc construction and different
40 All drivers support the basic mode of operation, where the watchdog
41 activates as soon as /dev/watchdog is opened and will reboot unless
45 like this source file: see samples/watchdog/watchdog-simple.c
53 crashes the system will not reboot. Because of this, some of the
57 started. So, if the watchdog daemon crashes, the system will reboot
71 cause a reboot if the watchdog is not re-opened in sufficient time.
140 Get the number of seconds before reboot
[all …]
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 41 inform the BIOS to enable the update in the next system reboot.
68 In packet update mode the packet size has to be given before any packets can
103 echo -1 > /sys/class/firmware/dell_rbu/loading
124 After updating the BIOS image a user mode application needs to execute
125 code which sends the BIOS update request to the BIOS. So on the next reboot
|
| D | lockup-watchdogs.rst | 9 kernel mode for more than 20 seconds (see "Implementation" below for
14 "softlockup_panic" (see "Documentation/admin-guide/kernel-parameters.rst" for
19 kernel mode for more than 10 seconds (see "Implementation" below for
26 (see "Documentation/admin-guide/kernel-parameters.rst" for details).
30 to cause the system to reboot automatically after a specified amount
43 (compile-time initialized to 10 and configurable through sysctl of the
64 event. The right value for a particular environment is a trade-off
77 to continue to run on the housekeeping (non-tickless) cores means
|
| /Documentation/filesystems/nfs/ |
| D | reexport.rst | 5 --------
15 ---------------------------------
18 filesystem. You can use "uuidgen -r" to generate a unique argument.
25 Reboot recovery
26 ---------------
28 The NFS protocol's normal reboot recovery mechanisms don't work for the
30 they held before the reboot, and further IO will result in errors.
34 -----------------
40 The result must fit into the RFC-mandated filehandle size limits:
42 +-------+-----------+
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress-config.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/vexpress-config.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andre Przywara <andre.przywara@arm.com>
16 function and device numbers - see motherboard's TRM for more details.
20 const: arm,vexpress,config-bus
22 arm,vexpress,config-bridge:
31 const: arm,vexpress-muxfpga
33 arm,vexpress-sysreg,func:
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | igb.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999-2018 Intel Corporation.
13 - Identifying Your Adapter
14 - Command Line Parameters
15 - Additional Configurations
16 - Support
46 -------
47 :Valid Range: 0-7
49 This parameter adds support for SR-IOV. It causes the driver to spawn up to
76 NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering
[all …]
|
| /Documentation/devicetree/bindings/soc/rockchip/ |
| D | grf.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Heiko Stuebner <heiko@sntech.de>
15 - items:
16 - enum:
17 - rockchip,rk3288-sgrf
18 - rockchip,rk3566-pipe-grf
19 - rockchip,rk3568-pcie3-phy-grf
20 - rockchip,rk3568-pipe-grf
[all …]
|
| /Documentation/security/ |
| D | sak.rst | 15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use
23 SAK works correctly when the keyboard is in raw mode. This means that
28 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot
29 the machine. CTRL-ALT-BACKSPACE is magical to the X server. We'll
30 choose CTRL-ALT-PAUSE.
57 # ls -l /proc/[0-9]*/fd/* | grep console
58 l-wx------ 1 root root 64 Mar 18 00:46 /proc/579/fd/0 -> /dev/console
63 root 579 0.0 0.1 1088 436 ? S 00:43 0:00 gpm -t ps/2
90 applications to malfunction - test everything well.
|
| /Documentation/cdrom/ |
| D | packet-writing.rst | 6 ---------------------
8 - Select packet support in the block device section and UDF support in
11 - Compile and install kernel and modules, reboot.
13 - You need the udftools package (pktsetup, mkudffs, cdrwtool).
16 - Grab a new CD-RW disc and format it (assuming CD-RW is hdc, substitute
19 # cdrwtool -d /dev/hdc -q
21 - Setup your writer::
25 - Now you can mount /dev/pktcdvd/dev_name and copy files to it. Enjoy::
27 # mount /dev/pktcdvd/dev_name /cdrom -t udf -o rw,noatime
30 Packet writing for DVD-RW media
[all …]
|
| /Documentation/hwmon/ |
| D | abituguru-datasheet.rst | 14 Olle Sandberg <ollebull@gmail.com>, 2005-05-25
27 Hans de Goede <j.w.r.degoede@hhs.nl>, 28-01-2006
33 As far as known the uGuru is always placed at and using the (ISA) I/O-ports
34 0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two
35 ports are holding for detection. We will refer to 0xE0 as CMD (command-port)
39 present. We have to check for two different values at data-port, because
40 after a reboot uGuru will hold 0x00 here, but if the driver is removed and
41 later on attached again data-port will hold 0x08, more about this later.
57 ----------
82 -----------
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | jedec,spi-nor.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/mtd/jedec,spi-nor.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
13 - $ref: mtd.yaml#
14 - $ref: /schemas/spi/spi-peripheral-props.yaml#
19 - items:
20 - pattern: "^((((micron|spansion|st),)?\
33 - const: jedec,spi-nor
[all …]
|
123