| /kernel/linux/linux-5.10/drivers/watchdog/ |
| D | Kconfig | 4 # Watchdog device configuration
7 menuconfig WATCHDOG config
8 bool "Watchdog Timer Support"
11 character special file /dev/watchdog with major number 10 and minor
12 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
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.
23 The watchdog is usually used together with the watchdog daemon
25 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
[all …]
|
| D | f71808e_wdt.c | 22 #include <linux/watchdog.h>
26 #define SIO_F71808FG_LD_WDT 0x07 /* Watchdog timer logical device */
76 watchdog signal */
77 #define WATCHDOG_F71862FG_PIN 63 /* default watchdog reset output
88 "Watchdog timeout in seconds. 1<= timeout <="
95 "Watchdog signal pulse width. 0(=level), 1, 25, 30, 125, 150, 5000 or 6000 ms"
101 "Watchdog f71862fg reset output pin configuration. Choose pin 56 or 63"
106 MODULE_PARM_DESC(nowayout, "Disable watchdog shutdown on close");
110 MODULE_PARM_DESC(start_withtimeout, "Start watchdog timer on module load with"
152 char caused_reboot; /* last reboot was by the watchdog */
[all …]
|
| D | watchdog_dev.c | 12 * by all the watchdog timer drivers.
15 * misc device: /dev/watchdog.
43 #include <linux/watchdog.h> /* For watchdog specific items */
50 * struct watchdog_core_data - watchdog core internal data
51 * @dev: The watchdog's internal device
52 * @cdev: The watchdog's Character device.
53 * @wdd: Pointer to watchdog device.
54 * @lock: Lock for watchdog core.
55 * @status: Watchdog core internal status bits.
73 /* the dev_t structure to store the dynamically allocated watchdog devices */
[all …]
|
| D | wdrtas.c | 8 * RTAS watchdog driver
11 * device driver to exploit watchdog RTAS functions
26 #include <linux/watchdog.h>
36 MODULE_DESCRIPTION("RTAS watchdog driver");
59 /*** watchdog access functions */
62 * wdrtas_set_interval - sets the watchdog interval
67 * wdrtas_set_interval sets the watchdog keepalive interval by calling the
83 pr_err("setting the watchdog to %i timeout failed: %li\n", in wdrtas_set_interval()
94 * wdrtas_get_interval - returns the current watchdog interval
99 * wdrtas_get_interval returns the current watchdog keepalive interval
[all …]
|
| /kernel/linux/linux-6.6/drivers/watchdog/ |
| D | Kconfig | 4 # Watchdog device configuration
7 menuconfig WATCHDOG config
8 bool "Watchdog Timer Support"
11 character special file /dev/watchdog with major number 10 and minor
12 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
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.
23 The watchdog is usually used together with the watchdog daemon
25 <https://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon
[all …]
|
| D | watchdog_dev.c | 13 * by all the watchdog timer drivers.
16 * misc device: /dev/watchdog.
45 #include <linux/watchdog.h> /* For watchdog specific items */
51 #include <trace/events/watchdog.h>
53 /* the dev_t structure to store the dynamically allocated watchdog devices */
55 /* Reference to watchdog device behind /dev/watchdog */
85 * - Userspace activated the watchdog. in watchdog_need_worker()
91 * Alternatively, if userspace has not opened the watchdog in watchdog_need_worker()
92 * device, we take care of feeding the watchdog if it is in watchdog_need_worker()
118 * To ensure that the watchdog times out wdd->timeout seconds in watchdog_next_keepalive()
[all …]
|
| D | wdrtas.c | 8 * RTAS watchdog driver
11 * device driver to exploit watchdog RTAS functions
26 #include <linux/watchdog.h>
36 MODULE_DESCRIPTION("RTAS watchdog driver");
59 /*** watchdog access functions */
62 * wdrtas_set_interval - sets the watchdog interval
67 * wdrtas_set_interval sets the watchdog keepalive interval by calling the
83 pr_err("setting the watchdog to %i timeout failed: %li\n", in wdrtas_set_interval()
94 * wdrtas_get_interval - returns the current watchdog interval
99 * wdrtas_get_interval returns the current watchdog keepalive interval
[all …]
|
| /kernel/linux/linux-6.6/drivers/greybus/ |
| D | svc_watchdog.c | 3 * SVC Greybus "watchdog" driver.
27 struct gb_svc_watchdog *watchdog = in svc_watchdog_pm_notifier() local
32 gb_svc_watchdog_disable(watchdog->svc); in svc_watchdog_pm_notifier()
35 gb_svc_watchdog_enable(watchdog->svc); in svc_watchdog_pm_notifier()
65 struct gb_svc_watchdog *watchdog; in do_work() local
69 watchdog = container_of(work, struct gb_svc_watchdog, work.work); in do_work()
70 svc = watchdog->svc; in do_work()
98 watchdog->enabled = false; in do_work()
103 if (watchdog->enabled) in do_work()
104 schedule_delayed_work(&watchdog->work, SVC_WATCHDOG_PERIOD); in do_work()
[all …]
|
| /kernel/linux/linux-5.10/drivers/greybus/ |
| D | svc_watchdog.c | 3 * SVC Greybus "watchdog" driver.
27 struct gb_svc_watchdog *watchdog = in svc_watchdog_pm_notifier() local
32 gb_svc_watchdog_disable(watchdog->svc); in svc_watchdog_pm_notifier()
35 gb_svc_watchdog_enable(watchdog->svc); in svc_watchdog_pm_notifier()
65 struct gb_svc_watchdog *watchdog; in do_work() local
69 watchdog = container_of(work, struct gb_svc_watchdog, work.work); in do_work()
70 svc = watchdog->svc; in do_work()
98 watchdog->enabled = false; in do_work()
103 if (watchdog->enabled) in do_work()
104 schedule_delayed_work(&watchdog->work, SVC_WATCHDOG_PERIOD); in do_work()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/watchdog/ |
| D | watchdog-kernel-api.rst | 2 The Linux WatchDog Timer Driver Core kernel API
11 This document does not describe what a WatchDog Timer (WDT) Driver or Device is.
13 with a WatchDog Timer. If you want to know this then please read the following
14 file: Documentation/watchdog/watchdog-api.rst .
17 WatchDog Timer Drivers that want to use the WatchDog Timer Driver Core
20 a watchdog timer driver then only needs to provide the different routines
21 (operations) that control the watchdog timer (WDT).
25 Each watchdog timer driver that wants to use the WatchDog Timer Driver Core
26 must #include <linux/watchdog.h> (you would have to do this anyway when
27 writing a watchdog device driver). This include file contains following
[all …]
|
| D | watchdog-parameters.rst | 2 WatchDog Module Parameters
6 the Linux watchdog drivers. Watchdog driver parameter specs should
16 watchdog core:
18 Maximum time, in seconds, for which the watchdog framework will take
19 care of pinging a running hardware watchdog until userspace opens the
33 Watchdog cannot be stopped once started
44 Watchdog timeout in seconds. 1<= timeout <=63, default=60.
46 Watchdog cannot be stopped once started
53 Watchdog timeout in seconds. (0 < timeout < 18000, default=60
55 Watchdog cannot be stopped once started
[all …]
|
| D | mlx-wdt.rst | 2 Mellanox watchdog drivers
8 This driver provides watchdog functionality for various Mellanox
11 Mellanox watchdog device is implemented in a programmable logic device.
13 There are 2 types of HW watchdog implementations.
31 Type 1 HW watchdog implementation exist in old systems and
32 all new systems have type 2 HW watchdog.
35 Type 3 HW watchdog implementation can exist on all Mellanox systems
38 Old systems still have only one main watchdog.
41 Main and auxiliary watchdog devices can be enabled together
43 There are several actions that can be defined in the watchdog:
[all …]
|
| D | watchdog-api.rst | 2 The Linux Watchdog driver API
19 A Watchdog Timer (WDT) is a hardware circuit that can reset the
23 Usually a userspace daemon will notify the kernel watchdog driver via the
24 /dev/watchdog special device file that userspace is still alive, at
26 usually tell the hardware watchdog that everything is in order, and
27 that the watchdog should wait for yet another little while to reset
29 notifications cease to occur, and the hardware watchdog will reset the
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/watchdog/ |
| D | watchdog-kernel-api.rst | 2 The Linux WatchDog Timer Driver Core kernel API
11 This document does not describe what a WatchDog Timer (WDT) Driver or Device is.
13 with a WatchDog Timer. If you want to know this then please read the following
14 file: Documentation/watchdog/watchdog-api.rst .
17 WatchDog Timer Drivers that want to use the WatchDog Timer Driver Core
20 a watchdog timer driver then only needs to provide the different routines
21 (operations) that control the watchdog timer (WDT).
25 Each watchdog timer driver that wants to use the WatchDog Timer Driver Core
26 must #include <linux/watchdog.h> (you would have to do this anyway when
27 writing a watchdog device driver). This include file contains following
[all …]
|
| D | watchdog-parameters.rst | 2 WatchDog Module Parameters
6 the Linux watchdog drivers. Watchdog driver parameter specs should
16 watchdog core:
18 Maximum time, in seconds, for which the watchdog framework will take
19 care of pinging a running hardware watchdog until userspace opens the
33 Watchdog cannot be stopped once started
44 Watchdog timeout in seconds. 1<= timeout <=63, default=60.
46 Watchdog cannot be stopped once started
53 Watchdog timeout in seconds. (0 < timeout < 18000, default=60
55 Watchdog cannot be stopped once started
[all …]
|
| D | mlx-wdt.rst | 2 Mellanox watchdog drivers
8 This driver provides watchdog functionality for various Mellanox
11 Mellanox watchdog device is implemented in a programmable logic device.
13 There are 2 types of HW watchdog implementations.
31 Type 1 HW watchdog implementation exist in old systems and
32 all new systems have type 2 HW watchdog.
35 Type 3 HW watchdog implementation can exist on all Mellanox systems
38 Old systems still have only one main watchdog.
41 Main and auxiliary watchdog devices can be enabled together
43 There are several actions that can be defined in the watchdog:
[all …]
|
| D | watchdog-api.rst | 2 The Linux Watchdog driver API
19 A Watchdog Timer (WDT) is a hardware circuit that can reset the
23 Usually a userspace daemon will notify the kernel watchdog driver via the
24 /dev/watchdog special device file that userspace is still alive, at
26 usually tell the hardware watchdog that everything is in order, and
27 that the watchdog should wait for yet another little while to reset
29 notifications cease to occur, and the hardware watchdog will reset the
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
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/watchdog/ |
| D | da9062-wdt.txt | 1 * Dialog Semiconductor DA9062/61 Watchdog Timer
6 "dlg,da9061-watchdog", "dlg,da9062-watchdog"
7 "dlg,da9062-watchdog"
10 - dlg,use-sw-pm: Add this property to disable the watchdog during suspend.
11 Only use this option if you can't use the watchdog automatic suspend
13 - dlg,wdt-sd: Set what happens on watchdog timeout. If this bit is set the
14 watchdog timeout triggers SHUTDOWN, if cleared the watchdog triggers
17 set the WATCHDOG_SD bit and on timeout watchdog behavior will match the
23 watchdog {
24 compatible = "dlg,da9062-watchdog";
[all …]
|
| D | atmel,sama5d4-wdt.yaml | 4 $id: http://devicetree.org/schemas/watchdog/atmel,sama5d4-wdt.yaml#
7 title: Atmel SAMA5D4 Watchdog Timer (WDT) Controller
13 - $ref: watchdog.yaml#
28 atmel,watchdog-type:
33 Enable watchdog fault reset. A watchdog fault triggers
34 watchdog reset.
37 Enable watchdog fault interrupt. A watchdog fault asserts
38 watchdog interrupt.
45 present if you want to stop the watchdog when the CPU is in idle state.
47 watchdog not counting when the CPU is in idle state, therefore the
[all …]
|
| D | atmel,at91sam9-wdt.yaml | 5 $id: http://devicetree.org/schemas/watchdog/atmel,at91sam9-wdt.yaml#
8 title: Atmel Watchdog Timers
39 atmel,watchdog-type:
45 Hardware watchdog uses the at91 watchdog reset.
48 Software watchdog uses the watchdog interrupt
56 Should be proc or all. This is valid only when using hardware watchdog.
69 Should be present if you want to stop the watchdog.
74 Should be present if you want to stop the watchdog when
77 watchdog not counting when the CPU is in idle state, therefore the
78 watchdog reset time depends on mean CPU usage and will not reset at all
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | watchdog.h | 3 * Generic watchdog defines. Derived from..
5 * Berkshire PC Watchdog Defines
18 #include <uapi/linux/watchdog.h>
25 /** struct watchdog_ops - The watchdog-devices operations
28 * @start: The routine for starting the watchdog device.
29 * @stop: The routine for stopping the watchdog device.
30 * @ping: The routine that sends a keepalive ping to the watchdog device.
31 * @status: The routine that shows the status of the watchdog device.
32 * @set_timeout:The routine for setting the watchdog devices timeout value (in seconds).
33 * @set_pretimeout:The routine for setting the watchdog devices pretimeout.
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | watchdog.h | 3 * Generic watchdog defines. Derived from..
5 * Berkshire PC Watchdog Defines
18 #include <uapi/linux/watchdog.h>
25 /** struct watchdog_ops - The watchdog-devices operations
28 * @start: The routine for starting the watchdog device.
29 * @stop: The routine for stopping the watchdog device.
30 * @ping: The routine that sends a keepalive ping to the watchdog device.
31 * @status: The routine that shows the status of the watchdog device.
32 * @set_timeout:The routine for setting the watchdog devices timeout value (in seconds).
33 * @set_pretimeout:The routine for setting the watchdog devices pretimeout.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | atmel-sama5d4-wdt.txt | 1 * Atmel SAMA5D4 Watchdog Timer (WDT) Controller
8 - timeout-sec: watchdog timeout value (in seconds).
10 - atmel,watchdog-type: should be "hardware" or "software".
11 "hardware": enable watchdog fault reset. A watchdog fault triggers
12 watchdog reset.
13 "software": enable watchdog fault interrupt. A watchdog fault asserts
14 watchdog interrupt.
15 - atmel,idle-halt: present if you want to stop the watchdog when the CPU is
18 watchdog not counting when the CPU is in idle state, therefore the
19 watchdog reset time depends on mean CPU usage and will not reset at all
[all …]
|
| D | da9062-wdt.txt | 1 * Dialog Semiconductor DA9062/61 Watchdog Timer
6 "dlg,da9061-watchdog", "dlg,da9062-watchdog"
7 "dlg,da9062-watchdog"
10 - dlg,use-sw-pm: Add this property to disable the watchdog during suspend.
11 Only use this option if you can't use the watchdog automatic suspend
17 watchdog {
18 compatible = "dlg,da9062-watchdog";
22 Example: DA9061 using a fall-back compatible for the DA9062 watchdog driver
25 watchdog {
26 compatible = "dlg,da9061-watchdog", "dlg,da9062-watchdog";
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 1 What: /sys/class/watchdog/watchdogn/bootstatus
5 It is a read only file. It contains status of the watchdog
9 What: /sys/class/watchdog/watchdogn/options
13 It is a read only file. It contains options of watchdog device.
15 What: /sys/class/watchdog/watchdogn/fw_version
20 watchdog device.
22 What: /sys/class/watchdog/watchdogn/identity
27 watchdog device.
29 What: /sys/class/watchdog/watchdogn/nowayout
41 What: /sys/class/watchdog/watchdogn/state
[all …]
|