Home
last modified time | relevance | path

Searched refs:watchdog (Results 1 – 200 of 298) sorted by relevance

12

/linux-4.4.14/drivers/watchdog/
Df71808e_wdt.c152 static struct watchdog_data watchdog = { variable
153 .lock = __MUTEX_INITIALIZER(watchdog.lock),
226 mutex_lock(&watchdog.lock); in watchdog_set_timeout()
228 watchdog.timeout = timeout; in watchdog_set_timeout()
230 watchdog.timer_val = DIV_ROUND_UP(timeout, 60); in watchdog_set_timeout()
231 watchdog.minutes_mode = true; in watchdog_set_timeout()
233 watchdog.timer_val = timeout; in watchdog_set_timeout()
234 watchdog.minutes_mode = false; in watchdog_set_timeout()
237 mutex_unlock(&watchdog.lock); in watchdog_set_timeout()
246 mutex_lock(&watchdog.lock); in watchdog_set_pulse_width()
[all …]
DKconfig10 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 …]
DMakefile6 watchdog-objs += watchdog_core.o watchdog_dev.o
7 obj-$(CONFIG_WATCHDOG_CORE) += watchdog.o
Dwm831x_wdt.c235 pdata = chip_pdata->watchdog; in wm831x_wdt_probe()
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Datmel-sama5d4-wdt.txt8 - 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 …]
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 …]
Dingenic,jz4740-wdt.txt4 compatible: "ingenic,jz4740-watchdog"
5 reg: Register address and length for watchdog registers
9 watchdog: jz4740-watchdog@0x10002000 {
10 compatible = "ingenic,jz4740-watchdog";
Dmoxa,moxart-watchdog.txt5 - compatible : Must be "moxa,moxart-watchdog"
11 watchdog: watchdog@98500000 {
12 compatible = "moxa,moxart-watchdog";
Dstericsson-coh901327.txt7 - interrupts: the interrupt used for the watchdog timeout warning.
10 - timeout-sec: contains the watchdog timeout in seconds.
14 watchdog: watchdog@c0012000 {
Dgpio-wdt.txt9 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 {
Ddigicolor-wdt.txt3 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 {
Dpnx4008-wdt.txt1 * NXP PNX watchdog timer
9 - timeout-sec: contains the watchdog timeout in seconds.
13 watchdog@4003C000 {
Ddw_wdt.txt6 - reg : Base address and size of the watchdog timer registers.
8 watchdog timer.
12 - interrupts : The interrupt used for the watchdog timeout warning.
Dcadence-wdt.txt7 - interrupts : This is wd_irq - watchdog timeout interrupt.
12 when watchdog times out.
16 watchdog@f8005000 {
Dtwl4030-wdt.txt1 Device tree bindings for twl4030-wdt driver (TWL4030 watchdog)
8 watchdog {
Dsamsung-wdt.txt23 - timeout-sec : contains the watchdog timeout in seconds.
27 watchdog@101D0000 {
32 clock-names = "watchdog";
Dbrcm,bcm2835-pm-wdog.txt10 - timeout-sec : Contains the watchdog timeout in seconds
14 watchdog {
Dst_lpc_wdt.txt23 Required properties [watchdog mode]
25 - st,syscfg : Phandle to syscfg node used to enable watchdog and configure
29 Optional properties [watchdog mode]
Dbrcm,kona-wdt.txt4 This watchdog timer is used in the following Broadcom SoCs:
12 watchdog@35002f40 {
Dbrcm,bcm7038-wdt.txt10 - clocks: The clock running the watchdog. If no clock is found the
15 watchdog@f040a7e8 {
Dlpc18xx-wdt.txt7 - clock-names: Should contain "wdtclk" and "reg"; the watchdog counter
13 watchdog@40080000 {
Dimgpdc-wdt.txt7 - clock-names: Should contain "wdt" and "sys"; the watchdog counter
13 watchdog@18102100 {
Dqcom-wdt.txt15 - timeout-sec : shall contain the default watchdog timeout in seconds,
19 watchdog@208a038 {
Ddavinci-wdt.txt8 - timeout-sec : Contains the watchdog timeout in seconds
9 - clocks : the clock feeding the watchdog timer.
Dmarvel.txt34 - interrupts : Contains the IRQ for watchdog expiration
35 - timeout-sec : Contains the watchdog timeout in seconds
Datmel-at91rm9200-wdt.txt7 watchdog@fffffd00 {
Dmtk-wdt.txt10 wdt: watchdog@010000000 {
Dmeson6-wdt.txt10 wdt: watchdog@c1109900 {
Dsunxi-wdt.txt11 wdt: watchdog@01c20c90 {
Drt2880-wdt.txt13 watchdog@120 {
Domap-wdt.txt8 - timeout-sec : default watchdog timeout in seconds
Dmen-a021-wdt.txt17 watchdog {
Dfsl-imx-wdt.txt9 - big-endian: If present the watchdog device's registers are implemented
Dof-xilinx-wdt.txt1 Xilinx AXI/PLB soft-core watchdog Device Tree Bindings
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-kernel-api.txt12 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 …]
Dwatchdog-api.txt19 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 …]
Dhpwdt.txt9 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.
14 Watchdog functionality is enabled like any other common watchdog driver. That
15 is, an application needs to be started that kicks off the watchdog timer. A
16 basic application exists in the Documentation/watchdog/src directory called
17 watchdog-test.c. Simply compile the C file and kick it off. If the system
24 soft_margin - allows the user to set the watchdog timer value
26 nowayout - basic watchdog parameter that does not allow the timer to
34 NOTE: More information about watchdog drivers in general, including the ioctl
[all …]
Dpcwd-watchdog.txt17 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 Documentation/watchdog/src/watchdog-test.c
52 read /dev/watchdog, which gives a temperature update
Dconvert_drivers_to_kernel_api.txt1 Converting old watchdog drivers to the watchdog framework
5 Before the watchdog framework came into the kernel, every driver had to
56 do limit-checking, if min_timeout and max_timeout in the watchdog
96 - .name = "watchdog",
112 Add the watchdog operations
116 explained in 'watchdog-kernel-api.txt' in this directory. start(), stop() and
150 Add the watchdog device
155 in 'watchdog-kernel-api.txt' in this directory. We pass it the mandatory
162 Here is a simple example for a watchdog device:
189 Register the watchdog device
[all …]
Dwdt.txt10 All the interfaces provide /dev/watchdog, which when open must be written
12 time another timeout. In the case of the software watchdog the ability to
50 Example Watchdog Driver: see Documentation/watchdog/src/watchdog-simple.c
Dwatchdog-parameters.txt2 the Linux watchdog drivers. Watchdog driver parameter specs should
33 use_gpio: Use the gpio watchdog (required by old cobalt boards).
40 nowayout: Disable watchdog shutdown on close
72 port: base address of watchdog card, default is 0x91
148 nowayout: Disable watchdog shutdown on close
154 system resets despite watchdog daemon running, default=0
179 action: after watchdog resets, generate:
210 timer_margin: initial watchdog timeout (in seconds)
216 heartbeat: Initial watchdog heartbeat in seconds
233 nowayout: Set to 1 to keep watchdog running after device release
[all …]
/linux-4.4.14/kernel/time/
Dclocksource.c114 static struct clocksource *watchdog; variable
193 wdnow = watchdog->read(watchdog); in clocksource_watchdog()
205 delta = clocksource_delta(wdnow, cs->wd_last, watchdog->mask); in clocksource_watchdog()
206 wd_nsec = clocksource_cyc2ns(delta, watchdog->mult, in clocksource_watchdog()
207 watchdog->shift); in clocksource_watchdog()
224 watchdog->name, wdnow, wdlast, watchdog->mask); in clocksource_watchdog()
233 (watchdog->flags & CLOCK_SOURCE_IS_CONTINUOUS)) { in clocksource_watchdog()
283 if (watchdog_running || !watchdog || list_empty(&watchdog_list)) in clocksource_start_watchdog()
294 if (!watchdog_running || (watchdog && !list_empty(&watchdog_list))) in clocksource_stop_watchdog()
327 if (!watchdog || cs->rating > watchdog->rating) { in clocksource_enqueue_watchdog()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dda9062.txt9 da9062-watchdog : : Watchdog Timer
49 - watchdog: This node defines the settings for the watchdog driver associated
50 with the DA9062 PMIC. The compatible = "dlg,da9062-watchdog" should be added
67 watchdog {
68 compatible = "dlg,da9062-watchdog";
Dda9063.txt10 da9063-watchdog : : Watchdog
67 - watchdog : This node defines settings for the Watchdog timer associated
69 compatible = "dlg,da9063-watchdog" should be added if a node is created.
86 compatible = "dlg,da9063-watchdog";
Dqriox.txt5 It is consists of a reset controller, watchdog timer, LEDs, and 2 IRQ capable
Drn5t618.txt5 fuel gauge, ADC, GPIOs and a watchdog timer. It can be controlled
Dda9055.txt12 da9055-watchdog : : Watchdog
Dab8500.txt49 : CH_WD_EXP : : Charger watchdog detected
Das3722.txt75 watchdog-in, soft-reset-in
/linux-4.4.14/Documentation/devicetree/bindings/power/reset/
Dltc2952-poweroff.txt4 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
27 watchdog-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
Dkeystone-reset.txt6 The Keystone SoCs can contain up to 4 watchdog timers to reset
7 SoC. Each watchdog timer event input is connected to the Reset Mux
/linux-4.4.14/Documentation/hwmon/
Dsch562720 watchdog. In order for this watchdog to function some motherboard specific
21 initialization most be done by the BIOS, so if the watchdog is not enabled
22 by the BIOS the sch5627 driver will not register a watchdog device.
Dsch563629 The Fujitsu Theseus hwmon solution also contains an integrated watchdog.
30 This watchdog is fully supported by the sch5636 driver.
/linux-4.4.14/arch/mn10300/kernel/
Dmn10300-watchdog.c30 static unsigned int watchdog; variable
86 watchdog = opt; in setup_watchdog()
87 if (watchdog) { in setup_watchdog()
108 if (watchdog) { in watchdog_go()
DMakefile16 obj-$(CONFIG_MN10300_WD_TIMER) += mn10300-watchdog.o mn10300-watchdog-low.o
/linux-4.4.14/Documentation/
Dlockup-watchdogs.txt5 The Linux kernel can act as a watchdog to detect both soft and hard
40 A periodic hrtimer runs to generate interrupts and kick the watchdog
49 The watchdog task is a high priority kernel thread that updates a
66 By default, the watchdog runs on all online cores. However, on a
67 kernel configured with NO_HZ_FULL, by default the watchdog runs only
69 boot argument. If we allowed the watchdog to run by default on
75 able to detect if they lock up. However, allowing the watchdog
79 In either case, the set of cores excluded from running the watchdog
DIPMI.txt13 standardized database for field-replaceable units (FRUs) and a watchdog
37 Kernel code (like the watchdog) can still use it. If you need access
64 IPMI defines a standard watchdog timer. You can enable this with the
67 watchdog timer start as soon as it initializes. It also have a lot
69 Note that you can also have the watchdog continue to run if it is
72 'Disable watchdog shutdown on close'.
114 ipmi_watchdog - IPMI requires systems to have a very capable watchdog
115 timer. This driver implements the standard Linux watchdog timer
308 (the watchdog timer uses this, for instance). You supply your own
543 this driver cannod to IPMI panic events, extend the watchdog at panic
[all …]
DMakefile4 watchdog
Dkernel-per-CPU-kthreads.txt260 Name: watchdog/%u
266 from being created. Other related watchdog and softlockup boot
268 and Documentation/watchdog/watchdog-parameters.txt.
269 3. Echo a zero to /proc/sys/kernel/watchdog to disable the
270 watchdog timer.
272 order to reduce the frequency of OS jitter due to the watchdog
Dramoops.txt43 to life (i.e. a watchdog triggered). In such cases, RAM may be somewhat
/linux-4.4.14/Documentation/watchdog/src/
D.gitignore1 watchdog-simple
2 watchdog-test
DMakefile2 hostprogs-y := watchdog-simple watchdog-test
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dtwd.txt5 and watchdog.
44 - reg : Specify the base address and the size of the TWD watchdog
49 twd-watchdog@2c000620 {
Datmel-at91.txt57 - watchdog: compatible should be "atmel,at91rm9200-wdt"
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dmpc5200.txt104 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-4.4.14/arch/arm/boot/dts/
Dmoxart.dtsi87 watchdog: watchdog@98500000 { label
88 compatible = "moxa,moxart-watchdog";
Ds3c2416.dtsi108 watchdog: watchdog@53000000 { label
111 clock-names = "watchdog";
Ds3c64xx.dtsi96 watchdog: watchdog@7e004000 { label
101 clock-names = "watchdog";
Dnspire.dtsi156 watchdog: watchdog@90060000 { label
Devk-pro3.dts44 watchdog@fffffd40 {
Ds3c2416-smdk2416.dts83 &watchdog {
Ds3c24xx.dtsi73 watchdog@53000000 {
Dat91-kizboxmini.dts57 watchdog@fffffe40 {
Dat91-cosino.dtsi89 watchdog@fffffe40 {
Dexynos5440.dtsi181 watchdog@110000 {
186 clock-names = "watchdog";
Dat91-kizbox.dts49 watchdog@fffffd40 {
Dat91-foxg20.dts126 watchdog@fffffd40 {
Danimeo_ip.dts90 watchdog@fffffd40 {
Dvexpress-v2p-ca9.dts135 watchdog@100e5000 {
154 watchdog@1e000620 {
Dhighbank.dts102 watchdog@fff10620 {
Dat91sam9g20ek_common.dtsi117 watchdog@fffffd40 {
Dtwl4030.dtsi28 watchdog {
Dmt6589.dtsi142 wdt: watchdog@010000000 {
Dat91sam9rlek.dts176 watchdog@fffffd40 {
Dat91sam9263ek.dts93 watchdog@fffffd40 {
Dbcm63138.dtsi106 twd_watchdog: watchdog@1e620 {
Dat91-kizbox2.dts131 watchdog@fffffe40 {
Dat91sam9261ek.dts151 watchdog@fffffd40 {
Dat91sam9x5ek.dtsi161 watchdog@fffffe40 {
Ds5pv210.dtsi310 watchdog: watchdog@e2700000 { label
315 clock-names = "watchdog";
Dsama5d3xmb.dtsi176 watchdog@fffffe40 {
Dste-u300.dts249 watchdog: watchdog@c0012000 { label
Dat91sam9n12ek.dts141 watchdog@fffffe40 {
Dvexpress-v2p-ca5s.dts99 watchdog@2c000620 {
Dbcm2835.dtsi60 watchdog@7e100000 {
Dcx92755.dtsi91 watchdog@f0000fc0 {
Dpicoxcell-pc3x2.dtsi217 wdog: watchdog@50000 {
Dat91sam9m10g45ek.dts82 watchdog@fffffd40 {
Dmeson.dtsi80 wdt: watchdog@c1109900 {
Dexynos5420-peach-pit.dts1057 * Use longest HW watchdog in SoC (32 seconds) since the hardware
1058 * watchdog provides no debugging information (compared to soft/hard
1061 &watchdog {
Dexynos5800-peach-pi.dts1020 * Use longest HW watchdog in SoC (32 seconds) since the hardware
1021 * watchdog provides no debugging information (compared to soft/hard
1024 &watchdog {
Dexynos4.dtsi263 watchdog: watchdog@10060000 { label
268 clock-names = "watchdog";
Dversatile-ab.dts181 watchdog@101e1000 {
Dat91-sama5d4_xplained.dts139 watchdog@fc068640 {
Dlpc32xx.dtsi259 watchdog@4003C000 {
Dexynos4210-origen.dts340 &watchdog {
Dsocfpga_arria10.dtsi708 watchdog0: watchdog@ffd00200 {
716 watchdog1: watchdog@ffd00300 {
Dexynos5420.dtsi842 watchdog: watchdog@101D0000 { label
847 clock-names = "watchdog";
Dsocfpga.dtsi829 watchdog0: watchdog@ffd02000 {
837 watchdog1: watchdog@ffd03000 {
Dat91-sama5d4ek.dts197 watchdog@fc068640 {
Dzynq-7000.dtsi356 watchdog0: watchdog@f8005000 {
Dpicoxcell-pc3x3.dtsi311 wdog: watchdog@50000 {
Darmada-370-xp.dtsi247 watchdog@20300 {
Dkirkwood.dtsi244 wdt: watchdog-timer@20300 {
Dbcm11351.dtsi110 watchdog@35002f40 {
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dnvidia,tegra30-timer.txt4 running counter, and 5 watchdog modules. The first two channels may also
5 trigger a legacy watchdog reset.
Dnvidia,tegra20-timer.txt4 running counter. The first two channels may also trigger a watchdog reset.
Dst,stih407-lpc7 [See: ../watchdog/st_lpc_wdt.txt for Watchdog options]
/linux-4.4.14/arch/m68k/mvme147/
Dconfig.c68 m147_pcc->watchdog = 0x0a; /* Clear timer */ in mvme147_reset()
69 m147_pcc->watchdog = 0xa5; /* Enable watchdog - 100ms to reset */ in mvme147_reset()
/linux-4.4.14/kernel/
Dhung_task.c225 static int watchdog(void *dummy) in watchdog() function
247 watchdog_task = kthread_run(watchdog, NULL, "khungtaskd"); in hung_task_init()
Dwatchdog.c542 static void watchdog(unsigned int cpu) in watchdog() function
670 .thread_fn = watchdog,
DMakefile75 obj-$(CONFIG_LOCKUP_DETECTOR) += watchdog.o
/linux-4.4.14/net/sched/
Dsch_tbf.c115 struct qdisc_watchdog watchdog; /* Watchdog timer */ member
272 qdisc_watchdog_schedule_ns(&q->watchdog, in tbf_dequeue()
301 qdisc_watchdog_cancel(&q->watchdog); in tbf_reset()
439 qdisc_watchdog_init(&q->watchdog, sch); in tbf_init()
449 qdisc_watchdog_cancel(&q->watchdog); in tbf_destroy()
Dsch_htb.c167 struct qdisc_watchdog watchdog; member
933 &qdisc_root_sleeping(q->watchdog.qdisc)->state)) { in htb_dequeue()
935 qdisc_throttled(q->watchdog.qdisc); in htb_dequeue()
936 hrtimer_start(&q->watchdog.timer, time, in htb_dequeue()
992 qdisc_watchdog_cancel(&q->watchdog); in htb_reset()
1015 struct Qdisc *sch = q->watchdog.qdisc; in htb_work_func()
1048 qdisc_watchdog_init(&q->watchdog, sch); in htb_init()
1246 qdisc_watchdog_cancel(&q->watchdog); in htb_destroy()
Dsch_netem.c78 struct qdisc_watchdog watchdog; member
672 qdisc_watchdog_schedule(&q->watchdog, time_to_send); in netem_dequeue()
691 qdisc_watchdog_cancel(&q->watchdog); in netem_reset()
949 qdisc_watchdog_init(&q->watchdog, sch); in netem_init()
962 qdisc_watchdog_cancel(&q->watchdog); in netem_destroy()
Dsch_fq.c112 struct qdisc_watchdog watchdog; member
447 qdisc_watchdog_schedule_ns(&q->watchdog, in fq_dequeue()
756 qdisc_watchdog_cancel(&q->watchdog); in fq_destroy()
777 qdisc_watchdog_init(&q->watchdog, sch); in fq_init()
Dsch_hfsc.c182 struct qdisc_watchdog watchdog; /* watchdog timer */ member
1427 qdisc_watchdog_schedule(&q->watchdog, next_time); in hfsc_schedule_watchdog()
1462 qdisc_watchdog_init(&q->watchdog, sch); in hfsc_init_qdisc()
1531 qdisc_watchdog_cancel(&q->watchdog); in hfsc_reset_qdisc()
1553 qdisc_watchdog_cancel(&q->watchdog); in hfsc_destroy_qdisc()
Dsch_cbq.c165 struct qdisc_watchdog watchdog; /* Watchdog timer, member
591 struct Qdisc *sch = q->watchdog.qdisc; in cbq_undelay()
1000 qdisc_watchdog_schedule(&q->watchdog, in cbq_dequeue()
1206 qdisc_watchdog_cancel(&q->watchdog); in cbq_reset()
1388 qdisc_watchdog_init(&q->watchdog, sch); in cbq_init()
/linux-4.4.14/arch/arm64/boot/dts/altera/
Dsocfpga_stratix10.dtsi330 watchdog0: watchdog@ffd00200 {
337 watchdog1: watchdog@ffd00300 {
344 watchdog2: watchdog@ffd00400 {
351 watchdog3: watchdog@ffd00500 {
/linux-4.4.14/arch/mips/include/asm/
Dm48t37.h20 volatile u8 watchdog; member
/linux-4.4.14/drivers/ide/
Dsiimage.c368 u8 watchdog = 0; in siimage_mmio_dma_test_irq() local
374 watchdog = (sata_error & 0x00680000) ? 1 : 0; in siimage_mmio_dma_test_irq()
377 drive->name, sata_error, watchdog, __func__); in siimage_mmio_dma_test_irq()
379 watchdog = (ext_stat & 0x8000) ? 1 : 0; in siimage_mmio_dma_test_irq()
382 if (!(ext_stat & 0x0404) && !watchdog) in siimage_mmio_dma_test_irq()
/linux-4.4.14/include/net/irda/
Daf_irda.h76 struct timer_list watchdog; /* Timeout for discovery */ member
/linux-4.4.14/arch/arm/plat-samsung/
DMakefile34 obj-$(CONFIG_SAMSUNG_WDT_RESET) += watchdog-reset.o
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt88 - watchdog
434 This parameter can be used to control the NMI watchdog
443 while a CPU is busy. Hence, the alternative name 'NMI watchdog'.
445 The NMI watchdog is disabled by default if the kernel is running as a guest
549 waits before rebooting on a panic. When you use the software watchdog,
848 without rescheduling voluntarily, and thus prevent the 'watchdog/N' threads
850 interrupts which are needed for the 'watchdog/N' threads to be woken up by
851 the watchdog timer function, otherwise the NMI watchdog - if enabled - can
919 watchdog:
922 _and_ the NMI watchdog (i.e. the hard lockup detector) at the same time.
[all …]
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dkernel.fuc344 // halt watchdog timer temporarily
349 // of the watchdog and add this time to the wanted ticks
363 // update the watchdog if this timer should expire first,
374 // re-enable the watchdog timer
530 // enable watchdog and subintr intrs
543 // enable watchdog timer
/linux-4.4.14/Documentation/misc-devices/mei/
Dmei.txt226 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
234 2) Intel MEI driver - connects to the watchdog feature, configures the
235 watchdog and sends the heartbeats.
237 The Intel MEI driver uses the kernel watchdog API to configure the Intel AMT
239 watchdog is 120 seconds.
/linux-4.4.14/drivers/char/hw_random/
Dn2rng.h43 unsigned long *watchdog,
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Drtc-st-lpc.txt7 [See: ../watchdog/st_lpc_wdt.txt for Watchdog options]
/linux-4.4.14/include/linux/mfd/wm831x/
Dpdata.h136 struct wm831x_watchdog_pdata *watchdog; member
/linux-4.4.14/drivers/mmc/host/
Dmxcmmc.c161 struct timer_list watchdog; member
360 mod_timer(&host->watchdog, jiffies + msecs_to_jiffies(MXCMCI_TIMEOUT_MS)); in mxcmci_setup_data()
373 del_timer(&host->watchdog); in mxcmci_dma_callback()
750 del_timer(&host->watchdog); in mxcmci_irq()
1161 init_timer(&host->watchdog); in mxcmci_probe()
1162 host->watchdog.function = &mxcmci_watchdog; in mxcmci_probe()
1163 host->watchdog.data = (unsigned long)mmc; in mxcmci_probe()
/linux-4.4.14/drivers/hwmon/
Dsch5636.c70 struct sch56xx_watchdog_data *watchdog; member
388 if (data->watchdog) in sch5636_remove()
389 sch56xx_watchdog_unregister(data->watchdog); in sch5636_remove()
511 data->watchdog = sch56xx_watchdog_register(&pdev->dev, data->addr, in sch5636_probe()
Dsch5627.c82 struct sch56xx_watchdog_data *watchdog; member
457 if (data->watchdog) in sch5627_remove()
458 sch56xx_watchdog_unregister(data->watchdog); in sch5627_remove()
581 data->watchdog = sch56xx_watchdog_register(&pdev->dev, data->addr, in sch5627_probe()
/linux-4.4.14/drivers/net/ethernet/8390/
Daxnet_cs.c114 struct timer_list watchdog; member
487 setup_timer(&info->watchdog, ei_watchdog, (u_long)dev); in axnet_open()
488 mod_timer(&info->watchdog, jiffies + HZ); in axnet_open()
507 del_timer_sync(&info->watchdog); in axnet_close()
571 info->watchdog.expires = jiffies + 1; in ei_watchdog()
572 add_timer(&info->watchdog); in ei_watchdog()
602 info->watchdog.expires = jiffies + HZ; in ei_watchdog()
603 add_timer(&info->watchdog); in ei_watchdog()
Dpcnet_cs.c207 struct timer_list watchdog; member
921 setup_timer(&info->watchdog, ei_watchdog, (u_long)dev); in pcnet_open()
922 mod_timer(&info->watchdog, jiffies + HZ); in pcnet_open()
941 del_timer_sync(&info->watchdog); in pcnet_close()
1030 info->watchdog.expires = jiffies + 1; in ei_watchdog()
1031 add_timer(&info->watchdog); in ei_watchdog()
1092 info->watchdog.expires = jiffies + HZ; in ei_watchdog()
1093 add_timer(&info->watchdog); in ei_watchdog()
/linux-4.4.14/drivers/dma/
Dimx-dma.c149 struct timer_list watchdog; member
352 del_timer(&imxdmac->watchdog); in imxdma_disable_hw()
461 mod_timer(&imxdmac->watchdog, in dma_irq_handle_channel()
482 del_timer(&imxdmac->watchdog); in dma_irq_handle_channel()
1153 init_timer(&imxdmac->watchdog); in imxdma_probe()
1154 imxdmac->watchdog.function = &imxdma_watchdog; in imxdma_probe()
1155 imxdmac->watchdog.data = (unsigned long)imxdmac; in imxdma_probe()
/linux-4.4.14/arch/m68k/include/asm/
Dmvme147hw.h39 volatile u_char watchdog; member
/linux-4.4.14/arch/mips/include/asm/ip32/
Dcrime.h89 volatile unsigned long watchdog; member
/linux-4.4.14/arch/sparc/include/uapi/asm/
DKbuild50 header-y += watchdog.h
/linux-4.4.14/Documentation/devicetree/bindings/arm/msm/
Dtimer.txt13 optionally as well, 2 watchdog interrupts, in that order.
/linux-4.4.14/arch/arm64/boot/dts/exynos/
Dexynos7-espresso.dts47 &watchdog {
Dexynos7.dtsi466 watchdog: watchdog@101d0000 { label
471 clock-names = "watchdog";
/linux-4.4.14/arch/mips/boot/dts/lantiq/
Ddanube.dtsi26 watchdog@803F0 {
/linux-4.4.14/arch/x86/kernel/cpu/
DMakefile59 obj-$(CONFIG_X86_LOCAL_APIC) += perfctr-watchdog.o perf_event_amd_ibs.o
/linux-4.4.14/arch/sh/include/mach-ecovec24/mach/
Dpartner-jet-setup.txt16 LIST "disable watchdog"
/linux-4.4.14/drivers/net/wireless/rt2x00/
Drt2x00link.c379 rt2x00dev->ops->lib->watchdog) in rt2x00link_start_watchdog()
403 rt2x00dev->ops->lib->watchdog(rt2x00dev); in rt2x00link_watchdog()
/linux-4.4.14/drivers/net/ethernet/allwinner/
Dsun4i-emac.c41 static int watchdog = 5000; variable
42 module_param(watchdog, int, 0400);
43 MODULE_PARM_DESC(watchdog, "transmit timeout in milliseconds");
895 ndev->watchdog_timeo = msecs_to_jiffies(watchdog); in emac_probe()
/linux-4.4.14/drivers/net/ethernet/micrel/
Dks8695net.c51 static int watchdog = 5000; variable
629 int reset_timeout = watchdog; in ks8695_reset()
1441 ndev->watchdog_timeo = msecs_to_jiffies(watchdog); in ks8695_probe()
1629 module_param(watchdog, int, 0400);
1630 MODULE_PARM_DESC(watchdog, "transmit timeout in milliseconds");
/linux-4.4.14/drivers/media/platform/s5p-tv/
Dmixer_video.c984 struct timer_list watchdog; in stop_streaming() local
1003 setup_timer_on_stack(&watchdog, mxr_watchdog, in stop_streaming()
1005 mod_timer(&watchdog, jiffies + msecs_to_jiffies(1000)); in stop_streaming()
1011 del_timer_sync(&watchdog); in stop_streaming()
1012 destroy_timer_on_stack(&watchdog); in stop_streaming()
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dmips-gic.txt6 global timer, per-CPU count/compare timers, and a watchdog.
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DS3C2412.txt83 The watchdog hardware is the same as the S3C2410, and is supported by
DOverview.txt174 The onchip watchdog is available via the standard watchdog
/linux-4.4.14/arch/cris/include/arch-v32/mach-fs/mach/hwregs/
Dintr_vect_defs.h202 unsigned int watchdog : 1; member
/linux-4.4.14/arch/cris/
DKconfig100 bool "Enable ETRAX watchdog"
102 Enable the built-in watchdog timer support on ETRAX based embedded
106 bool "Disable watchdog during Oops printouts"
109 By enabling this you make sure that the watchdog does not bite while
/linux-4.4.14/Documentation/gpio/
Ddrivers-on-gpio.txt76 - gpio-wdt: drivers/watchdog/gpio_wdt.c is used to provide a watchdog timer
/linux-4.4.14/drivers/net/wireless/brcm80211/include/
Dchipcommon.h75 u32 watchdog; /* 0x80 */ member
/linux-4.4.14/drivers/net/wan/
Dsbni.c73 struct timer_list watchdog; member
1037 struct timer_list *w = &nl->watchdog; in sbni_watchdog()
1159 struct timer_list *w = &nl->watchdog; in sbni_open()
1235 del_timer( &nl->watchdog ); in sbni_close()
/linux-4.4.14/drivers/
DMakefile112 obj-$(CONFIG_WATCHDOG) += watchdog/
DKconfig79 source "drivers/watchdog/Kconfig"
/linux-4.4.14/Documentation/devicetree/bindings/net/
Damd-xgbe.txt20 correct Rx interrupt watchdog timer value on a DMA channel
/linux-4.4.14/drivers/char/ipmi/
DKconfig82 This enables the IPMI watchdog timer.
/linux-4.4.14/Documentation/misc-devices/
Dmax687518 It provides timed outputs that can be used as a watchdog, if properly wired.
/linux-4.4.14/arch/sh/include/mach-kfr2r09/mach/
Dpartner-jet-setup.txt16 LIST "disable watchdog"
/linux-4.4.14/drivers/ssb/
Dembedded.c65 bus->watchdog = pdev; in ssb_watchdog_register()
/linux-4.4.14/arch/arm64/boot/dts/mediatek/
Dmt8173.dtsi244 watchdog: watchdog@10007000 { label
/linux-4.4.14/drivers/usb/host/
Doxu210hp.h418 struct timer_list watchdog; member
Doxu210hp-hcd.c297 && t > oxu->watchdog.expires in timer_action()
298 && timer_pending(&oxu->watchdog)) in timer_action()
300 mod_timer(&oxu->watchdog, t); in timer_action()
2602 setup_timer(&oxu->watchdog, oxu_watchdog, (unsigned long)oxu); in oxu_hcd_init()
2768 del_timer_sync(&oxu->watchdog); in oxu_stop()
3502 del_timer_sync(&oxu->watchdog); in oxu_bus_suspend()
/linux-4.4.14/drivers/net/ethernet/stmicro/stmmac/
Dstmmac_main.c61 static int watchdog = TX_TIMEO; variable
62 module_param(watchdog, int, S_IRUGO | S_IWUSR);
63 MODULE_PARM_DESC(watchdog, "Transmit timeout in milliseconds (default 5s)");
134 if (unlikely(watchdog < 0)) in stmmac_verify_args()
135 watchdog = TX_TIMEO; in stmmac_verify_args()
2917 ndev->watchdog_timeo = msecs_to_jiffies(watchdog); in stmmac_dvr_probe()
3156 if (kstrtoint(opt + 9, 0, &watchdog)) in stmmac_cmdline_opt()
/linux-4.4.14/drivers/net/ethernet/davicom/
Ddm9000.c59 static int watchdog = 5000; variable
60 module_param(watchdog, int, 0400);
61 MODULE_PARM_DESC(watchdog, "transmit timeout in milliseconds");
1657 ndev->watchdog_timeo = msecs_to_jiffies(watchdog); in dm9000_probe()
/linux-4.4.14/drivers/net/wan/lmc/
Dlmc_var.h219 void (* watchdog)(lmc_softc_t * const); member
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dmarvell,dove-pinctrl.txt28 mpp8 8 gpio, pmu, watchdog(rstout), pmu*
/linux-4.4.14/arch/powerpc/boot/dts/
Dmpc8349emitxgp.dts59 device_type = "watchdog";
Dasp834x-redboot.dts80 device_type = "watchdog";
Dmpc832x_rdb.dts60 device_type = "watchdog";
Dc2k.dts201 wdt@b410 { /* watchdog timer */
Dmpc5200b.dtsi72 // add 'fsl,has-wdt' to enable watchdog
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
Dge_imp3a.dts109 /* Second watchdog available, driver currently supports one.
/linux-4.4.14/Documentation/acpi/apei/
Doutput_format.txt80 target abort | parity error | watchdog timeout | invalid address | \
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dentry.S384 ;; If we receive a watchdog interrupt while it is not expected, then set
408 btstq REG_BIT(intr_vect, r_nmi, watchdog), $r0
/linux-4.4.14/drivers/power/
Dbq24190_charger.c168 u8 watchdog; member
362 BQ24190_SYSFS_FIELD_RO(watchdog, CTTC, WATCHDOG),
504 bdi->watchdog = ((v & BQ24190_REG_CTTC_WATCHDOG_MASK) >> in bq24190_set_mode_host()
/linux-4.4.14/drivers/net/ethernet/smsc/
Dsmc911x.c83 static int watchdog = 5000; variable
84 module_param(watchdog, int, 0400);
85 MODULE_PARM_DESC(watchdog, "transmit timeout in milliseconds");
1931 dev->watchdog_timeo = msecs_to_jiffies(watchdog); in smc911x_probe()
Dsmc91x.c109 static int watchdog = 1000; variable
110 module_param(watchdog, int, 0400);
111 MODULE_PARM_DESC(watchdog, "transmit timeout in milliseconds");
1976 dev->watchdog_timeo = msecs_to_jiffies(watchdog); in smc_probe()
/linux-4.4.14/drivers/net/ethernet/intel/
De100.c602 struct timer_list watchdog; member
1760 mod_timer(&nic->watchdog, in e100_watchdog()
2318 mod_timer(&nic->watchdog, jiffies); in e100_up()
2330 del_timer_sync(&nic->watchdog); in e100_up()
2345 del_timer_sync(&nic->watchdog); in e100_down()
2928 setup_timer(&nic->watchdog, e100_watchdog, (unsigned long)nic); in e100_probe()
3171 mod_timer(&nic->watchdog, jiffies); in e100_io_resume()
/linux-4.4.14/Documentation/laptops/
Dthinkpad-acpi.txt1196 fan commands: "enable", "disable", "level" or "watchdog", or if there
1199 120 seconds. This functionality is called fan safety watchdog.
1201 Note that the watchdog timer stops after it enables the fan. It will be
1203 above mentioned fan commands is received. The fan watchdog is,
1240 To program the safety watchdog, use the "watchdog" command.
1242 echo 'watchdog <interval in seconds>' > /proc/acpi/ibm/fan
1244 If you want to disable the watchdog, use 0 as the interval.
1249 part, and the exception is the fan safety watchdog.
1289 Fan safety watchdog timer interval, in seconds. Minimum is
1290 1 second, maximum is 120 seconds. 0 disables the watchdog.
/linux-4.4.14/drivers/bcma/
Ddriver_chipcommon.c111 cc->watchdog = pdev; in bcma_chipco_watchdog_register()
/linux-4.4.14/arch/mn10300/
DKconfig244 bool "Using MN10300 watchdog timer"
247 This options indicates that the watchdog timer will be used.
/linux-4.4.14/kernel/power/
DKconfig188 bool "Device suspend/resume watchdog"
191 Sets up a watchdog timer to capture drivers that are
/linux-4.4.14/include/linux/bcma/
Dbcma_driver_chipcommon.h637 struct platform_device *watchdog; member
/linux-4.4.14/arch/arm64/boot/dts/xilinx/
Dzynqmp.dtsi366 watchdog0: watchdog@fd4d0000 {
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dentry.S448 ;; is cleared by us however (when feeding the watchdog), which is why
451 move.d [R_IRQ_MASK0_RD], $r1 ; External NMI or watchdog?
/linux-4.4.14/include/linux/ssb/
Dssb.h492 struct platform_device *watchdog; member

12