1 # SPDX-License-Identifier: GPL-2.0-only
4 # Watchdog device configuration
8 bool "Watchdog Timer Support"
10 If you say Y here (and to one of the following options) and create a
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.:
13 subsequently opening the file and then failing to write to it for
14 longer than 1 minute will result in rebooting the machine. This
15 could be useful for a networked machine that needs to come back
16 on-line as fast as possible after a lock-up. There's both a watchdog
17 implementation entirely in software (which can sometimes fail to
18 reboot the machine) and a driver for hardware watchdog boards, which
19 are more robust and can also keep track of the temperature inside
20 your computer. For details, read
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
23 The watchdog is usually used together with the watchdog daemon
24 which is available from
25 <https://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon
26 can also monitor NFS connections and can reboot the machine when the
27 process table is full.
34 tristate "WatchDog Timer Driver Core"
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
41 config WATCHDOG_NOWAYOUT
42 bool "Disable watchdog shutdown on close"
44 The default watchdog behaviour (which you get if you say N here) is
45 to stop the timer if the process managing it closes the file
46 /dev/watchdog. It's always remotely possible that this process might
47 get killed. If you say Y here, the watchdog cannot be stopped once
50 config WATCHDOG_HANDLE_BOOT_ENABLED
51 bool "Update boot-enabled watchdog until userspace takes over"
54 The default watchdog behaviour (which you get if you say Y here) is
55 to ping watchdog devices that were enabled before the driver has
56 been loaded until control is taken over from userspace using the
57 /dev/watchdog file. If you say N here, the kernel will not update
58 the watchdog on its own. Thus if your userspace does not start fast
59 enough your device will reboot.
61 config WATCHDOG_OPEN_TIMEOUT
62 int "Timeout value for opening watchdog device"
65 The maximum time, in seconds, for which the watchdog framework takes
66 care of pinging a hardware watchdog. A value of 0 means infinite. The
67 value set here can be overridden by the commandline parameter
68 "watchdog.open_timeout".
71 bool "Read different watchdog information through sysfs"
73 Say Y here if you want to enable watchdog device status read through
76 config WATCHDOG_HRTIMER_PRETIMEOUT
77 bool "Enable watchdog hrtimer-based pretimeouts"
79 Enable this if you want to use a hrtimer timer based pretimeout for
80 watchdogs that do not natively support pretimeout support. Be aware
81 that because this pretimeout functionality uses hrtimers, it may not
82 be able to fire before the actual watchdog fires in some situations.
84 comment "Watchdog Pretimeout Governors"
86 config WATCHDOG_PRETIMEOUT_GOV
87 bool "Enable watchdog pretimeout governors"
88 depends on WATCHDOG_CORE
90 The option allows to select watchdog pretimeout governors.
92 config WATCHDOG_PRETIMEOUT_GOV_SEL
94 depends on WATCHDOG_PRETIMEOUT_GOV
96 select WATCHDOG_PRETIMEOUT_GOV_PANIC if WATCHDOG_PRETIMEOUT_GOV_NOOP=n
98 if WATCHDOG_PRETIMEOUT_GOV
100 config WATCHDOG_PRETIMEOUT_GOV_NOOP
101 tristate "Noop watchdog pretimeout governor"
102 depends on WATCHDOG_CORE
103 default WATCHDOG_CORE
105 Noop watchdog pretimeout governor, only an informational
106 message is added to kernel log buffer.
108 config WATCHDOG_PRETIMEOUT_GOV_PANIC
109 tristate "Panic watchdog pretimeout governor"
110 depends on WATCHDOG_CORE
111 default WATCHDOG_CORE
113 Panic watchdog pretimeout governor, on watchdog pretimeout
114 event put the kernel into panic.
117 prompt "Default Watchdog Pretimeout Governor"
118 default WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC
120 This option selects a default watchdog pretimeout governor.
121 The governor takes its action, if a watchdog is capable
122 to report a pretimeout event.
124 config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP
126 depends on WATCHDOG_PRETIMEOUT_GOV_NOOP
128 Use noop watchdog pretimeout governor by default. If noop
129 governor is selected by a user, write a short message to
130 the kernel log buffer and don't do any system changes.
132 config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC
134 depends on WATCHDOG_PRETIMEOUT_GOV_PANIC
136 Use panic watchdog pretimeout governor by default, if
137 a watchdog pretimeout event happens, consider that
138 a watchdog feeder is dead and reboot is unavoidable.
142 endif # WATCHDOG_PRETIMEOUT_GOV
145 # General Watchdog drivers
148 comment "Watchdog Device Drivers"
150 # Architecture Independent
153 tristate "Software watchdog"
156 A software monitoring watchdog. This will fail to reboot your system
157 from some situations that the hardware watchdog will recover
158 from. Equally it's a lot cheaper to install.
160 To compile this driver as a module, choose M here: the
161 module will be called softdog.
163 config SOFT_WATCHDOG_PRETIMEOUT
164 bool "Software watchdog pretimeout governor support"
165 depends on SOFT_WATCHDOG && WATCHDOG_PRETIMEOUT_GOV
167 Enable this if you want to use pretimeout governors with the software
168 watchdog. Be aware that governors might affect the watchdog because it
169 is purely software, e.g. the panic governor will stall it!
171 config BD70528_WATCHDOG
172 tristate "ROHM BD70528 PMIC Watchdog"
173 depends on MFD_ROHM_BD70528
176 Support for the watchdog in the ROHM BD70528 PMIC. Watchdog trigger
179 Say Y here to include support for the ROHM BD70528 watchdog.
180 Alternatively say M to compile the driver as a module,
181 which will be called bd70528_wdt.
183 config BD957XMUF_WATCHDOG
184 tristate "ROHM BD9576MUF and BD9573MUF PMIC Watchdog"
185 depends on MFD_ROHM_BD957XMUF
188 Support for the watchdog in the ROHM BD9576 and BD9573 PMICs.
189 These PMIC ICs contain watchdog block which can be configured
190 to toggle reset line if SoC fails to ping watchdog via GPIO.
192 Say Y here to include support for the ROHM BD9576 or BD9573
193 watchdog. Alternatively say M to compile the driver as a module,
194 which will be called bd9576_wdt.
196 config DA9052_WATCHDOG
197 tristate "Dialog DA9052 Watchdog"
198 depends on PMIC_DA9052 || COMPILE_TEST
201 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
204 Say Y here to include support for the DA9052 watchdog.
205 Alternatively say M to compile the driver as a module,
206 which will be called da9052_wdt.
208 config DA9055_WATCHDOG
209 tristate "Dialog Semiconductor DA9055 Watchdog"
210 depends on MFD_DA9055 || COMPILE_TEST
213 If you say yes here you get support for watchdog on the Dialog
214 Semiconductor DA9055 PMIC.
216 This driver can also be built as a module. If so, the module
217 will be called da9055_wdt.
219 config DA9063_WATCHDOG
220 tristate "Dialog DA9063 Watchdog"
221 depends on MFD_DA9063 || COMPILE_TEST
224 Support for the watchdog in the DA9063 PMIC.
226 This driver can be built as a module. The module name is da9063_wdt.
228 config DA9062_WATCHDOG
229 tristate "Dialog DA9062/61 Watchdog"
230 depends on MFD_DA9062 || COMPILE_TEST
234 Support for the watchdog in the DA9062 and DA9061 PMICs.
236 This driver can be built as a module. The module name is da9062_wdt.
239 tristate "Watchdog device controlled through GPIO-line"
243 If you say yes here you get support for watchdog device
244 controlled through GPIO-line.
246 config GPIO_WATCHDOG_ARCH_INITCALL
247 bool "Register the watchdog as early as possible"
248 depends on GPIO_WATCHDOG=y
250 In some situations, the default initcall level (module_init)
251 in not early enough in the boot process to avoid the watchdog
253 If you say yes here, the initcall level would be raised to
257 config MENF21BMC_WATCHDOG
258 tristate "MEN 14F021P00 BMC Watchdog"
259 depends on MFD_MENF21BMC || COMPILE_TEST
263 Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
265 This driver can also be built as a module. If so the module
266 will be called menf21bmc_wdt.
268 config MENZ069_WATCHDOG
269 tristate "MEN 16Z069 Watchdog"
273 Say Y here to include support for the MEN 16Z069 Watchdog.
275 This driver can also be built as a module. If so the module
276 will be called menz069_wdt.
279 tristate "ACPI Watchdog Action Table (WDAT)"
284 This driver adds support for systems with ACPI Watchdog Action
285 Table (WDAT) table. Servers typically have this but it can be
286 found on some desktop machines as well. This driver will take
287 over the native iTCO watchdog driver found on many Intel CPUs.
289 To compile this driver as module, choose M here: the module will
292 config WM831X_WATCHDOG
293 tristate "WM831x watchdog"
294 depends on MFD_WM831X
297 Support for the watchdog in the WM831x AudioPlus PMICs. When
298 the watchdog triggers the system will be reset.
300 config WM8350_WATCHDOG
301 tristate "WM8350 watchdog"
302 depends on MFD_WM8350
305 Support for the watchdog in the WM8350 AudioPlus PMIC. When
306 the watchdog triggers the system will be reset.
308 config XILINX_WATCHDOG
309 tristate "Xilinx Watchdog timer"
313 Watchdog driver for the xps_timebase_wdt IP core.
315 To compile this driver as a module, choose M here: the
316 module will be called of_xilinx_wdt.
318 config ZIIRAVE_WATCHDOG
319 tristate "Zodiac RAVE Watchdog Timer"
323 Watchdog driver for the Zodiac Aerospace RAVE Switch Watchdog
326 To compile this driver as a module, choose M here: the
327 module will be called ziirave_wdt.
329 config RAVE_SP_WATCHDOG
330 tristate "RAVE SP Watchdog timer"
331 depends on RAVE_SP_CORE
332 depends on NVMEM || !NVMEM
335 Support for the watchdog on RAVE SP device.
338 tristate "Mellanox Watchdog"
339 depends on MELLANOX_PLATFORM
343 This is the driver for the hardware watchdog on Mellanox systems.
344 If you are going to use it, say Y here, otherwise N.
345 This driver can be used together with the watchdog daemon.
346 It can also watch your kernel to make sure it doesn't freeze,
347 and if it does, it reboots your system after a certain amount of
350 To compile this driver as a module, choose M here: the
351 module will be called mlx-wdt.
353 config SL28CPLD_WATCHDOG
354 tristate "Kontron sl28cpld Watchdog"
355 depends on MFD_SL28CPLD || COMPILE_TEST
358 Say Y here to include support for the watchdog timer
359 on the Kontron sl28 CPLD.
361 To compile this driver as a module, choose M here: the
362 module will be called sl28cpld_wdt.
368 config ARM_SP805_WATCHDOG
369 tristate "ARM SP805 Watchdog"
370 depends on (ARM || ARM64 || COMPILE_TEST) && ARM_AMBA
373 ARM Primecell SP805 Watchdog timer. This will reboot your system when
374 the timeout is reached.
376 config ARM_SBSA_WATCHDOG
377 tristate "ARM SBSA Generic Watchdog"
379 depends on ARM_ARCH_TIMER
382 ARM SBSA Generic Watchdog has two stage timeouts:
383 the first signal (WS0) is for alerting the system by interrupt,
384 the second one (WS1) is a real hardware reset.
385 More details: ARM DEN0029B - Server Base System Architecture (SBSA)
387 This driver can operate ARM SBSA Generic Watchdog as a single stage
388 or a two stages watchdog, it depends on the module parameter "action".
390 Note: the maximum timeout in the two stages mode is half of that in
391 the single stage mode.
393 To compile this driver as module, choose M here: The module
394 will be called sbsa_gwdt.
396 config ARMADA_37XX_WATCHDOG
397 tristate "Armada 37xx watchdog"
398 depends on ARCH_MVEBU || COMPILE_TEST
403 Say Y here to include support for the watchdog timer found on
404 Marvell Armada 37xx SoCs.
405 To compile this driver as a module, choose M here: the
406 module will be called armada_37xx_wdt.
408 config ASM9260_WATCHDOG
409 tristate "Alphascale ASM9260 watchdog"
410 depends on MACH_ASM9260 || COMPILE_TEST
413 select RESET_CONTROLLER
415 Watchdog timer embedded into Alphascale asm9260 chips. This will
416 reboot your system when the timeout is reached.
418 config AT91RM9200_WATCHDOG
419 tristate "AT91RM9200 watchdog"
420 depends on (SOC_AT91RM9200 && MFD_SYSCON) || COMPILE_TEST
422 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
423 system when the timeout is reached.
425 config AT91SAM9X_WATCHDOG
426 tristate "AT91SAM9X / AT91CAP9 watchdog"
427 depends on ARCH_AT91 || COMPILE_TEST
430 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
431 reboot your system when the timeout is reached.
433 config SAMA5D4_WATCHDOG
434 tristate "Atmel SAMA5D4 Watchdog Timer"
435 depends on ARCH_AT91 || COMPILE_TEST
438 Atmel SAMA5D4 watchdog timer is embedded into SAMA5D4 chips.
439 Its Watchdog Timer Mode Register can be written more than once.
440 This will reboot your system when the timeout is reached.
442 config CADENCE_WATCHDOG
443 tristate "Cadence Watchdog Timer"
447 Say Y here if you want to include support for the watchdog
448 timer in the Xilinx Zynq.
450 config 21285_WATCHDOG
451 tristate "DC21285 watchdog"
452 depends on FOOTBRIDGE
454 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
455 here if you wish to use this. Alternatively say M to compile the
456 driver as a module, which will be called wdt285.
458 This driver does not work on all machines. In particular, early CATS
459 boards have hardware problems that will cause the machine to simply
460 lock up if the watchdog fires.
462 "If in doubt, leave it out" - say N.
465 tristate "NetWinder WB83C977 watchdog"
466 depends on (FOOTBRIDGE && ARCH_NETWINDER) || (ARM && COMPILE_TEST)
468 Say Y here to include support for the WB977 watchdog included in
469 NetWinder machines. Alternatively say M to compile the driver as
470 a module, which will be called wdt977.
472 Not sure? It's safe to say N.
474 config FTWDT010_WATCHDOG
475 tristate "Faraday Technology FTWDT010 watchdog"
476 depends on ARM || COMPILE_TEST
480 Say Y here if to include support for the Faraday Technology
481 FTWDT010 watchdog timer embedded in the Cortina Systems Gemini
484 To compile this driver as a module, choose M here: the
485 module will be called ftwdt010_wdt.
487 config IXP4XX_WATCHDOG
488 tristate "IXP4xx Watchdog"
489 depends on ARCH_IXP4XX
492 Say Y here if to include support for the watchdog timer
493 in the Intel IXP4xx network processors. This driver can
494 be built as a module by choosing M. The module will
495 be called ixp4xx_wdt.
497 Note: The internal IXP4xx watchdog does a soft CPU reset
498 which doesn't reset any peripherals. There are circumstances
499 where the watchdog will fail to reset the board correctly
500 (e.g., if the boot ROM is in an unreadable state).
502 Say N if you are unsure.
504 config S3C2410_WATCHDOG
505 tristate "S3C2410 Watchdog"
506 depends on ARCH_S3C24XX || ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS || \
509 select MFD_SYSCON if ARCH_EXYNOS
511 Watchdog timer block in the Samsung SoCs. This will reboot
512 the system when the timer expires with the watchdog enabled.
514 The driver is limited by the speed of the system's PCLK
515 signal, so with reasonably fast systems (PCLK around 50-66MHz)
516 then watchdog intervals of over approximately 20seconds are
519 The driver can be built as a module by choosing M, and will
520 be called s3c2410_wdt
522 config SA1100_WATCHDOG
523 tristate "SA1100/PXA2xx watchdog"
524 depends on ARCH_SA1100 || ARCH_PXA
526 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
527 reboot your system when timeout is reached.
529 NOTE: once enabled, this timer cannot be disabled.
531 To compile this driver as a module, choose M here: the
532 module will be called sa1100_wdt.
535 tristate "Synopsys DesignWare watchdog"
539 Say Y here if to include support for the Synopsys DesignWare
540 watchdog timer found in many chips.
541 To compile this driver as a module, choose M here: the
542 module will be called dw_wdt.
544 config EP93XX_WATCHDOG
545 tristate "EP93xx Watchdog"
546 depends on ARCH_EP93XX || COMPILE_TEST
549 Say Y here if to include support for the watchdog timer
550 embedded in the Cirrus Logic EP93xx family of devices.
552 To compile this driver as a module, choose M here: the
553 module will be called ep93xx_wdt.
556 tristate "OMAP Watchdog"
557 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || COMPILE_TEST
560 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog.
561 Say 'Y' here to enable the
562 OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
564 config PNX4008_WATCHDOG
565 tristate "LPC32XX Watchdog"
566 depends on ARCH_LPC32XX || COMPILE_TEST
569 Say Y here if to include support for the watchdog timer
570 in the LPC32XX processor.
571 This driver can be built as a module by choosing M. The module
572 will be called pnx4008_wdt.
574 Say N if you are unsure.
577 tristate "IOP Watchdog"
578 depends on ARCH_IOP13XX
579 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
581 Say Y here if to include support for the watchdog timer
582 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
583 be built as a module by choosing M. The module will
586 Note: The IOP13XX watchdog does an Internal Bus Reset which will
587 affect both cores and the peripherals of the IOP. The ATU-X
588 and/or ATUe configuration registers will remain intact, but if
589 operating as an Root Complex and/or Central Resource, the PCI-X
590 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
592 config DAVINCI_WATCHDOG
593 tristate "DaVinci watchdog"
594 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
597 Say Y here if to include support for the watchdog timer
598 in the DaVinci DM644x/DM646x or Keystone processors.
599 To compile this driver as a module, choose M here: the
600 module will be called davinci_wdt.
602 NOTE: once enabled, this timer cannot be disabled.
603 Say N if you are unsure.
605 config K3_RTI_WATCHDOG
606 tristate "Texas Instruments K3 RTI watchdog"
607 depends on ARCH_K3 || COMPILE_TEST
610 Say Y here if you want to include support for the K3 watchdog
611 timer (RTI module) available in the K3 generation of processors.
613 config ORION_WATCHDOG
614 tristate "Orion watchdog"
615 depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU || COMPILE_TEST
619 Say Y here if to include support for the watchdog timer
620 in the Marvell Orion5x and Kirkwood ARM SoCs.
621 To compile this driver as a module, choose M here: the
622 module will be called orion_wdt.
624 config RN5T618_WATCHDOG
625 tristate "Ricoh RN5T618 watchdog"
626 depends on MFD_RN5T618 || COMPILE_TEST
629 If you say yes here you get support for watchdog on the Ricoh
632 This driver can also be built as a module. If so, the module
633 will be called rn5t618_wdt.
635 config SUNXI_WATCHDOG
636 tristate "Allwinner SoCs watchdog support"
637 depends on ARCH_SUNXI || COMPILE_TEST
640 Say Y here to include support for the watchdog timer
642 To compile this driver as a module, choose M here: the
643 module will be called sunxi_wdt.
645 config NPCM7XX_WATCHDOG
646 tristate "Nuvoton NPCM750 watchdog"
647 depends on ARCH_NPCM || COMPILE_TEST
648 default y if ARCH_NPCM7XX
651 Say Y here to include Watchdog timer support for the
652 watchdog embedded into the NPCM7xx.
653 This watchdog is used to reset the system and thus cannot be
654 compiled as a module.
656 config TWL4030_WATCHDOG
657 tristate "TWL4030 Watchdog"
658 depends on TWL4030_CORE
661 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
662 watchdog timer support for TWL4030 chips.
664 config STMP3XXX_RTC_WATCHDOG
665 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
666 depends on RTC_DRV_STMP || COMPILE_TEST
669 Say Y here to include support for the watchdog timer inside
670 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
671 To compile this driver as a module, choose M here: the
672 module will be called stmp3xxx_rtc_wdt.
674 config TS4800_WATCHDOG
675 tristate "TS-4800 Watchdog"
676 depends on HAS_IOMEM && OF
677 depends on SOC_IMX51 || COMPILE_TEST
681 Technologic Systems TS-4800 has watchdog timer implemented in
682 an external FPGA. Say Y here if you want to support for the
683 watchdog timer on TS-4800 board.
685 config TS72XX_WATCHDOG
686 tristate "TS-72XX SBC Watchdog"
687 depends on MACH_TS72XX || COMPILE_TEST
690 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
691 watchdog timer implemented in a external CPLD chip. Say Y here
692 if you want to support for the watchdog timer on TS-72XX boards.
694 To compile this driver as a module, choose M here: the
695 module will be called ts72xx_wdt.
697 config MAX63XX_WATCHDOG
698 tristate "Max63xx watchdog"
702 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
704 config MAX77620_WATCHDOG
705 tristate "Maxim Max77620 Watchdog Timer"
706 depends on MFD_MAX77620 || COMPILE_TEST
709 This is the driver for the Max77620 watchdog timer.
710 Say 'Y' here to enable the watchdog timer support for
711 MAX77620 chips. To compile this driver as a module,
712 choose M here: the module will be called max77620_wdt.
715 tristate "IMX2+ Watchdog"
716 depends on ARCH_MXC || ARCH_LAYERSCAPE || COMPILE_TEST
720 This is the driver for the hardware watchdog
721 on the Freescale IMX2 and later processors.
722 If you have one of these processors and wish to have
723 watchdog support enabled, say Y, otherwise say N.
725 To compile this driver as a module, choose M here: the
726 module will be called imx2_wdt.
729 tristate "IMX SC Watchdog"
730 depends on HAVE_ARM_SMCCC
734 This is the driver for the system controller watchdog
735 on the NXP i.MX SoCs with system controller inside, the
736 watchdog driver will call ARM SMC API and trap into
737 ARM-Trusted-Firmware for operations, ARM-Trusted-Firmware
738 will request system controller to execute the operations.
739 If you have one of these processors and wish to have
740 watchdog support enabled, say Y, otherwise say N.
742 To compile this driver as a module, choose M here: the
743 module will be called imx_sc_wdt.
746 tristate "IMX7ULP Watchdog"
747 depends on ARCH_MXC || COMPILE_TEST
750 This is the driver for the hardware watchdog on the Freescale
751 IMX7ULP and later processors. If you have one of these
752 processors and wish to have watchdog support enabled,
753 say Y, otherwise say N.
755 To compile this driver as a module, choose M here: the
756 module will be called imx7ulp_wdt.
758 config UX500_WATCHDOG
759 tristate "ST-Ericsson Ux500 watchdog"
760 depends on MFD_DB8500_PRCMU
764 Say Y here to include Watchdog timer support for the watchdog
765 existing in the prcmu of ST-Ericsson Ux500 series platforms.
767 To compile this driver as a module, choose M here: the
768 module will be called ux500_wdt.
771 tristate "Retu watchdog"
775 Retu watchdog driver for Nokia Internet Tablets (770, N800,
776 N810). At least on N800 the watchdog cannot be disabled, so
777 this driver is essential and you should enable it.
779 To compile this driver as a module, choose M here: the
780 module will be called retu_wdt.
783 tristate "MOXART watchdog"
784 depends on ARCH_MOXART || COMPILE_TEST
786 Say Y here to include Watchdog timer support for the watchdog
787 existing on the MOXA ART SoC series platforms.
789 To compile this driver as a module, choose M here: the
790 module will be called moxart_wdt.
792 config ST_LPC_WATCHDOG
793 tristate "STMicroelectronics LPC Watchdog"
794 depends on ARCH_STI || COMPILE_TEST
798 Say Y here to include STMicroelectronics Low Power Controller
799 (LPC) based Watchdog timer support.
801 To compile this driver as a module, choose M here: the
802 module will be called st_lpc_wdt.
804 config TEGRA_WATCHDOG
805 tristate "Tegra watchdog"
806 depends on (ARCH_TEGRA || COMPILE_TEST) && HAS_IOMEM
809 Say Y here to include support for the watchdog timer
810 embedded in NVIDIA Tegra SoCs.
812 To compile this driver as a module, choose M here: the
813 module will be called tegra_wdt.
816 tristate "QCOM watchdog"
818 depends on ARCH_QCOM || COMPILE_TEST
821 Say Y here to include Watchdog timer support for the watchdog found
822 on QCOM chipsets. Currently supported targets are the MSM8960,
823 APQ8064, and IPQ8064.
825 To compile this driver as a module, choose M here: the
826 module will be called qcom_wdt.
828 config MESON_GXBB_WATCHDOG
829 tristate "Amlogic Meson GXBB SoCs watchdog support"
830 depends on ARCH_MESON || COMPILE_TEST
833 Say Y here to include support for the watchdog timer
834 in Amlogic Meson GXBB SoCs.
835 To compile this driver as a module, choose M here: the
836 module will be called meson_gxbb_wdt.
838 config MESON_WATCHDOG
839 tristate "Amlogic Meson SoCs watchdog support"
840 depends on ARCH_MESON || COMPILE_TEST
843 Say Y here to include support for the watchdog timer
844 in Amlogic Meson SoCs.
845 To compile this driver as a module, choose M here: the
846 module will be called meson_wdt.
848 config MEDIATEK_WATCHDOG
849 tristate "Mediatek SoCs watchdog support"
850 depends on ARCH_MEDIATEK || COMPILE_TEST
852 select RESET_CONTROLLER
854 Say Y here to include support for the watchdog timer
856 To compile this driver as a module, choose M here: the
857 module will be called mtk_wdt.
859 config DIGICOLOR_WATCHDOG
860 tristate "Conexant Digicolor SoCs watchdog support"
861 depends on ARCH_DIGICOLOR || COMPILE_TEST
864 Say Y here to include support for the watchdog timer
865 in Conexant Digicolor SoCs.
866 To compile this driver as a module, choose M here: the
867 module will be called digicolor_wdt.
869 config ARM_SMC_WATCHDOG
870 tristate "ARM Secure Monitor Call based watchdog support"
871 depends on ARM || ARM64
873 depends on HAVE_ARM_SMCCC
876 Say Y here to include support for a watchdog timer
877 implemented by the EL3 Secure Monitor on ARM platforms.
878 Requires firmware support.
879 To compile this driver as a module, choose M here: the
880 module will be called arm_smc_wdt.
882 config LPC18XX_WATCHDOG
883 tristate "LPC18xx/43xx Watchdog"
884 depends on ARCH_LPC18XX || COMPILE_TEST
888 Say Y here if to include support for the watchdog timer
889 in NXP LPC SoCs family, which includes LPC18xx/LPC43xx
891 To compile this driver as a module, choose M here: the
892 module will be called lpc18xx_wdt.
895 tristate "Renesas WDT Watchdog"
896 depends on ARCH_RENESAS || COMPILE_TEST
899 This driver adds watchdog support for the integrated watchdogs in the
900 Renesas R-Car and other SH-Mobile SoCs (usually named RWDT or SWDT).
902 config RENESAS_RZAWDT
903 tristate "Renesas RZ/A WDT Watchdog"
904 depends on ARCH_RENESAS || COMPILE_TEST
907 This driver adds watchdog support for the integrated watchdogs in the
908 Renesas RZ/A SoCs. These watchdogs can be used to reset a system.
910 config ASPEED_WATCHDOG
911 tristate "Aspeed BMC watchdog support"
912 depends on ARCH_ASPEED || COMPILE_TEST
915 Say Y here to include support for the watchdog timer
918 This driver is required to reboot the SoC.
920 To compile this driver as a module, choose M here: the
921 module will be called aspeed_wdt.
923 config STM32_WATCHDOG
924 tristate "STM32 Independent WatchDoG (IWDG) support"
925 depends on ARCH_STM32
929 Say Y here to include support for the watchdog timer
932 To compile this driver as a module, choose M here: the
933 module will be called stm32_iwdg.
935 config STPMIC1_WATCHDOG
936 tristate "STPMIC1 PMIC watchdog support"
937 depends on MFD_STPMIC1
940 Say Y here to include watchdog support embedded into STPMIC1 PMIC.
941 If the watchdog timer expires, stpmic1 will shut down all its power
944 To compile this driver as a module, choose M here: the
945 module will be called spmic1_wdt.
947 config UNIPHIER_WATCHDOG
948 tristate "UniPhier watchdog support"
949 depends on ARCH_UNIPHIER || COMPILE_TEST
950 depends on OF && MFD_SYSCON
953 Say Y here to include support watchdog timer embedded
954 into the UniPhier system.
956 To compile this driver as a module, choose M here: the
957 module will be called uniphier_wdt.
959 config RTD119X_WATCHDOG
960 bool "Realtek RTD119x/RTD129x watchdog support"
961 depends on ARCH_REALTEK || COMPILE_TEST
966 Say Y here to include support for the watchdog timer in
967 Realtek RTD1295 SoCs.
970 tristate "Spreadtrum watchdog support"
971 depends on ARCH_SPRD || COMPILE_TEST
974 Say Y here to include watchdog timer supported
975 by Spreadtrum system.
977 config PM8916_WATCHDOG
978 tristate "QCOM PM8916 pmic watchdog"
979 depends on OF && MFD_SPMI_PMIC
982 Say Y here to include support watchdog timer embedded into the
985 config VISCONTI_WATCHDOG
986 tristate "Toshiba Visconti series watchdog support"
987 depends on ARCH_VISCONTI || COMPILE_TEST
990 Say Y here to include support for the watchdog timer in Toshiba
993 config MSC313E_WATCHDOG
994 tristate "MStar MSC313e watchdog"
995 depends on ARCH_MSTARV7 || COMPILE_TEST
998 Say Y here to include support for the Watchdog timer embedded
999 into MStar MSC313e chips. This will reboot your system when the
1002 To compile this driver as a module, choose M here: the
1003 module will be called msc313e_wdt.
1005 # X86 (i386 + ia64 + x86_64) Architecture
1008 tristate "Acquire SBC Watchdog Timer"
1011 This is the driver for the hardware watchdog on Single Board
1012 Computers produced by Acquire Inc (and others). This watchdog
1013 simply watches your kernel to make sure it doesn't freeze, and if
1014 it does, it reboots your computer after a certain amount of time.
1016 To compile this driver as a module, choose M here: the
1017 module will be called acquirewdt.
1019 Most people will say N.
1021 config ADVANTECH_WDT
1022 tristate "Advantech SBC Watchdog Timer"
1025 If you are configuring a Linux kernel for the Advantech single-board
1026 computer, say `Y' here to support its built-in watchdog timer
1027 feature. More information can be found at
1028 <https://www.advantech.com.tw/products/>
1031 tristate "ALi M1535 PMU Watchdog Timer"
1032 depends on X86 && PCI
1034 This is the driver for the hardware watchdog on the ALi M1535 PMU.
1036 To compile this driver as a module, choose M here: the
1037 module will be called alim1535_wdt.
1039 Most people will say N.
1042 tristate "ALi M7101 PMU Computer Watchdog"
1045 This is the driver for the hardware watchdog on the ALi M7101 PMU
1046 as used in the x86 Cobalt servers and also found in some
1047 SPARC Netra servers too.
1049 To compile this driver as a module, choose M here: the
1050 module will be called alim7101_wdt.
1052 Most people will say N.
1055 tristate "WinSystems EBC-C384 Watchdog Timer"
1058 select WATCHDOG_CORE
1060 Enables watchdog timer support for the watchdog timer on the
1061 WinSystems EBC-C384 motherboard. The timeout may be configured via
1062 the timeout module parameter.
1065 tristate "Fintek F718xx, F818xx Super I/O Watchdog"
1068 This is the driver for the hardware watchdog on the Fintek F71808E,
1069 F71862FG, F71868, F71869, F71882FG, F71889FG, F81803, F81865, and
1070 F81866 Super I/O controllers.
1072 You can compile this driver directly into the kernel, or use
1073 it as a module. The module will be called f71808e_wdt.
1076 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
1077 depends on X86 && PCI
1078 select WATCHDOG_CORE
1080 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
1081 (Total Cost of Ownership) timer is a watchdog timer that will reboot
1082 the machine after its expiration. The expiration time can be
1083 configured with the "heartbeat" parameter.
1085 To compile this driver as a module, choose M here: the
1086 module will be called sp5100_tco.
1089 tristate "AMD Geode CS5535/CS5536 Watchdog"
1090 depends on CS5535_MFGPT
1092 This driver enables a watchdog capability built into the
1093 CS5535/CS5536 companion chips for the AMD Geode GX and LX
1094 processors. This watchdog watches your kernel to make sure
1095 it doesn't freeze, and if it does, it reboots your computer after
1096 a certain amount of time.
1098 You can compile this driver directly into the kernel, or use
1099 it as a module. The module will be called geodewdt.
1102 tristate "AMD Elan SC520 processor Watchdog"
1103 depends on MELAN || COMPILE_TEST
1105 This is the driver for the hardware watchdog built in to the
1106 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
1107 This watchdog simply watches your kernel to make sure it doesn't
1108 freeze, and if it does, it reboots your computer after a certain
1111 You can compile this driver directly into the kernel, or use
1112 it as a module. The module will be called sc520_wdt.
1114 config SBC_FITPC2_WATCHDOG
1115 tristate "Compulab SBC-FITPC2 watchdog"
1118 This is the driver for the built-in watchdog timer on the fit-PC2,
1119 fit-PC2i, CM-iAM single-board computers made by Compulab.
1121 It's possible to enable the watchdog timer either from BIOS (F2) or
1123 When the "Watchdog Timer Value" is enabled one can set 31-255 seconds
1126 Entering BIOS setup temporarily disables watchdog operation regardless
1127 of current state, so system will not be restarted while user is in
1130 Once the watchdog is enabled the system will be restarted every
1131 "Watchdog Timer Value" period, so to prevent it user can restart or
1132 disable the watchdog.
1134 To compile this driver as a module, choose M here: the
1135 module will be called sbc_fitpc2_wdt.
1137 Most people will say N.
1140 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
1143 Enable support for the watchdog timer on the Eurotech CPU-1220 and
1144 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
1145 information are at <http://www.eurotech.it/>.
1148 tristate "IB700 SBC Watchdog Timer"
1151 This is the driver for the hardware watchdog on the IB700 Single
1152 Board Computer produced by TMC Technology (www.tmc-uk.com). This
1153 watchdog simply watches your kernel to make sure it doesn't freeze,
1154 and if it does, it reboots your computer after a certain amount of time.
1156 This driver is like the WDT501 driver but for slightly different
1159 To compile this driver as a module, choose M here: the
1160 module will be called ib700wdt.
1162 Most people will say N.
1165 tristate "IBM Automatic Server Restart"
1168 This is the driver for the IBM Automatic Server Restart watchdog
1169 timer built-in into some eServer xSeries machines.
1171 To compile this driver as a module, choose M here: the
1172 module will be called ibmasr.
1175 tristate "ICP Single Board Computer Watchdog Timer"
1178 This is a driver for the hardware watchdog on the ICP Single
1179 Board Computer. This driver is working on (at least) the following
1180 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
1182 To compile this driver as a module, choose M here: the
1183 module will be called wafer5823wdt.
1186 tristate "Intel 6300ESB Timer/Watchdog"
1188 select WATCHDOG_CORE
1190 Hardware driver for the watchdog timer built into the Intel
1191 6300ESB controller hub.
1193 To compile this driver as a module, choose M here: the
1194 module will be called i6300esb.
1197 tristate "Intel Atom E6xx Watchdog"
1198 depends on X86 && PCI
1199 select WATCHDOG_CORE
1203 Hardware driver for the watchdog timer built into the Intel
1204 Atom E6XX (TunnelCreek) processor.
1206 To compile this driver as a module, choose M here: the
1207 module will be called ie6xx_wdt.
1209 config INTEL_MID_WATCHDOG
1210 tristate "Intel MID Watchdog Timer"
1211 depends on X86_INTEL_MID
1212 select WATCHDOG_CORE
1214 Watchdog timer driver built into the Intel SCU for Intel MID
1217 This driver currently supports only the watchdog evolution
1218 implementation in SCU, available for Merrifield generation.
1220 To compile this driver as a module, choose M here.
1223 tristate "Intel TCO Timer/Watchdog"
1224 depends on (X86 || IA64) && PCI
1225 select WATCHDOG_CORE
1226 depends on I2C || I2C=n
1227 depends on MFD_INTEL_PMC_BXT || !MFD_INTEL_PMC_BXT
1228 select LPC_ICH if !EXPERT
1229 select I2C_I801 if !EXPERT && I2C
1231 Hardware driver for the intel TCO timer based watchdog devices.
1232 These drivers are included in the Intel 82801 I/O Controller
1233 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
1236 The TCO (Total Cost of Ownership) timer is a watchdog timer
1237 that will reboot the machine after its second expiration. The
1238 expiration time can be configured with the "heartbeat" parameter.
1240 On some motherboards the driver may fail to reset the chipset's
1241 NO_REBOOT flag which prevents the watchdog from rebooting the
1242 machine. If this is the case you will get a kernel message like
1243 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
1245 To compile this driver as a module, choose M here: the
1246 module will be called iTCO_wdt.
1248 config ITCO_VENDOR_SUPPORT
1249 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
1252 Add vendor specific support to the intel TCO timer based watchdog
1253 devices. At this moment we only have additional support for some
1254 SuperMicro Inc. motherboards.
1257 tristate "IT8712F (Smart Guardian) Watchdog Timer"
1260 This is the driver for the built-in watchdog timer on the IT8712F
1261 Super I/0 chipset used on many motherboards.
1263 If the driver does not work, then make sure that the game port in
1264 the BIOS is enabled.
1266 To compile this driver as a module, choose M here: the
1267 module will be called it8712f_wdt.
1270 tristate "IT87 Watchdog Timer"
1272 select WATCHDOG_CORE
1274 This is the driver for the hardware watchdog on the ITE IT8607,
1275 IT8620, IT8622, IT8625, IT8628, IT8655, IT8665, IT8686, IT8702,
1276 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726, IT8728, and
1277 IT8783 Super I/O chips.
1279 This watchdog simply watches your kernel to make sure it doesn't
1280 freeze, and if it does, it reboots your computer after a certain
1283 To compile this driver as a module, choose M here: the module will
1287 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
1288 select WATCHDOG_CORE
1289 depends on X86 && PCI
1291 A software monitoring watchdog and NMI handling driver. This driver
1292 will detect lockups and provide a stack trace. This is a driver that
1293 will only load on an HP ProLiant system with a minimum of iLO2 support.
1294 To compile this driver as a module, choose M here: the module will be
1297 config HPWDT_NMI_DECODING
1298 bool "NMI support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
1299 depends on HP_WATCHDOG
1302 Enables the NMI handler for the watchdog pretimeout NMI and the iLO
1303 "Generate NMI to System" virtual button. When an NMI is claimed
1304 by the driver, panic is called.
1307 tristate "Kontron COM Watchdog Timer"
1308 depends on MFD_KEMPLD
1309 select WATCHDOG_CORE
1311 Support for the PLD watchdog on some Kontron ETX and COMexpress
1312 (ETXexpress) modules
1314 This driver can also be built as a module. If so, the module will be
1318 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
1321 This is a driver for National Semiconductor PC87307/PC97307 hardware
1322 watchdog cards as found on the SC1200. This watchdog is mainly used
1323 for power management purposes and can be used to power down the device
1324 during inactivity periods (includes interrupt activity monitoring).
1326 To compile this driver as a module, choose M here: the
1327 module will be called sc1200wdt.
1329 Most people will say N.
1332 tristate "National Semiconductor SCx200 Watchdog"
1333 depends on SCx200 && PCI
1335 Enable the built-in watchdog timer support on the National
1336 Semiconductor SCx200 processors.
1338 If compiled as a module, it will be called scx200_wdt.
1341 tristate "NS PC87413 watchdog"
1344 This is the driver for the hardware watchdog on the PC87413 chipset
1345 This watchdog simply watches your kernel to make sure it doesn't
1346 freeze, and if it does, it reboots your computer after a certain
1349 To compile this driver as a module, choose M here: the
1350 module will be called pc87413_wdt.
1352 Most people will say N.
1355 tristate "nVidia TCO Timer/Watchdog"
1356 depends on X86 && PCI
1358 Hardware driver for the TCO timer built into the nVidia Hub family
1359 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
1360 watchdog timer that will reboot the machine after its second
1361 expiration. The expiration time can be configured with the
1362 "heartbeat" parameter.
1364 On some motherboards the driver may fail to reset the chipset's
1365 NO_REBOOT flag which prevents the watchdog from rebooting the
1366 machine. If this is the case you will get a kernel message like
1367 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
1369 To compile this driver as a module, choose M here: the
1370 module will be called nv_tco.
1373 tristate "RDC R-321x SoC watchdog"
1374 depends on X86_RDC321X || COMPILE_TEST
1377 This is the driver for the built in hardware watchdog
1378 in the RDC R-321x SoC.
1380 To compile this driver as a module, choose M here: the
1381 module will be called rdc321x_wdt.
1384 tristate "SBC-60XX Watchdog Timer"
1387 This driver can be used with the watchdog timer found on some
1388 single board computers, namely the 6010 PII based computer.
1389 It may well work with other cards. It reads port 0x443 to enable
1390 and re-set the watchdog timer, and reads port 0x45 to disable
1391 the watchdog. If you have a card that behave in similar ways,
1392 you can probably make this driver work with your card as well.
1394 You can compile this driver directly into the kernel, or use
1395 it as a module. The module will be called sbc60xxwdt.
1398 tristate "SBC8360 Watchdog Timer"
1402 This is the driver for the hardware watchdog on the SBC8360 Single
1403 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
1405 To compile this driver as a module, choose M here: the
1406 module will be called sbc8360.
1408 Most people will say N.
1411 tristate "SBC Nano 7240 Watchdog Timer"
1412 depends on X86_32 && !UML
1414 This is the driver for the hardware watchdog found on the IEI
1415 single board computers EPIC Nano 7240 (and likely others). This
1416 watchdog simply watches your kernel to make sure it doesn't freeze,
1417 and if it does, it reboots your computer after a certain amount of
1420 To compile this driver as a module, choose M here: the
1421 module will be called sbc7240_wdt.
1424 tristate "SMA CPU5 Watchdog"
1428 To compile this driver as a module, choose M here: the
1429 module will be called cpu5wdt.
1431 config SMSC_SCH311X_WDT
1432 tristate "SMSC SCH311X Watchdog Timer"
1435 This is the driver for the hardware watchdog timer on the
1436 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
1437 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
1440 To compile this driver as a module, choose M here: the
1441 module will be called sch311x_wdt.
1443 config SMSC37B787_WDT
1444 tristate "Winbond SMsC37B787 Watchdog Timer"
1447 This is the driver for the hardware watchdog component on the
1448 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
1449 from Vision Systems and maybe others.
1451 This watchdog simply watches your kernel to make sure it doesn't
1452 freeze, and if it does, it reboots your computer after a certain
1455 Usually a userspace daemon will notify the kernel WDT driver that
1456 userspace is still alive, at regular intervals.
1458 To compile this driver as a module, choose M here: the
1459 module will be called smsc37b787_wdt.
1461 Most people will say N.
1464 tristate "TQ-Systems TQMX86 Watchdog Timer"
1466 select WATCHDOG_CORE
1468 This is the driver for the hardware watchdog timer in the TQMX86 IO
1469 controller found on some of their ComExpress Modules.
1471 To compile this driver as a module, choose M here; the module
1472 will be called tqmx86_wdt.
1474 Most people will say N.
1477 tristate "VIA Watchdog Timer"
1478 depends on X86 && PCI
1479 select WATCHDOG_CORE
1481 This is the driver for the hardware watchdog timer on VIA
1482 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
1484 To compile this driver as a module, choose M here; the module
1485 will be called via_wdt.
1487 Most people will say N.
1490 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
1492 select WATCHDOG_CORE
1494 This is the driver for the hardware watchdog on the following
1496 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
1510 This watchdog simply watches your kernel to make sure it doesn't
1511 freeze, and if it does, it reboots your computer after a certain
1514 To compile this driver as a module, choose M here: the
1515 module will be called w83627hf_wdt.
1517 Most people will say N.
1520 tristate "W83877F (EMACS) Watchdog Timer"
1523 This is the driver for the hardware watchdog on the W83877F chipset
1524 as used in EMACS PC-104 motherboards (and likely others). This
1525 watchdog simply watches your kernel to make sure it doesn't freeze,
1526 and if it does, it reboots your computer after a certain amount of
1529 To compile this driver as a module, choose M here: the
1530 module will be called w83877f_wdt.
1532 Most people will say N.
1535 tristate "W83977F (PCM-5335) Watchdog Timer"
1538 This is the driver for the hardware watchdog on the W83977F I/O chip
1539 as used in AAEON's PCM-5335 SBC (and likely others). This
1540 watchdog simply watches your kernel to make sure it doesn't freeze,
1541 and if it does, it reboots your computer after a certain amount of
1544 To compile this driver as a module, choose M here: the
1545 module will be called w83977f_wdt.
1548 tristate "ZF MachZ Watchdog"
1551 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1552 N. This is the driver for the watchdog timer built-in on that
1553 processor using ZF-Logic interface. This watchdog simply watches
1554 your kernel to make sure it doesn't freeze, and if it does, it
1555 reboots your computer after a certain amount of time.
1557 To compile this driver as a module, choose M here: the
1558 module will be called machzwd.
1560 config SBC_EPX_C3_WATCHDOG
1561 tristate "Winsystems SBC EPX-C3 watchdog"
1564 This is the driver for the built-in watchdog timer on the EPX-C3
1565 Single-board computer made by Winsystems, Inc.
1567 *Note*: This hardware watchdog is not probeable and thus there
1568 is no way to know if writing to its IO address will corrupt
1569 your system or have any real effect. The only way to be sure
1570 that this driver does what you want is to make sure you
1571 are running it on an EPX-C3 from Winsystems with the watchdog
1572 timer at IO address 0x1ee and 0x1ef. It will write to both those
1573 IO ports. Basically, the assumption is made that if you compile
1574 this driver into your kernel and/or load it as a module, that you
1575 know what you are doing and that you are in fact running on an
1578 To compile this driver as a module, choose M here: the
1579 module will be called sbc_epx_c3.
1581 config INTEL_MEI_WDT
1582 tristate "Intel MEI iAMT Watchdog"
1583 depends on INTEL_MEI && X86
1584 select WATCHDOG_CORE
1586 A device driver for the Intel MEI iAMT watchdog.
1588 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
1589 Whenever the OS hangs or crashes, iAMT will send an event
1590 to any subscriber to this event. The watchdog doesn't reset the
1593 To compile this driver as a module, choose M here:
1594 the module will be called mei_wdt.
1597 tristate "NI 903x/913x Watchdog"
1598 depends on X86 && ACPI
1599 select WATCHDOG_CORE
1601 This is the driver for the watchdog timer on the National Instruments
1602 903x/913x real-time controllers.
1604 To compile this driver as a module, choose M here: the module will be
1608 tristate "NIC7018 Watchdog"
1609 depends on X86 && ACPI
1610 select WATCHDOG_CORE
1612 Support for National Instruments NIC7018 Watchdog.
1614 To compile this driver as a module, choose M here: the module will be
1619 config M54xx_WATCHDOG
1620 tristate "MCF54xx watchdog support"
1623 To compile this driver as a module, choose M here: the
1624 module will be called m54xx_wdt.
1626 # MicroBlaze Architecture
1631 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1632 depends on ATH79 || (ARM && COMPILE_TEST)
1634 Hardware driver for the built-in watchdog timer on the Atheros
1635 AR71XX/AR724X/AR913X SoCs.
1638 tristate "Broadcom BCM47xx Watchdog Timer"
1639 depends on BCM47XX || ARCH_BCM_5301X || COMPILE_TEST
1640 select WATCHDOG_CORE
1642 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1645 tristate "IDT RC32434 SoC Watchdog Timer"
1646 depends on MIKROTIK_RB532
1648 Hardware driver for the IDT RC32434 SoC built-in
1651 To compile this driver as a module, choose M here: the
1652 module will be called rc32434_wdt.
1655 tristate "Indy/I2 Hardware Watchdog"
1656 depends on SGI_HAS_INDYDOG
1658 Hardware driver for the Indy's/I2's watchdog. This is a
1659 watchdog timer that will reboot the machine after a 60 second
1660 timer expired and no process has written to /dev/watchdog during
1664 tristate "Ingenic jz4740 SoC hardware watchdog"
1666 depends on COMMON_CLK
1667 select WATCHDOG_CORE
1670 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1673 tristate "MTX-1 Hardware Watchdog"
1674 depends on MIPS_MTX1 || (MIPS && COMPILE_TEST)
1676 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1677 will reboot the machine after a 100 seconds timer expired.
1680 tristate "Sibyte SoC hardware watchdog"
1681 depends on CPU_SB1 || (MIPS && COMPILE_TEST)
1683 Watchdog driver for the built in watchdog hardware in Sibyte
1684 SoC processors. There are apparently two watchdog timers
1685 on such processors; this driver supports only the first one,
1686 because currently Linux only supports exporting one watchdog
1689 To compile this driver as a loadable module, choose M here.
1690 The module will be called sb_wdog.
1693 tristate "TI AR7 Watchdog Timer"
1694 depends on AR7 || (MIPS && COMPILE_TEST)
1696 Hardware driver for the TI AR7 Watchdog Timer.
1699 tristate "Toshiba TXx9 Watchdog Timer"
1700 depends on CPU_TX39XX || CPU_TX49XX || (MIPS && COMPILE_TEST)
1701 select WATCHDOG_CORE
1703 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1706 tristate "Cavium OCTEON SOC family Watchdog Timer"
1707 depends on CAVIUM_OCTEON_SOC
1709 select WATCHDOG_CORE
1710 select EXPORT_UASM if OCTEON_WDT = m
1712 Hardware driver for OCTEON's on chip watchdog timer.
1713 Enables the watchdog for all cores running Linux. It
1714 installs a NMI handler and pokes the watchdog based on an
1715 interrupt. On first expiration of the watchdog, the
1716 interrupt handler pokes it. The second expiration causes an
1717 NMI that prints a message. The third expiration causes a
1720 When userspace has /dev/watchdog open, no poking is done
1721 from the first interrupt, it is then only poked when the
1725 tristate "Broadcom BCM63xx hardware watchdog"
1728 Watchdog driver for the built in watchdog hardware in Broadcom
1731 To compile this driver as a loadable module, choose M here.
1732 The module will be called bcm63xx_wdt.
1735 tristate "Broadcom BCM2835 hardware watchdog"
1736 depends on ARCH_BCM2835 || (OF && COMPILE_TEST)
1737 select WATCHDOG_CORE
1739 Watchdog driver for the built in watchdog hardware in Broadcom
1742 To compile this driver as a loadable module, choose M here.
1743 The module will be called bcm2835_wdt.
1746 tristate "BCM Kona Watchdog"
1747 depends on ARCH_BCM_MOBILE || COMPILE_TEST
1748 select WATCHDOG_CORE
1750 Support for the watchdog timer on the following Broadcom BCM281xx
1751 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1754 Say 'Y' or 'M' here to enable the driver. The module will be called
1757 config BCM_KONA_WDT_DEBUG
1758 bool "DEBUGFS support for BCM Kona Watchdog"
1759 depends on BCM_KONA_WDT
1761 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1762 access to the driver's internal data structures as well as watchdog
1763 timer hardware registres.
1765 If in doubt, say 'N'.
1768 tristate "BCM7038 Watchdog"
1769 select WATCHDOG_CORE
1770 depends on HAS_IOMEM
1771 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
1773 Watchdog driver for the built-in hardware in Broadcom 7038 and
1774 later SoCs used in set-top boxes. BCM7038 was made public
1775 during the 2004 CES, and since then, many Broadcom chips use this
1776 watchdog block, including some cable modem chips.
1779 tristate "Imagination Technologies PDC Watchdog Timer"
1780 depends on HAS_IOMEM
1781 depends on MIPS || COMPILE_TEST
1782 select WATCHDOG_CORE
1784 Driver for Imagination Technologies PowerDown Controller
1787 To compile this driver as a loadable module, choose M here.
1788 The module will be called imgpdc_wdt.
1791 tristate "Lantiq SoC watchdog"
1793 select WATCHDOG_CORE
1795 Hardware driver for the Lantiq SoC Watchdog Timer.
1797 config LOONGSON1_WDT
1798 tristate "Loongson1 SoC hardware watchdog"
1799 depends on MACH_LOONGSON32
1800 select WATCHDOG_CORE
1802 Hardware driver for the Loongson1 SoC Watchdog Timer.
1805 tristate "Ralink SoC watchdog"
1806 select WATCHDOG_CORE
1809 Hardware driver for the Ralink SoC Watchdog Timer.
1812 tristate "Mediatek SoC watchdog"
1813 select WATCHDOG_CORE
1814 depends on SOC_MT7620 || SOC_MT7621
1816 Hardware driver for the Mediatek/Ralink MT7621/8 SoC Watchdog Timer.
1819 tristate "Microchip PIC32 hardware watchdog"
1820 select WATCHDOG_CORE
1821 depends on MACH_PIC32 || (MIPS && COMPILE_TEST)
1823 Watchdog driver for the built in watchdog hardware in a PIC32.
1825 Configuration bits must be set appropriately for the watchdog to be
1826 controlled by this driver.
1828 To compile this driver as a loadable module, choose M here.
1829 The module will be called pic32-wdt.
1832 tristate "Microchip PIC32 Deadman Timer"
1833 select WATCHDOG_CORE
1834 depends on MACH_PIC32 || (MIPS && COMPILE_TEST)
1836 Watchdog driver for PIC32 instruction fetch counting timer. This
1837 specific timer is typically be used in mission critical and safety
1838 critical applications, where any single failure of the software
1839 functionality and sequencing must be detected.
1841 To compile this driver as a loadable module, choose M here.
1842 The module will be called pic32-dmt.
1844 # PARISC Architecture
1846 # POWERPC Architecture
1849 tristate "GE Watchdog Timer"
1852 Watchdog timer found in a number of GE single board computers.
1855 bool "MPC52xx Watchdog Timer"
1856 depends on PPC_MPC52xx || COMPILE_TEST
1858 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1861 tristate "MPC8xxx Platform Watchdog Timer"
1862 depends on PPC_8xx || PPC_83xx || PPC_86xx || PPC_MPC512x
1863 select WATCHDOG_CORE
1865 This driver is for a SoC level watchdog that exists on some
1866 Freescale PowerPC processors. So far this driver supports:
1871 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1874 tristate "PIKA FPGA Watchdog"
1875 depends on WARP || (PPC64 && COMPILE_TEST)
1878 This enables the watchdog in the PIKA FPGA. Currently used on
1882 tristate "PowerPC Book-E Watchdog Timer"
1883 depends on BOOKE || 4xx
1884 select WATCHDOG_CORE
1886 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1887 MPC85xx SOCs and the IBM PowerPC 440.
1889 Please see Documentation/watchdog/watchdog-api.rst for
1892 config BOOKE_WDT_DEFAULT_TIMEOUT
1893 int "PowerPC Book-E Watchdog Timer Default Timeout"
1894 depends on BOOKE_WDT
1895 default 38 if PPC_FSL_BOOK3E
1896 range 0 63 if PPC_FSL_BOOK3E
1897 default 3 if !PPC_FSL_BOOK3E
1898 range 0 3 if !PPC_FSL_BOOK3E
1900 Select the default watchdog timer period to be used by the PowerPC
1901 Book-E watchdog driver. A watchdog "event" occurs when the bit
1902 position represented by this number transitions from zero to one.
1904 For Freescale Book-E processors, this is a number between 0 and 63.
1905 For other Book-E processors, this is a number between 0 and 3.
1907 The value can be overridden by the wdt_period command-line parameter.
1910 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1911 select WATCHDOG_CORE
1912 depends on GPIOLIB || COMPILE_TEST
1914 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1916 The driver can also be built as a module. If so, the module will be
1919 If unsure select N here.
1921 # PPC64 Architecture
1923 config WATCHDOG_RTAS
1924 tristate "RTAS watchdog"
1927 This driver adds watchdog support for the RTAS watchdog.
1929 To compile this driver as a module, choose M here. The module
1930 will be called wdrtas.
1934 config DIAG288_WATCHDOG
1935 tristate "System z diag288 Watchdog"
1937 select WATCHDOG_CORE
1939 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1940 provide a virtual watchdog timer to their guest that cause a
1941 user define Control Program command to be executed after a
1943 LPAR provides a very similar interface. This driver handles
1946 To compile this driver as a module, choose M here. The module
1947 will be called diag288_wdt.
1949 # SUPERH (sh + sh64) Architecture
1952 tristate "SuperH Watchdog"
1953 depends on SUPERH && (CPU_SH3 || CPU_SH4 || COMPILE_TEST)
1954 select WATCHDOG_CORE
1956 This driver adds watchdog support for the integrated watchdog in the
1957 SuperH processors. If you have one of these processors and wish
1958 to have watchdog support enabled, say Y, otherwise say N.
1960 As a side note, saying Y here will automatically boost HZ to 1000
1961 so that the timer has a chance to clear the overflow counter. On
1962 slower systems (such as the SH-2 and SH-3) this will likely yield
1963 some performance issues. As such, the WDT should be avoided here
1964 unless it is absolutely necessary.
1966 To compile this driver as a module, choose M here: the
1967 module will be called shwdt.
1969 # SPARC Architecture
1971 # SPARC64 Architecture
1973 config WATCHDOG_CP1XXX
1974 tristate "CP1XXX Hardware Watchdog support"
1975 depends on SPARC64 && PCI
1977 This is the driver for the hardware watchdog timers present on
1978 Sun Microsystems CompactPCI models CP1400 and CP1500.
1980 To compile this driver as a module, choose M here: the
1981 module will be called cpwatchdog.
1983 If you do not have a CompactPCI model CP1400 or CP1500, or
1984 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1985 you should say N to this option.
1988 tristate "RIO Hardware Watchdog support"
1989 depends on SPARC64 && PCI
1991 Say Y here to support the hardware watchdog capability on Sun RIO
1992 machines. The watchdog timeout period is normally one minute but
1993 can be changed with a boot-time parameter.
1995 config WATCHDOG_SUN4V
1996 tristate "Sun4v Watchdog support"
1997 select WATCHDOG_CORE
2000 Say Y here to support the hypervisor watchdog capability embedded
2001 in the SPARC sun4v architecture.
2003 To compile this driver as a module, choose M here. The module will
2004 be called sun4v_wdt.
2006 # XTENSA Architecture
2011 tristate "Xen Watchdog support"
2013 select WATCHDOG_CORE
2015 Say Y here to support the hypervisor watchdog capability provided
2016 by Xen 4.0 and newer. The watchdog timeout period is normally one
2017 minute but can be changed with a boot-time parameter.
2020 tristate "UML watchdog"
2021 depends on UML || COMPILE_TEST
2024 # ISA-based Watchdog Cards
2027 comment "ISA-based Watchdog Cards"
2031 tristate "Berkshire Products ISA-PC Watchdog"
2034 This is the driver for the Berkshire Products ISA-PC Watchdog card.
2035 This card simply watches your kernel to make sure it doesn't freeze,
2036 and if it does, it reboots your computer after a certain amount of
2037 time. This driver is like the WDT501 driver but for different
2038 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.rst>.
2039 The PC watchdog cards can be ordered from <http://www.berkprod.com/>.
2041 To compile this driver as a module, choose M here: the
2042 module will be called pcwd.
2044 Most people will say N.
2047 tristate "Mixcom Watchdog"
2050 This is a driver for the Mixcom hardware watchdog cards. This
2051 watchdog simply watches your kernel to make sure it doesn't freeze,
2052 and if it does, it reboots your computer after a certain amount of
2055 To compile this driver as a module, choose M here: the
2056 module will be called mixcomwd.
2058 Most people will say N.
2061 tristate "WDT Watchdog timer"
2064 If you have a WDT500P or WDT501P watchdog board, say Y here,
2065 otherwise N. It is not possible to probe for this board, which means
2066 that you have to inform the kernel about the IO port and IRQ that
2067 is needed (you can do this via the io and irq parameters)
2069 To compile this driver as a module, choose M here: the
2070 module will be called wdt.
2073 # PCI-based Watchdog Cards
2076 comment "PCI-based Watchdog Cards"
2079 config PCIPCWATCHDOG
2080 tristate "Berkshire Products PCI-PC Watchdog"
2083 This is the driver for the Berkshire Products PCI-PC Watchdog card.
2084 This card simply watches your kernel to make sure it doesn't freeze,
2085 and if it does, it reboots your computer after a certain amount of
2086 time. The card can also monitor the internal temperature of the PC.
2087 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
2089 To compile this driver as a module, choose M here: the
2090 module will be called pcwd_pci.
2092 Most people will say N.
2095 tristate "PCI-WDT500/501 Watchdog timer"
2098 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
2100 If you have a PCI-WDT501 watchdog board then you can enable the
2101 temperature sensor by setting the type parameter to 501.
2103 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
2104 can do this via the tachometer parameter. Only do this if you have a
2105 fan tachometer actually set up.
2107 To compile this driver as a module, choose M here: the
2108 module will be called wdt_pci.
2111 # USB-based Watchdog Cards
2114 comment "USB-based Watchdog Cards"
2117 config USBPCWATCHDOG
2118 tristate "Berkshire Products USB-PC Watchdog"
2121 This is the driver for the Berkshire Products USB-PC Watchdog card.
2122 This card simply watches your kernel to make sure it doesn't freeze,
2123 and if it does, it reboots your computer after a certain amount of
2124 time. The card can also monitor the internal temperature of the PC.
2125 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
2127 To compile this driver as a module, choose M here: the
2128 module will be called pcwd_usb.
2130 Most people will say N.
2132 config KEEMBAY_WATCHDOG
2133 tristate "Intel Keem Bay SoC non-secure watchdog"
2134 depends on ARCH_KEEMBAY || (ARM64 && COMPILE_TEST)
2135 select WATCHDOG_CORE
2137 This option enable support for an In-secure watchdog timer driver for
2138 Intel Keem Bay SoC. This WDT has a 32 bit timer and decrements in every
2139 count unit. An interrupt will be triggered, when the count crosses
2140 the threshold configured in the register.
2142 To compile this driver as a module, choose M here: the
2143 module will be called keembay_wdt.