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"
59 A software monitoring watchdog. This will fail to reboot your system
60 from some situations that the hardware watchdog will recover
61 from. Equally it's a lot cheaper to install.
63 To compile this driver as a module, choose M here: the
64 module will be called softdog.
66 config WM831X_WATCHDOG
67 tristate "WM831x watchdog"
71 Support for the watchdog in the WM831x AudioPlus PMICs. When
72 the watchdog triggers the system will be reset.
74 config WM8350_WATCHDOG
75 tristate "WM8350 watchdog"
78 Support for the watchdog in the WM8350 AudioPlus PMIC. When
79 the watchdog triggers the system will be reset.
85 config ARM_SP805_WATCHDOG
86 tristate "ARM SP805 Watchdog"
89 ARM Primecell SP805 Watchdog timer. This will reboot your system when
90 the timeout is reached.
92 config AT91RM9200_WATCHDOG
93 tristate "AT91RM9200 watchdog"
94 depends on ARCH_AT91RM9200
96 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
97 system when the timeout is reached.
99 config AT91SAM9X_WATCHDOG
100 tristate "AT91SAM9X / AT91CAP9 watchdog"
101 depends on ARCH_AT91 && !ARCH_AT91RM9200
103 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
104 reboot your system when the timeout is reached.
106 config 21285_WATCHDOG
107 tristate "DC21285 watchdog"
108 depends on FOOTBRIDGE
110 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
111 here if you wish to use this. Alternatively say M to compile the
112 driver as a module, which will be called wdt285.
114 This driver does not work on all machines. In particular, early CATS
115 boards have hardware problems that will cause the machine to simply
116 lock up if the watchdog fires.
118 "If in doubt, leave it out" - say N.
121 tristate "NetWinder WB83C977 watchdog"
122 depends on FOOTBRIDGE && ARCH_NETWINDER
124 Say Y here to include support for the WB977 watchdog included in
125 NetWinder machines. Alternatively say M to compile the driver as
126 a module, which will be called wdt977.
128 Not sure? It's safe to say N.
130 config IXP2000_WATCHDOG
131 tristate "IXP2000 Watchdog"
132 depends on ARCH_IXP2000
134 Say Y here if to include support for the watchdog timer
135 in the Intel IXP2000(2400, 2800, 2850) network processors.
136 This driver can be built as a module by choosing M. The module
137 will be called ixp2000_wdt.
139 Say N if you are unsure.
141 config IXP4XX_WATCHDOG
142 tristate "IXP4xx Watchdog"
143 depends on ARCH_IXP4XX
145 Say Y here if to include support for the watchdog timer
146 in the Intel IXP4xx network processors. This driver can
147 be built as a module by choosing M. The module will
148 be called ixp4xx_wdt.
150 Note: The internal IXP4xx watchdog does a soft CPU reset
151 which doesn't reset any peripherals. There are circumstances
152 where the watchdog will fail to reset the board correctly
153 (e.g., if the boot ROM is in an unreadable state).
155 Say N if you are unsure.
157 config KS8695_WATCHDOG
158 tristate "KS8695 watchdog"
159 depends on ARCH_KS8695
161 Watchdog timer embedded into KS8695 processor. This will reboot your
162 system when the timeout is reached.
164 config HAVE_S3C2410_WATCHDOG
167 This will include watchdog timer support for Samsung SoCs. If
168 you want to include watchdog support for any machine, kindly
169 select this in the respective mach-XXXX/Kconfig file.
171 config S3C2410_WATCHDOG
172 tristate "S3C2410 Watchdog"
173 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
176 Watchdog timer block in the Samsung SoCs. This will reboot
177 the system when the timer expires with the watchdog enabled.
179 The driver is limited by the speed of the system's PCLK
180 signal, so with reasonably fast systems (PCLK around 50-66MHz)
181 then watchdog intervals of over approximately 20seconds are
184 The driver can be built as a module by choosing M, and will
185 be called s3c2410_wdt
187 config SA1100_WATCHDOG
188 tristate "SA1100/PXA2xx watchdog"
189 depends on ARCH_SA1100 || ARCH_PXA
191 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
192 reboot your system when timeout is reached.
194 NOTE: once enabled, this timer cannot be disabled.
196 To compile this driver as a module, choose M here: the
197 module will be called sa1100_wdt.
200 tristate "Synopsys DesignWare watchdog"
201 depends on ARM && HAVE_CLK
203 Say Y here if to include support for the Synopsys DesignWare
204 watchdog timer found in many ARM chips.
205 To compile this driver as a module, choose M here: the
206 module will be called dw_wdt.
208 config MPCORE_WATCHDOG
209 tristate "MPcore watchdog"
210 depends on HAVE_ARM_TWD
212 Watchdog timer embedded into the MPcore system.
214 To compile this driver as a module, choose M here: the
215 module will be called mpcore_wdt.
217 config EP93XX_WATCHDOG
218 tristate "EP93xx Watchdog"
219 depends on ARCH_EP93XX
221 Say Y here if to include support for the watchdog timer
222 embedded in the Cirrus Logic EP93xx family of devices.
224 To compile this driver as a module, choose M here: the
225 module will be called ep93xx_wdt.
228 tristate "OMAP Watchdog"
229 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
231 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
232 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
234 config PNX4008_WATCHDOG
235 tristate "PNX4008 and LPC32XX Watchdog"
236 depends on ARCH_PNX4008 || ARCH_LPC32XX
238 Say Y here if to include support for the watchdog timer
239 in the PNX4008 or LPC32XX processor.
240 This driver can be built as a module by choosing M. The module
241 will be called pnx4008_wdt.
243 Say N if you are unsure.
246 tristate "IOP Watchdog"
248 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
250 Say Y here if to include support for the watchdog timer
251 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
252 be built as a module by choosing M. The module will
255 Note: The IOP13XX watchdog does an Internal Bus Reset which will
256 affect both cores and the peripherals of the IOP. The ATU-X
257 and/or ATUe configuration registers will remain intact, but if
258 operating as an Root Complex and/or Central Resource, the PCI-X
259 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
261 config DAVINCI_WATCHDOG
262 tristate "DaVinci watchdog"
263 depends on ARCH_DAVINCI
265 Say Y here if to include support for the watchdog timer
266 in the DaVinci DM644x/DM646x processors.
267 To compile this driver as a module, choose M here: the
268 module will be called davinci_wdt.
270 NOTE: once enabled, this timer cannot be disabled.
271 Say N if you are unsure.
273 config ORION_WATCHDOG
274 tristate "Orion watchdog"
275 depends on ARCH_ORION5X || ARCH_KIRKWOOD
277 Say Y here if to include support for the watchdog timer
278 in the Marvell Orion5x and Kirkwood ARM SoCs.
279 To compile this driver as a module, choose M here: the
280 module will be called orion_wdt.
282 config COH901327_WATCHDOG
283 bool "ST-Ericsson COH 901 327 watchdog"
285 default y if MACH_U300
287 Say Y here to include Watchdog timer support for the
288 watchdog embedded into the ST-Ericsson U300 series platforms.
289 This watchdog is used to reset the system and thus cannot be
290 compiled as a module.
292 config TWL4030_WATCHDOG
293 tristate "TWL4030 Watchdog"
294 depends on TWL4030_CORE
296 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
297 watchdog timer support for TWL4030 chips.
299 config STMP3XXX_WATCHDOG
300 tristate "Freescale STMP3XXX watchdog"
301 depends on ARCH_STMP3XXX
303 Say Y here if to include support for the watchdog timer
304 for the Sigmatel STMP37XX/378X SoC.
305 To compile this driver as a module, choose M here: the
306 module will be called stmp3xxx_wdt.
308 config NUC900_WATCHDOG
309 tristate "Nuvoton NUC900 watchdog"
310 depends on ARCH_W90X900
312 Say Y here if to include support for the watchdog timer
313 for the Nuvoton NUC900 series SoCs.
314 To compile this driver as a module, choose M here: the
315 module will be called nuc900_wdt.
318 tristate "Avionic Design Xanthos watchdog"
319 depends on ARCH_PXA_ADX
321 Say Y here if you want support for the watchdog timer on Avionic
322 Design Xanthos boards.
324 config TS72XX_WATCHDOG
325 tristate "TS-72XX SBC Watchdog"
326 depends on MACH_TS72XX
328 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
329 watchdog timer implemented in a external CPLD chip. Say Y here
330 if you want to support for the watchdog timer on TS-72XX boards.
332 To compile this driver as a module, choose M here: the
333 module will be called ts72xx_wdt.
335 config MAX63XX_WATCHDOG
336 tristate "Max63xx watchdog"
337 depends on ARM && HAS_IOMEM
339 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
342 tristate "IMX2+ Watchdog"
343 depends on IMX_HAVE_PLATFORM_IMX2_WDT
345 This is the driver for the hardware watchdog
346 on the Freescale IMX2 and later processors.
347 If you have one of these processors and wish to have
348 watchdog support enabled, say Y, otherwise say N.
350 To compile this driver as a module, choose M here: the
351 module will be called imx2_wdt.
355 config AT32AP700X_WDT
356 tristate "AT32AP700x watchdog"
357 depends on CPU_AT32AP700X
359 Watchdog timer embedded into AT32AP700x devices. This will reboot
360 your system when the timeout is reached.
362 # BLACKFIN Architecture
365 tristate "Blackfin On-Chip Watchdog Timer"
368 If you say yes here you will get support for the Blackfin On-Chip
369 Watchdog Timer. If you have one of these processors and wish to
370 have watchdog support enabled, say Y, otherwise say N.
372 To compile this driver as a module, choose M here: the
373 module will be called bfin_wdt.
381 # X86 (i386 + ia64 + x86_64) Architecture
384 tristate "Acquire SBC Watchdog Timer"
387 This is the driver for the hardware watchdog on Single Board
388 Computers produced by Acquire Inc (and others). This watchdog
389 simply watches your kernel to make sure it doesn't freeze, and if
390 it does, it reboots your computer after a certain amount of time.
392 To compile this driver as a module, choose M here: the
393 module will be called acquirewdt.
395 Most people will say N.
398 tristate "Advantech SBC Watchdog Timer"
401 If you are configuring a Linux kernel for the Advantech single-board
402 computer, say `Y' here to support its built-in watchdog timer
403 feature. More information can be found at
404 <http://www.advantech.com.tw/products/>
407 tristate "ALi M1535 PMU Watchdog Timer"
408 depends on X86 && PCI
410 This is the driver for the hardware watchdog on the ALi M1535 PMU.
412 To compile this driver as a module, choose M here: the
413 module will be called alim1535_wdt.
415 Most people will say N.
418 tristate "ALi M7101 PMU Computer Watchdog"
421 This is the driver for the hardware watchdog on the ALi M7101 PMU
422 as used in the x86 Cobalt servers and also found in some
423 SPARC Netra servers too.
425 To compile this driver as a module, choose M here: the
426 module will be called alim7101_wdt.
428 Most people will say N.
431 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
432 depends on X86 && EXPERIMENTAL
434 This is the driver for the hardware watchdog on the Fintek
435 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
437 You can compile this driver directly into the kernel, or use
438 it as a module. The module will be called f71808e_wdt.
441 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
442 depends on X86 && PCI
444 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
445 (Total Cost of Ownership) timer is a watchdog timer that will reboot
446 the machine after its expiration. The expiration time can be
447 configured with the "heartbeat" parameter.
449 To compile this driver as a module, choose M here: the
450 module will be called sp5100_tco.
453 tristate "AMD Geode CS5535/CS5536 Watchdog"
454 depends on CS5535_MFGPT
456 This driver enables a watchdog capability built into the
457 CS5535/CS5536 companion chips for the AMD Geode GX and LX
458 processors. This watchdog watches your kernel to make sure
459 it doesn't freeze, and if it does, it reboots your computer after
460 a certain amount of time.
462 You can compile this driver directly into the kernel, or use
463 it as a module. The module will be called geodewdt.
466 tristate "AMD Elan SC520 processor Watchdog"
469 This is the driver for the hardware watchdog built in to the
470 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
471 This watchdog simply watches your kernel to make sure it doesn't
472 freeze, and if it does, it reboots your computer after a certain
475 You can compile this driver directly into the kernel, or use
476 it as a module. The module will be called sc520_wdt.
478 config SBC_FITPC2_WATCHDOG
479 tristate "Compulab SBC-FITPC2 watchdog"
482 This is the driver for the built-in watchdog timer on the fit-PC2,
483 fit-PC2i, CM-iAM single-board computers made by Compulab.
485 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
486 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
488 Entering BIOS setup temporary disables watchdog operation regardless to current state,
489 so system will not be restarted while user in BIOS setup.
491 Once watchdog was enabled the system will be restarted every
492 "Watchdog Timer Value" period, so to prevent it user can restart or
493 disable the watchdog.
495 To compile this driver as a module, choose M here: the
496 module will be called sbc_fitpc2_wdt.
498 Most people will say N.
501 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
504 Enable support for the watchdog timer on the Eurotech CPU-1220 and
505 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
506 information are at <http://www.eurotech.it/>.
509 tristate "IB700 SBC Watchdog Timer"
512 This is the driver for the hardware watchdog on the IB700 Single
513 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
514 simply watches your kernel to make sure it doesn't freeze, and if
515 it does, it reboots your computer after a certain amount of time.
517 This driver is like the WDT501 driver but for slightly different hardware.
519 To compile this driver as a module, choose M here: the
520 module will be called ib700wdt.
522 Most people will say N.
525 tristate "IBM Automatic Server Restart"
528 This is the driver for the IBM Automatic Server Restart watchdog
529 timer built-in into some eServer xSeries machines.
531 To compile this driver as a module, choose M here: the
532 module will be called ibmasr.
535 tristate "ICP Single Board Computer Watchdog Timer"
538 This is a driver for the hardware watchdog on the ICP Single
539 Board Computer. This driver is working on (at least) the following
540 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
542 To compile this driver as a module, choose M here: the
543 module will be called wafer5823wdt.
546 tristate "Intel 6300ESB Timer/Watchdog"
547 depends on X86 && PCI
549 Hardware driver for the watchdog timer built into the Intel
550 6300ESB controller hub.
552 To compile this driver as a module, choose M here: the
553 module will be called i6300esb.
555 config INTEL_SCU_WATCHDOG
556 bool "Intel SCU Watchdog for Mobile Platforms"
559 Hardware driver for the watchdog time built into the Intel SCU
560 for Intel Mobile Platforms.
562 To compile this driver as a module, choose M here.
565 tristate "Intel TCO Timer/Watchdog"
566 depends on (X86 || IA64) && PCI
568 Hardware driver for the intel TCO timer based watchdog devices.
569 These drivers are included in the Intel 82801 I/O Controller
570 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
573 The TCO (Total Cost of Ownership) timer is a watchdog timer
574 that will reboot the machine after its second expiration. The
575 expiration time can be configured with the "heartbeat" parameter.
577 On some motherboards the driver may fail to reset the chipset's
578 NO_REBOOT flag which prevents the watchdog from rebooting the
579 machine. If this is the case you will get a kernel message like
580 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
582 To compile this driver as a module, choose M here: the
583 module will be called iTCO_wdt.
585 config ITCO_VENDOR_SUPPORT
586 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
589 Add vendor specific support to the intel TCO timer based watchdog
590 devices. At this moment we only have additional support for some
591 SuperMicro Inc. motherboards.
594 tristate "IT8712F (Smart Guardian) Watchdog Timer"
597 This is the driver for the built-in watchdog timer on the IT8712F
598 Super I/0 chipset used on many motherboards.
600 If the driver does not work, then make sure that the game port in
603 To compile this driver as a module, choose M here: the
604 module will be called it8712f_wdt.
607 tristate "IT87 Watchdog Timer"
608 depends on X86 && EXPERIMENTAL
610 This is the driver for the hardware watchdog on the ITE IT8702,
611 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
612 This watchdog simply watches your kernel to make sure it doesn't
613 freeze, and if it does, it reboots your computer after a certain
616 To compile this driver as a module, choose M here: the module will
620 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
621 depends on X86 && PCI
623 A software monitoring watchdog and NMI sourcing driver. This driver
624 will detect lockups and provide a stack trace. This is a driver that
625 will only load on an HP ProLiant system with a minimum of iLO2 support.
626 To compile this driver as a module, choose M here: the module will be
629 config HPWDT_NMI_DECODING
630 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
631 depends on HP_WATCHDOG
634 When an NMI occurs this feature will make the necessary BIOS calls to
635 log the cause of the NMI.
638 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
641 This is a driver for National Semiconductor PC87307/PC97307 hardware
642 watchdog cards as found on the SC1200. This watchdog is mainly used
643 for power management purposes and can be used to power down the device
644 during inactivity periods (includes interrupt activity monitoring).
646 To compile this driver as a module, choose M here: the
647 module will be called sc1200wdt.
649 Most people will say N.
652 tristate "National Semiconductor SCx200 Watchdog"
653 depends on SCx200 && PCI
655 Enable the built-in watchdog timer support on the National
656 Semiconductor SCx200 processors.
658 If compiled as a module, it will be called scx200_wdt.
661 tristate "NS PC87413 watchdog"
664 This is the driver for the hardware watchdog on the PC87413 chipset
665 This watchdog simply watches your kernel to make sure it doesn't
666 freeze, and if it does, it reboots your computer after a certain
669 To compile this driver as a module, choose M here: the
670 module will be called pc87413_wdt.
672 Most people will say N.
675 tristate "nVidia TCO Timer/Watchdog"
676 depends on X86 && PCI
678 Hardware driver for the TCO timer built into the nVidia Hub family
679 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
680 watchdog timer that will reboot the machine after its second
681 expiration. The expiration time can be configured with the
682 "heartbeat" parameter.
684 On some motherboards the driver may fail to reset the chipset's
685 NO_REBOOT flag which prevents the watchdog from rebooting the
686 machine. If this is the case you will get a kernel message like
687 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
689 To compile this driver as a module, choose M here: the
690 module will be called nv_tco.
693 tristate "RDC R-321x SoC watchdog"
694 depends on X86_RDC321X
696 This is the driver for the built in hardware watchdog
697 in the RDC R-321x SoC.
699 To compile this driver as a module, choose M here: the
700 module will be called rdc321x_wdt.
703 tristate "SBC-60XX Watchdog Timer"
706 This driver can be used with the watchdog timer found on some
707 single board computers, namely the 6010 PII based computer.
708 It may well work with other cards. It reads port 0x443 to enable
709 and re-set the watchdog timer, and reads port 0x45 to disable
710 the watchdog. If you have a card that behave in similar ways,
711 you can probably make this driver work with your card as well.
713 You can compile this driver directly into the kernel, or use
714 it as a module. The module will be called sbc60xxwdt.
717 tristate "SBC8360 Watchdog Timer"
721 This is the driver for the hardware watchdog on the SBC8360 Single
722 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
724 To compile this driver as a module, choose M here: the
725 module will be called sbc8360.
727 Most people will say N.
730 tristate "SBC Nano 7240 Watchdog Timer"
731 depends on X86_32 && !UML
733 This is the driver for the hardware watchdog found on the IEI
734 single board computers EPIC Nano 7240 (and likely others). This
735 watchdog simply watches your kernel to make sure it doesn't freeze,
736 and if it does, it reboots your computer after a certain amount of
739 To compile this driver as a module, choose M here: the
740 module will be called sbc7240_wdt.
743 tristate "SMA CPU5 Watchdog"
747 To compile this driver as a module, choose M here: the
748 module will be called cpu5wdt.
750 config SMSC_SCH311X_WDT
751 tristate "SMSC SCH311X Watchdog Timer"
754 This is the driver for the hardware watchdog timer on the
755 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
756 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
759 To compile this driver as a module, choose M here: the
760 module will be called sch311x_wdt.
762 config SMSC37B787_WDT
763 tristate "Winbond SMsC37B787 Watchdog Timer"
766 This is the driver for the hardware watchdog component on the
767 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
768 from Vision Systems and maybe others.
770 This watchdog simply watches your kernel to make sure it doesn't
771 freeze, and if it does, it reboots your computer after a certain
774 Usually a userspace daemon will notify the kernel WDT driver that
775 userspace is still alive, at regular intervals.
777 To compile this driver as a module, choose M here: the
778 module will be called smsc37b787_wdt.
780 Most people will say N.
783 tristate "W83627HF/W83627DHG Watchdog Timer"
786 This is the driver for the hardware watchdog on the W83627HF chipset
787 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
788 (and likely others). The driver also supports the W83627DHG chip.
789 This watchdog simply watches your kernel to make sure it doesn't
790 freeze, and if it does, it reboots your computer after a certain
793 To compile this driver as a module, choose M here: the
794 module will be called w83627hf_wdt.
796 Most people will say N.
799 tristate "W83697HF/W83697HG Watchdog Timer"
802 This is the driver for the hardware watchdog on the W83697HF/HG
803 chipset as used in Dedibox/VIA motherboards (and likely others).
804 This watchdog simply watches your kernel to make sure it doesn't
805 freeze, and if it does, it reboots your computer after a certain
808 To compile this driver as a module, choose M here: the
809 module will be called w83697hf_wdt.
811 Most people will say N.
814 tristate "W83697UG/W83697UF Watchdog Timer"
817 This is the driver for the hardware watchdog on the W83697UG/UF
818 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
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
824 module will be called w83697ug_wdt.
826 Most people will say N.
829 tristate "W83877F (EMACS) Watchdog Timer"
832 This is the driver for the hardware watchdog on the W83877F chipset
833 as used in EMACS PC-104 motherboards (and likely others). This
834 watchdog simply watches your kernel to make sure it doesn't freeze,
835 and if it does, it reboots your computer after a certain amount of
838 To compile this driver as a module, choose M here: the
839 module will be called w83877f_wdt.
841 Most people will say N.
844 tristate "W83977F (PCM-5335) Watchdog Timer"
847 This is the driver for the hardware watchdog on the W83977F I/O chip
848 as used in AAEON's PCM-5335 SBC (and likely others). This
849 watchdog simply watches your kernel to make sure it doesn't freeze,
850 and if it does, it reboots your computer after a certain amount of
853 To compile this driver as a module, choose M here: the
854 module will be called w83977f_wdt.
857 tristate "ZF MachZ Watchdog"
860 If you are using a ZF Micro MachZ processor, say Y here, otherwise
861 N. This is the driver for the watchdog timer built-in on that
862 processor using ZF-Logic interface. This watchdog simply watches
863 your kernel to make sure it doesn't freeze, and if it does, it
864 reboots your computer after a certain amount of time.
866 To compile this driver as a module, choose M here: the
867 module will be called machzwd.
869 config SBC_EPX_C3_WATCHDOG
870 tristate "Winsystems SBC EPX-C3 watchdog"
873 This is the driver for the built-in watchdog timer on the EPX-C3
874 Single-board computer made by Winsystems, Inc.
876 *Note*: This hardware watchdog is not probeable and thus there
877 is no way to know if writing to its IO address will corrupt
878 your system or have any real effect. The only way to be sure
879 that this driver does what you want is to make sure you
880 are running it on an EPX-C3 from Winsystems with the watchdog
881 timer at IO address 0x1ee and 0x1ef. It will write to both those
882 IO ports. Basically, the assumption is made that if you compile
883 this driver into your kernel and/or load it as a module, that you
884 know what you are doing and that you are in fact running on an
887 To compile this driver as a module, choose M here: the
888 module will be called sbc_epx_c3.
894 config M54xx_WATCHDOG
895 tristate "MCF54xx watchdog support"
898 To compile this driver as a module, choose M here: the
899 module will be called m54xx_wdt.
901 # MicroBlaze Architecture
903 config XILINX_WATCHDOG
904 tristate "Xilinx Watchdog timer"
905 depends on MICROBLAZE
907 Watchdog driver for the xps_timebase_wdt ip core.
909 IMPORTANT: The xps_timebase_wdt parent must have the property
910 "clock-frequency" at device tree.
912 To compile this driver as a module, choose M here: the
913 module will be called of_xilinx_wdt.
918 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
921 Hardware driver for the built-in watchdog timer on the Atheros
922 AR71XX/AR724X/AR913X SoCs.
925 tristate "Broadcom BCM47xx Watchdog Timer"
928 Hardware driver for the Broadcom BCM47xx Watchog Timer.
931 tristate "IDT RC32434 SoC Watchdog Timer"
932 depends on MIKROTIK_RB532
934 Hardware driver for the IDT RC32434 SoC built-in
937 To compile this driver as a module, choose M here: the
938 module will be called rc32434_wdt.
941 tristate "Indy/I2 Hardware Watchdog"
942 depends on SGI_HAS_INDYDOG
944 Hardware driver for the Indy's/I2's watchdog. This is a
945 watchdog timer that will reboot the machine after a 60 second
946 timer expired and no process has written to /dev/watchdog during
950 tristate "Ingenic jz4740 SoC hardware watchdog"
951 depends on MACH_JZ4740
953 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
956 tristate "MTX-1 Hardware Watchdog"
959 Hardware driver for the MTX-1 boards. This is a watchdog timer that
960 will reboot the machine after a 100 seconds timer expired.
963 tristate "PNX833x Hardware Watchdog"
964 depends on SOC_PNX8335
966 Hardware driver for the PNX833x's watchdog. This is a
967 watchdog timer that will reboot the machine after a programmable
968 timer has expired and no process has written to /dev/watchdog during
972 tristate "Sibyte SoC hardware watchdog"
975 Watchdog driver for the built in watchdog hardware in Sibyte
976 SoC processors. There are apparently two watchdog timers
977 on such processors; this driver supports only the first one,
978 because currently Linux only supports exporting one watchdog
981 To compile this driver as a loadable module, choose M here.
982 The module will be called sb_wdog.
985 tristate "TI AR7 Watchdog Timer"
988 Hardware driver for the TI AR7 Watchdog Timer.
991 tristate "Toshiba TXx9 Watchdog Timer"
992 depends on CPU_TX39XX || CPU_TX49XX
994 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
997 tristate "Cavium OCTEON SOC family Watchdog Timer"
998 depends on CPU_CAVIUM_OCTEON
1000 select EXPORT_UASM if OCTEON_WDT = m
1002 Hardware driver for OCTEON's on chip watchdog timer.
1003 Enables the watchdog for all cores running Linux. It
1004 installs a NMI handler and pokes the watchdog based on an
1005 interrupt. On first expiration of the watchdog, the
1006 interrupt handler pokes it. The second expiration causes an
1007 NMI that prints a message. The third expiration causes a
1010 When userspace has /dev/watchdog open, no poking is done
1011 from the first interrupt, it is then only poked when the
1015 tristate "Broadcom BCM63xx hardware watchdog"
1018 Watchdog driver for the built in watchdog hardware in Broadcom
1021 To compile this driver as a loadable module, choose M here.
1022 The module will be called bcm63xx_wdt.
1025 tristate "Lantiq SoC watchdog"
1028 Hardware driver for the Lantiq SoC Watchdog Timer.
1030 # PARISC Architecture
1032 # POWERPC Architecture
1035 tristate "GE Watchdog Timer"
1036 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
1038 Watchdog timer found in a number of GE single board computers.
1041 bool "MPC52xx Watchdog Timer"
1042 depends on PPC_MPC52xx
1044 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1047 tristate "MPC8xxx Platform Watchdog Timer"
1048 depends on PPC_8xx || PPC_83xx || PPC_86xx
1050 This driver is for a SoC level watchdog that exists on some
1051 Freescale PowerPC processors. So far this driver supports:
1056 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1059 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1063 tristate "PIKA FPGA Watchdog"
1067 This enables the watchdog in the PIKA FPGA. Currently used on
1071 tristate "PowerPC Book-E Watchdog Timer"
1072 depends on BOOKE || 4xx
1074 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1075 MPC85xx SOCs and the IBM PowerPC 440.
1077 Please see Documentation/watchdog/watchdog-api.txt for
1080 config BOOKE_WDT_DEFAULT_TIMEOUT
1081 int "PowerPC Book-E Watchdog Timer Default Timeout"
1082 depends on BOOKE_WDT
1083 default 38 if FSL_BOOKE
1084 range 0 63 if FSL_BOOKE
1085 default 3 if !FSL_BOOKE
1086 range 0 3 if !FSL_BOOKE
1088 Select the default watchdog timer period to be used by the PowerPC
1089 Book-E watchdog driver. A watchdog "event" occurs when the bit
1090 position represented by this number transitions from zero to one.
1092 For Freescale Book-E processors, this is a number between 0 and 63.
1093 For other Book-E processors, this is a number between 0 and 3.
1095 The value can be overidden by the wdt_period command-line parameter.
1097 # PPC64 Architecture
1099 config WATCHDOG_RTAS
1100 tristate "RTAS watchdog"
1103 This driver adds watchdog support for the RTAS watchdog.
1105 To compile this driver as a module, choose M here. The module
1106 will be called wdrtas.
1111 tristate "z/VM Watchdog Timer"
1114 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1115 provide a virtual watchdog timer to their guest that cause a
1116 user define Control Program command to be executed after a
1119 To compile this driver as a module, choose M here. The module
1120 will be called vmwatchdog.
1122 # SUPERH (sh + sh64) Architecture
1125 tristate "SuperH Watchdog"
1126 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1128 This driver adds watchdog support for the integrated watchdog in the
1129 SuperH processors. If you have one of these processors and wish
1130 to have watchdog support enabled, say Y, otherwise say N.
1132 As a side note, saying Y here will automatically boost HZ to 1000
1133 so that the timer has a chance to clear the overflow counter. On
1134 slower systems (such as the SH-2 and SH-3) this will likely yield
1135 some performance issues. As such, the WDT should be avoided here
1136 unless it is absolutely necessary.
1138 To compile this driver as a module, choose M here: the
1139 module will be called shwdt.
1141 # SPARC Architecture
1143 # SPARC64 Architecture
1145 config WATCHDOG_CP1XXX
1146 tristate "CP1XXX Hardware Watchdog support"
1147 depends on SPARC64 && PCI
1149 This is the driver for the hardware watchdog timers present on
1150 Sun Microsystems CompactPCI models CP1400 and CP1500.
1152 To compile this driver as a module, choose M here: the
1153 module will be called cpwatchdog.
1155 If you do not have a CompactPCI model CP1400 or CP1500, or
1156 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1157 you should say N to this option.
1160 tristate "RIO Hardware Watchdog support"
1161 depends on SPARC64 && PCI
1163 Say Y here to support the hardware watchdog capability on Sun RIO
1164 machines. The watchdog timeout period is normally one minute but
1165 can be changed with a boot-time parameter.
1167 # XTENSA Architecture
1172 tristate "Xen Watchdog support"
1175 Say Y here to support the hypervisor watchdog capability provided
1176 by Xen 4.0 and newer. The watchdog timeout period is normally one
1177 minute but can be changed with a boot-time parameter.
1180 tristate "UML watchdog"
1184 # ISA-based Watchdog Cards
1187 comment "ISA-based Watchdog Cards"
1191 tristate "Berkshire Products ISA-PC Watchdog"
1194 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1195 This card simply watches your kernel to make sure it doesn't freeze,
1196 and if it does, it reboots your computer after a certain amount of
1197 time. This driver is like the WDT501 driver but for different
1198 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1199 watchdog cards can be ordered from <http://www.berkprod.com/>.
1201 To compile this driver as a module, choose M here: the
1202 module will be called pcwd.
1204 Most people will say N.
1207 tristate "Mixcom Watchdog"
1210 This is a driver for the Mixcom hardware watchdog cards. This
1211 watchdog simply watches your kernel to make sure it doesn't freeze,
1212 and if it does, it reboots your computer after a certain amount of
1215 To compile this driver as a module, choose M here: the
1216 module will be called mixcomwd.
1218 Most people will say N.
1221 tristate "WDT Watchdog timer"
1224 If you have a WDT500P or WDT501P watchdog board, say Y here,
1225 otherwise N. It is not possible to probe for this board, which means
1226 that you have to inform the kernel about the IO port and IRQ that
1227 is needed (you can do this via the io and irq parameters)
1229 To compile this driver as a module, choose M here: the
1230 module will be called wdt.
1233 # PCI-based Watchdog Cards
1236 comment "PCI-based Watchdog Cards"
1239 config PCIPCWATCHDOG
1240 tristate "Berkshire Products PCI-PC Watchdog"
1243 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1244 This card simply watches your kernel to make sure it doesn't freeze,
1245 and if it does, it reboots your computer after a certain amount of
1246 time. The card can also monitor the internal temperature of the PC.
1247 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1249 To compile this driver as a module, choose M here: the
1250 module will be called pcwd_pci.
1252 Most people will say N.
1255 tristate "PCI-WDT500/501 Watchdog timer"
1258 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1260 If you have a PCI-WDT501 watchdog board then you can enable the
1261 temperature sensor by setting the type parameter to 501.
1263 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1264 can do this via the tachometer parameter. Only do this if you have a
1265 fan tachometer actually set up.
1267 To compile this driver as a module, choose M here: the
1268 module will be called wdt_pci.
1271 # USB-based Watchdog Cards
1274 comment "USB-based Watchdog Cards"
1277 config USBPCWATCHDOG
1278 tristate "Berkshire Products USB-PC Watchdog"
1281 This is the driver for the Berkshire Products USB-PC Watchdog card.
1282 This card simply watches your kernel to make sure it doesn't freeze,
1283 and if it does, it reboots your computer after a certain amount of
1284 time. The card can also monitor the internal temperature of the PC.
1285 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1287 To compile this driver as a module, choose M here: the
1288 module will be called pcwd_usb.
1290 Most people will say N.