| /Linux-v5.15/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-v5.15/drivers/watchdog/ |
| D | f71808e_wdt.c | 155 static struct watchdog_data watchdog = { variable
156 .lock = __MUTEX_INITIALIZER(watchdog.lock),
229 mutex_lock(&watchdog.lock); in watchdog_set_timeout()
231 watchdog.timeout = timeout; in watchdog_set_timeout()
233 watchdog.timer_val = DIV_ROUND_UP(timeout, 60); in watchdog_set_timeout()
234 watchdog.minutes_mode = true; in watchdog_set_timeout()
236 watchdog.timer_val = timeout; in watchdog_set_timeout()
237 watchdog.minutes_mode = false; in watchdog_set_timeout()
240 mutex_unlock(&watchdog.lock); in watchdog_set_timeout()
250 if (watchdog.type == f71868) { in watchdog_set_pulse_width()
[all …]
|
| 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-v5.15/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
|
| /Linux-v5.15/Documentation/devicetree/bindings/watchdog/ |
| D | da9062-wdt.txt | 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";
|
| D | atmel-wdt.txt | 12 - timeout-sec: contains the watchdog timeout in seconds.
20 - atmel,watchdog-type : Should be "hardware" or "software". Hardware watchdog
21 use the at91 watchdog reset. Software watchdog use the watchdog
26 This is valid only when using "hardware" watchdog.
27 - atmel,disable : Should be present if you want to disable the watchdog.
28 - atmel,idle-halt : Should be present if you want to stop the watchdog when
31 watchdog not counting when the CPU is in idle state, therefore the
32 watchdog reset time depends on mean CPU usage and will not reset at all
35 - atmel,dbg-halt : Should be present if you want to stop the watchdog when
39 watchdog@fffffd40 {
[all …]
|
| D | faraday,ftwdt010.txt | 1 Faraday Technology FTWDT010 watchdog
9 "cortina,gemini-watchdog", "faraday,ftwdt010"
11 - interrupts : shall contain the interrupt for the watchdog
14 - timeout-sec : the default watchdog timeout in seconds.
18 watchdog@41000000 {
|
| 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 | aspeed-wdt.txt | 16 Reset behavior - Whenever a timeout occurs the watchdog can be programmed
20 This is useful in situations where another watchdog engine on chip is
28 - cpu: Reset CPU on watchdog timeout
30 - soc: Reset 'System on Chip' on watchdog timeout
32 - system: Reset system on watchdog timeout
34 - none: No reset is performed on timeout. Assumes another watchdog
52 wdt1: watchdog@1e785000 {
|
| D | gpio-wdt.txt | 9 the WDT counter. The watchdog timer is disabled when GPIO is
14 - hw_margin_ms: Maximum time to reset watchdog circuit (milliseconds).
17 - always-running: If the watchdog timer cannot be disabled, add this flag to
22 watchdog: watchdog {
|
| D | digicolor-wdt.txt | 3 The watchdog functionality in Conexant Digicolor SoCs relies on the so called
6 used as watchdog.
16 - timeout-sec : Contains the watchdog timeout in seconds
20 watchdog@f0000fc0 {
|
| D | realtek,rtd119x.txt | 6 - compatible : Should be "realtek,rtd1295-watchdog"
13 watchdog@98007680 {
14 compatible = "realtek,rtd1295-watchdog";
|
| D | pnx4008-wdt.txt | 1 * NXP PNX watchdog timer
9 - timeout-sec: contains the watchdog timeout in seconds.
13 watchdog@4003c000 {
|
| D | alphascale-asm9260.txt | 7 - clocks : the clocks feeding the watchdog timer. See clock-bindings.txt
12 line index for the watchdog.
16 - timeout-sec : shall contain the default watchdog timeout in seconds,
25 watchdog0: watchdog@80048000 {
|
| /Linux-v5.15/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-v5.15/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/identity
14 watchdog device.
16 What: /sys/class/watchdog/watchdogn/nowayout
28 What: /sys/class/watchdog/watchdogn/state
33 watchdog device.
35 What: /sys/class/watchdog/watchdogn/status
39 It is a read only file. It contains watchdog device's
43 What: /sys/class/watchdog/watchdogn/timeleft
[all …]
|
| /Linux-v5.15/kernel/time/ |
| D | clocksource.c | 117 static struct clocksource *watchdog; variable
216 *wdnow = watchdog->read(watchdog); in cs_watchdog_read()
218 wd_end = watchdog->read(watchdog); in cs_watchdog_read()
221 wd_delta = clocksource_delta(wd_end, *wdnow, watchdog->mask); in cs_watchdog_read()
222 wd_delay = clocksource_cyc2ns(wd_delta, watchdog->mult, in cs_watchdog_read()
223 watchdog->shift); in cs_watchdog_read()
227 smp_processor_id(), watchdog->name, nretries); in cs_watchdog_read()
234 smp_processor_id(), watchdog->name, wd_delay, nretries); in cs_watchdog_read()
391 delta = clocksource_delta(wdnow, cs->wd_last, watchdog->mask); in clocksource_watchdog()
392 wd_nsec = clocksource_cyc2ns(delta, watchdog->mult, in clocksource_watchdog()
[all …]
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | sch5627.rst | 24 watchdog. In order for this watchdog to function some motherboard specific
25 initialization most be done by the BIOS, so if the watchdog is not enabled
26 by the BIOS the sch5627 driver will not register a watchdog device.
|
