| /linux/drivers/greybus/ |
| H A 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/Documentation/translations/zh_CN/admin-guide/ |
| H A 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/Documentation/translations/zh_TW/admin-guide/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A D | sysfs-bus-siox | 7 expected to not do anything because their watchdog triggered. 71 What: /sys/bus/siox/devices/siox-X-Y/watchdog 75 Read-only value reporting if the watchdog of the siox device is 76 active. "0" means the watchdog is not active and the device is expected to 77 be operational. "1" means the watchdog keeps the device in reset. 84 watchdog was active.
|
| /linux/Documentation/watchdog/ |
| H A 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 …]
|
| H A D | watchdog-parameters.rst | 6 the Linux watchdog drivers. Watchdog driver parameter specs should 16 watchdog core: 23 Maximum time, in seconds, for which the watchdog framework will take 24 care of pinging a running hardware watchdog until userspace opens the 73 Use the gpio watchdog (required by old cobalt boards). 85 Disable watchdog shutdown on close 94 Disable watchdog shutdown on close 264 Disable watchdog shutdown on close 274 system resets despite watchdog daemon running, default=0 335 Initial watchdog timeout in seconds (0<timeout<516, default=60) [all …]
|
| H A D | watchdog-pm.rst | 11 This document states rules about watchdog devices and their power management 17 On resume, a watchdog timer shall be reset to its selected value to give
|
| /linux/Documentation/ABI/stable/ |
| H A 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/drivers/gpu/drm/imagination/ |
| H A D | pvr_power.c | 98 cancel_delayed_work_sync(&pvr_dev->watchdog.work); in pvr_power_fw_disable() 140 queue_delayed_work(pvr_dev->sched_wq, &pvr_dev->watchdog.work, in pvr_power_fw_enable() 172 if (pvr_dev->watchdog.old_kccb_cmds_executed == kccb_cmds_executed && !kccb_is_idle) { in pvr_watchdog_kccb_stalled() 173 pvr_dev->watchdog.kccb_stall_count++; in pvr_watchdog_kccb_stalled() 179 if (pvr_dev->watchdog.kccb_stall_count == 2) { in pvr_watchdog_kccb_stalled() 180 pvr_dev->watchdog.kccb_stall_count = 0; in pvr_watchdog_kccb_stalled() 183 } else if (pvr_dev->watchdog.old_kccb_cmds_executed == kccb_cmds_executed) { in pvr_watchdog_kccb_stalled() 199 pvr_dev->watchdog.old_kccb_cmds_executed = kccb_cmds_executed; in pvr_watchdog_kccb_stalled() 200 pvr_dev->watchdog.kccb_stall_count = 0; in pvr_watchdog_kccb_stalled() 210 watchdog.work.work); in pvr_watchdog_worker() [all …]
|
| /linux/Documentation/driver-api/mei/ |
| H A 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/Documentation/devicetree/bindings/power/reset/ |
| H A 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/arch/arm/boot/dts/ti/omap/ |
| H A D | dra7-ipu-dsp-common.dtsi | 26 ti,watchdog-timers = <&timer4>, <&timer9>; 32 ti,watchdog-timers = <&timer7>, <&timer8>; 38 ti,watchdog-timers = <&timer10>;
|
| /linux/Documentation/devicetree/bindings/watchdog/ |
| H A D | st_lpc_wdt.txt | 22 Required properties [watchdog mode] 24 - st,syscfg : Phandle to syscfg node used to enable watchdog and configure 28 Optional properties [watchdog mode]
|
| /linux/net/sched/ |
| H A D | sch_etf.c | 36 struct qdisc_watchdog watchdog; member 127 qdisc_watchdog_cancel(&q->watchdog); in reset_watchdog() 132 qdisc_watchdog_schedule_ns(&q->watchdog, ktime_to_ns(next)); in reset_watchdog() 194 /* Now we may need to re-arm the qdisc watchdog for the next packet. */ in etf_enqueue_timesortedlist() 290 /* Now we may need to re-arm the qdisc watchdog for the next packet. */ in etf_dequeue_timesortedlist() 412 qdisc_watchdog_init_clockid(&q->watchdog, sch, q->clockid); in etf_init() 437 /* Only cancel watchdog if it's been initialized. */ in etf_reset() 438 if (q->watchdog.qdisc == sch) in etf_reset() 439 qdisc_watchdog_cancel(&q->watchdog); in etf_reset() 453 /* Only cancel watchdog i in etf_destroy() [all...] |
| H A D | sch_cbs.c | 80 struct qdisc_watchdog watchdog; member 187 qdisc_watchdog_schedule_ns(&q->watchdog, q->last); in cbs_dequeue_soft() 200 qdisc_watchdog_schedule_ns(&q->watchdog, now + delay); in cbs_dequeue_soft() 255 qdisc_watchdog_cancel(&q->watchdog); in cbs_reset() 442 qdisc_watchdog_init(&q->watchdog, sch); in cbs_init() 456 qdisc_watchdog_cancel(&q->watchdog); in cbs_destroy()
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | mpc5200.txt | 104 On the mpc5200 and 5200b, GPT0 has a watchdog timer function. If the board 107 the watchdog. The timer will function as a GPT if the timer api is used, and 108 it will function as watchdog if the watchdog device is used. The watchdog 109 mode has priority over the gpt mode, i.e. if the watchdog is activated, any 114 GPT0 will be marked as in-use watchdog, i.e. blocking every gpt access to it. 115 If n>0, the watchdog is started with a timeout of n seconds. If n=0, the 116 configuration of the watchdog is not touched. This is useful in two cases: 117 - just mark GPT0 as watchdog, blocking gpt accesses, and configure it later; 121 The watchdog will respect the CONFIG_WATCHDOG_NOWAYOUT option.
|
| /linux/arch/powerpc/boot/dts/ |
| H A D | turris1x.dts | 355 /* MAX6370KA+T watchdog */ 356 watchdog@2 { 372 * watchdog registers has bugs. It does not 374 * and watchdog ignores reset line on immediate 375 * succeeding reset cycle triggered by watchdog. 379 * do not have workaround for watchdog. 383 * watchdog has priority level 0 and default 387 * level 64 (between rstcr and watchdog) because 389 * method and reset via watchdog is more broken
|
| /linux/Documentation/arch/mips/ |
| H A D | ingenic-tcu.rst | 21 - The watchdog and OST hardware blocks also feature a TCSR register with the same 23 - The TCU registers used to gate/ungate can also gate/ungate the watchdog and 63 watchdog drivers/watchdog/jz4740_wdt.c
|
| /linux/arch/arm/boot/dts/mediatek/ |
| H A D | mt7629-rfb.dts | 241 watchdog_pins: watchdog-pins { 243 function = "watchdog"; 244 groups = "watchdog"; 271 &watchdog {
|
| /linux/arch/arm/boot/dts/moxa/ |
| H A D | moxart.dtsi | 89 watchdog: watchdog@98500000 { label 90 compatible = "moxa,moxart-watchdog", "faraday,ftwdt010";
|
| /linux/sound/soc/cirrus/ |
| H A D | Kconfig | 22 bool "IRQ based underflow watchdog workaround" 28 until I2S is disabled. This option enables IRQ based watchdog
|
| /linux/Documentation/hwmon/ |
| H A D | sch5636.rst | 32 The Fujitsu Theseus hwmon solution also contains an integrated watchdog. 33 This watchdog is fully supported by the sch5636 driver.
|
| /linux/arch/powerpc/boot/dts/fsl/ |
| H A D | gef_sbc610.dts | 85 watchdog@4,2000 { 91 /* Second watchdog available, driver currently supports one. 92 watchdog@4,2010 {
|
| /linux/arch/m68k/mvme147/ |
| H A D | config.c | 55 m147_pcc->watchdog = 0x0a; /* Clear timer */ in mvme147_reset() 56 m147_pcc->watchdog = 0xa5; /* Enable watchdog - 100ms to reset */ in mvme147_reset()
|