| /linux-6.12.1/drivers/greybus/ |
| D | svc_watchdog.c | 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()
109 struct gb_svc_watchdog *watchdog; in gb_svc_watchdog_create() local
[all …]
|
| /linux-6.12.1/Documentation/watchdog/ |
| D | watchdog-kernel-api.rst | 14 file: Documentation/watchdog/watchdog-api.rst .
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
33 The watchdog_register_device routine registers a watchdog timer device.
37 The watchdog_unregister_device routine deregisters a registered watchdog timer
41 The watchdog subsystem includes an registration deferral mechanism,
42 which allows you to register an watchdog as early as you wish during
[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 | 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
42 the watchdog is pinged within a certain time, this time is called the
43 timeout or margin. The simplest way to ping the watchdog is to write
[all …]
|
| D | hpwdt.rst | 12 watchdog functionality and handler for the iLO "Generate NMI to System"
18 Watchdog functionality is enabled like any other common watchdog driver. That
19 is, an application needs to be started that kicks off the watchdog timer. A
20 basic application exists in tools/testing/selftests/watchdog/ named
21 watchdog-test.c. Simply compile the C file and kick it off. If the system
29 soft_margin allows the user to set the watchdog timer value.
32 pretimeout allows the user to set the watchdog pretimeout value.
37 nowayout basic watchdog parameter that does not allow the timer to
40 to "Y", then there is no way of disabling the watchdog once
43 before calling panic. (-1) disables the watchdog. When value
[all …]
|
| D | index.rst | 12 pcwd-watchdog
13 watchdog-api
14 watchdog-kernel-api
15 watchdog-parameters
16 watchdog-pm
|
| D | pcwd-watchdog.rst | 22 The Watchdog Driver will automatically find your watchdog card, and will
23 attach a running driver for use with that card. After the watchdog
27 I suggest putting a "watchdog -d" before the beginning of an fsck, and
28 a "watchdog -e -t 1" immediately after the end of an fsck. (Remember
32 driver, simply use of modify the watchdog test program:
33 tools/testing/selftests/watchdog/watchdog-test.c
50 are in include/uapi/linux/watchdog.h)
58 read /dev/watchdog, which gives a temperature update
|
| D | watchdog-parameters.rst | 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
64 Use the gpio watchdog (required by old cobalt boards).
76 Disable watchdog shutdown on close
85 Disable watchdog shutdown on close
125 base address of watchdog card, default is 0x91
272 Disable watchdog shutdown on close
282 system resets despite watchdog daemon running, default=0
[all …]
|
| D | convert_drivers_to_kernel_api.rst | 2 Converting old watchdog drivers to the watchdog framework
7 Before the watchdog framework came into the kernel, every driver had to
58 do limit-checking, if min_timeout and max_timeout in the watchdog
97 - .name = "watchdog",
113 Add the watchdog operations
117 explained in 'watchdog-kernel-api.txt' in this directory. start() and
151 Add the watchdog device
156 in 'watchdog-kernel-api.txt' in this directory. We pass it the mandatory
163 Here is a simple example for a watchdog device::
190 Register the watchdog device
[all …]
|
| /linux-6.12.1/drivers/watchdog/ |
| D | Kconfig | 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
36 Say Y here if you want to use the new watchdog timer driver core.
37 This driver provides a framework for all watchdog timer drivers
38 and gives them the /dev/watchdog interface (and later also the
[all …]
|
| /linux-6.12.1/Documentation/translations/zh_CN/admin-guide/ |
| D | lockup-watchdogs.rst | 37 Hrtimer用于周期性产生中断并唤醒watchdog线程；NMI perf事件则以”watchdog_thresh“
43 而watchdog线程本质上是一个高优先级内核线程，每调度一次就对时间戳进行一次更新。
55 默认情况下所有在线cpu上都会运行一个watchdog线程。不过在内核配置了”NO_HZ_FULL“的
56 情况下watchdog线程默认只会运行在管家(housekeeping)cpu上，而”nohz_full“启动参数指
57 定的cpu上则不会有watchdog线程运行。试想，如果我们允许watchdog线程在”nohz_full“指
58 定的cpu上运行，这些cpu上必须得运行时钟定时器来激发watchdog线程调度；这样一来就会
60 的cpu即使在内核产生了lockup问题我们也无法检测到。不过，至少我们可以允许watchdog
64 不论哪种情况都可以通过sysctl命令kernel.watchdog_cpumask来对没有运行watchdog线程
66 这种方式打开这些cpu上的watchdog进行调试可能会有所作用。
|
| /linux-6.12.1/Documentation/translations/zh_TW/admin-guide/ |
| D | lockup-watchdogs.rst | 37 Hrtimer用於週期性產生中斷並喚醒watchdog線程；NMI perf事件則以”watchdog_thresh“
43 而watchdog線程本質上是一個高優先級內核線程，每調度一次就對時間戳進行一次更新。
55 默認情況下所有在線cpu上都會運行一個watchdog線程。不過在內核配置了”NO_HZ_FULL“的
56 情況下watchdog線程默認只會運行在管家(housekeeping)cpu上，而”nohz_full“啓動參數指
57 定的cpu上則不會有watchdog線程運行。試想，如果我們允許watchdog線程在”nohz_full“指
58 定的cpu上運行，這些cpu上必須得運行時鐘定時器來激發watchdog線程調度；這樣一來就會
60 的cpu即使在內核產生了lockup問題我們也無法檢測到。不過，至少我們可以允許watchdog
64 不論哪種情況都可以通過sysctl命令kernel.watchdog_cpumask來對沒有運行watchdog線程
66 這種方式打開這些cpu上的watchdog進行調試可能會有所作用。
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/drivers/gpu/drm/imagination/ |
| D | pvr_power.c | 92 cancel_delayed_work_sync(&pvr_dev->watchdog.work); in pvr_power_fw_disable()
122 queue_delayed_work(pvr_dev->sched_wq, &pvr_dev->watchdog.work, in pvr_power_fw_enable()
148 if (pvr_dev->watchdog.old_kccb_cmds_executed == kccb_cmds_executed && !kccb_is_idle) { in pvr_watchdog_kccb_stalled()
149 pvr_dev->watchdog.kccb_stall_count++; in pvr_watchdog_kccb_stalled()
155 if (pvr_dev->watchdog.kccb_stall_count == 2) { in pvr_watchdog_kccb_stalled()
156 pvr_dev->watchdog.kccb_stall_count = 0; in pvr_watchdog_kccb_stalled()
159 } else if (pvr_dev->watchdog.old_kccb_cmds_executed == kccb_cmds_executed) { in pvr_watchdog_kccb_stalled()
175 pvr_dev->watchdog.old_kccb_cmds_executed = kccb_cmds_executed; in pvr_watchdog_kccb_stalled()
176 pvr_dev->watchdog.kccb_stall_count = 0; in pvr_watchdog_kccb_stalled()
186 watchdog.work.work); in pvr_watchdog_worker()
[all …]
|
| /linux-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 126 temperature and external watchdog. Here, the external watchdog
127 is completely different than the /dev/watchdog as the external
128 watchdog is running on the firmware and it is used to monitor
130 watchdog is interfaced outside of the zynqmp soc.
138 the external watchdog feature.
140 external watchdog feature.
158 Select external watchdog config ID to enable/disable feature
161 Check external watchdog config ID is selected or not
165 Select external watchdog config ID to configure time interval
168 Check external watchdog config ID is selected or not
[all …]
|
| /linux-6.12.1/kernel/time/ |
| D | clocksource.c | 155 static struct clocksource *watchdog; variable
247 int64_t md = 2 * watchdog->uncertainty_margin; in cs_watchdog_read()
255 *wdnow = watchdog->read(watchdog); in cs_watchdog_read()
257 wd_end = watchdog->read(watchdog); in cs_watchdog_read()
258 wd_end2 = watchdog->read(watchdog); in cs_watchdog_read()
261 wd_delay = cycles_to_nsec_safe(watchdog, *wdnow, wd_end); in cs_watchdog_read()
265 smp_processor_id(), watchdog->name, nretries); in cs_watchdog_read()
279 wd_seq_delay = cycles_to_nsec_safe(watchdog, wd_end, wd_end2); in cs_watchdog_read()
290 smp_processor_id(), watchdog->name, wd_seq_delay); in cs_watchdog_read()
479 wd_nsec = cycles_to_nsec_safe(watchdog, cs->wd_last, wdnow); in clocksource_watchdog()
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/watchdog/ |
| D | zii,rave-sp-wdt.txt | 3 RAVE SP watchdog device is a "MFD cell" device corresponding to
4 watchdog functionality of RAVE Supervisory Processor. It is expected
13 - "zii,rave-sp-watchdog"
14 - "zii,rave-sp-watchdog-legacy"
33 watchdog {
34 compatible = "zii,rave-sp-watchdog";
|
| D | lantiq-wdt.txt | 1 Lantiq WTD watchdog binding
4 This describes the binding of the Lantiq watchdog driver.
13 - reg : Address of the watchdog block
18 Example for the watchdog on the xRX200 SoCs:
19 watchdog@803f0 {
|
| D | moxa,moxart-watchdog.txt | 5 - compatible : Must be "moxa,moxart-watchdog"
11 watchdog: watchdog@98500000 {
12 compatible = "moxa,moxart-watchdog";
|
| D | nuvoton,npcm-wdt.txt | 3 Nuvoton NPCM timer module provides five 24-bit timer counters, and a watchdog.
4 The watchdog supports a pre-timeout interrupt that fires 10ms before the
21 - timeout-sec : Contains the watchdog timeout in seconds
|
| /linux-6.12.1/Documentation/driver-api/mei/ |
| D | iamt.rst | 82 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
90 2) Intel MEI iAMT watchdog driver - connects to the watchdog feature,
91 configures the watchdog and sends the heartbeats.
93 The Intel iAMT watchdog MEI driver uses the kernel watchdog API to configure
95 watchdog is 120 seconds.
97 If the Intel AMT is not enabled in the firmware then the watchdog client won't enumerate
98 on the me client bus and watchdog devices won't be exposed.
|
| /linux-6.12.1/Documentation/devicetree/bindings/power/reset/ |
| D | ltc2952-poweroff.txt | 4 been sent, the chip's watchdog has to be reset to gracefully shut down.
10 - watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
11 chip's watchdog line
31 watchdog-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
|
| /linux-6.12.1/arch/arm/boot/dts/ti/omap/ |
| D | dra7-ipu-dsp-common.dtsi | 26 ti,watchdog-timers = <&timer4>, <&timer9>;
32 ti,watchdog-timers = <&timer7>, <&timer8>;
38 ti,watchdog-timers = <&timer10>;
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | lockup-watchdogs.rst | 5 The Linux kernel can act as a watchdog to detect both soft and hard
41 A periodic hrtimer runs to generate interrupts and kick the watchdog
50 The watchdog job runs in a stop scheduling thread that updates a
67 By default, the watchdog runs on all online cores. However, on a
68 kernel configured with NO_HZ_FULL, by default the watchdog runs only
70 boot argument. If we allowed the watchdog to run by default on
76 able to detect if they lock up. However, allowing the watchdog
80 In either case, the set of cores excluded from running the watchdog
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | sch5627.rst | 28 watchdog. In order for this watchdog to function some motherboard specific
29 initialization most be done by the BIOS, so if the watchdog is not enabled
30 by the BIOS the sch5627 driver will not register a watchdog device.
|