| /Linux-v4.19/drivers/staging/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-v4.19/drivers/watchdog/ |
| D | f71808e_wdt.c | 164 static struct watchdog_data watchdog = { variable
165 .lock = __MUTEX_INITIALIZER(watchdog.lock),
238 mutex_lock(&watchdog.lock); in watchdog_set_timeout()
240 watchdog.timeout = timeout; in watchdog_set_timeout()
242 watchdog.timer_val = DIV_ROUND_UP(timeout, 60); in watchdog_set_timeout()
243 watchdog.minutes_mode = true; in watchdog_set_timeout()
245 watchdog.timer_val = timeout; in watchdog_set_timeout()
246 watchdog.minutes_mode = false; in watchdog_set_timeout()
249 mutex_unlock(&watchdog.lock); in watchdog_set_timeout()
259 if (watchdog.type == f71868) { in watchdog_set_pulse_width()
[all …]
|
| D | Kconfig | 10 character special file /dev/watchdog with major number 10 and minor
11 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
15 on-line as fast as possible after a lock-up. There's both a watchdog
17 reboot the machine) and a driver for hardware watchdog boards, which
20 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
22 The watchdog is usually used together with the watchdog daemon
24 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
35 Say Y here if you want to use the new watchdog timer driver core.
36 This driver provides a framework for all watchdog timer drivers
37 and gives them the /dev/watchdog interface (and later also the
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/watchdog/ |
| D | atmel-sama5d4-wdt.txt | 8 - timeout-sec: watchdog timeout value (in seconds).
10 - atmel,watchdog-type: should be "hardware" or "software".
11 "hardware": enable watchdog fault reset. A watchdog fault triggers
12 watchdog reset.
13 "software": enable watchdog fault interrupt. A watchdog fault asserts
14 watchdog interrupt.
15 - atmel,idle-halt: present if you want to stop the watchdog when the CPU is
18 watchdog not counting when the CPU is in idle state, therefore the
19 watchdog reset time depends on mean CPU usage and will not reset at all
22 - atmel,dbg-halt: present if you want to stop the watchdog when the CPU is
[all …]
|
| D | da9062-wdt.txt | 6 "dlg,da9061-watchdog", "dlg,da9062-watchdog"
7 "dlg,da9062-watchdog"
12 watchdog {
13 compatible = "dlg,da9062-watchdog";
17 Example: DA9061 using a fall-back compatible for the DA9062 watchdog driver
20 watchdog {
21 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 | ingenic,jz4740-wdt.txt | 4 compatible: "ingenic,jz4740-watchdog" or "ingenic,jz4780-watchdog"
5 reg: Register address and length for watchdog registers
11 watchdog: jz4740-watchdog@10002000 {
12 compatible = "ingenic,jz4740-watchdog";
|
| 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 | stericsson-coh901327.txt | 7 - interrupts: the interrupt used for the watchdog timeout warning.
10 - timeout-sec: contains the watchdog timeout in seconds.
14 watchdog: watchdog@c0012000 {
|
| D | aspeed-wdt.txt | 15 Reset behavior - Whenever a timeout occurs the watchdog can be programmed
19 This is useful in situations where another watchdog engine on chip is
27 - cpu: Reset CPU on watchdog timeout
29 - soc: Reset 'System on Chip' on watchdog timeout
31 - system: Reset system on watchdog timeout
33 - none: No reset is performed on timeout. Assumes another watchdog
51 wdt1: watchdog@1e785000 {
|
| D | zte,zx2967-wdt.txt | 9 - resets : Reference to the reset controller controlling the watchdog
14 - timeout-sec : Contains the watchdog timeout in seconds.
15 - zte,wdt-reset-sysctrl : Directs how to reset system by the watchdog.
16 if we don't want to restart system when watchdog been triggered,
26 wdt: watchdog@1465000 {
|
| D | dw_wdt.txt | 6 - reg : Base address and size of the watchdog timer registers.
8 watchdog timer.
12 - interrupts : The interrupt used for the watchdog timeout warning.
14 line index for the watchdog.
|
| 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 | uniphier-wdt.txt | 1 UniPhier watchdog timer controller
3 This UniPhier watchdog timer controller must be under sysctrl node.
15 watchdog {
|
| /Linux-v4.19/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 12 file: Documentation/watchdog/watchdog-api.txt .
18 a watchdog timer driver then only needs to provide the different routines
19 (operations) that control the watchdog timer (WDT).
23 Each watchdog timer driver that wants to use the WatchDog Timer Driver Core
24 must #include <linux/watchdog.h> (you would have to do this anyway when
25 writing a watchdog device driver). This include file contains following
31 The watchdog_register_device routine registers a watchdog timer device.
35 The watchdog_unregister_device routine deregisters a registered watchdog timer
39 The watchdog subsystem includes an registration deferral mechanism,
40 which allows you to register an watchdog as early as you wish during
[all …]
|
| D | watchdog-api.txt | 19 Usually a userspace daemon will notify the kernel watchdog driver via the
20 /dev/watchdog special device file that userspace is still alive, at
22 usually tell the hardware watchdog that everything is in order, and
23 that the watchdog should wait for yet another little while to reset
25 notifications cease to occur, and the hardware watchdog will reset the
28 The Linux watchdog API is a rather ad-hoc construction and different
35 All drivers support the basic mode of operation, where the watchdog
36 activates as soon as /dev/watchdog is opened and will reboot unless
37 the watchdog is pinged within a certain time, this time is called the
38 timeout or margin. The simplest way to ping the watchdog is to write
[all …]
|
| D | hpwdt.txt | 9 watchdog functionality and the added benefit of NMI sourcing. Both the
10 watchdog functionality and the NMI sourcing capability need to be enabled
12 A user can have the NMI sourcing without the watchdog timer and vice-versa.
16 Watchdog functionality is enabled like any other common watchdog driver. That
17 is, an application needs to be started that kicks off the watchdog timer. A
18 basic application exists in tools/testing/selftests/watchdog/ named
19 watchdog-test.c. Simply compile the C file and kick it off. If the system
26 soft_margin - allows the user to set the watchdog timer value.
30 nowayout - basic watchdog parameter that does not allow the timer to
33 to "Y", then there is no way of disabling the watchdog once
[all …]
|
| D | pcwd-watchdog.txt | 17 The Watchdog Driver will automatically find your watchdog card, and will
18 attach a running driver for use with that card. After the watchdog
22 I suggest putting a "watchdog -d" before the beginning of an fsck, and
23 a "watchdog -e -t 1" immediately after the end of an fsck. (Remember
27 driver, simply use of modify the watchdog test program:
28 tools/testing/selftests/watchdog/watchdog-test.c
52 read /dev/watchdog, which gives a temperature update
|
| /Linux-v4.19/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
23 What: /sys/class/watchdog/watchdogn/state
28 watchdog device.
30 What: /sys/class/watchdog/watchdogn/status
34 It is a read only file. It contains watchdog device's
38 What: /sys/class/watchdog/watchdogn/timeleft
[all …]
|
| /Linux-v4.19/kernel/time/ |
| D | clocksource.c | 119 static struct clocksource *watchdog; variable
229 wdnow = watchdog->read(watchdog); in clocksource_watchdog()
241 delta = clocksource_delta(wdnow, cs->wd_last, watchdog->mask); in clocksource_watchdog()
242 wd_nsec = clocksource_cyc2ns(delta, watchdog->mult, in clocksource_watchdog()
243 watchdog->shift); in clocksource_watchdog()
260 watchdog->name, wdnow, wdlast, watchdog->mask); in clocksource_watchdog()
272 (watchdog->flags & CLOCK_SOURCE_IS_CONTINUOUS)) { in clocksource_watchdog()
322 if (watchdog_running || !watchdog || list_empty(&watchdog_list)) in clocksource_start_watchdog()
332 if (!watchdog_running || (watchdog && !list_empty(&watchdog_list))) in clocksource_stop_watchdog()
373 old_wd = watchdog; in clocksource_select_watchdog()
[all …]
|
