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 WM831X_WATCHDOG
80 tristate "WM831x watchdog"
84 Support for the watchdog in the WM831x AudioPlus PMICs. When
85 the watchdog triggers the system will be reset.
87 config WM8350_WATCHDOG
88 tristate "WM8350 watchdog"
92 Support for the watchdog in the WM8350 AudioPlus PMIC. When
93 the watchdog triggers the system will be reset.
99 config ARM_SP805_WATCHDOG
100 tristate "ARM SP805 Watchdog"
104 ARM Primecell SP805 Watchdog timer. This will reboot your system when
105 the timeout is reached.
107 config AT91RM9200_WATCHDOG
108 tristate "AT91RM9200 watchdog"
109 depends on ARCH_AT91RM9200
111 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
112 system when the timeout is reached.
114 config AT91SAM9X_WATCHDOG
115 tristate "AT91SAM9X / AT91CAP9 watchdog"
116 depends on ARCH_AT91 && !ARCH_AT91RM9200
118 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
119 reboot your system when the timeout is reached.
121 config 21285_WATCHDOG
122 tristate "DC21285 watchdog"
123 depends on FOOTBRIDGE
125 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
126 here if you wish to use this. Alternatively say M to compile the
127 driver as a module, which will be called wdt285.
129 This driver does not work on all machines. In particular, early CATS
130 boards have hardware problems that will cause the machine to simply
131 lock up if the watchdog fires.
133 "If in doubt, leave it out" - say N.
136 tristate "NetWinder WB83C977 watchdog"
137 depends on FOOTBRIDGE && ARCH_NETWINDER
139 Say Y here to include support for the WB977 watchdog included in
140 NetWinder machines. Alternatively say M to compile the driver as
141 a module, which will be called wdt977.
143 Not sure? It's safe to say N.
145 config IXP4XX_WATCHDOG
146 tristate "IXP4xx Watchdog"
147 depends on ARCH_IXP4XX
149 Say Y here if to include support for the watchdog timer
150 in the Intel IXP4xx network processors. This driver can
151 be built as a module by choosing M. The module will
152 be called ixp4xx_wdt.
154 Note: The internal IXP4xx watchdog does a soft CPU reset
155 which doesn't reset any peripherals. There are circumstances
156 where the watchdog will fail to reset the board correctly
157 (e.g., if the boot ROM is in an unreadable state).
159 Say N if you are unsure.
161 config KS8695_WATCHDOG
162 tristate "KS8695 watchdog"
163 depends on ARCH_KS8695
165 Watchdog timer embedded into KS8695 processor. This will reboot your
166 system when the timeout is reached.
168 config HAVE_S3C2410_WATCHDOG
171 This will include watchdog timer support for Samsung SoCs. If
172 you want to include watchdog support for any machine, kindly
173 select this in the respective mach-XXXX/Kconfig file.
175 config S3C2410_WATCHDOG
176 tristate "S3C2410 Watchdog"
177 depends on HAVE_S3C2410_WATCHDOG
180 Watchdog timer block in the Samsung SoCs. This will reboot
181 the system when the timer expires with the watchdog enabled.
183 The driver is limited by the speed of the system's PCLK
184 signal, so with reasonably fast systems (PCLK around 50-66MHz)
185 then watchdog intervals of over approximately 20seconds are
188 The driver can be built as a module by choosing M, and will
189 be called s3c2410_wdt
191 config SA1100_WATCHDOG
192 tristate "SA1100/PXA2xx watchdog"
193 depends on ARCH_SA1100 || ARCH_PXA
195 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
196 reboot your system when timeout is reached.
198 NOTE: once enabled, this timer cannot be disabled.
200 To compile this driver as a module, choose M here: the
201 module will be called sa1100_wdt.
204 tristate "Synopsys DesignWare watchdog"
205 depends on ARM && HAVE_CLK
207 Say Y here if to include support for the Synopsys DesignWare
208 watchdog timer found in many ARM chips.
209 To compile this driver as a module, choose M here: the
210 module will be called dw_wdt.
212 config MPCORE_WATCHDOG
213 tristate "MPcore watchdog"
214 depends on HAVE_ARM_TWD
216 Watchdog timer embedded into the MPcore system.
218 To compile this driver as a module, choose M here: the
219 module will be called mpcore_wdt.
221 config EP93XX_WATCHDOG
222 tristate "EP93xx Watchdog"
223 depends on ARCH_EP93XX
226 Say Y here if to include support for the watchdog timer
227 embedded in the Cirrus Logic EP93xx family of devices.
229 To compile this driver as a module, choose M here: the
230 module will be called ep93xx_wdt.
233 tristate "OMAP Watchdog"
234 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
236 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
237 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
239 config PNX4008_WATCHDOG
240 tristate "LPC32XX Watchdog"
241 depends on ARCH_LPC32XX
244 Say Y here if to include support for the watchdog timer
245 in the LPC32XX processor.
246 This driver can be built as a module by choosing M. The module
247 will be called pnx4008_wdt.
249 Say N if you are unsure.
252 tristate "IOP Watchdog"
254 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
256 Say Y here if to include support for the watchdog timer
257 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
258 be built as a module by choosing M. The module will
261 Note: The IOP13XX watchdog does an Internal Bus Reset which will
262 affect both cores and the peripherals of the IOP. The ATU-X
263 and/or ATUe configuration registers will remain intact, but if
264 operating as an Root Complex and/or Central Resource, the PCI-X
265 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
267 config DAVINCI_WATCHDOG
268 tristate "DaVinci watchdog"
269 depends on ARCH_DAVINCI
271 Say Y here if to include support for the watchdog timer
272 in the DaVinci DM644x/DM646x processors.
273 To compile this driver as a module, choose M here: the
274 module will be called davinci_wdt.
276 NOTE: once enabled, this timer cannot be disabled.
277 Say N if you are unsure.
279 config ORION_WATCHDOG
280 tristate "Orion watchdog"
281 depends on ARCH_ORION5X || ARCH_KIRKWOOD
284 Say Y here if to include support for the watchdog timer
285 in the Marvell Orion5x and Kirkwood ARM SoCs.
286 To compile this driver as a module, choose M here: the
287 module will be called orion_wdt.
289 config COH901327_WATCHDOG
290 bool "ST-Ericsson COH 901 327 watchdog"
292 default y if MACH_U300
295 Say Y here to include Watchdog timer support for the
296 watchdog embedded into the ST-Ericsson U300 series platforms.
297 This watchdog is used to reset the system and thus cannot be
298 compiled as a module.
300 config TWL4030_WATCHDOG
301 tristate "TWL4030 Watchdog"
302 depends on TWL4030_CORE
305 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
306 watchdog timer support for TWL4030 chips.
308 config STMP3XXX_WATCHDOG
309 tristate "Freescale STMP3XXX watchdog"
310 depends on ARCH_STMP3XXX
312 Say Y here if to include support for the watchdog timer
313 for the Sigmatel STMP37XX/378X SoC.
314 To compile this driver as a module, choose M here: the
315 module will be called stmp3xxx_wdt.
317 config NUC900_WATCHDOG
318 tristate "Nuvoton NUC900 watchdog"
319 depends on ARCH_W90X900
321 Say Y here if to include support for the watchdog timer
322 for the Nuvoton NUC900 series SoCs.
323 To compile this driver as a module, choose M here: the
324 module will be called nuc900_wdt.
326 config TS72XX_WATCHDOG
327 tristate "TS-72XX SBC Watchdog"
328 depends on MACH_TS72XX
330 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
331 watchdog timer implemented in a external CPLD chip. Say Y here
332 if you want to support for the watchdog timer on TS-72XX boards.
334 To compile this driver as a module, choose M here: the
335 module will be called ts72xx_wdt.
337 config MAX63XX_WATCHDOG
338 tristate "Max63xx watchdog"
339 depends on ARM && HAS_IOMEM
342 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
345 tristate "IMX2+ Watchdog"
348 This is the driver for the hardware watchdog
349 on the Freescale IMX2 and later processors.
350 If you have one of these processors and wish to have
351 watchdog support enabled, say Y, otherwise say N.
353 To compile this driver as a module, choose M here: the
354 module will be called imx2_wdt.
358 config AT32AP700X_WDT
359 tristate "AT32AP700x watchdog"
360 depends on CPU_AT32AP700X
362 Watchdog timer embedded into AT32AP700x devices. This will reboot
363 your system when the timeout is reached.
365 # BLACKFIN Architecture
368 tristate "Blackfin On-Chip Watchdog Timer"
371 If you say yes here you will get support for the Blackfin On-Chip
372 Watchdog Timer. If you have one of these processors and wish to
373 have watchdog support enabled, say Y, otherwise say N.
375 To compile this driver as a module, choose M here: the
376 module will be called bfin_wdt.
384 # X86 (i386 + ia64 + x86_64) Architecture
387 tristate "Acquire SBC Watchdog Timer"
390 This is the driver for the hardware watchdog on Single Board
391 Computers produced by Acquire Inc (and others). This watchdog
392 simply watches your kernel to make sure it doesn't freeze, and if
393 it does, it reboots your computer after a certain amount of time.
395 To compile this driver as a module, choose M here: the
396 module will be called acquirewdt.
398 Most people will say N.
401 tristate "Advantech SBC Watchdog Timer"
404 If you are configuring a Linux kernel for the Advantech single-board
405 computer, say `Y' here to support its built-in watchdog timer
406 feature. More information can be found at
407 <http://www.advantech.com.tw/products/>
410 tristate "ALi M1535 PMU Watchdog Timer"
411 depends on X86 && PCI
413 This is the driver for the hardware watchdog on the ALi M1535 PMU.
415 To compile this driver as a module, choose M here: the
416 module will be called alim1535_wdt.
418 Most people will say N.
421 tristate "ALi M7101 PMU Computer Watchdog"
424 This is the driver for the hardware watchdog on the ALi M7101 PMU
425 as used in the x86 Cobalt servers and also found in some
426 SPARC Netra servers too.
428 To compile this driver as a module, choose M here: the
429 module will be called alim7101_wdt.
431 Most people will say N.
434 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
435 depends on X86 && EXPERIMENTAL
437 This is the driver for the hardware watchdog on the Fintek
438 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
440 You can compile this driver directly into the kernel, or use
441 it as a module. The module will be called f71808e_wdt.
444 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
445 depends on X86 && PCI
447 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
448 (Total Cost of Ownership) timer is a watchdog timer that will reboot
449 the machine after its expiration. The expiration time can be
450 configured with the "heartbeat" parameter.
452 To compile this driver as a module, choose M here: the
453 module will be called sp5100_tco.
456 tristate "AMD Geode CS5535/CS5536 Watchdog"
457 depends on CS5535_MFGPT
459 This driver enables a watchdog capability built into the
460 CS5535/CS5536 companion chips for the AMD Geode GX and LX
461 processors. This watchdog watches your kernel to make sure
462 it doesn't freeze, and if it does, it reboots your computer after
463 a certain amount of time.
465 You can compile this driver directly into the kernel, or use
466 it as a module. The module will be called geodewdt.
469 tristate "AMD Elan SC520 processor Watchdog"
472 This is the driver for the hardware watchdog built in to the
473 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
474 This watchdog simply watches your kernel to make sure it doesn't
475 freeze, and if it does, it reboots your computer after a certain
478 You can compile this driver directly into the kernel, or use
479 it as a module. The module will be called sc520_wdt.
481 config SBC_FITPC2_WATCHDOG
482 tristate "Compulab SBC-FITPC2 watchdog"
485 This is the driver for the built-in watchdog timer on the fit-PC2,
486 fit-PC2i, CM-iAM single-board computers made by Compulab.
488 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
489 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
491 Entering BIOS setup temporary disables watchdog operation regardless to current state,
492 so system will not be restarted while user in BIOS setup.
494 Once watchdog was enabled the system will be restarted every
495 "Watchdog Timer Value" period, so to prevent it user can restart or
496 disable the watchdog.
498 To compile this driver as a module, choose M here: the
499 module will be called sbc_fitpc2_wdt.
501 Most people will say N.
504 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
507 Enable support for the watchdog timer on the Eurotech CPU-1220 and
508 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
509 information are at <http://www.eurotech.it/>.
512 tristate "IB700 SBC Watchdog Timer"
515 This is the driver for the hardware watchdog on the IB700 Single
516 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
517 simply watches your kernel to make sure it doesn't freeze, and if
518 it does, it reboots your computer after a certain amount of time.
520 This driver is like the WDT501 driver but for slightly different hardware.
522 To compile this driver as a module, choose M here: the
523 module will be called ib700wdt.
525 Most people will say N.
528 tristate "IBM Automatic Server Restart"
531 This is the driver for the IBM Automatic Server Restart watchdog
532 timer built-in into some eServer xSeries machines.
534 To compile this driver as a module, choose M here: the
535 module will be called ibmasr.
538 tristate "ICP Single Board Computer Watchdog Timer"
541 This is a driver for the hardware watchdog on the ICP Single
542 Board Computer. This driver is working on (at least) the following
543 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
545 To compile this driver as a module, choose M here: the
546 module will be called wafer5823wdt.
549 tristate "Intel 6300ESB Timer/Watchdog"
552 Hardware driver for the watchdog timer built into the Intel
553 6300ESB controller hub.
555 To compile this driver as a module, choose M here: the
556 module will be called i6300esb.
559 tristate "Intel Atom E6xx Watchdog"
560 depends on X86 && PCI
565 Hardware driver for the watchdog timer built into the Intel
566 Atom E6XX (TunnelCreek) processor.
568 To compile this driver as a module, choose M here: the
569 module will be called ie6xx_wdt.
571 config INTEL_SCU_WATCHDOG
572 bool "Intel SCU Watchdog for Mobile Platforms"
575 Hardware driver for the watchdog time built into the Intel SCU
576 for Intel Mobile Platforms.
578 To compile this driver as a module, choose M here.
581 tristate "Intel TCO Timer/Watchdog"
582 depends on (X86 || IA64) && PCI
586 Hardware driver for the intel TCO timer based watchdog devices.
587 These drivers are included in the Intel 82801 I/O Controller
588 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
591 The TCO (Total Cost of Ownership) timer is a watchdog timer
592 that will reboot the machine after its second expiration. The
593 expiration time can be configured with the "heartbeat" parameter.
595 On some motherboards the driver may fail to reset the chipset's
596 NO_REBOOT flag which prevents the watchdog from rebooting the
597 machine. If this is the case you will get a kernel message like
598 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
600 To compile this driver as a module, choose M here: the
601 module will be called iTCO_wdt.
603 config ITCO_VENDOR_SUPPORT
604 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
607 Add vendor specific support to the intel TCO timer based watchdog
608 devices. At this moment we only have additional support for some
609 SuperMicro Inc. motherboards.
612 tristate "IT8712F (Smart Guardian) Watchdog Timer"
615 This is the driver for the built-in watchdog timer on the IT8712F
616 Super I/0 chipset used on many motherboards.
618 If the driver does not work, then make sure that the game port in
621 To compile this driver as a module, choose M here: the
622 module will be called it8712f_wdt.
625 tristate "IT87 Watchdog Timer"
626 depends on X86 && EXPERIMENTAL
628 This is the driver for the hardware watchdog on the ITE IT8702,
629 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
632 If the driver does not work, then make sure that the game port in
635 This watchdog simply watches your kernel to make sure it doesn't
636 freeze, and if it does, it reboots your computer after a certain
639 To compile this driver as a module, choose M here: the module will
643 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
644 depends on X86 && PCI
646 A software monitoring watchdog and NMI sourcing driver. This driver
647 will detect lockups and provide a stack trace. This is a driver that
648 will only load on an HP ProLiant system with a minimum of iLO2 support.
649 To compile this driver as a module, choose M here: the module will be
652 config HPWDT_NMI_DECODING
653 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
654 depends on HP_WATCHDOG
657 When an NMI occurs this feature will make the necessary BIOS calls to
658 log the cause of the NMI.
661 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
664 This is a driver for National Semiconductor PC87307/PC97307 hardware
665 watchdog cards as found on the SC1200. This watchdog is mainly used
666 for power management purposes and can be used to power down the device
667 during inactivity periods (includes interrupt activity monitoring).
669 To compile this driver as a module, choose M here: the
670 module will be called sc1200wdt.
672 Most people will say N.
675 tristate "National Semiconductor SCx200 Watchdog"
676 depends on SCx200 && PCI
678 Enable the built-in watchdog timer support on the National
679 Semiconductor SCx200 processors.
681 If compiled as a module, it will be called scx200_wdt.
684 tristate "NS PC87413 watchdog"
687 This is the driver for the hardware watchdog on the PC87413 chipset
688 This watchdog simply watches your kernel to make sure it doesn't
689 freeze, and if it does, it reboots your computer after a certain
692 To compile this driver as a module, choose M here: the
693 module will be called pc87413_wdt.
695 Most people will say N.
698 tristate "nVidia TCO Timer/Watchdog"
699 depends on X86 && PCI
701 Hardware driver for the TCO timer built into the nVidia Hub family
702 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
703 watchdog timer that will reboot the machine after its second
704 expiration. The expiration time can be configured with the
705 "heartbeat" parameter.
707 On some motherboards the driver may fail to reset the chipset's
708 NO_REBOOT flag which prevents the watchdog from rebooting the
709 machine. If this is the case you will get a kernel message like
710 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
712 To compile this driver as a module, choose M here: the
713 module will be called nv_tco.
716 tristate "RDC R-321x SoC watchdog"
717 depends on X86_RDC321X
719 This is the driver for the built in hardware watchdog
720 in the RDC R-321x SoC.
722 To compile this driver as a module, choose M here: the
723 module will be called rdc321x_wdt.
726 tristate "SBC-60XX Watchdog Timer"
729 This driver can be used with the watchdog timer found on some
730 single board computers, namely the 6010 PII based computer.
731 It may well work with other cards. It reads port 0x443 to enable
732 and re-set the watchdog timer, and reads port 0x45 to disable
733 the watchdog. If you have a card that behave in similar ways,
734 you can probably make this driver work with your card as well.
736 You can compile this driver directly into the kernel, or use
737 it as a module. The module will be called sbc60xxwdt.
740 tristate "SBC8360 Watchdog Timer"
744 This is the driver for the hardware watchdog on the SBC8360 Single
745 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
747 To compile this driver as a module, choose M here: the
748 module will be called sbc8360.
750 Most people will say N.
753 tristate "SBC Nano 7240 Watchdog Timer"
754 depends on X86_32 && !UML
756 This is the driver for the hardware watchdog found on the IEI
757 single board computers EPIC Nano 7240 (and likely others). This
758 watchdog simply watches your kernel to make sure it doesn't freeze,
759 and if it does, it reboots your computer after a certain amount of
762 To compile this driver as a module, choose M here: the
763 module will be called sbc7240_wdt.
766 tristate "SMA CPU5 Watchdog"
770 To compile this driver as a module, choose M here: the
771 module will be called cpu5wdt.
773 config SMSC_SCH311X_WDT
774 tristate "SMSC SCH311X Watchdog Timer"
777 This is the driver for the hardware watchdog timer on the
778 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
779 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
782 To compile this driver as a module, choose M here: the
783 module will be called sch311x_wdt.
785 config SMSC37B787_WDT
786 tristate "Winbond SMsC37B787 Watchdog Timer"
789 This is the driver for the hardware watchdog component on the
790 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
791 from Vision Systems and maybe others.
793 This watchdog simply watches your kernel to make sure it doesn't
794 freeze, and if it does, it reboots your computer after a certain
797 Usually a userspace daemon will notify the kernel WDT driver that
798 userspace is still alive, at regular intervals.
800 To compile this driver as a module, choose M here: the
801 module will be called smsc37b787_wdt.
803 Most people will say N.
806 tristate "VIA Watchdog Timer"
807 depends on X86 && PCI
810 This is the driver for the hardware watchdog timer on VIA
811 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
813 To compile this driver as a module, choose M here; the module
814 will be called via_wdt.
816 Most people will say N.
819 tristate "W83627HF/W83627DHG Watchdog Timer"
822 This is the driver for the hardware watchdog on the W83627HF chipset
823 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
824 (and likely others). The driver also supports the W83627DHG chip.
825 This watchdog simply watches your kernel to make sure it doesn't
826 freeze, and if it does, it reboots your computer after a certain
829 To compile this driver as a module, choose M here: the
830 module will be called w83627hf_wdt.
832 Most people will say N.
835 tristate "W83697HF/W83697HG Watchdog Timer"
838 This is the driver for the hardware watchdog on the W83697HF/HG
839 chipset as used in Dedibox/VIA motherboards (and likely others).
840 This watchdog simply watches your kernel to make sure it doesn't
841 freeze, and if it does, it reboots your computer after a certain
844 To compile this driver as a module, choose M here: the
845 module will be called w83697hf_wdt.
847 Most people will say N.
850 tristate "W83697UG/W83697UF Watchdog Timer"
853 This is the driver for the hardware watchdog on the W83697UG/UF
854 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
855 This watchdog simply watches your kernel to make sure it doesn't
856 freeze, and if it does, it reboots your computer after a certain
859 To compile this driver as a module, choose M here: the
860 module will be called w83697ug_wdt.
862 Most people will say N.
865 tristate "W83877F (EMACS) Watchdog Timer"
868 This is the driver for the hardware watchdog on the W83877F chipset
869 as used in EMACS PC-104 motherboards (and likely others). This
870 watchdog simply watches your kernel to make sure it doesn't freeze,
871 and if it does, it reboots your computer after a certain amount of
874 To compile this driver as a module, choose M here: the
875 module will be called w83877f_wdt.
877 Most people will say N.
880 tristate "W83977F (PCM-5335) Watchdog Timer"
883 This is the driver for the hardware watchdog on the W83977F I/O chip
884 as used in AAEON's PCM-5335 SBC (and likely others). This
885 watchdog simply watches your kernel to make sure it doesn't freeze,
886 and if it does, it reboots your computer after a certain amount of
889 To compile this driver as a module, choose M here: the
890 module will be called w83977f_wdt.
893 tristate "ZF MachZ Watchdog"
896 If you are using a ZF Micro MachZ processor, say Y here, otherwise
897 N. This is the driver for the watchdog timer built-in on that
898 processor using ZF-Logic interface. This watchdog simply watches
899 your kernel to make sure it doesn't freeze, and if it does, it
900 reboots your computer after a certain amount of time.
902 To compile this driver as a module, choose M here: the
903 module will be called machzwd.
905 config SBC_EPX_C3_WATCHDOG
906 tristate "Winsystems SBC EPX-C3 watchdog"
909 This is the driver for the built-in watchdog timer on the EPX-C3
910 Single-board computer made by Winsystems, Inc.
912 *Note*: This hardware watchdog is not probeable and thus there
913 is no way to know if writing to its IO address will corrupt
914 your system or have any real effect. The only way to be sure
915 that this driver does what you want is to make sure you
916 are running it on an EPX-C3 from Winsystems with the watchdog
917 timer at IO address 0x1ee and 0x1ef. It will write to both those
918 IO ports. Basically, the assumption is made that if you compile
919 this driver into your kernel and/or load it as a module, that you
920 know what you are doing and that you are in fact running on an
923 To compile this driver as a module, choose M here: the
924 module will be called sbc_epx_c3.
930 config M54xx_WATCHDOG
931 tristate "MCF54xx watchdog support"
934 To compile this driver as a module, choose M here: the
935 module will be called m54xx_wdt.
937 # MicroBlaze Architecture
939 config XILINX_WATCHDOG
940 tristate "Xilinx Watchdog timer"
941 depends on MICROBLAZE
943 Watchdog driver for the xps_timebase_wdt ip core.
945 IMPORTANT: The xps_timebase_wdt parent must have the property
946 "clock-frequency" at device tree.
948 To compile this driver as a module, choose M here: the
949 module will be called of_xilinx_wdt.
954 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
957 Hardware driver for the built-in watchdog timer on the Atheros
958 AR71XX/AR724X/AR913X SoCs.
961 tristate "Broadcom BCM47xx Watchdog Timer"
964 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
967 tristate "IDT RC32434 SoC Watchdog Timer"
968 depends on MIKROTIK_RB532
970 Hardware driver for the IDT RC32434 SoC built-in
973 To compile this driver as a module, choose M here: the
974 module will be called rc32434_wdt.
977 tristate "Indy/I2 Hardware Watchdog"
978 depends on SGI_HAS_INDYDOG
980 Hardware driver for the Indy's/I2's watchdog. This is a
981 watchdog timer that will reboot the machine after a 60 second
982 timer expired and no process has written to /dev/watchdog during
986 tristate "Ingenic jz4740 SoC hardware watchdog"
987 depends on MACH_JZ4740
990 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
993 tristate "MTX-1 Hardware Watchdog"
996 Hardware driver for the MTX-1 boards. This is a watchdog timer that
997 will reboot the machine after a 100 seconds timer expired.
1000 tristate "PNX833x Hardware Watchdog"
1001 depends on SOC_PNX8335
1003 Hardware driver for the PNX833x's watchdog. This is a
1004 watchdog timer that will reboot the machine after a programmable
1005 timer has expired and no process has written to /dev/watchdog during
1009 tristate "Sibyte SoC hardware watchdog"
1012 Watchdog driver for the built in watchdog hardware in Sibyte
1013 SoC processors. There are apparently two watchdog timers
1014 on such processors; this driver supports only the first one,
1015 because currently Linux only supports exporting one watchdog
1018 To compile this driver as a loadable module, choose M here.
1019 The module will be called sb_wdog.
1022 tristate "TI AR7 Watchdog Timer"
1025 Hardware driver for the TI AR7 Watchdog Timer.
1028 tristate "Toshiba TXx9 Watchdog Timer"
1029 depends on CPU_TX39XX || CPU_TX49XX
1030 select WATCHDOG_CORE
1032 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1035 tristate "Cavium OCTEON SOC family Watchdog Timer"
1036 depends on CPU_CAVIUM_OCTEON
1038 select EXPORT_UASM if OCTEON_WDT = m
1040 Hardware driver for OCTEON's on chip watchdog timer.
1041 Enables the watchdog for all cores running Linux. It
1042 installs a NMI handler and pokes the watchdog based on an
1043 interrupt. On first expiration of the watchdog, the
1044 interrupt handler pokes it. The second expiration causes an
1045 NMI that prints a message. The third expiration causes a
1048 When userspace has /dev/watchdog open, no poking is done
1049 from the first interrupt, it is then only poked when the
1053 tristate "Broadcom BCM63xx hardware watchdog"
1056 Watchdog driver for the built in watchdog hardware in Broadcom
1059 To compile this driver as a loadable module, choose M here.
1060 The module will be called bcm63xx_wdt.
1063 tristate "Lantiq SoC watchdog"
1066 Hardware driver for the Lantiq SoC Watchdog Timer.
1068 # PARISC Architecture
1070 # POWERPC Architecture
1073 tristate "GE Watchdog Timer"
1076 Watchdog timer found in a number of GE single board computers.
1079 bool "MPC52xx Watchdog Timer"
1080 depends on PPC_MPC52xx
1082 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1085 tristate "MPC8xxx Platform Watchdog Timer"
1086 depends on PPC_8xx || PPC_83xx || PPC_86xx
1088 This driver is for a SoC level watchdog that exists on some
1089 Freescale PowerPC processors. So far this driver supports:
1094 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1097 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1101 tristate "PIKA FPGA Watchdog"
1105 This enables the watchdog in the PIKA FPGA. Currently used on
1109 tristate "PowerPC Book-E Watchdog Timer"
1110 depends on BOOKE || 4xx
1112 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1113 MPC85xx SOCs and the IBM PowerPC 440.
1115 Please see Documentation/watchdog/watchdog-api.txt for
1118 config BOOKE_WDT_DEFAULT_TIMEOUT
1119 int "PowerPC Book-E Watchdog Timer Default Timeout"
1120 depends on BOOKE_WDT
1121 default 38 if PPC_FSL_BOOK3E
1122 range 0 63 if PPC_FSL_BOOK3E
1123 default 3 if !PPC_FSL_BOOK3E
1124 range 0 3 if !PPC_FSL_BOOK3E
1126 Select the default watchdog timer period to be used by the PowerPC
1127 Book-E watchdog driver. A watchdog "event" occurs when the bit
1128 position represented by this number transitions from zero to one.
1130 For Freescale Book-E processors, this is a number between 0 and 63.
1131 For other Book-E processors, this is a number between 0 and 3.
1133 The value can be overridden by the wdt_period command-line parameter.
1135 # PPC64 Architecture
1137 config WATCHDOG_RTAS
1138 tristate "RTAS watchdog"
1141 This driver adds watchdog support for the RTAS watchdog.
1143 To compile this driver as a module, choose M here. The module
1144 will be called wdrtas.
1149 tristate "z/VM Watchdog Timer"
1152 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1153 provide a virtual watchdog timer to their guest that cause a
1154 user define Control Program command to be executed after a
1157 To compile this driver as a module, choose M here. The module
1158 will be called vmwatchdog.
1160 # SUPERH (sh + sh64) Architecture
1163 tristate "SuperH Watchdog"
1164 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1165 select WATCHDOG_CORE
1167 This driver adds watchdog support for the integrated watchdog in the
1168 SuperH processors. If you have one of these processors and wish
1169 to have watchdog support enabled, say Y, otherwise say N.
1171 As a side note, saying Y here will automatically boost HZ to 1000
1172 so that the timer has a chance to clear the overflow counter. On
1173 slower systems (such as the SH-2 and SH-3) this will likely yield
1174 some performance issues. As such, the WDT should be avoided here
1175 unless it is absolutely necessary.
1177 To compile this driver as a module, choose M here: the
1178 module will be called shwdt.
1180 # SPARC Architecture
1182 # SPARC64 Architecture
1184 config WATCHDOG_CP1XXX
1185 tristate "CP1XXX Hardware Watchdog support"
1186 depends on SPARC64 && PCI
1188 This is the driver for the hardware watchdog timers present on
1189 Sun Microsystems CompactPCI models CP1400 and CP1500.
1191 To compile this driver as a module, choose M here: the
1192 module will be called cpwatchdog.
1194 If you do not have a CompactPCI model CP1400 or CP1500, or
1195 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1196 you should say N to this option.
1199 tristate "RIO Hardware Watchdog support"
1200 depends on SPARC64 && PCI
1202 Say Y here to support the hardware watchdog capability on Sun RIO
1203 machines. The watchdog timeout period is normally one minute but
1204 can be changed with a boot-time parameter.
1206 # XTENSA Architecture
1211 tristate "Xen Watchdog support"
1214 Say Y here to support the hypervisor watchdog capability provided
1215 by Xen 4.0 and newer. The watchdog timeout period is normally one
1216 minute but can be changed with a boot-time parameter.
1219 tristate "UML watchdog"
1223 # ISA-based Watchdog Cards
1226 comment "ISA-based Watchdog Cards"
1230 tristate "Berkshire Products ISA-PC Watchdog"
1233 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1234 This card simply watches your kernel to make sure it doesn't freeze,
1235 and if it does, it reboots your computer after a certain amount of
1236 time. This driver is like the WDT501 driver but for different
1237 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1238 watchdog cards can be ordered from <http://www.berkprod.com/>.
1240 To compile this driver as a module, choose M here: the
1241 module will be called pcwd.
1243 Most people will say N.
1246 tristate "Mixcom Watchdog"
1249 This is a driver for the Mixcom hardware watchdog cards. This
1250 watchdog simply watches your kernel to make sure it doesn't freeze,
1251 and if it does, it reboots your computer after a certain amount of
1254 To compile this driver as a module, choose M here: the
1255 module will be called mixcomwd.
1257 Most people will say N.
1260 tristate "WDT Watchdog timer"
1263 If you have a WDT500P or WDT501P watchdog board, say Y here,
1264 otherwise N. It is not possible to probe for this board, which means
1265 that you have to inform the kernel about the IO port and IRQ that
1266 is needed (you can do this via the io and irq parameters)
1268 To compile this driver as a module, choose M here: the
1269 module will be called wdt.
1272 # PCI-based Watchdog Cards
1275 comment "PCI-based Watchdog Cards"
1278 config PCIPCWATCHDOG
1279 tristate "Berkshire Products PCI-PC Watchdog"
1282 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1283 This card simply watches your kernel to make sure it doesn't freeze,
1284 and if it does, it reboots your computer after a certain amount of
1285 time. The card can also monitor the internal temperature of the PC.
1286 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1288 To compile this driver as a module, choose M here: the
1289 module will be called pcwd_pci.
1291 Most people will say N.
1294 tristate "PCI-WDT500/501 Watchdog timer"
1297 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1299 If you have a PCI-WDT501 watchdog board then you can enable the
1300 temperature sensor by setting the type parameter to 501.
1302 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1303 can do this via the tachometer parameter. Only do this if you have a
1304 fan tachometer actually set up.
1306 To compile this driver as a module, choose M here: the
1307 module will be called wdt_pci.
1310 # USB-based Watchdog Cards
1313 comment "USB-based Watchdog Cards"
1316 config USBPCWATCHDOG
1317 tristate "Berkshire Products USB-PC Watchdog"
1320 This is the driver for the Berkshire Products USB-PC Watchdog card.
1321 This card simply watches your kernel to make sure it doesn't freeze,
1322 and if it does, it reboots your computer after a certain amount of
1323 time. The card can also monitor the internal temperature of the PC.
1324 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1326 To compile this driver as a module, choose M here: the
1327 module will be called pcwd_usb.
1329 Most people will say N.