| /linux-6.1.9/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.1.9/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
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";
28 Example: DA9061 using a fall-back compatible for the DA9062 watchdog driver
[all …]
|
| D | atmel,sama5d4-wdt.yaml | 4 $id: http://devicetree.org/schemas/watchdog/atmel,sama5d4-wdt.yaml#
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
48 watchdog reset time depends on mean CPU usage and will not reset at all
[all …]
|
| D | atmel,at91sam9-wdt.yaml | 5 $id: http://devicetree.org/schemas/watchdog/atmel,at91sam9-wdt.yaml#
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
85 Should be present if you want to stop the watchdog when
[all …]
|
| D | faraday,ftwdt010.yaml | 4 $id: http://devicetree.org/schemas/watchdog/faraday,ftwdt010.yaml#
7 title: Faraday Technology FTWDT010 watchdog
18 - $ref: "watchdog.yaml#"
26 - cortina,gemini-watchdog
27 - moxa,moxart-watchdog
54 watchdog@41000000 {
61 watchdog: watchdog@98500000 {
62 compatible = "moxa,moxart-watchdog", "faraday,ftwdt010";
|
| D | watchdog.yaml | 4 $id: http://devicetree.org/schemas/watchdog/watchdog.yaml#
11 - Wim Van Sebroeck <wim@linux-watchdog.org>
15 describe watchdog devices in a device tree.
19 pattern: "^watchdog(@.*|-[0-9a-f])?$"
23 Contains the watchdog timeout in seconds.
|
| D | arm,sp805.yaml | 4 $id: http://devicetree.org/schemas/watchdog/arm,sp805.yaml#
13 The Arm SP805 IP implements a watchdog device, which triggers an interrupt
18 - $ref: /schemas/watchdog/watchdog.yaml#
43 Clocks driving the watchdog timer hardware. The first clock is used
44 for the actual watchdog counter. The second clock drives the register
65 watchdog@66090000 {
|
| D | ti,rti-wdt.yaml | 4 $id: http://devicetree.org/schemas/watchdog/ti,rti-wdt.yaml#
13 The TI K3 SoC watchdog timer is implemented via the RTI (Real Time
14 Interrupt) IP module. This timer adds a support for windowed watchdog
15 mode, which will signal an error if it is pinged outside the watchdog
21 - $ref: "watchdog.yaml#"
49 * select the source clock for the watchdog, forcing it to tick with
54 watchdog@2200000 {
|
| 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 | socionext,uniphier-wdt.yaml | 4 $id: http://devicetree.org/schemas/watchdog/socionext,uniphier-wdt.yaml#
7 title: Socionext UniPhier watchdog timer
13 - $ref: "watchdog.yaml#"
26 // The UniPhier watchdog should be a subnode of a "syscon" compatible node.
33 watchdog {
|
| D | sunplus,sp7021-wdt.yaml | 5 $id: http://devicetree.org/schemas/watchdog/sunplus,sp7021-wdt.yaml#
14 - $ref: watchdog.yaml#
22 - description: watchdog registers regions
41 watchdog: watchdog@9c000630 {
|
| D | samsung-wdt.yaml | 4 $id: http://devicetree.org/schemas/watchdog/samsung-wdt.yaml#
45 Index of CPU cluster on which watchdog is running (in case of Exynos850)
61 - $ref: watchdog.yaml#
87 - description: Source clock (driving watchdog counter)
90 - const: watchdog
103 - const: watchdog
110 watchdog@101d0000 {
115 clock-names = "watchdog";
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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.1.9/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.1.9/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-6.1.9/kernel/time/ |
| D | clocksource.c | 123 static struct clocksource *watchdog; variable
228 *wdnow = watchdog->read(watchdog); in cs_watchdog_read()
230 wd_end = watchdog->read(watchdog); in cs_watchdog_read()
231 wd_end2 = watchdog->read(watchdog); in cs_watchdog_read()
234 wd_delta = clocksource_delta(wd_end, *wdnow, watchdog->mask); in cs_watchdog_read()
235 wd_delay = clocksource_cyc2ns(wd_delta, watchdog->mult, in cs_watchdog_read()
236 watchdog->shift); in cs_watchdog_read()
240 smp_processor_id(), watchdog->name, nretries); in cs_watchdog_read()
254 wd_delta = clocksource_delta(wd_end2, wd_end, watchdog->mask); in cs_watchdog_read()
255 wd_seq_delay = clocksource_cyc2ns(wd_delta, watchdog->mult, watchdog->shift); in cs_watchdog_read()
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/timer/ |
| D | ingenic,tcu.yaml | 114 "^watchdog@[a-f0-9]+$":
116 $ref: /schemas/watchdog/watchdog.yaml#
123 - ingenic,jz4740-watchdog
124 - ingenic,jz4780-watchdog
127 - ingenic,jz4770-watchdog
128 - ingenic,jz4760b-watchdog
129 - ingenic,jz4760-watchdog
130 - ingenic,jz4725b-watchdog
131 - const: ingenic,jz4740-watchdog
267 watchdog: watchdog@0 {
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd9576-pmic.yaml | 16 monitoring. A watchdog logic with slow ping/windowed modes is also included.
53 rohm,watchdog-enable-gpios:
54 description: The GPIO line used to enable the watchdog.
57 rohm,watchdog-ping-gpios:
58 description: The GPIO line used to ping the watchdog.
65 the maximum timeout. Eg. if pinging watchdog is not done within this time
66 limit the watchdog will be triggered. If two values are given watchdog
68 Eg. if watchdog is pinged sooner than that the watchdog will trigger.
98 rohm,watchdog-enable-gpios = <&gpio2 6 GPIO_ACTIVE_HIGH>;
99 rohm,watchdog-ping-gpios = <&gpio2 7 GPIO_ACTIVE_HIGH>;
|
| /linux-6.1.9/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 …]
|