Searched full:restart (Results 1 – 25 of 111) sorted by relevance
12345
| /Documentation/devicetree/bindings/power/reset/ |
| D | restart-handler.yaml | 4 $id: http://devicetree.org/schemas/power/reset/restart-handler.yaml#
7 title: Restart and shutdown handler Common Properties
13 Restart and shutdown handler device is responsible for powering off the
14 system, e.g. my cutting off the power. System might have several restart
22 0:: Restart handler of last resort, with limited restart capabilities.
23 128:: Typical, default restart handler; use if no other restart handler
24 is expected to be available, and/or if restart functionality is
25 sufficient to restart the entire system.
26 255:: Highest priority restart handler, will preempt all other restart handlers.
|
| D | gpio-restart.yaml | 4 $id: http://devicetree.org/schemas/power/reset/gpio-restart.yaml#
13 Drive a GPIO line that can be used to restart the system from a restart handler.
16 request the given gpio line and install a restart handler. If the optional properties
18 not driven until the restart is initiated.
20 When the system is restarted, the restart handler will be invoked in priority order. The GPIO
26 restart handler completes allowing other restart handlers to be attempted.
29 - $ref: restart-handler.yaml#
33 const: gpio-restart
42 description: Treat the GPIO as being open source and defer driving it to when the restart is
61 description: Delay (default 3000) to wait after completing restart sequence [ms]
[all …]
|
| D | st-reset.txt | 4 - compatible: should be "stih407-restart".
8 restart {
9 compatible = "st,stih407-restart";
|
| D | qcom,pshold.yaml | 7 title: Qualcomm SoC restart and power off
14 Clearing that bit allows us to restart/power off. The difference between
15 power off and restart is determined by unique power manager IC settings.
|
| D | restart-poweroff.txt | 1 * Restart Power Off
8 - compatible: Should be "restart-poweroff"
|
| D | axxia-reset.txt | 1 Axxia Restart Driver
|
| D | gpio-poweroff.yaml | 22 - $ref: restart-handler.yaml#
|
| /Documentation/watchdog/ |
| D | watchdog-kernel-api.rst | 104 * restart_nb: notifier block that is registered for machine restart, for
106 should define ops->restart. Priority can be changed through
133 int (*restart)(struct watchdog_device *);
174 start function to restart the watchdog timer hardware. And that's also what
232 * restart: this routine restarts the machine. It returns 0 on success or a
317 To change the priority of the restart handler the following helper should be
324 * 0: should be called in last resort, has limited restart capabilities
325 * 128: default restart handler, use if no other handler is expected to be
326 available, and/or if restart is sufficient to restart the entire system
327 * 255: highest priority, will preempt all other restart handlers
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-jpeg.rst | 55 The restart interval determines an interval of inserting RSTm
58 image independently. For the lossy compression processes the restart
60 in DRI (Define Restart Interval) marker. If
|
| D | vidioc-g-jpegcomp.rst | 52 and the restart interval information (all JPEG-specific stuff) should be
111 - Define Restart Interval
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 41 - restart-gpio: drivers/power/reset/gpio-restart.c is used to restart/reboot
42 the system by pulling a GPIO line and will register a restart handler so
43 userspace can issue the right system call to restart the system.
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,qcs404-cdsp-pil.yaml | 70 - description: AOSS restart
74 - const: restart
156 reset-names = "restart";
|
| D | qcom,sc7280-wpss-pil.yaml | 70 - description: AOSS restart
75 - const: restart
197 reset-names = "restart", "pdc_sync";
|
| /Documentation/networking/device_drivers/atm/ |
| D | cxacru.rst | 39 - Up to 7 parameters at a time will be sent and the modem will restart
109 - "restart" (stops, waits 1.5s, then starts)
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 52 r1/x1 = restart address
58 into place (arm64 only), and jump to the restart address while at HYP/EL2.
|
| /Documentation/driver-api/media/ |
| D | camera-sensor.rst | 80 restart when the system is resumed. This requires coordination between the
83 restart streaming by calling the appropriate subdev operations
86 stop streaming in the PM suspend handler and restart it in the resume handler.
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 93 Restart smb service::
95 # systemctl restart smb
|
| /Documentation/userspace-api/media/drivers/ |
| D | imx-uapi.rst | 53 Userland can issue a streaming restart when this event is received
84 How many frames to skip after a FIM reset or stream restart before
|
| /Documentation/admin-guide/ |
| D | ramoops.rst | 14 survive after a restart.
52 on restart (i.e. new dumps after the restart will overwrite old ones).
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | xlnx,versal-wwdt.yaml | 18 restarted within the open window time. If software tries to restart
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | qcom,spmi-sdam.yaml | 52 restart_reason: restart@50 {
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 93 new list and restart the list traversal. I think that this can be
150 is not the slot number, then we must restart the lookup at
183 // not the expected one, we must restart lookup.
|
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 15 related errors that should be handled similarly (e.g. transaction restart
|
| /Documentation/devicetree/bindings/reset/ |
| D | nuvoton,npcm750-reset.yaml | 33 Contains the software reset number to restart the SoC.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-raid.rst | 35 - rotating parity 0 with data restart
38 - rotating parity N with data restart
39 raid6_zr RAID6 zero restart
41 - rotating parity zero (left-to-right) with data restart
42 raid6_nr RAID6 N restart
44 - rotating parity N (right-to-left) with data restart
|
12345