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.
90 config DA9063_WATCHDOG
91 tristate "Dialog DA9063 Watchdog"
95 Support for the watchdog in the DA9063 PMIC.
97 This driver can be built as a module. The module name is da9063_wdt.
100 tristate "Watchdog device controlled through GPIO-line"
104 If you say yes here you get support for watchdog device
105 controlled through GPIO-line.
107 config MENF21BMC_WATCHDOG
108 tristate "MEN 14F021P00 BMC Watchdog"
109 depends on MFD_MENF21BMC
112 Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
114 This driver can also be built as a module. If so the module
115 will be called menf21bmc_wdt.
117 config WM831X_WATCHDOG
118 tristate "WM831x watchdog"
119 depends on MFD_WM831X
122 Support for the watchdog in the WM831x AudioPlus PMICs. When
123 the watchdog triggers the system will be reset.
125 config WM8350_WATCHDOG
126 tristate "WM8350 watchdog"
127 depends on MFD_WM8350
130 Support for the watchdog in the WM8350 AudioPlus PMIC. When
131 the watchdog triggers the system will be reset.
133 config XILINX_WATCHDOG
134 tristate "Xilinx Watchdog timer"
138 Watchdog driver for the xps_timebase_wdt ip core.
140 To compile this driver as a module, choose M here: the
141 module will be called of_xilinx_wdt.
147 config ARM_SP805_WATCHDOG
148 tristate "ARM SP805 Watchdog"
149 depends on (ARM || ARM64) && ARM_AMBA
152 ARM Primecell SP805 Watchdog timer. This will reboot your system when
153 the timeout is reached.
155 config AT91RM9200_WATCHDOG
156 tristate "AT91RM9200 watchdog"
157 depends on SOC_AT91RM9200 && MFD_SYSCON
159 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
160 system when the timeout is reached.
162 config AT91SAM9X_WATCHDOG
163 tristate "AT91SAM9X / AT91CAP9 watchdog"
167 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
168 reboot your system when the timeout is reached.
170 config CADENCE_WATCHDOG
171 tristate "Cadence Watchdog Timer"
174 Say Y here if you want to include support for the watchdog
175 timer in the Xilinx Zynq.
177 config 21285_WATCHDOG
178 tristate "DC21285 watchdog"
179 depends on FOOTBRIDGE
181 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
182 here if you wish to use this. Alternatively say M to compile the
183 driver as a module, which will be called wdt285.
185 This driver does not work on all machines. In particular, early CATS
186 boards have hardware problems that will cause the machine to simply
187 lock up if the watchdog fires.
189 "If in doubt, leave it out" - say N.
192 tristate "NetWinder WB83C977 watchdog"
193 depends on FOOTBRIDGE && ARCH_NETWINDER
195 Say Y here to include support for the WB977 watchdog included in
196 NetWinder machines. Alternatively say M to compile the driver as
197 a module, which will be called wdt977.
199 Not sure? It's safe to say N.
201 config IXP4XX_WATCHDOG
202 tristate "IXP4xx Watchdog"
203 depends on ARCH_IXP4XX
205 Say Y here if to include support for the watchdog timer
206 in the Intel IXP4xx network processors. This driver can
207 be built as a module by choosing M. The module will
208 be called ixp4xx_wdt.
210 Note: The internal IXP4xx watchdog does a soft CPU reset
211 which doesn't reset any peripherals. There are circumstances
212 where the watchdog will fail to reset the board correctly
213 (e.g., if the boot ROM is in an unreadable state).
215 Say N if you are unsure.
217 config KS8695_WATCHDOG
218 tristate "KS8695 watchdog"
219 depends on ARCH_KS8695
221 Watchdog timer embedded into KS8695 processor. This will reboot your
222 system when the timeout is reached.
224 config HAVE_S3C2410_WATCHDOG
227 This will include watchdog timer support for Samsung SoCs. If
228 you want to include watchdog support for any machine, kindly
229 select this in the respective mach-XXXX/Kconfig file.
231 config S3C2410_WATCHDOG
232 tristate "S3C2410 Watchdog"
233 depends on HAVE_S3C2410_WATCHDOG
235 select MFD_SYSCON if ARCH_EXYNOS5
237 Watchdog timer block in the Samsung SoCs. This will reboot
238 the system when the timer expires with the watchdog enabled.
240 The driver is limited by the speed of the system's PCLK
241 signal, so with reasonably fast systems (PCLK around 50-66MHz)
242 then watchdog intervals of over approximately 20seconds are
245 The driver can be built as a module by choosing M, and will
246 be called s3c2410_wdt
248 config SA1100_WATCHDOG
249 tristate "SA1100/PXA2xx watchdog"
250 depends on ARCH_SA1100 || ARCH_PXA
252 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
253 reboot your system when timeout is reached.
255 NOTE: once enabled, this timer cannot be disabled.
257 To compile this driver as a module, choose M here: the
258 module will be called sa1100_wdt.
261 tristate "Synopsys DesignWare watchdog"
264 Say Y here if to include support for the Synopsys DesignWare
265 watchdog timer found in many chips.
266 To compile this driver as a module, choose M here: the
267 module will be called dw_wdt.
269 config EP93XX_WATCHDOG
270 tristate "EP93xx Watchdog"
271 depends on ARCH_EP93XX
274 Say Y here if to include support for the watchdog timer
275 embedded in the Cirrus Logic EP93xx family of devices.
277 To compile this driver as a module, choose M here: the
278 module will be called ep93xx_wdt.
281 tristate "OMAP Watchdog"
282 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
285 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
286 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
288 config PNX4008_WATCHDOG
289 tristate "LPC32XX Watchdog"
290 depends on ARCH_LPC32XX
293 Say Y here if to include support for the watchdog timer
294 in the LPC32XX processor.
295 This driver can be built as a module by choosing M. The module
296 will be called pnx4008_wdt.
298 Say N if you are unsure.
301 tristate "IOP Watchdog"
302 depends on ARCH_IOP13XX
303 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
305 Say Y here if to include support for the watchdog timer
306 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
307 be built as a module by choosing M. The module will
310 Note: The IOP13XX watchdog does an Internal Bus Reset which will
311 affect both cores and the peripherals of the IOP. The ATU-X
312 and/or ATUe configuration registers will remain intact, but if
313 operating as an Root Complex and/or Central Resource, the PCI-X
314 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
316 config DAVINCI_WATCHDOG
317 tristate "DaVinci watchdog"
318 depends on ARCH_DAVINCI || ARCH_KEYSTONE
321 Say Y here if to include support for the watchdog timer
322 in the DaVinci DM644x/DM646x or Keystone processors.
323 To compile this driver as a module, choose M here: the
324 module will be called davinci_wdt.
326 NOTE: once enabled, this timer cannot be disabled.
327 Say N if you are unsure.
329 config ORION_WATCHDOG
330 tristate "Orion watchdog"
331 depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
334 Say Y here if to include support for the watchdog timer
335 in the Marvell Orion5x and Kirkwood ARM SoCs.
336 To compile this driver as a module, choose M here: the
337 module will be called orion_wdt.
339 config RN5T618_WATCHDOG
340 tristate "Ricoh RN5T618 watchdog"
341 depends on MFD_RN5T618
344 If you say yes here you get support for watchdog on the Ricoh
347 This driver can also be built as a module. If so, the module
348 will be called rn5t618_wdt.
350 config SUNXI_WATCHDOG
351 tristate "Allwinner SoCs watchdog support"
352 depends on ARCH_SUNXI
355 Say Y here to include support for the watchdog timer
357 To compile this driver as a module, choose M here: the
358 module will be called sunxi_wdt.
360 config COH901327_WATCHDOG
361 bool "ST-Ericsson COH 901 327 watchdog"
363 default y if MACH_U300
366 Say Y here to include Watchdog timer support for the
367 watchdog embedded into the ST-Ericsson U300 series platforms.
368 This watchdog is used to reset the system and thus cannot be
369 compiled as a module.
371 config TWL4030_WATCHDOG
372 tristate "TWL4030 Watchdog"
373 depends on TWL4030_CORE
376 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
377 watchdog timer support for TWL4030 chips.
379 config STMP3XXX_RTC_WATCHDOG
380 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
381 depends on RTC_DRV_STMP
384 Say Y here to include support for the watchdog timer inside
385 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
386 To compile this driver as a module, choose M here: the
387 module will be called stmp3xxx_rtc_wdt.
389 config NUC900_WATCHDOG
390 tristate "Nuvoton NUC900 watchdog"
391 depends on ARCH_W90X900
393 Say Y here if to include support for the watchdog timer
394 for the Nuvoton NUC900 series SoCs.
395 To compile this driver as a module, choose M here: the
396 module will be called nuc900_wdt.
398 config TS72XX_WATCHDOG
399 tristate "TS-72XX SBC Watchdog"
400 depends on MACH_TS72XX
402 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
403 watchdog timer implemented in a external CPLD chip. Say Y here
404 if you want to support for the watchdog timer on TS-72XX boards.
406 To compile this driver as a module, choose M here: the
407 module will be called ts72xx_wdt.
409 config MAX63XX_WATCHDOG
410 tristate "Max63xx watchdog"
411 depends on ARM && HAS_IOMEM
414 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
417 tristate "IMX2+ Watchdog"
422 This is the driver for the hardware watchdog
423 on the Freescale IMX2 and later processors.
424 If you have one of these processors and wish to have
425 watchdog support enabled, say Y, otherwise say N.
427 To compile this driver as a module, choose M here: the
428 module will be called imx2_wdt.
430 config UX500_WATCHDOG
431 tristate "ST-Ericsson Ux500 watchdog"
432 depends on MFD_DB8500_PRCMU
436 Say Y here to include Watchdog timer support for the watchdog
437 existing in the prcmu of ST-Ericsson Ux500 series platforms.
439 To compile this driver as a module, choose M here: the
440 module will be called ux500_wdt.
443 tristate "Retu watchdog"
447 Retu watchdog driver for Nokia Internet Tablets (770, N800,
448 N810). At least on N800 the watchdog cannot be disabled, so
449 this driver is essential and you should enable it.
451 To compile this driver as a module, choose M here: the
452 module will be called retu_wdt.
455 tristate "MOXART watchdog"
456 depends on ARCH_MOXART
458 Say Y here to include Watchdog timer support for the watchdog
459 existing on the MOXA ART SoC series platforms.
461 To compile this driver as a module, choose M here: the
462 module will be called moxart_wdt.
464 config SIRFSOC_WATCHDOG
465 tristate "SiRFSOC watchdog"
470 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
471 the watchdog triggers the system will be reset.
473 config ST_LPC_WATCHDOG
474 tristate "STMicroelectronics LPC Watchdog"
479 Say Y here to include STMicroelectronics Low Power Controller
480 (LPC) based Watchdog timer support.
482 To compile this driver as a module, choose M here: the
483 module will be called st_lpc_wdt.
485 config TEGRA_WATCHDOG
486 tristate "Tegra watchdog"
487 depends on (ARCH_TEGRA || COMPILE_TEST) && HAS_IOMEM
490 Say Y here to include support for the watchdog timer
491 embedded in NVIDIA Tegra SoCs.
493 To compile this driver as a module, choose M here: the
494 module will be called tegra_wdt.
497 tristate "QCOM watchdog"
502 Say Y here to include Watchdog timer support for the watchdog found
503 on QCOM chipsets. Currently supported targets are the MSM8960,
504 APQ8064, and IPQ8064.
506 To compile this driver as a module, choose M here: the
507 module will be called qcom_wdt.
509 config MESON_WATCHDOG
510 tristate "Amlogic Meson SoCs watchdog support"
511 depends on ARCH_MESON
514 Say Y here to include support for the watchdog timer
515 in Amlogic Meson SoCs.
516 To compile this driver as a module, choose M here: the
517 module will be called meson_wdt.
519 config MEDIATEK_WATCHDOG
520 tristate "Mediatek SoCs watchdog support"
521 depends on ARCH_MEDIATEK
524 Say Y here to include support for the watchdog timer
526 To compile this driver as a module, choose M here: the
527 module will be called mtk_wdt.
531 config AT32AP700X_WDT
532 tristate "AT32AP700x watchdog"
533 depends on CPU_AT32AP700X
535 Watchdog timer embedded into AT32AP700x devices. This will reboot
536 your system when the timeout is reached.
538 # BLACKFIN Architecture
541 tristate "Blackfin On-Chip Watchdog Timer"
544 If you say yes here you will get support for the Blackfin On-Chip
545 Watchdog Timer. If you have one of these processors and wish to
546 have watchdog support enabled, say Y, otherwise say N.
548 To compile this driver as a module, choose M here: the
549 module will be called bfin_wdt.
555 # X86 (i386 + ia64 + x86_64) Architecture
558 tristate "Acquire SBC Watchdog Timer"
561 This is the driver for the hardware watchdog on Single Board
562 Computers produced by Acquire Inc (and others). This watchdog
563 simply watches your kernel to make sure it doesn't freeze, and if
564 it does, it reboots your computer after a certain amount of time.
566 To compile this driver as a module, choose M here: the
567 module will be called acquirewdt.
569 Most people will say N.
572 tristate "Advantech SBC Watchdog Timer"
575 If you are configuring a Linux kernel for the Advantech single-board
576 computer, say `Y' here to support its built-in watchdog timer
577 feature. More information can be found at
578 <http://www.advantech.com.tw/products/>
581 tristate "ALi M1535 PMU Watchdog Timer"
582 depends on X86 && PCI
584 This is the driver for the hardware watchdog on the ALi M1535 PMU.
586 To compile this driver as a module, choose M here: the
587 module will be called alim1535_wdt.
589 Most people will say N.
592 tristate "ALi M7101 PMU Computer Watchdog"
595 This is the driver for the hardware watchdog on the ALi M7101 PMU
596 as used in the x86 Cobalt servers and also found in some
597 SPARC Netra servers too.
599 To compile this driver as a module, choose M here: the
600 module will be called alim7101_wdt.
602 Most people will say N.
605 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
608 This is the driver for the hardware watchdog on the Fintek
609 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
611 You can compile this driver directly into the kernel, or use
612 it as a module. The module will be called f71808e_wdt.
615 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
616 depends on X86 && PCI
618 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
619 (Total Cost of Ownership) timer is a watchdog timer that will reboot
620 the machine after its expiration. The expiration time can be
621 configured with the "heartbeat" parameter.
623 To compile this driver as a module, choose M here: the
624 module will be called sp5100_tco.
627 tristate "AMD Geode CS5535/CS5536 Watchdog"
628 depends on CS5535_MFGPT
630 This driver enables a watchdog capability built into the
631 CS5535/CS5536 companion chips for the AMD Geode GX and LX
632 processors. This watchdog watches your kernel to make sure
633 it doesn't freeze, and if it does, it reboots your computer after
634 a certain amount of time.
636 You can compile this driver directly into the kernel, or use
637 it as a module. The module will be called geodewdt.
640 tristate "AMD Elan SC520 processor Watchdog"
643 This is the driver for the hardware watchdog built in to the
644 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
645 This watchdog simply watches your kernel to make sure it doesn't
646 freeze, and if it does, it reboots your computer after a certain
649 You can compile this driver directly into the kernel, or use
650 it as a module. The module will be called sc520_wdt.
652 config SBC_FITPC2_WATCHDOG
653 tristate "Compulab SBC-FITPC2 watchdog"
656 This is the driver for the built-in watchdog timer on the fit-PC2,
657 fit-PC2i, CM-iAM single-board computers made by Compulab.
659 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
660 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
662 Entering BIOS setup temporary disables watchdog operation regardless to current state,
663 so system will not be restarted while user in BIOS setup.
665 Once watchdog was enabled the system will be restarted every
666 "Watchdog Timer Value" period, so to prevent it user can restart or
667 disable the watchdog.
669 To compile this driver as a module, choose M here: the
670 module will be called sbc_fitpc2_wdt.
672 Most people will say N.
675 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
678 Enable support for the watchdog timer on the Eurotech CPU-1220 and
679 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
680 information are at <http://www.eurotech.it/>.
683 tristate "IB700 SBC Watchdog Timer"
686 This is the driver for the hardware watchdog on the IB700 Single
687 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
688 simply watches your kernel to make sure it doesn't freeze, and if
689 it does, it reboots your computer after a certain amount of time.
691 This driver is like the WDT501 driver but for slightly different hardware.
693 To compile this driver as a module, choose M here: the
694 module will be called ib700wdt.
696 Most people will say N.
699 tristate "IBM Automatic Server Restart"
702 This is the driver for the IBM Automatic Server Restart watchdog
703 timer built-in into some eServer xSeries machines.
705 To compile this driver as a module, choose M here: the
706 module will be called ibmasr.
709 tristate "ICP Single Board Computer Watchdog Timer"
712 This is a driver for the hardware watchdog on the ICP Single
713 Board Computer. This driver is working on (at least) the following
714 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
716 To compile this driver as a module, choose M here: the
717 module will be called wafer5823wdt.
720 tristate "Intel 6300ESB Timer/Watchdog"
723 Hardware driver for the watchdog timer built into the Intel
724 6300ESB controller hub.
726 To compile this driver as a module, choose M here: the
727 module will be called i6300esb.
730 tristate "Intel Atom E6xx Watchdog"
731 depends on X86 && PCI
736 Hardware driver for the watchdog timer built into the Intel
737 Atom E6XX (TunnelCreek) processor.
739 To compile this driver as a module, choose M here: the
740 module will be called ie6xx_wdt.
742 config INTEL_SCU_WATCHDOG
743 bool "Intel SCU Watchdog for Mobile Platforms"
744 depends on X86_INTEL_MID
746 Hardware driver for the watchdog time built into the Intel SCU
747 for Intel Mobile Platforms.
749 To compile this driver as a module, choose M here.
751 config INTEL_MID_WATCHDOG
752 tristate "Intel MID Watchdog Timer"
753 depends on X86_INTEL_MID
756 Watchdog timer driver built into the Intel SCU for Intel MID
759 This driver currently supports only the watchdog evolution
760 implementation in SCU, available for Merrifield generation.
762 To compile this driver as a module, choose M here.
765 tristate "Intel TCO Timer/Watchdog"
766 depends on (X86 || IA64) && PCI
770 Hardware driver for the intel TCO timer based watchdog devices.
771 These drivers are included in the Intel 82801 I/O Controller
772 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
775 The TCO (Total Cost of Ownership) timer is a watchdog timer
776 that will reboot the machine after its second expiration. The
777 expiration time can be configured with the "heartbeat" parameter.
779 On some motherboards the driver may fail to reset the chipset's
780 NO_REBOOT flag which prevents the watchdog from rebooting the
781 machine. If this is the case you will get a kernel message like
782 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
784 To compile this driver as a module, choose M here: the
785 module will be called iTCO_wdt.
787 config ITCO_VENDOR_SUPPORT
788 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
791 Add vendor specific support to the intel TCO timer based watchdog
792 devices. At this moment we only have additional support for some
793 SuperMicro Inc. motherboards.
796 tristate "IT8712F (Smart Guardian) Watchdog Timer"
799 This is the driver for the built-in watchdog timer on the IT8712F
800 Super I/0 chipset used on many motherboards.
802 If the driver does not work, then make sure that the game port in
805 To compile this driver as a module, choose M here: the
806 module will be called it8712f_wdt.
809 tristate "IT87 Watchdog Timer"
812 This is the driver for the hardware watchdog on the ITE IT8702,
813 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
816 If the driver does not work, then make sure that the game port in
819 This watchdog simply watches your kernel to make sure it doesn't
820 freeze, and if it does, it reboots your computer after a certain
823 To compile this driver as a module, choose M here: the module will
827 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
828 depends on X86 && PCI
830 A software monitoring watchdog and NMI sourcing driver. This driver
831 will detect lockups and provide a stack trace. This is a driver that
832 will only load on an HP ProLiant system with a minimum of iLO2 support.
833 To compile this driver as a module, choose M here: the module will be
837 tristate "Kontron COM Watchdog Timer"
838 depends on MFD_KEMPLD
841 Support for the PLD watchdog on some Kontron ETX and COMexpress
844 This driver can also be built as a module. If so, the module will be
847 config HPWDT_NMI_DECODING
848 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
849 depends on HP_WATCHDOG
852 When an NMI occurs this feature will make the necessary BIOS calls to
853 log the cause of the NMI.
856 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
859 This is a driver for National Semiconductor PC87307/PC97307 hardware
860 watchdog cards as found on the SC1200. This watchdog is mainly used
861 for power management purposes and can be used to power down the device
862 during inactivity periods (includes interrupt activity monitoring).
864 To compile this driver as a module, choose M here: the
865 module will be called sc1200wdt.
867 Most people will say N.
870 tristate "National Semiconductor SCx200 Watchdog"
871 depends on SCx200 && PCI
873 Enable the built-in watchdog timer support on the National
874 Semiconductor SCx200 processors.
876 If compiled as a module, it will be called scx200_wdt.
879 tristate "NS PC87413 watchdog"
882 This is the driver for the hardware watchdog on the PC87413 chipset
883 This watchdog simply watches your kernel to make sure it doesn't
884 freeze, and if it does, it reboots your computer after a certain
887 To compile this driver as a module, choose M here: the
888 module will be called pc87413_wdt.
890 Most people will say N.
893 tristate "nVidia TCO Timer/Watchdog"
894 depends on X86 && PCI
896 Hardware driver for the TCO timer built into the nVidia Hub family
897 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
898 watchdog timer that will reboot the machine after its second
899 expiration. The expiration time can be configured with the
900 "heartbeat" parameter.
902 On some motherboards the driver may fail to reset the chipset's
903 NO_REBOOT flag which prevents the watchdog from rebooting the
904 machine. If this is the case you will get a kernel message like
905 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
907 To compile this driver as a module, choose M here: the
908 module will be called nv_tco.
911 tristate "RDC R-321x SoC watchdog"
912 depends on X86_RDC321X
914 This is the driver for the built in hardware watchdog
915 in the RDC R-321x SoC.
917 To compile this driver as a module, choose M here: the
918 module will be called rdc321x_wdt.
921 tristate "SBC-60XX Watchdog Timer"
924 This driver can be used with the watchdog timer found on some
925 single board computers, namely the 6010 PII based computer.
926 It may well work with other cards. It reads port 0x443 to enable
927 and re-set the watchdog timer, and reads port 0x45 to disable
928 the watchdog. If you have a card that behave in similar ways,
929 you can probably make this driver work with your card as well.
931 You can compile this driver directly into the kernel, or use
932 it as a module. The module will be called sbc60xxwdt.
935 tristate "SBC8360 Watchdog Timer"
939 This is the driver for the hardware watchdog on the SBC8360 Single
940 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
942 To compile this driver as a module, choose M here: the
943 module will be called sbc8360.
945 Most people will say N.
948 tristate "SBC Nano 7240 Watchdog Timer"
949 depends on X86_32 && !UML
951 This is the driver for the hardware watchdog found on the IEI
952 single board computers EPIC Nano 7240 (and likely others). This
953 watchdog simply watches your kernel to make sure it doesn't freeze,
954 and if it does, it reboots your computer after a certain amount of
957 To compile this driver as a module, choose M here: the
958 module will be called sbc7240_wdt.
961 tristate "SMA CPU5 Watchdog"
965 To compile this driver as a module, choose M here: the
966 module will be called cpu5wdt.
968 config SMSC_SCH311X_WDT
969 tristate "SMSC SCH311X Watchdog Timer"
972 This is the driver for the hardware watchdog timer on the
973 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
974 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
977 To compile this driver as a module, choose M here: the
978 module will be called sch311x_wdt.
980 config SMSC37B787_WDT
981 tristate "Winbond SMsC37B787 Watchdog Timer"
984 This is the driver for the hardware watchdog component on the
985 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
986 from Vision Systems and maybe others.
988 This watchdog simply watches your kernel to make sure it doesn't
989 freeze, and if it does, it reboots your computer after a certain
992 Usually a userspace daemon will notify the kernel WDT driver that
993 userspace is still alive, at regular intervals.
995 To compile this driver as a module, choose M here: the
996 module will be called smsc37b787_wdt.
998 Most people will say N.
1001 tristate "VIA Watchdog Timer"
1002 depends on X86 && PCI
1003 select WATCHDOG_CORE
1005 This is the driver for the hardware watchdog timer on VIA
1006 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
1008 To compile this driver as a module, choose M here; the module
1009 will be called via_wdt.
1011 Most people will say N.
1014 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
1016 select WATCHDOG_CORE
1018 This is the driver for the hardware watchdog on the following
1020 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
1032 This watchdog simply watches your kernel to make sure it doesn't
1033 freeze, and if it does, it reboots your computer after a certain
1036 To compile this driver as a module, choose M here: the
1037 module will be called w83627hf_wdt.
1039 Most people will say N.
1042 tristate "W83877F (EMACS) Watchdog Timer"
1045 This is the driver for the hardware watchdog on the W83877F chipset
1046 as used in EMACS PC-104 motherboards (and likely others). This
1047 watchdog simply watches your kernel to make sure it doesn't freeze,
1048 and if it does, it reboots your computer after a certain amount of
1051 To compile this driver as a module, choose M here: the
1052 module will be called w83877f_wdt.
1054 Most people will say N.
1057 tristate "W83977F (PCM-5335) Watchdog Timer"
1060 This is the driver for the hardware watchdog on the W83977F I/O chip
1061 as used in AAEON's PCM-5335 SBC (and likely others). This
1062 watchdog simply watches your kernel to make sure it doesn't freeze,
1063 and if it does, it reboots your computer after a certain amount of
1066 To compile this driver as a module, choose M here: the
1067 module will be called w83977f_wdt.
1070 tristate "ZF MachZ Watchdog"
1073 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1074 N. This is the driver for the watchdog timer built-in on that
1075 processor using ZF-Logic interface. This watchdog simply watches
1076 your kernel to make sure it doesn't freeze, and if it does, it
1077 reboots your computer after a certain amount of time.
1079 To compile this driver as a module, choose M here: the
1080 module will be called machzwd.
1082 config SBC_EPX_C3_WATCHDOG
1083 tristate "Winsystems SBC EPX-C3 watchdog"
1086 This is the driver for the built-in watchdog timer on the EPX-C3
1087 Single-board computer made by Winsystems, Inc.
1089 *Note*: This hardware watchdog is not probeable and thus there
1090 is no way to know if writing to its IO address will corrupt
1091 your system or have any real effect. The only way to be sure
1092 that this driver does what you want is to make sure you
1093 are running it on an EPX-C3 from Winsystems with the watchdog
1094 timer at IO address 0x1ee and 0x1ef. It will write to both those
1095 IO ports. Basically, the assumption is made that if you compile
1096 this driver into your kernel and/or load it as a module, that you
1097 know what you are doing and that you are in fact running on an
1100 To compile this driver as a module, choose M here: the
1101 module will be called sbc_epx_c3.
1107 config M54xx_WATCHDOG
1108 tristate "MCF54xx watchdog support"
1111 To compile this driver as a module, choose M here: the
1112 module will be called m54xx_wdt.
1114 # MicroBlaze Architecture
1119 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1122 Hardware driver for the built-in watchdog timer on the Atheros
1123 AR71XX/AR724X/AR913X SoCs.
1126 tristate "Broadcom BCM47xx Watchdog Timer"
1127 depends on BCM47XX || ARCH_BCM_5301X
1128 select WATCHDOG_CORE
1130 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1133 tristate "IDT RC32434 SoC Watchdog Timer"
1134 depends on MIKROTIK_RB532
1136 Hardware driver for the IDT RC32434 SoC built-in
1139 To compile this driver as a module, choose M here: the
1140 module will be called rc32434_wdt.
1143 tristate "Indy/I2 Hardware Watchdog"
1144 depends on SGI_HAS_INDYDOG
1146 Hardware driver for the Indy's/I2's watchdog. This is a
1147 watchdog timer that will reboot the machine after a 60 second
1148 timer expired and no process has written to /dev/watchdog during
1152 tristate "Ingenic jz4740 SoC hardware watchdog"
1153 depends on MACH_JZ4740
1154 select WATCHDOG_CORE
1156 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1159 tristate "MTX-1 Hardware Watchdog"
1160 depends on MIPS_MTX1
1162 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1163 will reboot the machine after a 100 seconds timer expired.
1166 tristate "PNX833x Hardware Watchdog"
1167 depends on SOC_PNX8335
1169 Hardware driver for the PNX833x's watchdog. This is a
1170 watchdog timer that will reboot the machine after a programmable
1171 timer has expired and no process has written to /dev/watchdog during
1175 tristate "Sibyte SoC hardware watchdog"
1178 Watchdog driver for the built in watchdog hardware in Sibyte
1179 SoC processors. There are apparently two watchdog timers
1180 on such processors; this driver supports only the first one,
1181 because currently Linux only supports exporting one watchdog
1184 To compile this driver as a loadable module, choose M here.
1185 The module will be called sb_wdog.
1188 tristate "TI AR7 Watchdog Timer"
1191 Hardware driver for the TI AR7 Watchdog Timer.
1194 tristate "Toshiba TXx9 Watchdog Timer"
1195 depends on CPU_TX39XX || CPU_TX49XX
1196 select WATCHDOG_CORE
1198 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1201 tristate "Cavium OCTEON SOC family Watchdog Timer"
1202 depends on CAVIUM_OCTEON_SOC
1204 select WATCHDOG_CORE
1205 select EXPORT_UASM if OCTEON_WDT = m
1207 Hardware driver for OCTEON's on chip watchdog timer.
1208 Enables the watchdog for all cores running Linux. It
1209 installs a NMI handler and pokes the watchdog based on an
1210 interrupt. On first expiration of the watchdog, the
1211 interrupt handler pokes it. The second expiration causes an
1212 NMI that prints a message. The third expiration causes a
1215 When userspace has /dev/watchdog open, no poking is done
1216 from the first interrupt, it is then only poked when the
1220 tristate "Broadcom BCM63xx hardware watchdog"
1223 Watchdog driver for the built in watchdog hardware in Broadcom
1226 To compile this driver as a loadable module, choose M here.
1227 The module will be called bcm63xx_wdt.
1230 tristate "Broadcom BCM2835 hardware watchdog"
1231 depends on ARCH_BCM2835
1232 select WATCHDOG_CORE
1234 Watchdog driver for the built in watchdog hardware in Broadcom
1237 To compile this driver as a loadable module, choose M here.
1238 The module will be called bcm2835_wdt.
1241 tristate "BCM Kona Watchdog"
1242 depends on ARCH_BCM_MOBILE
1243 select WATCHDOG_CORE
1245 Support for the watchdog timer on the following Broadcom BCM281xx
1246 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1249 Say 'Y' or 'M' here to enable the driver. The module will be called
1252 config BCM_KONA_WDT_DEBUG
1253 bool "DEBUGFS support for BCM Kona Watchdog"
1254 depends on BCM_KONA_WDT
1256 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1257 access to the driver's internal data structures as well as watchdog
1258 timer hardware registres.
1260 If in doubt, say 'N'.
1263 tristate "Imagination Technologies PDC Watchdog Timer"
1264 depends on HAS_IOMEM
1265 depends on METAG || MIPS || COMPILE_TEST
1267 Driver for Imagination Technologies PowerDown Controller
1270 To compile this driver as a loadable module, choose M here.
1271 The module will be called imgpdc_wdt.
1274 tristate "Lantiq SoC watchdog"
1277 Hardware driver for the Lantiq SoC Watchdog Timer.
1280 tristate "Ralink SoC watchdog"
1281 select WATCHDOG_CORE
1284 Hardware driver for the Ralink SoC Watchdog Timer.
1286 # PARISC Architecture
1288 # POWERPC Architecture
1291 tristate "GE Watchdog Timer"
1294 Watchdog timer found in a number of GE single board computers.
1297 bool "MPC52xx Watchdog Timer"
1298 depends on PPC_MPC52xx
1300 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1303 tristate "MPC8xxx Platform Watchdog Timer"
1304 depends on PPC_8xx || PPC_83xx || PPC_86xx
1305 select WATCHDOG_CORE
1307 This driver is for a SoC level watchdog that exists on some
1308 Freescale PowerPC processors. So far this driver supports:
1313 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1316 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1320 tristate "PIKA FPGA Watchdog"
1324 This enables the watchdog in the PIKA FPGA. Currently used on
1328 tristate "PowerPC Book-E Watchdog Timer"
1329 depends on BOOKE || 4xx
1330 select WATCHDOG_CORE
1332 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1333 MPC85xx SOCs and the IBM PowerPC 440.
1335 Please see Documentation/watchdog/watchdog-api.txt for
1338 config BOOKE_WDT_DEFAULT_TIMEOUT
1339 int "PowerPC Book-E Watchdog Timer Default Timeout"
1340 depends on BOOKE_WDT
1341 default 38 if PPC_FSL_BOOK3E
1342 range 0 63 if PPC_FSL_BOOK3E
1343 default 3 if !PPC_FSL_BOOK3E
1344 range 0 3 if !PPC_FSL_BOOK3E
1346 Select the default watchdog timer period to be used by the PowerPC
1347 Book-E watchdog driver. A watchdog "event" occurs when the bit
1348 position represented by this number transitions from zero to one.
1350 For Freescale Book-E processors, this is a number between 0 and 63.
1351 For other Book-E processors, this is a number between 0 and 3.
1353 The value can be overridden by the wdt_period command-line parameter.
1356 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1357 select WATCHDOG_CORE
1360 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1362 The driver can also be built as a module. If so, the module will be
1365 If unsure select N here.
1367 # PPC64 Architecture
1369 config WATCHDOG_RTAS
1370 tristate "RTAS watchdog"
1373 This driver adds watchdog support for the RTAS watchdog.
1375 To compile this driver as a module, choose M here. The module
1376 will be called wdrtas.
1380 config DIAG288_WATCHDOG
1381 tristate "System z diag288 Watchdog"
1383 select WATCHDOG_CORE
1385 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1386 provide a virtual watchdog timer to their guest that cause a
1387 user define Control Program command to be executed after a
1389 LPAR provides a very similar interface. This driver handles
1392 To compile this driver as a module, choose M here. The module
1393 will be called diag288_wdt.
1395 # SUPERH (sh + sh64) Architecture
1398 tristate "SuperH Watchdog"
1399 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1400 select WATCHDOG_CORE
1402 This driver adds watchdog support for the integrated watchdog in the
1403 SuperH processors. If you have one of these processors and wish
1404 to have watchdog support enabled, say Y, otherwise say N.
1406 As a side note, saying Y here will automatically boost HZ to 1000
1407 so that the timer has a chance to clear the overflow counter. On
1408 slower systems (such as the SH-2 and SH-3) this will likely yield
1409 some performance issues. As such, the WDT should be avoided here
1410 unless it is absolutely necessary.
1412 To compile this driver as a module, choose M here: the
1413 module will be called shwdt.
1415 # SPARC Architecture
1417 # SPARC64 Architecture
1419 config WATCHDOG_CP1XXX
1420 tristate "CP1XXX Hardware Watchdog support"
1421 depends on SPARC64 && PCI
1423 This is the driver for the hardware watchdog timers present on
1424 Sun Microsystems CompactPCI models CP1400 and CP1500.
1426 To compile this driver as a module, choose M here: the
1427 module will be called cpwatchdog.
1429 If you do not have a CompactPCI model CP1400 or CP1500, or
1430 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1431 you should say N to this option.
1434 tristate "RIO Hardware Watchdog support"
1435 depends on SPARC64 && PCI
1437 Say Y here to support the hardware watchdog capability on Sun RIO
1438 machines. The watchdog timeout period is normally one minute but
1439 can be changed with a boot-time parameter.
1441 # XTENSA Architecture
1446 tristate "Xen Watchdog support"
1449 Say Y here to support the hypervisor watchdog capability provided
1450 by Xen 4.0 and newer. The watchdog timeout period is normally one
1451 minute but can be changed with a boot-time parameter.
1454 tristate "UML watchdog"
1458 # ISA-based Watchdog Cards
1461 comment "ISA-based Watchdog Cards"
1465 tristate "Berkshire Products ISA-PC Watchdog"
1468 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1469 This card simply watches your kernel to make sure it doesn't freeze,
1470 and if it does, it reboots your computer after a certain amount of
1471 time. This driver is like the WDT501 driver but for different
1472 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1473 watchdog cards can be ordered from <http://www.berkprod.com/>.
1475 To compile this driver as a module, choose M here: the
1476 module will be called pcwd.
1478 Most people will say N.
1481 tristate "Mixcom Watchdog"
1484 This is a driver for the Mixcom hardware watchdog cards. This
1485 watchdog simply watches your kernel to make sure it doesn't freeze,
1486 and if it does, it reboots your computer after a certain amount of
1489 To compile this driver as a module, choose M here: the
1490 module will be called mixcomwd.
1492 Most people will say N.
1495 tristate "WDT Watchdog timer"
1498 If you have a WDT500P or WDT501P watchdog board, say Y here,
1499 otherwise N. It is not possible to probe for this board, which means
1500 that you have to inform the kernel about the IO port and IRQ that
1501 is needed (you can do this via the io and irq parameters)
1503 To compile this driver as a module, choose M here: the
1504 module will be called wdt.
1507 # PCI-based Watchdog Cards
1510 comment "PCI-based Watchdog Cards"
1513 config PCIPCWATCHDOG
1514 tristate "Berkshire Products PCI-PC Watchdog"
1517 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1518 This card simply watches your kernel to make sure it doesn't freeze,
1519 and if it does, it reboots your computer after a certain amount of
1520 time. The card can also monitor the internal temperature of the PC.
1521 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1523 To compile this driver as a module, choose M here: the
1524 module will be called pcwd_pci.
1526 Most people will say N.
1529 tristate "PCI-WDT500/501 Watchdog timer"
1532 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1534 If you have a PCI-WDT501 watchdog board then you can enable the
1535 temperature sensor by setting the type parameter to 501.
1537 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1538 can do this via the tachometer parameter. Only do this if you have a
1539 fan tachometer actually set up.
1541 To compile this driver as a module, choose M here: the
1542 module will be called wdt_pci.
1545 # USB-based Watchdog Cards
1548 comment "USB-based Watchdog Cards"
1551 config USBPCWATCHDOG
1552 tristate "Berkshire Products USB-PC Watchdog"
1555 This is the driver for the Berkshire Products USB-PC Watchdog card.
1556 This card simply watches your kernel to make sure it doesn't freeze,
1557 and if it does, it reboots your computer after a certain amount of
1558 time. The card can also monitor the internal temperature of the PC.
1559 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1561 To compile this driver as a module, choose M here: the
1562 module will be called pcwd_usb.
1564 Most people will say N.