Home
last modified time | relevance | path

Searched refs:watchdog (Results 1 – 25 of 633) sorted by relevance

12345678910>>...26

/linux/drivers/greybus/
A Dsvc_watchdog.c70 svc = watchdog->svc; in do_work()
112 if (svc->watchdog) in gb_svc_watchdog_create()
115 watchdog = kmalloc(sizeof(*watchdog), GFP_KERNEL); in gb_svc_watchdog_create()
116 if (!watchdog) in gb_svc_watchdog_create()
122 svc->watchdog = watchdog; in gb_svc_watchdog_create()
142 kfree(watchdog); in gb_svc_watchdog_create()
149 struct gb_svc_watchdog *watchdog = svc->watchdog; in gb_svc_watchdog_destroy() local
151 if (!watchdog) in gb_svc_watchdog_destroy()
157 kfree(watchdog); in gb_svc_watchdog_destroy()
174 watchdog = svc->watchdog; in gb_svc_watchdog_enable()
[all …]
/linux/drivers/watchdog/
A D.built-in.a.cmd1 …watchdog/built-in.a := echo >/dev/null; rm -f drivers/watchdog/built-in.a; /usr/bin/ccache /home/t…
A DKconfig21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
23 The watchdog is usually used together with the watchdog daemon
113 Panic watchdog pretimeout governor, on watchdog pretimeout
168 watchdog. Be aware that governors might affect the watchdog because it
1034 Enables watchdog timer support for the watchdog timer on the
1297 watchdog cards as found on the SC1200. This watchdog is mainly used
1624 watchdog timer.
1864 Please see Documentation/watchdog/watchdog-api.rst for
1876 Book-E watchdog driver. A watchdog "event" occurs when the bit
1902 This driver adds watchdog support for the RTAS watchdog.
[all …]
/linux/Documentation/watchdog/
A Dwatchdog-kernel-api.rst14 file: Documentation/watchdog/watchdog-api.rst .
45 The watchdog device structure looks like this::
81 * ops: a pointer to the list of watchdog operations that the watchdog supports.
140 module and /dev/watchdog is still open).
175 the watchdog timer driver core does: to send a keepalive ping to the watchdog
202 watchdog's info structure).
223 watchdog's info structure).
247 * WDOG_HW_RUNNING: Set by the watchdog driver if the hardware watchdog is
250 booting, before the watchdog device is opened. If set, the watchdog
309 To disable the watchdog when unregistering the watchdog, the user must call
[all …]
A Dmlx-wdt.rst2 Mellanox watchdog drivers
8 This driver provides watchdog functionality for various Mellanox
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.
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:
49 pinged by watchdog core before watchdog device will be opened by
54 This mlx-wdt driver supports both HW watchdog implementations.
[all …]
A Dwatchdog-api.rst24 /dev/watchdog special device file that userspace is still alive, at
45 like this source file: see samples/watchdog/watchdog-simple.c
78 Pinging the watchdog using an ioctl:
138 Not all watchdog drivers will support a pretimeout.
164 identity a string identifying the watchdog driver
184 A system fan monitored by the watchdog card has failed
210 The last reboot was caused by the watchdog card
224 The watchdog saw a keepalive ping since it was last queried.
230 The watchdog can do pretimeouts.
266 WDIOS_DISABLECARD Turn off the watchdog timer
[all …]
A Dhpwdt.rst12 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
50 interface to /dev/watchdog can be found in
51 Documentation/watchdog/watchdog-api.rst and Documentation/IPMI.txt.
[all …]
A Dindex.rst12 pcwd-watchdog
13 watchdog-api
14 watchdog-kernel-api
15 watchdog-parameters
16 watchdog-pm
A Dpcwd-watchdog.rst22 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/Documentation/devicetree/bindings/watchdog/
A Dda9062-wdt.txt6 "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";
A Datmel,sama5d4-wdt.yaml4 $id: http://devicetree.org/schemas/watchdog/atmel,sama5d4-wdt.yaml#
13 - $ref: "watchdog.yaml#"
25 atmel,watchdog-type:
30 Enable watchdog fault reset. A watchdog fault triggers
31 watchdog reset.
34 Enable watchdog fault interrupt. A watchdog fault asserts
35 watchdog interrupt.
42 present if you want to stop the watchdog when the CPU is in idle state.
44 watchdog not counting when the CPU is in idle state, therefore the
64 watchdog@fc068640 {
[all …]
A Datmel-wdt.txt12 - 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 …]
A Dwatchdog.yaml4 $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.
A Darm,sp805.yaml4 $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 {
A Dzii,rave-sp-wdt.txt3 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";
A Dti,rti-wdt.yaml4 $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#"
55 * select the source clock for the watchdog, forcing it to tick with
60 watchdog@2200000 {
A Dfaraday,ftwdt010.txt1 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 {
A Dlantiq-wdt.txt1 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 {
A Dsocionext,uniphier-wdt.yaml4 $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 {
A Daspeed-wdt.txt16 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 {
/linux/Documentation/translations/zh_CN/admin-guide/
A Dlockup-watchdogs.rst37 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/
A Dsysfs-class-watchdog1 What: /sys/class/watchdog/watchdogn/bootstatus
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
43 What: /sys/class/watchdog/watchdogn/timeleft
51 What: /sys/class/watchdog/watchdogn/timeout
58 What: /sys/class/watchdog/watchdogn/pretimeout
[all …]
/linux/Documentation/devicetree/bindings/timer/
A Dingenic,tcu.yaml114 "^watchdog@[a-f0-9]+$":
116 $ref: ../watchdog/watchdog.yaml#
121 - ingenic,jz4740-watchdog
122 - ingenic,jz4780-watchdog
125 - ingenic,jz4770-watchdog
126 - ingenic,jz4760b-watchdog
127 - ingenic,jz4760-watchdog
128 - ingenic,jz4725b-watchdog
129 - const: ingenic,jz4740-watchdog
262 watchdog: watchdog@0 {
[all …]
/linux/Documentation/devicetree/bindings/mfd/
A Drohm,bd9576-pmic.yaml16 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/kernel/time/
A Dclocksource.c216 *wdnow = watchdog->read(watchdog); in cs_watchdog_read()
218 wd_end = watchdog->read(watchdog); in cs_watchdog_read()
411 watchdog->name, wd_nsec, wdnow, wdlast, watchdog->mask); in clocksource_watchdog()
537 old_wd = watchdog; in clocksource_select_watchdog()
539 watchdog = NULL; in clocksource_select_watchdog()
551 if (!watchdog || cs->rating > watchdog->rating) in clocksource_select_watchdog()
552 watchdog = cs; in clocksource_select_watchdog()
555 if (!watchdog) in clocksource_select_watchdog()
556 watchdog = old_wd; in clocksource_select_watchdog()
569 if (cs != watchdog) { in clocksource_dequeue_watchdog()
[all …]

Completed in 37 milliseconds

12345678910>>...26