2 # Watchdog device configuration
6 bool "Watchdog Timer Support"
8 If you say Y here (and to one of the following options) and create a
9 character special file /dev/watchdog with major number 10 and minor
10 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
11 subsequently opening the file and then failing to write to it for
12 longer than 1 minute will result in rebooting the machine. This
13 could be useful for a networked machine that needs to come back
14 on-line as fast as possible after a lock-up. There's both a watchdog
15 implementation entirely in software (which can sometimes fail to
16 reboot the machine) and a driver for hardware watchdog boards, which
17 are more robust and can also keep track of the temperature inside
18 your computer. For details, read
19 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
21 The watchdog is usually used together with the watchdog daemon
22 which is available from
23 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
24 also monitor NFS connections and can reboot the machine when the process
32 bool "WatchDog Timer Driver Core"
34 Say Y here if you want to use the new watchdog timer driver core.
35 This driver provides a framework for all watchdog timer drivers
36 and gives them the /dev/watchdog interface (and later also the
39 config WATCHDOG_NOWAYOUT
40 bool "Disable watchdog shutdown on close"
42 The default watchdog behaviour (which you get if you say N here) is
43 to stop the timer if the process managing it closes the file
44 /dev/watchdog. It's always remotely possible that this process might
45 get killed. If you say Y here, the watchdog cannot be stopped once
49 # General Watchdog drivers
52 comment "Watchdog Device Drivers"
54 # Architecture Independent
57 tristate "Software watchdog"
60 A software monitoring watchdog. This will fail to reboot your system
61 from some situations that the hardware watchdog will recover
62 from. Equally it's a lot cheaper to install.
64 To compile this driver as a module, choose M here: the
65 module will be called softdog.
67 config DA9052_WATCHDOG
68 tristate "Dialog DA9052 Watchdog"
69 depends on PMIC_DA9052
72 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
75 Say Y here to include support for the DA9052 watchdog.
76 Alternatively say M to compile the driver as a module,
77 which will be called da9052_wdt.
79 config DA9055_WATCHDOG
80 tristate "Dialog Semiconductor DA9055 Watchdog"
84 If you say yes here you get support for watchdog on the Dialog
85 Semiconductor DA9055 PMIC.
87 This driver can also be built as a module. If so, the module
88 will be called da9055_wdt.
91 tristate "Watchdog device controlled through GPIO-line"
95 If you say yes here you get support for watchdog device
96 controlled through GPIO-line.
98 config MENF21BMC_WATCHDOG
99 tristate "MEN 14F021P00 BMC Watchdog"
100 depends on MFD_MENF21BMC
103 Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
105 This driver can also be built as a module. If so the module
106 will be called menf21bmc_wdt.
108 config WM831X_WATCHDOG
109 tristate "WM831x watchdog"
110 depends on MFD_WM831X
113 Support for the watchdog in the WM831x AudioPlus PMICs. When
114 the watchdog triggers the system will be reset.
116 config WM8350_WATCHDOG
117 tristate "WM8350 watchdog"
118 depends on MFD_WM8350
121 Support for the watchdog in the WM8350 AudioPlus PMIC. When
122 the watchdog triggers the system will be reset.
124 config XILINX_WATCHDOG
125 tristate "Xilinx Watchdog timer"
128 Watchdog driver for the xps_timebase_wdt ip core.
130 To compile this driver as a module, choose M here: the
131 module will be called of_xilinx_wdt.
137 config ARM_SP805_WATCHDOG
138 tristate "ARM SP805 Watchdog"
139 depends on (ARM || ARM64) && ARM_AMBA
142 ARM Primecell SP805 Watchdog timer. This will reboot your system when
143 the timeout is reached.
145 config AT91RM9200_WATCHDOG
146 tristate "AT91RM9200 watchdog"
147 depends on ARCH_AT91RM9200
149 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
150 system when the timeout is reached.
152 config AT91SAM9X_WATCHDOG
153 tristate "AT91SAM9X / AT91CAP9 watchdog"
154 depends on ARCH_AT91 && !ARCH_AT91RM9200
157 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
158 reboot your system when the timeout is reached.
160 config CADENCE_WATCHDOG
161 tristate "Cadence Watchdog Timer"
165 Say Y here if you want to include support for the watchdog
166 timer in the Xilinx Zynq.
168 config 21285_WATCHDOG
169 tristate "DC21285 watchdog"
170 depends on FOOTBRIDGE
172 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
173 here if you wish to use this. Alternatively say M to compile the
174 driver as a module, which will be called wdt285.
176 This driver does not work on all machines. In particular, early CATS
177 boards have hardware problems that will cause the machine to simply
178 lock up if the watchdog fires.
180 "If in doubt, leave it out" - say N.
183 tristate "NetWinder WB83C977 watchdog"
184 depends on FOOTBRIDGE && ARCH_NETWINDER
186 Say Y here to include support for the WB977 watchdog included in
187 NetWinder machines. Alternatively say M to compile the driver as
188 a module, which will be called wdt977.
190 Not sure? It's safe to say N.
192 config IXP4XX_WATCHDOG
193 tristate "IXP4xx Watchdog"
194 depends on ARCH_IXP4XX
196 Say Y here if to include support for the watchdog timer
197 in the Intel IXP4xx network processors. This driver can
198 be built as a module by choosing M. The module will
199 be called ixp4xx_wdt.
201 Note: The internal IXP4xx watchdog does a soft CPU reset
202 which doesn't reset any peripherals. There are circumstances
203 where the watchdog will fail to reset the board correctly
204 (e.g., if the boot ROM is in an unreadable state).
206 Say N if you are unsure.
208 config KS8695_WATCHDOG
209 tristate "KS8695 watchdog"
210 depends on ARCH_KS8695
212 Watchdog timer embedded into KS8695 processor. This will reboot your
213 system when the timeout is reached.
215 config HAVE_S3C2410_WATCHDOG
218 This will include watchdog timer support for Samsung SoCs. If
219 you want to include watchdog support for any machine, kindly
220 select this in the respective mach-XXXX/Kconfig file.
222 config S3C2410_WATCHDOG
223 tristate "S3C2410 Watchdog"
224 depends on HAVE_S3C2410_WATCHDOG
226 select MFD_SYSCON if ARCH_EXYNOS5
228 Watchdog timer block in the Samsung SoCs. This will reboot
229 the system when the timer expires with the watchdog enabled.
231 The driver is limited by the speed of the system's PCLK
232 signal, so with reasonably fast systems (PCLK around 50-66MHz)
233 then watchdog intervals of over approximately 20seconds are
236 The driver can be built as a module by choosing M, and will
237 be called s3c2410_wdt
239 config SA1100_WATCHDOG
240 tristate "SA1100/PXA2xx watchdog"
241 depends on ARCH_SA1100 || ARCH_PXA
243 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
244 reboot your system when timeout is reached.
246 NOTE: once enabled, this timer cannot be disabled.
248 To compile this driver as a module, choose M here: the
249 module will be called sa1100_wdt.
252 tristate "Synopsys DesignWare watchdog"
255 Say Y here if to include support for the Synopsys DesignWare
256 watchdog timer found in many chips.
257 To compile this driver as a module, choose M here: the
258 module will be called dw_wdt.
260 config EP93XX_WATCHDOG
261 tristate "EP93xx Watchdog"
262 depends on ARCH_EP93XX
265 Say Y here if to include support for the watchdog timer
266 embedded in the Cirrus Logic EP93xx family of devices.
268 To compile this driver as a module, choose M here: the
269 module will be called ep93xx_wdt.
272 tristate "OMAP Watchdog"
273 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
276 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
277 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
279 config PNX4008_WATCHDOG
280 tristate "LPC32XX Watchdog"
281 depends on ARCH_LPC32XX
284 Say Y here if to include support for the watchdog timer
285 in the LPC32XX processor.
286 This driver can be built as a module by choosing M. The module
287 will be called pnx4008_wdt.
289 Say N if you are unsure.
292 tristate "IOP Watchdog"
293 depends on ARCH_IOP13XX
294 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
296 Say Y here if to include support for the watchdog timer
297 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
298 be built as a module by choosing M. The module will
301 Note: The IOP13XX watchdog does an Internal Bus Reset which will
302 affect both cores and the peripherals of the IOP. The ATU-X
303 and/or ATUe configuration registers will remain intact, but if
304 operating as an Root Complex and/or Central Resource, the PCI-X
305 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
307 config DAVINCI_WATCHDOG
308 tristate "DaVinci watchdog"
309 depends on ARCH_DAVINCI || ARCH_KEYSTONE
312 Say Y here if to include support for the watchdog timer
313 in the DaVinci DM644x/DM646x or Keystone processors.
314 To compile this driver as a module, choose M here: the
315 module will be called davinci_wdt.
317 NOTE: once enabled, this timer cannot be disabled.
318 Say N if you are unsure.
320 config ORION_WATCHDOG
321 tristate "Orion watchdog"
322 depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
325 Say Y here if to include support for the watchdog timer
326 in the Marvell Orion5x and Kirkwood ARM SoCs.
327 To compile this driver as a module, choose M here: the
328 module will be called orion_wdt.
330 config RN5T618_WATCHDOG
331 tristate "Ricoh RN5T618 watchdog"
332 depends on MFD_RN5T618
335 If you say yes here you get support for watchdog on the Ricoh
338 This driver can also be built as a module. If so, the module
339 will be called rn5t618_wdt.
341 config SUNXI_WATCHDOG
342 tristate "Allwinner SoCs watchdog support"
343 depends on ARCH_SUNXI
346 Say Y here to include support for the watchdog timer
348 To compile this driver as a module, choose M here: the
349 module will be called sunxi_wdt.
351 config COH901327_WATCHDOG
352 bool "ST-Ericsson COH 901 327 watchdog"
354 default y if MACH_U300
357 Say Y here to include Watchdog timer support for the
358 watchdog embedded into the ST-Ericsson U300 series platforms.
359 This watchdog is used to reset the system and thus cannot be
360 compiled as a module.
362 config TWL4030_WATCHDOG
363 tristate "TWL4030 Watchdog"
364 depends on TWL4030_CORE
367 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
368 watchdog timer support for TWL4030 chips.
370 config STMP3XXX_RTC_WATCHDOG
371 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
372 depends on RTC_DRV_STMP
375 Say Y here to include support for the watchdog timer inside
376 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
377 To compile this driver as a module, choose M here: the
378 module will be called stmp3xxx_rtc_wdt.
380 config NUC900_WATCHDOG
381 tristate "Nuvoton NUC900 watchdog"
382 depends on ARCH_W90X900
384 Say Y here if to include support for the watchdog timer
385 for the Nuvoton NUC900 series SoCs.
386 To compile this driver as a module, choose M here: the
387 module will be called nuc900_wdt.
389 config TS72XX_WATCHDOG
390 tristate "TS-72XX SBC Watchdog"
391 depends on MACH_TS72XX
393 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
394 watchdog timer implemented in a external CPLD chip. Say Y here
395 if you want to support for the watchdog timer on TS-72XX boards.
397 To compile this driver as a module, choose M here: the
398 module will be called ts72xx_wdt.
400 config MAX63XX_WATCHDOG
401 tristate "Max63xx watchdog"
402 depends on ARM && HAS_IOMEM
405 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
408 tristate "IMX2+ Watchdog"
413 This is the driver for the hardware watchdog
414 on the Freescale IMX2 and later processors.
415 If you have one of these processors and wish to have
416 watchdog support enabled, say Y, otherwise say N.
418 To compile this driver as a module, choose M here: the
419 module will be called imx2_wdt.
421 config UX500_WATCHDOG
422 tristate "ST-Ericsson Ux500 watchdog"
423 depends on MFD_DB8500_PRCMU
427 Say Y here to include Watchdog timer support for the watchdog
428 existing in the prcmu of ST-Ericsson Ux500 series platforms.
430 To compile this driver as a module, choose M here: the
431 module will be called ux500_wdt.
434 tristate "Retu watchdog"
438 Retu watchdog driver for Nokia Internet Tablets (770, N800,
439 N810). At least on N800 the watchdog cannot be disabled, so
440 this driver is essential and you should enable it.
442 To compile this driver as a module, choose M here: the
443 module will be called retu_wdt.
446 tristate "MOXART watchdog"
447 depends on ARCH_MOXART
449 Say Y here to include Watchdog timer support for the watchdog
450 existing on the MOXA ART SoC series platforms.
452 To compile this driver as a module, choose M here: the
453 module will be called moxart_wdt.
455 config SIRFSOC_WATCHDOG
456 tristate "SiRFSOC watchdog"
461 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
462 the watchdog triggers the system will be reset.
464 config TEGRA_WATCHDOG
465 tristate "Tegra watchdog"
466 depends on ARCH_TEGRA || COMPILE_TEST
469 Say Y here to include support for the watchdog timer
470 embedded in NVIDIA Tegra SoCs.
472 To compile this driver as a module, choose M here: the
473 module will be called tegra_wdt.
476 tristate "QCOM watchdog"
481 Say Y here to include Watchdog timer support for the watchdog found
482 on QCOM chipsets. Currently supported targets are the MSM8960,
483 APQ8064, and IPQ8064.
485 To compile this driver as a module, choose M here: the
486 module will be called qcom_wdt.
490 config AT32AP700X_WDT
491 tristate "AT32AP700x watchdog"
492 depends on CPU_AT32AP700X
494 Watchdog timer embedded into AT32AP700x devices. This will reboot
495 your system when the timeout is reached.
497 # BLACKFIN Architecture
500 tristate "Blackfin On-Chip Watchdog Timer"
503 If you say yes here you will get support for the Blackfin On-Chip
504 Watchdog Timer. If you have one of these processors and wish to
505 have watchdog support enabled, say Y, otherwise say N.
507 To compile this driver as a module, choose M here: the
508 module will be called bfin_wdt.
514 # X86 (i386 + ia64 + x86_64) Architecture
517 tristate "Acquire SBC Watchdog Timer"
520 This is the driver for the hardware watchdog on Single Board
521 Computers produced by Acquire Inc (and others). This watchdog
522 simply watches your kernel to make sure it doesn't freeze, and if
523 it does, it reboots your computer after a certain amount of time.
525 To compile this driver as a module, choose M here: the
526 module will be called acquirewdt.
528 Most people will say N.
531 tristate "Advantech SBC Watchdog Timer"
534 If you are configuring a Linux kernel for the Advantech single-board
535 computer, say `Y' here to support its built-in watchdog timer
536 feature. More information can be found at
537 <http://www.advantech.com.tw/products/>
540 tristate "ALi M1535 PMU Watchdog Timer"
541 depends on X86 && PCI
543 This is the driver for the hardware watchdog on the ALi M1535 PMU.
545 To compile this driver as a module, choose M here: the
546 module will be called alim1535_wdt.
548 Most people will say N.
551 tristate "ALi M7101 PMU Computer Watchdog"
554 This is the driver for the hardware watchdog on the ALi M7101 PMU
555 as used in the x86 Cobalt servers and also found in some
556 SPARC Netra servers too.
558 To compile this driver as a module, choose M here: the
559 module will be called alim7101_wdt.
561 Most people will say N.
564 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
567 This is the driver for the hardware watchdog on the Fintek
568 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
570 You can compile this driver directly into the kernel, or use
571 it as a module. The module will be called f71808e_wdt.
574 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
575 depends on X86 && PCI
577 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
578 (Total Cost of Ownership) timer is a watchdog timer that will reboot
579 the machine after its expiration. The expiration time can be
580 configured with the "heartbeat" parameter.
582 To compile this driver as a module, choose M here: the
583 module will be called sp5100_tco.
586 tristate "AMD Geode CS5535/CS5536 Watchdog"
587 depends on CS5535_MFGPT
589 This driver enables a watchdog capability built into the
590 CS5535/CS5536 companion chips for the AMD Geode GX and LX
591 processors. This watchdog watches your kernel to make sure
592 it doesn't freeze, and if it does, it reboots your computer after
593 a certain amount of time.
595 You can compile this driver directly into the kernel, or use
596 it as a module. The module will be called geodewdt.
599 tristate "AMD Elan SC520 processor Watchdog"
602 This is the driver for the hardware watchdog built in to the
603 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
604 This watchdog simply watches your kernel to make sure it doesn't
605 freeze, and if it does, it reboots your computer after a certain
608 You can compile this driver directly into the kernel, or use
609 it as a module. The module will be called sc520_wdt.
611 config SBC_FITPC2_WATCHDOG
612 tristate "Compulab SBC-FITPC2 watchdog"
615 This is the driver for the built-in watchdog timer on the fit-PC2,
616 fit-PC2i, CM-iAM single-board computers made by Compulab.
618 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
619 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
621 Entering BIOS setup temporary disables watchdog operation regardless to current state,
622 so system will not be restarted while user in BIOS setup.
624 Once watchdog was enabled the system will be restarted every
625 "Watchdog Timer Value" period, so to prevent it user can restart or
626 disable the watchdog.
628 To compile this driver as a module, choose M here: the
629 module will be called sbc_fitpc2_wdt.
631 Most people will say N.
634 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
637 Enable support for the watchdog timer on the Eurotech CPU-1220 and
638 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
639 information are at <http://www.eurotech.it/>.
642 tristate "IB700 SBC Watchdog Timer"
645 This is the driver for the hardware watchdog on the IB700 Single
646 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
647 simply watches your kernel to make sure it doesn't freeze, and if
648 it does, it reboots your computer after a certain amount of time.
650 This driver is like the WDT501 driver but for slightly different hardware.
652 To compile this driver as a module, choose M here: the
653 module will be called ib700wdt.
655 Most people will say N.
658 tristate "IBM Automatic Server Restart"
661 This is the driver for the IBM Automatic Server Restart watchdog
662 timer built-in into some eServer xSeries machines.
664 To compile this driver as a module, choose M here: the
665 module will be called ibmasr.
668 tristate "ICP Single Board Computer Watchdog Timer"
671 This is a driver for the hardware watchdog on the ICP Single
672 Board Computer. This driver is working on (at least) the following
673 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
675 To compile this driver as a module, choose M here: the
676 module will be called wafer5823wdt.
679 tristate "Intel 6300ESB Timer/Watchdog"
682 Hardware driver for the watchdog timer built into the Intel
683 6300ESB controller hub.
685 To compile this driver as a module, choose M here: the
686 module will be called i6300esb.
689 tristate "Intel Atom E6xx Watchdog"
690 depends on X86 && PCI
695 Hardware driver for the watchdog timer built into the Intel
696 Atom E6XX (TunnelCreek) processor.
698 To compile this driver as a module, choose M here: the
699 module will be called ie6xx_wdt.
701 config INTEL_SCU_WATCHDOG
702 bool "Intel SCU Watchdog for Mobile Platforms"
703 depends on X86_INTEL_MID
705 Hardware driver for the watchdog time built into the Intel SCU
706 for Intel Mobile Platforms.
708 To compile this driver as a module, choose M here.
710 config INTEL_MID_WATCHDOG
711 tristate "Intel MID Watchdog Timer"
712 depends on X86_INTEL_MID
715 Watchdog timer driver built into the Intel SCU for Intel MID
718 This driver currently supports only the watchdog evolution
719 implementation in SCU, available for Merrifield generation.
721 To compile this driver as a module, choose M here.
724 tristate "Intel TCO Timer/Watchdog"
725 depends on (X86 || IA64) && PCI
729 Hardware driver for the intel TCO timer based watchdog devices.
730 These drivers are included in the Intel 82801 I/O Controller
731 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
734 The TCO (Total Cost of Ownership) timer is a watchdog timer
735 that will reboot the machine after its second expiration. The
736 expiration time can be configured with the "heartbeat" parameter.
738 On some motherboards the driver may fail to reset the chipset's
739 NO_REBOOT flag which prevents the watchdog from rebooting the
740 machine. If this is the case you will get a kernel message like
741 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
743 To compile this driver as a module, choose M here: the
744 module will be called iTCO_wdt.
746 config ITCO_VENDOR_SUPPORT
747 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
750 Add vendor specific support to the intel TCO timer based watchdog
751 devices. At this moment we only have additional support for some
752 SuperMicro Inc. motherboards.
755 tristate "IT8712F (Smart Guardian) Watchdog Timer"
758 This is the driver for the built-in watchdog timer on the IT8712F
759 Super I/0 chipset used on many motherboards.
761 If the driver does not work, then make sure that the game port in
764 To compile this driver as a module, choose M here: the
765 module will be called it8712f_wdt.
768 tristate "IT87 Watchdog Timer"
771 This is the driver for the hardware watchdog on the ITE IT8702,
772 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
775 If the driver does not work, then make sure that the game port in
778 This watchdog simply watches your kernel to make sure it doesn't
779 freeze, and if it does, it reboots your computer after a certain
782 To compile this driver as a module, choose M here: the module will
786 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
787 depends on X86 && PCI
789 A software monitoring watchdog and NMI sourcing driver. This driver
790 will detect lockups and provide a stack trace. This is a driver that
791 will only load on an HP ProLiant system with a minimum of iLO2 support.
792 To compile this driver as a module, choose M here: the module will be
796 tristate "Kontron COM Watchdog Timer"
797 depends on MFD_KEMPLD
800 Support for the PLD watchdog on some Kontron ETX and COMexpress
803 This driver can also be built as a module. If so, the module will be
806 config HPWDT_NMI_DECODING
807 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
808 depends on HP_WATCHDOG
811 When an NMI occurs this feature will make the necessary BIOS calls to
812 log the cause of the NMI.
815 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
818 This is a driver for National Semiconductor PC87307/PC97307 hardware
819 watchdog cards as found on the SC1200. This watchdog is mainly used
820 for power management purposes and can be used to power down the device
821 during inactivity periods (includes interrupt activity monitoring).
823 To compile this driver as a module, choose M here: the
824 module will be called sc1200wdt.
826 Most people will say N.
829 tristate "National Semiconductor SCx200 Watchdog"
830 depends on SCx200 && PCI
832 Enable the built-in watchdog timer support on the National
833 Semiconductor SCx200 processors.
835 If compiled as a module, it will be called scx200_wdt.
838 tristate "NS PC87413 watchdog"
841 This is the driver for the hardware watchdog on the PC87413 chipset
842 This watchdog simply watches your kernel to make sure it doesn't
843 freeze, and if it does, it reboots your computer after a certain
846 To compile this driver as a module, choose M here: the
847 module will be called pc87413_wdt.
849 Most people will say N.
852 tristate "nVidia TCO Timer/Watchdog"
853 depends on X86 && PCI
855 Hardware driver for the TCO timer built into the nVidia Hub family
856 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
857 watchdog timer that will reboot the machine after its second
858 expiration. The expiration time can be configured with the
859 "heartbeat" parameter.
861 On some motherboards the driver may fail to reset the chipset's
862 NO_REBOOT flag which prevents the watchdog from rebooting the
863 machine. If this is the case you will get a kernel message like
864 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
866 To compile this driver as a module, choose M here: the
867 module will be called nv_tco.
870 tristate "RDC R-321x SoC watchdog"
871 depends on X86_RDC321X
873 This is the driver for the built in hardware watchdog
874 in the RDC R-321x SoC.
876 To compile this driver as a module, choose M here: the
877 module will be called rdc321x_wdt.
880 tristate "SBC-60XX Watchdog Timer"
883 This driver can be used with the watchdog timer found on some
884 single board computers, namely the 6010 PII based computer.
885 It may well work with other cards. It reads port 0x443 to enable
886 and re-set the watchdog timer, and reads port 0x45 to disable
887 the watchdog. If you have a card that behave in similar ways,
888 you can probably make this driver work with your card as well.
890 You can compile this driver directly into the kernel, or use
891 it as a module. The module will be called sbc60xxwdt.
894 tristate "SBC8360 Watchdog Timer"
898 This is the driver for the hardware watchdog on the SBC8360 Single
899 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
901 To compile this driver as a module, choose M here: the
902 module will be called sbc8360.
904 Most people will say N.
907 tristate "SBC Nano 7240 Watchdog Timer"
908 depends on X86_32 && !UML
910 This is the driver for the hardware watchdog found on the IEI
911 single board computers EPIC Nano 7240 (and likely others). This
912 watchdog simply watches your kernel to make sure it doesn't freeze,
913 and if it does, it reboots your computer after a certain amount of
916 To compile this driver as a module, choose M here: the
917 module will be called sbc7240_wdt.
920 tristate "SMA CPU5 Watchdog"
924 To compile this driver as a module, choose M here: the
925 module will be called cpu5wdt.
927 config SMSC_SCH311X_WDT
928 tristate "SMSC SCH311X Watchdog Timer"
931 This is the driver for the hardware watchdog timer on the
932 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
933 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
936 To compile this driver as a module, choose M here: the
937 module will be called sch311x_wdt.
939 config SMSC37B787_WDT
940 tristate "Winbond SMsC37B787 Watchdog Timer"
943 This is the driver for the hardware watchdog component on the
944 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
945 from Vision Systems and maybe others.
947 This watchdog simply watches your kernel to make sure it doesn't
948 freeze, and if it does, it reboots your computer after a certain
951 Usually a userspace daemon will notify the kernel WDT driver that
952 userspace is still alive, at regular intervals.
954 To compile this driver as a module, choose M here: the
955 module will be called smsc37b787_wdt.
957 Most people will say N.
960 tristate "VIA Watchdog Timer"
961 depends on X86 && PCI
964 This is the driver for the hardware watchdog timer on VIA
965 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
967 To compile this driver as a module, choose M here; the module
968 will be called via_wdt.
970 Most people will say N.
973 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
977 This is the driver for the hardware watchdog on the following
979 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
989 This watchdog simply watches your kernel to make sure it doesn't
990 freeze, and if it does, it reboots your computer after a certain
993 To compile this driver as a module, choose M here: the
994 module will be called w83627hf_wdt.
996 Most people will say N.
999 tristate "W83877F (EMACS) Watchdog Timer"
1002 This is the driver for the hardware watchdog on the W83877F chipset
1003 as used in EMACS PC-104 motherboards (and likely others). This
1004 watchdog simply watches your kernel to make sure it doesn't freeze,
1005 and if it does, it reboots your computer after a certain amount of
1008 To compile this driver as a module, choose M here: the
1009 module will be called w83877f_wdt.
1011 Most people will say N.
1014 tristate "W83977F (PCM-5335) Watchdog Timer"
1017 This is the driver for the hardware watchdog on the W83977F I/O chip
1018 as used in AAEON's PCM-5335 SBC (and likely others). This
1019 watchdog simply watches your kernel to make sure it doesn't freeze,
1020 and if it does, it reboots your computer after a certain amount of
1023 To compile this driver as a module, choose M here: the
1024 module will be called w83977f_wdt.
1027 tristate "ZF MachZ Watchdog"
1030 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1031 N. This is the driver for the watchdog timer built-in on that
1032 processor using ZF-Logic interface. This watchdog simply watches
1033 your kernel to make sure it doesn't freeze, and if it does, it
1034 reboots your computer after a certain amount of time.
1036 To compile this driver as a module, choose M here: the
1037 module will be called machzwd.
1039 config SBC_EPX_C3_WATCHDOG
1040 tristate "Winsystems SBC EPX-C3 watchdog"
1043 This is the driver for the built-in watchdog timer on the EPX-C3
1044 Single-board computer made by Winsystems, Inc.
1046 *Note*: This hardware watchdog is not probeable and thus there
1047 is no way to know if writing to its IO address will corrupt
1048 your system or have any real effect. The only way to be sure
1049 that this driver does what you want is to make sure you
1050 are running it on an EPX-C3 from Winsystems with the watchdog
1051 timer at IO address 0x1ee and 0x1ef. It will write to both those
1052 IO ports. Basically, the assumption is made that if you compile
1053 this driver into your kernel and/or load it as a module, that you
1054 know what you are doing and that you are in fact running on an
1057 To compile this driver as a module, choose M here: the
1058 module will be called sbc_epx_c3.
1064 config M54xx_WATCHDOG
1065 tristate "MCF54xx watchdog support"
1068 To compile this driver as a module, choose M here: the
1069 module will be called m54xx_wdt.
1071 # MicroBlaze Architecture
1076 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1079 Hardware driver for the built-in watchdog timer on the Atheros
1080 AR71XX/AR724X/AR913X SoCs.
1083 tristate "Broadcom BCM47xx Watchdog Timer"
1085 select WATCHDOG_CORE
1087 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1090 tristate "IDT RC32434 SoC Watchdog Timer"
1091 depends on MIKROTIK_RB532
1093 Hardware driver for the IDT RC32434 SoC built-in
1096 To compile this driver as a module, choose M here: the
1097 module will be called rc32434_wdt.
1100 tristate "Indy/I2 Hardware Watchdog"
1101 depends on SGI_HAS_INDYDOG
1103 Hardware driver for the Indy's/I2's watchdog. This is a
1104 watchdog timer that will reboot the machine after a 60 second
1105 timer expired and no process has written to /dev/watchdog during
1109 tristate "Ingenic jz4740 SoC hardware watchdog"
1110 depends on MACH_JZ4740
1111 select WATCHDOG_CORE
1113 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1116 tristate "MTX-1 Hardware Watchdog"
1117 depends on MIPS_MTX1
1119 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1120 will reboot the machine after a 100 seconds timer expired.
1123 tristate "PNX833x Hardware Watchdog"
1124 depends on SOC_PNX8335
1126 Hardware driver for the PNX833x's watchdog. This is a
1127 watchdog timer that will reboot the machine after a programmable
1128 timer has expired and no process has written to /dev/watchdog during
1132 tristate "Sibyte SoC hardware watchdog"
1135 Watchdog driver for the built in watchdog hardware in Sibyte
1136 SoC processors. There are apparently two watchdog timers
1137 on such processors; this driver supports only the first one,
1138 because currently Linux only supports exporting one watchdog
1141 To compile this driver as a loadable module, choose M here.
1142 The module will be called sb_wdog.
1145 tristate "TI AR7 Watchdog Timer"
1148 Hardware driver for the TI AR7 Watchdog Timer.
1151 tristate "Toshiba TXx9 Watchdog Timer"
1152 depends on CPU_TX39XX || CPU_TX49XX
1153 select WATCHDOG_CORE
1155 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1158 tristate "Cavium OCTEON SOC family Watchdog Timer"
1159 depends on CAVIUM_OCTEON_SOC
1161 select EXPORT_UASM if OCTEON_WDT = m
1163 Hardware driver for OCTEON's on chip watchdog timer.
1164 Enables the watchdog for all cores running Linux. It
1165 installs a NMI handler and pokes the watchdog based on an
1166 interrupt. On first expiration of the watchdog, the
1167 interrupt handler pokes it. The second expiration causes an
1168 NMI that prints a message. The third expiration causes a
1171 When userspace has /dev/watchdog open, no poking is done
1172 from the first interrupt, it is then only poked when the
1176 tristate "Broadcom BCM63xx hardware watchdog"
1179 Watchdog driver for the built in watchdog hardware in Broadcom
1182 To compile this driver as a loadable module, choose M here.
1183 The module will be called bcm63xx_wdt.
1186 tristate "Broadcom BCM2835 hardware watchdog"
1187 depends on ARCH_BCM2835
1188 select WATCHDOG_CORE
1190 Watchdog driver for the built in watchdog hardware in Broadcom
1193 To compile this driver as a loadable module, choose M here.
1194 The module will be called bcm2835_wdt.
1197 tristate "BCM Kona Watchdog"
1198 depends on ARCH_BCM_MOBILE
1199 select WATCHDOG_CORE
1201 Support for the watchdog timer on the following Broadcom BCM281xx
1202 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1205 Say 'Y' or 'M' here to enable the driver. The module will be called
1208 config BCM_KONA_WDT_DEBUG
1209 bool "DEBUGFS support for BCM Kona Watchdog"
1210 depends on BCM_KONA_WDT
1212 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1213 access to the driver's internal data structures as well as watchdog
1214 timer hardware registres.
1216 If in doubt, say 'N'.
1219 tristate "Lantiq SoC watchdog"
1222 Hardware driver for the Lantiq SoC Watchdog Timer.
1225 tristate "Ralink SoC watchdog"
1226 select WATCHDOG_CORE
1229 Hardware driver for the Ralink SoC Watchdog Timer.
1231 # PARISC Architecture
1233 # POWERPC Architecture
1236 tristate "GE Watchdog Timer"
1239 Watchdog timer found in a number of GE single board computers.
1242 bool "MPC52xx Watchdog Timer"
1243 depends on PPC_MPC52xx
1245 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1248 tristate "MPC8xxx Platform Watchdog Timer"
1249 depends on PPC_8xx || PPC_83xx || PPC_86xx
1250 select WATCHDOG_CORE
1252 This driver is for a SoC level watchdog that exists on some
1253 Freescale PowerPC processors. So far this driver supports:
1258 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1261 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1265 tristate "PIKA FPGA Watchdog"
1269 This enables the watchdog in the PIKA FPGA. Currently used on
1273 tristate "PowerPC Book-E Watchdog Timer"
1274 depends on BOOKE || 4xx
1275 select WATCHDOG_CORE
1277 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1278 MPC85xx SOCs and the IBM PowerPC 440.
1280 Please see Documentation/watchdog/watchdog-api.txt for
1283 config BOOKE_WDT_DEFAULT_TIMEOUT
1284 int "PowerPC Book-E Watchdog Timer Default Timeout"
1285 depends on BOOKE_WDT
1286 default 38 if PPC_FSL_BOOK3E
1287 range 0 63 if PPC_FSL_BOOK3E
1288 default 3 if !PPC_FSL_BOOK3E
1289 range 0 3 if !PPC_FSL_BOOK3E
1291 Select the default watchdog timer period to be used by the PowerPC
1292 Book-E watchdog driver. A watchdog "event" occurs when the bit
1293 position represented by this number transitions from zero to one.
1295 For Freescale Book-E processors, this is a number between 0 and 63.
1296 For other Book-E processors, this is a number between 0 and 3.
1298 The value can be overridden by the wdt_period command-line parameter.
1301 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1302 select WATCHDOG_CORE
1305 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1307 The driver can also be built as a module. If so, the module will be
1310 If unsure select N here.
1312 # PPC64 Architecture
1314 config WATCHDOG_RTAS
1315 tristate "RTAS watchdog"
1318 This driver adds watchdog support for the RTAS watchdog.
1320 To compile this driver as a module, choose M here. The module
1321 will be called wdrtas.
1325 config DIAG288_WATCHDOG
1326 tristate "System z diag288 Watchdog"
1328 select WATCHDOG_CORE
1330 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1331 provide a virtual watchdog timer to their guest that cause a
1332 user define Control Program command to be executed after a
1334 LPAR provides a very similar interface. This driver handles
1337 To compile this driver as a module, choose M here. The module
1338 will be called diag288_wdt.
1340 # SUPERH (sh + sh64) Architecture
1343 tristate "SuperH Watchdog"
1344 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1345 select WATCHDOG_CORE
1347 This driver adds watchdog support for the integrated watchdog in the
1348 SuperH processors. If you have one of these processors and wish
1349 to have watchdog support enabled, say Y, otherwise say N.
1351 As a side note, saying Y here will automatically boost HZ to 1000
1352 so that the timer has a chance to clear the overflow counter. On
1353 slower systems (such as the SH-2 and SH-3) this will likely yield
1354 some performance issues. As such, the WDT should be avoided here
1355 unless it is absolutely necessary.
1357 To compile this driver as a module, choose M here: the
1358 module will be called shwdt.
1360 # SPARC Architecture
1362 # SPARC64 Architecture
1364 config WATCHDOG_CP1XXX
1365 tristate "CP1XXX Hardware Watchdog support"
1366 depends on SPARC64 && PCI
1368 This is the driver for the hardware watchdog timers present on
1369 Sun Microsystems CompactPCI models CP1400 and CP1500.
1371 To compile this driver as a module, choose M here: the
1372 module will be called cpwatchdog.
1374 If you do not have a CompactPCI model CP1400 or CP1500, or
1375 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1376 you should say N to this option.
1379 tristate "RIO Hardware Watchdog support"
1380 depends on SPARC64 && PCI
1382 Say Y here to support the hardware watchdog capability on Sun RIO
1383 machines. The watchdog timeout period is normally one minute but
1384 can be changed with a boot-time parameter.
1386 # XTENSA Architecture
1391 tristate "Xen Watchdog support"
1394 Say Y here to support the hypervisor watchdog capability provided
1395 by Xen 4.0 and newer. The watchdog timeout period is normally one
1396 minute but can be changed with a boot-time parameter.
1399 tristate "UML watchdog"
1403 # ISA-based Watchdog Cards
1406 comment "ISA-based Watchdog Cards"
1410 tristate "Berkshire Products ISA-PC Watchdog"
1413 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1414 This card simply watches your kernel to make sure it doesn't freeze,
1415 and if it does, it reboots your computer after a certain amount of
1416 time. This driver is like the WDT501 driver but for different
1417 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1418 watchdog cards can be ordered from <http://www.berkprod.com/>.
1420 To compile this driver as a module, choose M here: the
1421 module will be called pcwd.
1423 Most people will say N.
1426 tristate "Mixcom Watchdog"
1429 This is a driver for the Mixcom hardware watchdog cards. This
1430 watchdog simply watches your kernel to make sure it doesn't freeze,
1431 and if it does, it reboots your computer after a certain amount of
1434 To compile this driver as a module, choose M here: the
1435 module will be called mixcomwd.
1437 Most people will say N.
1440 tristate "WDT Watchdog timer"
1443 If you have a WDT500P or WDT501P watchdog board, say Y here,
1444 otherwise N. It is not possible to probe for this board, which means
1445 that you have to inform the kernel about the IO port and IRQ that
1446 is needed (you can do this via the io and irq parameters)
1448 To compile this driver as a module, choose M here: the
1449 module will be called wdt.
1452 # PCI-based Watchdog Cards
1455 comment "PCI-based Watchdog Cards"
1458 config PCIPCWATCHDOG
1459 tristate "Berkshire Products PCI-PC Watchdog"
1462 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1463 This card simply watches your kernel to make sure it doesn't freeze,
1464 and if it does, it reboots your computer after a certain amount of
1465 time. The card can also monitor the internal temperature of the PC.
1466 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1468 To compile this driver as a module, choose M here: the
1469 module will be called pcwd_pci.
1471 Most people will say N.
1474 tristate "PCI-WDT500/501 Watchdog timer"
1477 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1479 If you have a PCI-WDT501 watchdog board then you can enable the
1480 temperature sensor by setting the type parameter to 501.
1482 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1483 can do this via the tachometer parameter. Only do this if you have a
1484 fan tachometer actually set up.
1486 To compile this driver as a module, choose M here: the
1487 module will be called wdt_pci.
1490 # USB-based Watchdog Cards
1493 comment "USB-based Watchdog Cards"
1496 config USBPCWATCHDOG
1497 tristate "Berkshire Products USB-PC Watchdog"
1500 This is the driver for the Berkshire Products USB-PC Watchdog card.
1501 This card simply watches your kernel to make sure it doesn't freeze,
1502 and if it does, it reboots your computer after a certain amount of
1503 time. The card can also monitor the internal temperature of the PC.
1504 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1506 To compile this driver as a module, choose M here: the
1507 module will be called pcwd_usb.
1509 Most people will say N.