3 # Watchdog device configuration
7 bool "Watchdog Timer Support"
9 If you say Y here (and to one of the following options) and create a
10 character special file /dev/watchdog with major number 10 and minor
11 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
12 subsequently opening the file and then failing to write to it for
13 longer than 1 minute will result in rebooting the machine. This
14 could be useful for a networked machine that needs to come back
15 on-line as fast as possible after a lock-up. There's both a watchdog
16 implementation entirely in software (which can sometimes fail to
17 reboot the machine) and a driver for hardware watchdog boards, which
18 are more robust and can also keep track of the temperature inside
19 your computer. For details, read
20 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
22 The watchdog is usually used together with the watchdog daemon
23 which is available from
24 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
25 also monitor NFS connections and can reboot the machine when the process
33 bool "WatchDog Timer Driver Core"
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
40 config WATCHDOG_NOWAYOUT
41 bool "Disable watchdog shutdown on close"
43 The default watchdog behaviour (which you get if you say N here) is
44 to stop the timer if the process managing it closes the file
45 /dev/watchdog. It's always remotely possible that this process might
46 get killed. If you say Y here, the watchdog cannot be stopped once
49 config WATCHDOG_HANDLE_BOOT_ENABLED
50 bool "Update boot-enabled watchdog until userspace takes over"
53 The default watchdog behaviour (which you get if you say Y here) is
54 to ping watchdog devices that were enabled before the driver has
55 been loaded until control is taken over from userspace using the
56 /dev/watchdog file. If you say N here, the kernel will not update
57 the watchdog on its own. Thus if your userspace does not start fast
58 enough your device will reboot.
61 bool "Read different watchdog information through sysfs"
63 Say Y here if you want to enable watchdog device status read through
67 # General Watchdog drivers
70 comment "Watchdog Device Drivers"
72 # Architecture Independent
75 tristate "Software watchdog"
78 A software monitoring watchdog. This will fail to reboot your system
79 from some situations that the hardware watchdog will recover
80 from. Equally it's a lot cheaper to install.
82 To compile this driver as a module, choose M here: the
83 module will be called softdog.
85 config SOFT_WATCHDOG_PRETIMEOUT
86 bool "Software watchdog pretimeout governor support"
87 depends on SOFT_WATCHDOG && WATCHDOG_PRETIMEOUT_GOV
89 Enable this if you want to use pretimeout governors with the software
90 watchdog. Be aware that governors might affect the watchdog because it
91 is purely software, e.g. the panic governor will stall it!
93 config DA9052_WATCHDOG
94 tristate "Dialog DA9052 Watchdog"
95 depends on PMIC_DA9052 || COMPILE_TEST
98 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
101 Say Y here to include support for the DA9052 watchdog.
102 Alternatively say M to compile the driver as a module,
103 which will be called da9052_wdt.
105 config DA9055_WATCHDOG
106 tristate "Dialog Semiconductor DA9055 Watchdog"
107 depends on MFD_DA9055 || COMPILE_TEST
110 If you say yes here you get support for watchdog on the Dialog
111 Semiconductor DA9055 PMIC.
113 This driver can also be built as a module. If so, the module
114 will be called da9055_wdt.
116 config DA9063_WATCHDOG
117 tristate "Dialog DA9063 Watchdog"
118 depends on MFD_DA9063 || COMPILE_TEST
121 Support for the watchdog in the DA9063 PMIC.
123 This driver can be built as a module. The module name is da9063_wdt.
125 config DA9062_WATCHDOG
126 tristate "Dialog DA9062/61 Watchdog"
127 depends on MFD_DA9062 || COMPILE_TEST
130 Support for the watchdog in the DA9062 and DA9061 PMICs.
132 This driver can be built as a module. The module name is da9062_wdt.
135 tristate "Watchdog device controlled through GPIO-line"
139 If you say yes here you get support for watchdog device
140 controlled through GPIO-line.
142 config GPIO_WATCHDOG_ARCH_INITCALL
143 bool "Register the watchdog as early as possible"
144 depends on GPIO_WATCHDOG=y
146 In some situations, the default initcall level (module_init)
147 in not early enough in the boot process to avoid the watchdog
149 If you say yes here, the initcall level would be raised to
153 config MENF21BMC_WATCHDOG
154 tristate "MEN 14F021P00 BMC Watchdog"
155 depends on MFD_MENF21BMC || COMPILE_TEST
159 Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
161 This driver can also be built as a module. If so the module
162 will be called menf21bmc_wdt.
164 config TANGOX_WATCHDOG
165 tristate "Sigma Designs SMP86xx/SMP87xx watchdog"
167 depends on ARCH_TANGO || COMPILE_TEST
170 Support for the watchdog in Sigma Designs SMP86xx (tango3)
171 and SMP87xx (tango4) family chips.
173 This driver can be built as a module. The module name is tangox_wdt.
176 tristate "ACPI Watchdog Action Table (WDAT)"
181 This driver adds support for systems with ACPI Watchdog Action
182 Table (WDAT) table. Servers typically have this but it can be
183 found on some desktop machines as well. This driver will take
184 over the native iTCO watchdog driver found on many Intel CPUs.
186 To compile this driver as module, choose M here: the module will
189 config WM831X_WATCHDOG
190 tristate "WM831x watchdog"
191 depends on MFD_WM831X
194 Support for the watchdog in the WM831x AudioPlus PMICs. When
195 the watchdog triggers the system will be reset.
197 config WM8350_WATCHDOG
198 tristate "WM8350 watchdog"
199 depends on MFD_WM8350
202 Support for the watchdog in the WM8350 AudioPlus PMIC. When
203 the watchdog triggers the system will be reset.
205 config XILINX_WATCHDOG
206 tristate "Xilinx Watchdog timer"
210 Watchdog driver for the xps_timebase_wdt ip core.
212 To compile this driver as a module, choose M here: the
213 module will be called of_xilinx_wdt.
215 config ZIIRAVE_WATCHDOG
216 tristate "Zodiac RAVE Watchdog Timer"
220 Watchdog driver for the Zodiac Aerospace RAVE Switch Watchdog
223 To compile this driver as a module, choose M here: the
224 module will be called ziirave_wdt.
226 config RAVE_SP_WATCHDOG
227 tristate "RAVE SP Watchdog timer"
228 depends on RAVE_SP_CORE
231 Support for the watchdog on RAVE SP device.
237 config ARM_SP805_WATCHDOG
238 tristate "ARM SP805 Watchdog"
239 depends on (ARM || ARM64 || COMPILE_TEST) && ARM_AMBA
242 ARM Primecell SP805 Watchdog timer. This will reboot your system when
243 the timeout is reached.
245 config ARM_SBSA_WATCHDOG
246 tristate "ARM SBSA Generic Watchdog"
248 depends on ARM_ARCH_TIMER
251 ARM SBSA Generic Watchdog has two stage timeouts:
252 the first signal (WS0) is for alerting the system by interrupt,
253 the second one (WS1) is a real hardware reset.
254 More details: ARM DEN0029B - Server Base System Architecture (SBSA)
256 This driver can operate ARM SBSA Generic Watchdog as a single stage
257 or a two stages watchdog, it depends on the module parameter "action".
259 Note: the maximum timeout in the two stages mode is half of that in
260 the single stage mode.
262 To compile this driver as module, choose M here: The module
263 will be called sbsa_gwdt.
265 config ASM9260_WATCHDOG
266 tristate "Alphascale ASM9260 watchdog"
267 depends on MACH_ASM9260 || COMPILE_TEST
270 select RESET_CONTROLLER
272 Watchdog timer embedded into Alphascale asm9260 chips. This will reboot your
273 system when the timeout is reached.
275 config AT91RM9200_WATCHDOG
276 tristate "AT91RM9200 watchdog"
277 depends on (SOC_AT91RM9200 && MFD_SYSCON) || COMPILE_TEST
279 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
280 system when the timeout is reached.
282 config AT91SAM9X_WATCHDOG
283 tristate "AT91SAM9X / AT91CAP9 watchdog"
284 depends on ARCH_AT91 || COMPILE_TEST
287 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
288 reboot your system when the timeout is reached.
290 config SAMA5D4_WATCHDOG
291 tristate "Atmel SAMA5D4 Watchdog Timer"
292 depends on ARCH_AT91 || COMPILE_TEST
295 Atmel SAMA5D4 watchdog timer is embedded into SAMA5D4 chips.
296 Its Watchdog Timer Mode Register can be written more than once.
297 This will reboot your system when the timeout is reached.
299 config CADENCE_WATCHDOG
300 tristate "Cadence Watchdog Timer"
304 Say Y here if you want to include support for the watchdog
305 timer in the Xilinx Zynq.
307 config 21285_WATCHDOG
308 tristate "DC21285 watchdog"
309 depends on FOOTBRIDGE
311 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
312 here if you wish to use this. Alternatively say M to compile the
313 driver as a module, which will be called wdt285.
315 This driver does not work on all machines. In particular, early CATS
316 boards have hardware problems that will cause the machine to simply
317 lock up if the watchdog fires.
319 "If in doubt, leave it out" - say N.
322 tristate "NetWinder WB83C977 watchdog"
323 depends on (FOOTBRIDGE && ARCH_NETWINDER) || (ARM && COMPILE_TEST)
325 Say Y here to include support for the WB977 watchdog included in
326 NetWinder machines. Alternatively say M to compile the driver as
327 a module, which will be called wdt977.
329 Not sure? It's safe to say N.
331 config GEMINI_WATCHDOG
332 tristate "Gemini watchdog"
333 depends on ARCH_GEMINI
336 Say Y here if to include support for the watchdog timer
337 embedded in the Cortina Systems Gemini family of devices.
339 To compile this driver as a module, choose M here: the
340 module will be called gemini_wdt.
342 config IXP4XX_WATCHDOG
343 tristate "IXP4xx Watchdog"
344 depends on ARCH_IXP4XX
346 Say Y here if to include support for the watchdog timer
347 in the Intel IXP4xx network processors. This driver can
348 be built as a module by choosing M. The module will
349 be called ixp4xx_wdt.
351 Note: The internal IXP4xx watchdog does a soft CPU reset
352 which doesn't reset any peripherals. There are circumstances
353 where the watchdog will fail to reset the board correctly
354 (e.g., if the boot ROM is in an unreadable state).
356 Say N if you are unsure.
358 config KS8695_WATCHDOG
359 tristate "KS8695 watchdog"
360 depends on ARCH_KS8695
362 Watchdog timer embedded into KS8695 processor. This will reboot your
363 system when the timeout is reached.
365 config HAVE_S3C2410_WATCHDOG
368 This will include watchdog timer support for Samsung SoCs. If
369 you want to include watchdog support for any machine, kindly
370 select this in the respective mach-XXXX/Kconfig file.
372 config S3C2410_WATCHDOG
373 tristate "S3C2410 Watchdog"
374 depends on HAVE_S3C2410_WATCHDOG || COMPILE_TEST
376 select MFD_SYSCON if ARCH_EXYNOS
378 Watchdog timer block in the Samsung SoCs. This will reboot
379 the system when the timer expires with the watchdog enabled.
381 The driver is limited by the speed of the system's PCLK
382 signal, so with reasonably fast systems (PCLK around 50-66MHz)
383 then watchdog intervals of over approximately 20seconds are
386 The driver can be built as a module by choosing M, and will
387 be called s3c2410_wdt
389 config SA1100_WATCHDOG
390 tristate "SA1100/PXA2xx watchdog"
391 depends on ARCH_SA1100 || ARCH_PXA
393 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
394 reboot your system when timeout is reached.
396 NOTE: once enabled, this timer cannot be disabled.
398 To compile this driver as a module, choose M here: the
399 module will be called sa1100_wdt.
402 tristate "Synopsys DesignWare watchdog"
406 Say Y here if to include support for the Synopsys DesignWare
407 watchdog timer found in many chips.
408 To compile this driver as a module, choose M here: the
409 module will be called dw_wdt.
411 config EP93XX_WATCHDOG
412 tristate "EP93xx Watchdog"
413 depends on ARCH_EP93XX || COMPILE_TEST
416 Say Y here if to include support for the watchdog timer
417 embedded in the Cirrus Logic EP93xx family of devices.
419 To compile this driver as a module, choose M here: the
420 module will be called ep93xx_wdt.
423 tristate "OMAP Watchdog"
424 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || COMPILE_TEST
427 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
428 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
430 config PNX4008_WATCHDOG
431 tristate "LPC32XX Watchdog"
432 depends on ARCH_LPC32XX
435 Say Y here if to include support for the watchdog timer
436 in the LPC32XX processor.
437 This driver can be built as a module by choosing M. The module
438 will be called pnx4008_wdt.
440 Say N if you are unsure.
443 tristate "IOP Watchdog"
444 depends on ARCH_IOP13XX
445 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
447 Say Y here if to include support for the watchdog timer
448 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
449 be built as a module by choosing M. The module will
452 Note: The IOP13XX watchdog does an Internal Bus Reset which will
453 affect both cores and the peripherals of the IOP. The ATU-X
454 and/or ATUe configuration registers will remain intact, but if
455 operating as an Root Complex and/or Central Resource, the PCI-X
456 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
458 config DAVINCI_WATCHDOG
459 tristate "DaVinci watchdog"
460 depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
463 Say Y here if to include support for the watchdog timer
464 in the DaVinci DM644x/DM646x or Keystone processors.
465 To compile this driver as a module, choose M here: the
466 module will be called davinci_wdt.
468 NOTE: once enabled, this timer cannot be disabled.
469 Say N if you are unsure.
471 config ORION_WATCHDOG
472 tristate "Orion watchdog"
473 depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU || (COMPILE_TEST && !ARCH_EBSA110)
477 Say Y here if to include support for the watchdog timer
478 in the Marvell Orion5x and Kirkwood ARM SoCs.
479 To compile this driver as a module, choose M here: the
480 module will be called orion_wdt.
482 config RN5T618_WATCHDOG
483 tristate "Ricoh RN5T618 watchdog"
484 depends on MFD_RN5T618 || COMPILE_TEST
487 If you say yes here you get support for watchdog on the Ricoh
490 This driver can also be built as a module. If so, the module
491 will be called rn5t618_wdt.
493 config SUNXI_WATCHDOG
494 tristate "Allwinner SoCs watchdog support"
495 depends on ARCH_SUNXI || COMPILE_TEST
498 Say Y here to include support for the watchdog timer
500 To compile this driver as a module, choose M here: the
501 module will be called sunxi_wdt.
503 config COH901327_WATCHDOG
504 bool "ST-Ericsson COH 901 327 watchdog"
505 depends on ARCH_U300 || (ARM && COMPILE_TEST)
506 default y if MACH_U300
509 Say Y here to include Watchdog timer support for the
510 watchdog embedded into the ST-Ericsson U300 series platforms.
511 This watchdog is used to reset the system and thus cannot be
512 compiled as a module.
514 config TWL4030_WATCHDOG
515 tristate "TWL4030 Watchdog"
516 depends on TWL4030_CORE
519 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
520 watchdog timer support for TWL4030 chips.
522 config STMP3XXX_RTC_WATCHDOG
523 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
524 depends on RTC_DRV_STMP || COMPILE_TEST
527 Say Y here to include support for the watchdog timer inside
528 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
529 To compile this driver as a module, choose M here: the
530 module will be called stmp3xxx_rtc_wdt.
532 config NUC900_WATCHDOG
533 tristate "Nuvoton NUC900 watchdog"
534 depends on ARCH_W90X900 || COMPILE_TEST
536 Say Y here if to include support for the watchdog timer
537 for the Nuvoton NUC900 series SoCs.
538 To compile this driver as a module, choose M here: the
539 module will be called nuc900_wdt.
541 config TS4800_WATCHDOG
542 tristate "TS-4800 Watchdog"
543 depends on HAS_IOMEM && OF
544 depends on SOC_IMX51 || COMPILE_TEST
548 Technologic Systems TS-4800 has watchdog timer implemented in
549 an external FPGA. Say Y here if you want to support for the
550 watchdog timer on TS-4800 board.
552 config TS72XX_WATCHDOG
553 tristate "TS-72XX SBC Watchdog"
554 depends on MACH_TS72XX || COMPILE_TEST
556 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
557 watchdog timer implemented in a external CPLD chip. Say Y here
558 if you want to support for the watchdog timer on TS-72XX boards.
560 To compile this driver as a module, choose M here: the
561 module will be called ts72xx_wdt.
563 config MAX63XX_WATCHDOG
564 tristate "Max63xx watchdog"
568 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
570 config MAX77620_WATCHDOG
571 tristate "Maxim Max77620 Watchdog Timer"
572 depends on MFD_MAX77620 || COMPILE_TEST
574 This is the driver for the Max77620 watchdog timer.
575 Say 'Y' here to enable the watchdog timer support for
576 MAX77620 chips. To compile this driver as a module,
577 choose M here: the module will be called max77620_wdt.
580 tristate "IMX2+ Watchdog"
581 depends on ARCH_MXC || ARCH_LAYERSCAPE || COMPILE_TEST
585 This is the driver for the hardware watchdog
586 on the Freescale IMX2 and later processors.
587 If you have one of these processors and wish to have
588 watchdog support enabled, say Y, otherwise say N.
590 To compile this driver as a module, choose M here: the
591 module will be called imx2_wdt.
593 config UX500_WATCHDOG
594 tristate "ST-Ericsson Ux500 watchdog"
595 depends on MFD_DB8500_PRCMU
599 Say Y here to include Watchdog timer support for the watchdog
600 existing in the prcmu of ST-Ericsson Ux500 series platforms.
602 To compile this driver as a module, choose M here: the
603 module will be called ux500_wdt.
606 tristate "Retu watchdog"
610 Retu watchdog driver for Nokia Internet Tablets (770, N800,
611 N810). At least on N800 the watchdog cannot be disabled, so
612 this driver is essential and you should enable it.
614 To compile this driver as a module, choose M here: the
615 module will be called retu_wdt.
618 tristate "MOXART watchdog"
619 depends on ARCH_MOXART || COMPILE_TEST
621 Say Y here to include Watchdog timer support for the watchdog
622 existing on the MOXA ART SoC series platforms.
624 To compile this driver as a module, choose M here: the
625 module will be called moxart_wdt.
627 config SIRFSOC_WATCHDOG
628 tristate "SiRFSOC watchdog"
629 depends on ARCH_SIRF || COMPILE_TEST
633 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
634 the watchdog triggers the system will be reset.
636 config ST_LPC_WATCHDOG
637 tristate "STMicroelectronics LPC Watchdog"
638 depends on ARCH_STI || COMPILE_TEST
642 Say Y here to include STMicroelectronics Low Power Controller
643 (LPC) based Watchdog timer support.
645 To compile this driver as a module, choose M here: the
646 module will be called st_lpc_wdt.
648 config TEGRA_WATCHDOG
649 tristate "Tegra watchdog"
650 depends on (ARCH_TEGRA || COMPILE_TEST) && HAS_IOMEM
653 Say Y here to include support for the watchdog timer
654 embedded in NVIDIA Tegra SoCs.
656 To compile this driver as a module, choose M here: the
657 module will be called tegra_wdt.
660 tristate "QCOM watchdog"
662 depends on ARCH_QCOM || COMPILE_TEST
665 Say Y here to include Watchdog timer support for the watchdog found
666 on QCOM chipsets. Currently supported targets are the MSM8960,
667 APQ8064, and IPQ8064.
669 To compile this driver as a module, choose M here: the
670 module will be called qcom_wdt.
672 config MESON_GXBB_WATCHDOG
673 tristate "Amlogic Meson GXBB SoCs watchdog support"
674 depends on ARCH_MESON || COMPILE_TEST
677 Say Y here to include support for the watchdog timer
678 in Amlogic Meson GXBB SoCs.
679 To compile this driver as a module, choose M here: the
680 module will be called meson_gxbb_wdt.
682 config MESON_WATCHDOG
683 tristate "Amlogic Meson SoCs watchdog support"
684 depends on ARCH_MESON || COMPILE_TEST
687 Say Y here to include support for the watchdog timer
688 in Amlogic Meson SoCs.
689 To compile this driver as a module, choose M here: the
690 module will be called meson_wdt.
692 config MEDIATEK_WATCHDOG
693 tristate "Mediatek SoCs watchdog support"
694 depends on ARCH_MEDIATEK || COMPILE_TEST
697 Say Y here to include support for the watchdog timer
699 To compile this driver as a module, choose M here: the
700 module will be called mtk_wdt.
702 config DIGICOLOR_WATCHDOG
703 tristate "Conexant Digicolor SoCs watchdog support"
704 depends on ARCH_DIGICOLOR || COMPILE_TEST
707 Say Y here to include support for the watchdog timer
708 in Conexant Digicolor SoCs.
709 To compile this driver as a module, choose M here: the
710 module will be called digicolor_wdt.
712 config LPC18XX_WATCHDOG
713 tristate "LPC18xx/43xx Watchdog"
714 depends on ARCH_LPC18XX || COMPILE_TEST
718 Say Y here if to include support for the watchdog timer
719 in NXP LPC SoCs family, which includes LPC18xx/LPC43xx
721 To compile this driver as a module, choose M here: the
722 module will be called lpc18xx_wdt.
724 config ATLAS7_WATCHDOG
725 tristate "CSRatlas7 watchdog"
726 depends on ARCH_ATLAS7 || COMPILE_TEST
728 Say Y here to include Watchdog timer support for the watchdog
729 existing on the CSRatlas7 series platforms.
731 To compile this driver as a module, choose M here: the
732 module will be called atlas7_wdt.
735 tristate "Renesas WDT Watchdog"
736 depends on ARCH_RENESAS || COMPILE_TEST
739 This driver adds watchdog support for the integrated watchdogs in the
740 Renesas R-Car and other SH-Mobile SoCs (usually named RWDT or SWDT).
742 config RENESAS_RZAWDT
743 tristate "Renesas RZ/A WDT Watchdog"
744 depends on ARCH_RENESAS || COMPILE_TEST
747 This driver adds watchdog support for the integrated watchdogs in the
748 Renesas RZ/A SoCs. These watchdogs can be used to reset a system.
750 config ASPEED_WATCHDOG
751 tristate "Aspeed 2400 watchdog support"
752 depends on ARCH_ASPEED || COMPILE_TEST
755 Say Y here to include support for the watchdog timer
758 This driver is required to reboot the SoC.
760 To compile this driver as a module, choose M here: the
761 module will be called aspeed_wdt.
763 config ZX2967_WATCHDOG
764 tristate "ZTE zx2967 SoCs watchdog support"
768 Say Y here to include support for the watchdog timer
770 To compile this driver as a module, choose M here: the
771 module will be called zx2967_wdt.
773 config STM32_WATCHDOG
774 tristate "STM32 Independent WatchDoG (IWDG) support"
775 depends on ARCH_STM32
779 Say Y here to include support for the watchdog timer
782 To compile this driver as a module, choose M here: the
783 module will be called stm32_iwdg.
785 config UNIPHIER_WATCHDOG
786 tristate "UniPhier watchdog support"
787 depends on ARCH_UNIPHIER || COMPILE_TEST
788 depends on OF && MFD_SYSCON
791 Say Y here to include support watchdog timer embedded
792 into the UniPhier system.
794 To compile this driver as a module, choose M here: the
795 module will be called uniphier_wdt.
799 config AT32AP700X_WDT
800 tristate "AT32AP700x watchdog"
801 depends on CPU_AT32AP700X || COMPILE_TEST
803 Watchdog timer embedded into AT32AP700x devices. This will reboot
804 your system when the timeout is reached.
806 # BLACKFIN Architecture
809 tristate "Blackfin On-Chip Watchdog Timer"
812 If you say yes here you will get support for the Blackfin On-Chip
813 Watchdog Timer. If you have one of these processors and wish to
814 have watchdog support enabled, say Y, otherwise say N.
816 To compile this driver as a module, choose M here: the
817 module will be called bfin_wdt.
823 # X86 (i386 + ia64 + x86_64) Architecture
826 tristate "Acquire SBC Watchdog Timer"
829 This is the driver for the hardware watchdog on Single Board
830 Computers produced by Acquire Inc (and others). This watchdog
831 simply watches your kernel to make sure it doesn't freeze, and if
832 it does, it reboots your computer after a certain amount of time.
834 To compile this driver as a module, choose M here: the
835 module will be called acquirewdt.
837 Most people will say N.
840 tristate "Advantech SBC Watchdog Timer"
843 If you are configuring a Linux kernel for the Advantech single-board
844 computer, say `Y' here to support its built-in watchdog timer
845 feature. More information can be found at
846 <http://www.advantech.com.tw/products/>
849 tristate "ALi M1535 PMU Watchdog Timer"
850 depends on X86 && PCI
852 This is the driver for the hardware watchdog on the ALi M1535 PMU.
854 To compile this driver as a module, choose M here: the
855 module will be called alim1535_wdt.
857 Most people will say N.
860 tristate "ALi M7101 PMU Computer Watchdog"
863 This is the driver for the hardware watchdog on the ALi M7101 PMU
864 as used in the x86 Cobalt servers and also found in some
865 SPARC Netra servers too.
867 To compile this driver as a module, choose M here: the
868 module will be called alim7101_wdt.
870 Most people will say N.
873 tristate "WinSystems EBC-C384 Watchdog Timer"
874 depends on X86 && ISA_BUS_API
877 Enables watchdog timer support for the watchdog timer on the
878 WinSystems EBC-C384 motherboard. The timeout may be configured via
879 the timeout module parameter.
882 tristate "Fintek F718xx, F818xx Super I/O Watchdog"
885 This is the driver for the hardware watchdog on the Fintek F71808E,
886 F71862FG, F71868, F71869, F71882FG, F71889FG, F81865 and F81866
887 Super I/O controllers.
889 You can compile this driver directly into the kernel, or use
890 it as a module. The module will be called f71808e_wdt.
893 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
894 depends on X86 && PCI
896 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
897 (Total Cost of Ownership) timer is a watchdog timer that will reboot
898 the machine after its expiration. The expiration time can be
899 configured with the "heartbeat" parameter.
901 To compile this driver as a module, choose M here: the
902 module will be called sp5100_tco.
905 tristate "AMD Geode CS5535/CS5536 Watchdog"
906 depends on CS5535_MFGPT
908 This driver enables a watchdog capability built into the
909 CS5535/CS5536 companion chips for the AMD Geode GX and LX
910 processors. This watchdog watches your kernel to make sure
911 it doesn't freeze, and if it does, it reboots your computer after
912 a certain amount of time.
914 You can compile this driver directly into the kernel, or use
915 it as a module. The module will be called geodewdt.
918 tristate "AMD Elan SC520 processor Watchdog"
919 depends on MELAN || COMPILE_TEST
921 This is the driver for the hardware watchdog built in to the
922 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
923 This watchdog simply watches your kernel to make sure it doesn't
924 freeze, and if it does, it reboots your computer after a certain
927 You can compile this driver directly into the kernel, or use
928 it as a module. The module will be called sc520_wdt.
930 config SBC_FITPC2_WATCHDOG
931 tristate "Compulab SBC-FITPC2 watchdog"
934 This is the driver for the built-in watchdog timer on the fit-PC2,
935 fit-PC2i, CM-iAM single-board computers made by Compulab.
937 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
938 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
940 Entering BIOS setup temporary disables watchdog operation regardless to current state,
941 so system will not be restarted while user in BIOS setup.
943 Once watchdog was enabled the system will be restarted every
944 "Watchdog Timer Value" period, so to prevent it user can restart or
945 disable the watchdog.
947 To compile this driver as a module, choose M here: the
948 module will be called sbc_fitpc2_wdt.
950 Most people will say N.
953 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
956 Enable support for the watchdog timer on the Eurotech CPU-1220 and
957 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
958 information are at <http://www.eurotech.it/>.
961 tristate "IB700 SBC Watchdog Timer"
964 This is the driver for the hardware watchdog on the IB700 Single
965 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
966 simply watches your kernel to make sure it doesn't freeze, and if
967 it does, it reboots your computer after a certain amount of time.
969 This driver is like the WDT501 driver but for slightly different hardware.
971 To compile this driver as a module, choose M here: the
972 module will be called ib700wdt.
974 Most people will say N.
977 tristate "IBM Automatic Server Restart"
980 This is the driver for the IBM Automatic Server Restart watchdog
981 timer built-in into some eServer xSeries machines.
983 To compile this driver as a module, choose M here: the
984 module will be called ibmasr.
987 tristate "ICP Single Board Computer Watchdog Timer"
990 This is a driver for the hardware watchdog on the ICP Single
991 Board Computer. This driver is working on (at least) the following
992 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
994 To compile this driver as a module, choose M here: the
995 module will be called wafer5823wdt.
998 tristate "Intel 6300ESB Timer/Watchdog"
1001 Hardware driver for the watchdog timer built into the Intel
1002 6300ESB controller hub.
1004 To compile this driver as a module, choose M here: the
1005 module will be called i6300esb.
1008 tristate "Intel Atom E6xx Watchdog"
1009 depends on X86 && PCI
1010 select WATCHDOG_CORE
1014 Hardware driver for the watchdog timer built into the Intel
1015 Atom E6XX (TunnelCreek) processor.
1017 To compile this driver as a module, choose M here: the
1018 module will be called ie6xx_wdt.
1020 config INTEL_SCU_WATCHDOG
1021 bool "Intel SCU Watchdog for Mobile Platforms"
1022 depends on X86_INTEL_MID
1024 Hardware driver for the watchdog time built into the Intel SCU
1025 for Intel Mobile Platforms.
1027 To compile this driver as a module, choose M here.
1029 config INTEL_MID_WATCHDOG
1030 tristate "Intel MID Watchdog Timer"
1031 depends on X86_INTEL_MID
1032 select WATCHDOG_CORE
1034 Watchdog timer driver built into the Intel SCU for Intel MID
1037 This driver currently supports only the watchdog evolution
1038 implementation in SCU, available for Merrifield generation.
1040 To compile this driver as a module, choose M here.
1043 tristate "Intel TCO Timer/Watchdog"
1044 depends on (X86 || IA64) && PCI
1045 select WATCHDOG_CORE
1046 depends on I2C || I2C=n
1047 select LPC_ICH if !EXPERT
1048 select I2C_I801 if !EXPERT && I2C
1050 Hardware driver for the intel TCO timer based watchdog devices.
1051 These drivers are included in the Intel 82801 I/O Controller
1052 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
1055 The TCO (Total Cost of Ownership) timer is a watchdog timer
1056 that will reboot the machine after its second expiration. The
1057 expiration time can be configured with the "heartbeat" parameter.
1059 On some motherboards the driver may fail to reset the chipset's
1060 NO_REBOOT flag which prevents the watchdog from rebooting the
1061 machine. If this is the case you will get a kernel message like
1062 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
1064 To compile this driver as a module, choose M here: the
1065 module will be called iTCO_wdt.
1067 config ITCO_VENDOR_SUPPORT
1068 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
1071 Add vendor specific support to the intel TCO timer based watchdog
1072 devices. At this moment we only have additional support for some
1073 SuperMicro Inc. motherboards.
1076 tristate "IT8712F (Smart Guardian) Watchdog Timer"
1079 This is the driver for the built-in watchdog timer on the IT8712F
1080 Super I/0 chipset used on many motherboards.
1082 If the driver does not work, then make sure that the game port in
1083 the BIOS is enabled.
1085 To compile this driver as a module, choose M here: the
1086 module will be called it8712f_wdt.
1089 tristate "IT87 Watchdog Timer"
1091 select WATCHDOG_CORE
1093 This is the driver for the hardware watchdog on the ITE IT8607,
1094 IT8620, IT8622, IT8625, IT8628, IT8655, IT8665, IT8686, IT8702,
1095 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726, IT8728, and
1096 IT8783 Super I/O chips.
1098 This watchdog simply watches your kernel to make sure it doesn't
1099 freeze, and if it does, it reboots your computer after a certain
1102 To compile this driver as a module, choose M here: the module will
1106 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
1107 depends on X86 && PCI
1109 A software monitoring watchdog and NMI sourcing driver. This driver
1110 will detect lockups and provide a stack trace. This is a driver that
1111 will only load on an HP ProLiant system with a minimum of iLO2 support.
1112 To compile this driver as a module, choose M here: the module will be
1116 tristate "Kontron COM Watchdog Timer"
1117 depends on MFD_KEMPLD
1118 select WATCHDOG_CORE
1120 Support for the PLD watchdog on some Kontron ETX and COMexpress
1121 (ETXexpress) modules
1123 This driver can also be built as a module. If so, the module will be
1126 config HPWDT_NMI_DECODING
1127 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
1128 depends on HP_WATCHDOG
1131 When an NMI occurs this feature will make the necessary BIOS calls to
1132 log the cause of the NMI.
1135 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
1138 This is a driver for National Semiconductor PC87307/PC97307 hardware
1139 watchdog cards as found on the SC1200. This watchdog is mainly used
1140 for power management purposes and can be used to power down the device
1141 during inactivity periods (includes interrupt activity monitoring).
1143 To compile this driver as a module, choose M here: the
1144 module will be called sc1200wdt.
1146 Most people will say N.
1149 tristate "National Semiconductor SCx200 Watchdog"
1150 depends on SCx200 && PCI
1152 Enable the built-in watchdog timer support on the National
1153 Semiconductor SCx200 processors.
1155 If compiled as a module, it will be called scx200_wdt.
1158 tristate "NS PC87413 watchdog"
1161 This is the driver for the hardware watchdog on the PC87413 chipset
1162 This watchdog simply watches your kernel to make sure it doesn't
1163 freeze, and if it does, it reboots your computer after a certain
1166 To compile this driver as a module, choose M here: the
1167 module will be called pc87413_wdt.
1169 Most people will say N.
1172 tristate "nVidia TCO Timer/Watchdog"
1173 depends on X86 && PCI
1175 Hardware driver for the TCO timer built into the nVidia Hub family
1176 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
1177 watchdog timer that will reboot the machine after its second
1178 expiration. The expiration time can be configured with the
1179 "heartbeat" parameter.
1181 On some motherboards the driver may fail to reset the chipset's
1182 NO_REBOOT flag which prevents the watchdog from rebooting the
1183 machine. If this is the case you will get a kernel message like
1184 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
1186 To compile this driver as a module, choose M here: the
1187 module will be called nv_tco.
1190 tristate "RDC R-321x SoC watchdog"
1191 depends on X86_RDC321X || COMPILE_TEST
1194 This is the driver for the built in hardware watchdog
1195 in the RDC R-321x SoC.
1197 To compile this driver as a module, choose M here: the
1198 module will be called rdc321x_wdt.
1201 tristate "SBC-60XX Watchdog Timer"
1204 This driver can be used with the watchdog timer found on some
1205 single board computers, namely the 6010 PII based computer.
1206 It may well work with other cards. It reads port 0x443 to enable
1207 and re-set the watchdog timer, and reads port 0x45 to disable
1208 the watchdog. If you have a card that behave in similar ways,
1209 you can probably make this driver work with your card as well.
1211 You can compile this driver directly into the kernel, or use
1212 it as a module. The module will be called sbc60xxwdt.
1215 tristate "SBC8360 Watchdog Timer"
1219 This is the driver for the hardware watchdog on the SBC8360 Single
1220 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
1222 To compile this driver as a module, choose M here: the
1223 module will be called sbc8360.
1225 Most people will say N.
1228 tristate "SBC Nano 7240 Watchdog Timer"
1229 depends on X86_32 && !UML
1231 This is the driver for the hardware watchdog found on the IEI
1232 single board computers EPIC Nano 7240 (and likely others). This
1233 watchdog simply watches your kernel to make sure it doesn't freeze,
1234 and if it does, it reboots your computer after a certain amount of
1237 To compile this driver as a module, choose M here: the
1238 module will be called sbc7240_wdt.
1241 tristate "SMA CPU5 Watchdog"
1245 To compile this driver as a module, choose M here: the
1246 module will be called cpu5wdt.
1248 config SMSC_SCH311X_WDT
1249 tristate "SMSC SCH311X Watchdog Timer"
1252 This is the driver for the hardware watchdog timer on the
1253 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
1254 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
1257 To compile this driver as a module, choose M here: the
1258 module will be called sch311x_wdt.
1260 config SMSC37B787_WDT
1261 tristate "Winbond SMsC37B787 Watchdog Timer"
1264 This is the driver for the hardware watchdog component on the
1265 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
1266 from Vision Systems and maybe others.
1268 This watchdog simply watches your kernel to make sure it doesn't
1269 freeze, and if it does, it reboots your computer after a certain
1272 Usually a userspace daemon will notify the kernel WDT driver that
1273 userspace is still alive, at regular intervals.
1275 To compile this driver as a module, choose M here: the
1276 module will be called smsc37b787_wdt.
1278 Most people will say N.
1281 tristate "VIA Watchdog Timer"
1282 depends on X86 && PCI
1283 select WATCHDOG_CORE
1285 This is the driver for the hardware watchdog timer on VIA
1286 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
1288 To compile this driver as a module, choose M here; the module
1289 will be called via_wdt.
1291 Most people will say N.
1294 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
1296 select WATCHDOG_CORE
1298 This is the driver for the hardware watchdog on the following
1300 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
1313 This watchdog simply watches your kernel to make sure it doesn't
1314 freeze, and if it does, it reboots your computer after a certain
1317 To compile this driver as a module, choose M here: the
1318 module will be called w83627hf_wdt.
1320 Most people will say N.
1323 tristate "W83877F (EMACS) Watchdog Timer"
1326 This is the driver for the hardware watchdog on the W83877F chipset
1327 as used in EMACS PC-104 motherboards (and likely others). This
1328 watchdog simply watches your kernel to make sure it doesn't freeze,
1329 and if it does, it reboots your computer after a certain amount of
1332 To compile this driver as a module, choose M here: the
1333 module will be called w83877f_wdt.
1335 Most people will say N.
1338 tristate "W83977F (PCM-5335) Watchdog Timer"
1341 This is the driver for the hardware watchdog on the W83977F I/O chip
1342 as used in AAEON's PCM-5335 SBC (and likely others). This
1343 watchdog simply watches your kernel to make sure it doesn't freeze,
1344 and if it does, it reboots your computer after a certain amount of
1347 To compile this driver as a module, choose M here: the
1348 module will be called w83977f_wdt.
1351 tristate "ZF MachZ Watchdog"
1354 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1355 N. This is the driver for the watchdog timer built-in on that
1356 processor using ZF-Logic interface. This watchdog simply watches
1357 your kernel to make sure it doesn't freeze, and if it does, it
1358 reboots your computer after a certain amount of time.
1360 To compile this driver as a module, choose M here: the
1361 module will be called machzwd.
1363 config SBC_EPX_C3_WATCHDOG
1364 tristate "Winsystems SBC EPX-C3 watchdog"
1367 This is the driver for the built-in watchdog timer on the EPX-C3
1368 Single-board computer made by Winsystems, Inc.
1370 *Note*: This hardware watchdog is not probeable and thus there
1371 is no way to know if writing to its IO address will corrupt
1372 your system or have any real effect. The only way to be sure
1373 that this driver does what you want is to make sure you
1374 are running it on an EPX-C3 from Winsystems with the watchdog
1375 timer at IO address 0x1ee and 0x1ef. It will write to both those
1376 IO ports. Basically, the assumption is made that if you compile
1377 this driver into your kernel and/or load it as a module, that you
1378 know what you are doing and that you are in fact running on an
1381 To compile this driver as a module, choose M here: the
1382 module will be called sbc_epx_c3.
1384 config INTEL_MEI_WDT
1385 tristate "Intel MEI iAMT Watchdog"
1386 depends on INTEL_MEI && X86
1387 select WATCHDOG_CORE
1389 A device driver for the Intel MEI iAMT watchdog.
1391 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
1392 Whenever the OS hangs or crashes, iAMT will send an event
1393 to any subscriber to this event. The watchdog doesn't reset the
1396 To compile this driver as a module, choose M here:
1397 the module will be called mei_wdt.
1400 tristate "NI 903x/913x Watchdog"
1401 depends on X86 && ACPI
1402 select WATCHDOG_CORE
1404 This is the driver for the watchdog timer on the National Instruments
1405 903x/913x real-time controllers.
1407 To compile this driver as a module, choose M here: the module will be
1411 tristate "NIC7018 Watchdog"
1412 depends on X86 && ACPI
1413 select WATCHDOG_CORE
1415 Support for National Instruments NIC7018 Watchdog.
1417 To compile this driver as a module, choose M here: the module will be
1424 config M54xx_WATCHDOG
1425 tristate "MCF54xx watchdog support"
1428 To compile this driver as a module, choose M here: the
1429 module will be called m54xx_wdt.
1431 # MicroBlaze Architecture
1436 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1437 depends on ATH79 || (ARM && COMPILE_TEST)
1439 Hardware driver for the built-in watchdog timer on the Atheros
1440 AR71XX/AR724X/AR913X SoCs.
1443 tristate "Broadcom BCM47xx Watchdog Timer"
1444 depends on BCM47XX || ARCH_BCM_5301X || COMPILE_TEST
1445 select WATCHDOG_CORE
1447 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1450 tristate "IDT RC32434 SoC Watchdog Timer"
1451 depends on MIKROTIK_RB532
1453 Hardware driver for the IDT RC32434 SoC built-in
1456 To compile this driver as a module, choose M here: the
1457 module will be called rc32434_wdt.
1460 tristate "Indy/I2 Hardware Watchdog"
1461 depends on SGI_HAS_INDYDOG || (MIPS && COMPILE_TEST)
1463 Hardware driver for the Indy's/I2's watchdog. This is a
1464 watchdog timer that will reboot the machine after a 60 second
1465 timer expired and no process has written to /dev/watchdog during
1469 tristate "Ingenic jz4740 SoC hardware watchdog"
1470 depends on MACH_JZ4740 || MACH_JZ4780
1471 select WATCHDOG_CORE
1473 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1476 tristate "MTX-1 Hardware Watchdog"
1477 depends on MIPS_MTX1 || (MIPS && COMPILE_TEST)
1479 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1480 will reboot the machine after a 100 seconds timer expired.
1483 tristate "PNX833x Hardware Watchdog"
1484 depends on SOC_PNX8335
1487 Hardware driver for the PNX833x's watchdog. This is a
1488 watchdog timer that will reboot the machine after a programmable
1489 timer has expired and no process has written to /dev/watchdog during
1493 tristate "Sibyte SoC hardware watchdog"
1494 depends on CPU_SB1 || (MIPS && COMPILE_TEST)
1496 Watchdog driver for the built in watchdog hardware in Sibyte
1497 SoC processors. There are apparently two watchdog timers
1498 on such processors; this driver supports only the first one,
1499 because currently Linux only supports exporting one watchdog
1502 To compile this driver as a loadable module, choose M here.
1503 The module will be called sb_wdog.
1506 tristate "TI AR7 Watchdog Timer"
1507 depends on AR7 || (MIPS && COMPILE_TEST)
1509 Hardware driver for the TI AR7 Watchdog Timer.
1512 tristate "Toshiba TXx9 Watchdog Timer"
1513 depends on CPU_TX39XX || CPU_TX49XX || (MIPS && COMPILE_TEST)
1514 select WATCHDOG_CORE
1516 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1519 tristate "Cavium OCTEON SOC family Watchdog Timer"
1520 depends on CAVIUM_OCTEON_SOC
1522 select WATCHDOG_CORE
1523 select EXPORT_UASM if OCTEON_WDT = m
1525 Hardware driver for OCTEON's on chip watchdog timer.
1526 Enables the watchdog for all cores running Linux. It
1527 installs a NMI handler and pokes the watchdog based on an
1528 interrupt. On first expiration of the watchdog, the
1529 interrupt handler pokes it. The second expiration causes an
1530 NMI that prints a message. The third expiration causes a
1533 When userspace has /dev/watchdog open, no poking is done
1534 from the first interrupt, it is then only poked when the
1538 tristate "Broadcom BCM63xx hardware watchdog"
1541 Watchdog driver for the built in watchdog hardware in Broadcom
1544 To compile this driver as a loadable module, choose M here.
1545 The module will be called bcm63xx_wdt.
1548 tristate "Broadcom BCM2835 hardware watchdog"
1549 depends on ARCH_BCM2835 || (OF && COMPILE_TEST)
1550 select WATCHDOG_CORE
1552 Watchdog driver for the built in watchdog hardware in Broadcom
1555 To compile this driver as a loadable module, choose M here.
1556 The module will be called bcm2835_wdt.
1559 tristate "BCM Kona Watchdog"
1560 depends on ARCH_BCM_MOBILE || COMPILE_TEST
1561 select WATCHDOG_CORE
1563 Support for the watchdog timer on the following Broadcom BCM281xx
1564 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1567 Say 'Y' or 'M' here to enable the driver. The module will be called
1570 config BCM_KONA_WDT_DEBUG
1571 bool "DEBUGFS support for BCM Kona Watchdog"
1572 depends on BCM_KONA_WDT || COMPILE_TEST
1574 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1575 access to the driver's internal data structures as well as watchdog
1576 timer hardware registres.
1578 If in doubt, say 'N'.
1581 tristate "BCM7038 Watchdog"
1582 select WATCHDOG_CORE
1583 depends on HAS_IOMEM
1584 depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
1586 Watchdog driver for the built-in hardware in Broadcom 7038 and
1587 later SoCs used in set-top boxes. BCM7038 was made public
1588 during the 2004 CES, and since then, many Broadcom chips use this
1589 watchdog block, including some cable modem chips.
1592 tristate "Imagination Technologies PDC Watchdog Timer"
1593 depends on HAS_IOMEM
1594 depends on METAG || MIPS || COMPILE_TEST
1595 select WATCHDOG_CORE
1597 Driver for Imagination Technologies PowerDown Controller
1600 To compile this driver as a loadable module, choose M here.
1601 The module will be called imgpdc_wdt.
1604 tristate "Lantiq SoC watchdog"
1607 Hardware driver for the Lantiq SoC Watchdog Timer.
1609 config LOONGSON1_WDT
1610 tristate "Loongson1 SoC hardware watchdog"
1611 depends on MACH_LOONGSON32
1612 select WATCHDOG_CORE
1614 Hardware driver for the Loongson1 SoC Watchdog Timer.
1617 tristate "Ralink SoC watchdog"
1618 select WATCHDOG_CORE
1621 Hardware driver for the Ralink SoC Watchdog Timer.
1624 tristate "Mediatek SoC watchdog"
1625 select WATCHDOG_CORE
1626 depends on SOC_MT7620 || SOC_MT7621
1628 Hardware driver for the Mediatek/Ralink MT7621/8 SoC Watchdog Timer.
1631 tristate "Microchip PIC32 hardware watchdog"
1632 select WATCHDOG_CORE
1633 depends on MACH_PIC32 || (MIPS && COMPILE_TEST)
1635 Watchdog driver for the built in watchdog hardware in a PIC32.
1637 Configuration bits must be set appropriately for the watchdog to be
1638 controlled by this driver.
1640 To compile this driver as a loadable module, choose M here.
1641 The module will be called pic32-wdt.
1644 tristate "Microchip PIC32 Deadman Timer"
1645 select WATCHDOG_CORE
1646 depends on MACH_PIC32 || (MIPS && COMPILE_TEST)
1648 Watchdog driver for PIC32 instruction fetch counting timer. This specific
1649 timer is typically be used in misson critical and safety critical
1650 applications, where any single failure of the software functionality
1651 and sequencing must be detected.
1653 To compile this driver as a loadable module, choose M here.
1654 The module will be called pic32-dmt.
1656 # PARISC Architecture
1658 # POWERPC Architecture
1661 tristate "GE Watchdog Timer"
1664 Watchdog timer found in a number of GE single board computers.
1667 bool "MPC52xx Watchdog Timer"
1668 depends on PPC_MPC52xx || COMPILE_TEST
1670 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1673 tristate "MPC8xxx Platform Watchdog Timer"
1674 depends on PPC_8xx || PPC_83xx || PPC_86xx || PPC_MPC512x
1675 select WATCHDOG_CORE
1677 This driver is for a SoC level watchdog that exists on some
1678 Freescale PowerPC processors. So far this driver supports:
1683 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1686 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1687 depends on MV64X60 || COMPILE_TEST
1690 tristate "PIKA FPGA Watchdog"
1691 depends on WARP || (PPC64 && COMPILE_TEST)
1694 This enables the watchdog in the PIKA FPGA. Currently used on
1698 tristate "PowerPC Book-E Watchdog Timer"
1699 depends on BOOKE || 4xx
1700 select WATCHDOG_CORE
1702 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1703 MPC85xx SOCs and the IBM PowerPC 440.
1705 Please see Documentation/watchdog/watchdog-api.txt for
1708 config BOOKE_WDT_DEFAULT_TIMEOUT
1709 int "PowerPC Book-E Watchdog Timer Default Timeout"
1710 depends on BOOKE_WDT
1711 default 38 if PPC_FSL_BOOK3E
1712 range 0 63 if PPC_FSL_BOOK3E
1713 default 3 if !PPC_FSL_BOOK3E
1714 range 0 3 if !PPC_FSL_BOOK3E
1716 Select the default watchdog timer period to be used by the PowerPC
1717 Book-E watchdog driver. A watchdog "event" occurs when the bit
1718 position represented by this number transitions from zero to one.
1720 For Freescale Book-E processors, this is a number between 0 and 63.
1721 For other Book-E processors, this is a number between 0 and 3.
1723 The value can be overridden by the wdt_period command-line parameter.
1726 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1727 select WATCHDOG_CORE
1728 depends on GPIOLIB || COMPILE_TEST
1730 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1732 The driver can also be built as a module. If so, the module will be
1735 If unsure select N here.
1737 # PPC64 Architecture
1739 config WATCHDOG_RTAS
1740 tristate "RTAS watchdog"
1743 This driver adds watchdog support for the RTAS watchdog.
1745 To compile this driver as a module, choose M here. The module
1746 will be called wdrtas.
1750 config DIAG288_WATCHDOG
1751 tristate "System z diag288 Watchdog"
1753 select WATCHDOG_CORE
1755 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1756 provide a virtual watchdog timer to their guest that cause a
1757 user define Control Program command to be executed after a
1759 LPAR provides a very similar interface. This driver handles
1762 To compile this driver as a module, choose M here. The module
1763 will be called diag288_wdt.
1765 # SUPERH (sh + sh64) Architecture
1768 tristate "SuperH Watchdog"
1769 depends on SUPERH && (CPU_SH3 || CPU_SH4 || COMPILE_TEST)
1770 select WATCHDOG_CORE
1772 This driver adds watchdog support for the integrated watchdog in the
1773 SuperH processors. If you have one of these processors and wish
1774 to have watchdog support enabled, say Y, otherwise say N.
1776 As a side note, saying Y here will automatically boost HZ to 1000
1777 so that the timer has a chance to clear the overflow counter. On
1778 slower systems (such as the SH-2 and SH-3) this will likely yield
1779 some performance issues. As such, the WDT should be avoided here
1780 unless it is absolutely necessary.
1782 To compile this driver as a module, choose M here: the
1783 module will be called shwdt.
1785 # SPARC Architecture
1787 # SPARC64 Architecture
1789 config WATCHDOG_CP1XXX
1790 tristate "CP1XXX Hardware Watchdog support"
1791 depends on SPARC64 && PCI
1793 This is the driver for the hardware watchdog timers present on
1794 Sun Microsystems CompactPCI models CP1400 and CP1500.
1796 To compile this driver as a module, choose M here: the
1797 module will be called cpwatchdog.
1799 If you do not have a CompactPCI model CP1400 or CP1500, or
1800 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1801 you should say N to this option.
1804 tristate "RIO Hardware Watchdog support"
1805 depends on SPARC64 && PCI
1807 Say Y here to support the hardware watchdog capability on Sun RIO
1808 machines. The watchdog timeout period is normally one minute but
1809 can be changed with a boot-time parameter.
1811 config WATCHDOG_SUN4V
1812 tristate "Sun4v Watchdog support"
1813 select WATCHDOG_CORE
1816 Say Y here to support the hypervisor watchdog capability embedded
1817 in the SPARC sun4v architecture.
1819 To compile this driver as a module, choose M here. The module will
1820 be called sun4v_wdt.
1822 # XTENSA Architecture
1827 tristate "Xen Watchdog support"
1830 Say Y here to support the hypervisor watchdog capability provided
1831 by Xen 4.0 and newer. The watchdog timeout period is normally one
1832 minute but can be changed with a boot-time parameter.
1835 tristate "UML watchdog"
1836 depends on UML || COMPILE_TEST
1839 # ISA-based Watchdog Cards
1842 comment "ISA-based Watchdog Cards"
1846 tristate "Berkshire Products ISA-PC Watchdog"
1849 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1850 This card simply watches your kernel to make sure it doesn't freeze,
1851 and if it does, it reboots your computer after a certain amount of
1852 time. This driver is like the WDT501 driver but for different
1853 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1854 watchdog cards can be ordered from <http://www.berkprod.com/>.
1856 To compile this driver as a module, choose M here: the
1857 module will be called pcwd.
1859 Most people will say N.
1862 tristate "Mixcom Watchdog"
1865 This is a driver for the Mixcom hardware watchdog cards. This
1866 watchdog simply watches your kernel to make sure it doesn't freeze,
1867 and if it does, it reboots your computer after a certain amount of
1870 To compile this driver as a module, choose M here: the
1871 module will be called mixcomwd.
1873 Most people will say N.
1876 tristate "WDT Watchdog timer"
1879 If you have a WDT500P or WDT501P watchdog board, say Y here,
1880 otherwise N. It is not possible to probe for this board, which means
1881 that you have to inform the kernel about the IO port and IRQ that
1882 is needed (you can do this via the io and irq parameters)
1884 To compile this driver as a module, choose M here: the
1885 module will be called wdt.
1888 # PCI-based Watchdog Cards
1891 comment "PCI-based Watchdog Cards"
1894 config PCIPCWATCHDOG
1895 tristate "Berkshire Products PCI-PC Watchdog"
1898 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1899 This card simply watches your kernel to make sure it doesn't freeze,
1900 and if it does, it reboots your computer after a certain amount of
1901 time. The card can also monitor the internal temperature of the PC.
1902 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1904 To compile this driver as a module, choose M here: the
1905 module will be called pcwd_pci.
1907 Most people will say N.
1910 tristate "PCI-WDT500/501 Watchdog timer"
1913 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1915 If you have a PCI-WDT501 watchdog board then you can enable the
1916 temperature sensor by setting the type parameter to 501.
1918 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1919 can do this via the tachometer parameter. Only do this if you have a
1920 fan tachometer actually set up.
1922 To compile this driver as a module, choose M here: the
1923 module will be called wdt_pci.
1926 # USB-based Watchdog Cards
1929 comment "USB-based Watchdog Cards"
1932 config USBPCWATCHDOG
1933 tristate "Berkshire Products USB-PC Watchdog"
1936 This is the driver for the Berkshire Products USB-PC Watchdog card.
1937 This card simply watches your kernel to make sure it doesn't freeze,
1938 and if it does, it reboots your computer after a certain amount of
1939 time. The card can also monitor the internal temperature of the PC.
1940 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1942 To compile this driver as a module, choose M here: the
1943 module will be called pcwd_usb.
1945 Most people will say N.
1947 comment "Watchdog Pretimeout Governors"
1949 config WATCHDOG_PRETIMEOUT_GOV
1950 bool "Enable watchdog pretimeout governors"
1952 The option allows to select watchdog pretimeout governors.
1954 if WATCHDOG_PRETIMEOUT_GOV
1957 prompt "Default Watchdog Pretimeout Governor"
1958 default WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC
1960 This option selects a default watchdog pretimeout governor.
1961 The governor takes its action, if a watchdog is capable
1962 to report a pretimeout event.
1964 config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP
1966 select WATCHDOG_PRETIMEOUT_GOV_NOOP
1968 Use noop watchdog pretimeout governor by default. If noop
1969 governor is selected by a user, write a short message to
1970 the kernel log buffer and don't do any system changes.
1972 config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC
1974 select WATCHDOG_PRETIMEOUT_GOV_PANIC
1976 Use panic watchdog pretimeout governor by default, if
1977 a watchdog pretimeout event happens, consider that
1978 a watchdog feeder is dead and reboot is unavoidable.
1982 config WATCHDOG_PRETIMEOUT_GOV_NOOP
1983 tristate "Noop watchdog pretimeout governor"
1985 Noop watchdog pretimeout governor, only an informational
1986 message is added to kernel log buffer.
1988 config WATCHDOG_PRETIMEOUT_GOV_PANIC
1989 tristate "Panic watchdog pretimeout governor"
1991 Panic watchdog pretimeout governor, on watchdog pretimeout
1992 event put the kernel into panic.
1994 endif # WATCHDOG_PRETIMEOUT_GOV