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.
317 config TS72XX_WATCHDOG
318 tristate "TS-72XX SBC Watchdog"
319 depends on MACH_TS72XX
321 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
322 watchdog timer implemented in a external CPLD chip. Say Y here
323 if you want to support for the watchdog timer on TS-72XX boards.
325 To compile this driver as a module, choose M here: the
326 module will be called ts72xx_wdt.
328 config MAX63XX_WATCHDOG
329 tristate "Max63xx watchdog"
330 depends on ARM && HAS_IOMEM
332 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
335 tristate "IMX2+ Watchdog"
336 depends on IMX_HAVE_PLATFORM_IMX2_WDT
338 This is the driver for the hardware watchdog
339 on the Freescale IMX2 and later processors.
340 If you have one of these processors and wish to have
341 watchdog support enabled, say Y, otherwise say N.
343 To compile this driver as a module, choose M here: the
344 module will be called imx2_wdt.
348 config AT32AP700X_WDT
349 tristate "AT32AP700x watchdog"
350 depends on CPU_AT32AP700X
352 Watchdog timer embedded into AT32AP700x devices. This will reboot
353 your system when the timeout is reached.
355 # BLACKFIN Architecture
358 tristate "Blackfin On-Chip Watchdog Timer"
361 If you say yes here you will get support for the Blackfin On-Chip
362 Watchdog Timer. If you have one of these processors and wish to
363 have watchdog support enabled, say Y, otherwise say N.
365 To compile this driver as a module, choose M here: the
366 module will be called bfin_wdt.
374 # X86 (i386 + ia64 + x86_64) Architecture
377 tristate "Acquire SBC Watchdog Timer"
380 This is the driver for the hardware watchdog on Single Board
381 Computers produced by Acquire Inc (and others). This watchdog
382 simply watches your kernel to make sure it doesn't freeze, and if
383 it does, it reboots your computer after a certain amount of time.
385 To compile this driver as a module, choose M here: the
386 module will be called acquirewdt.
388 Most people will say N.
391 tristate "Advantech SBC Watchdog Timer"
394 If you are configuring a Linux kernel for the Advantech single-board
395 computer, say `Y' here to support its built-in watchdog timer
396 feature. More information can be found at
397 <http://www.advantech.com.tw/products/>
400 tristate "ALi M1535 PMU Watchdog Timer"
401 depends on X86 && PCI
403 This is the driver for the hardware watchdog on the ALi M1535 PMU.
405 To compile this driver as a module, choose M here: the
406 module will be called alim1535_wdt.
408 Most people will say N.
411 tristate "ALi M7101 PMU Computer Watchdog"
414 This is the driver for the hardware watchdog on the ALi M7101 PMU
415 as used in the x86 Cobalt servers and also found in some
416 SPARC Netra servers too.
418 To compile this driver as a module, choose M here: the
419 module will be called alim7101_wdt.
421 Most people will say N.
424 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
425 depends on X86 && EXPERIMENTAL
427 This is the driver for the hardware watchdog on the Fintek
428 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
430 You can compile this driver directly into the kernel, or use
431 it as a module. The module will be called f71808e_wdt.
434 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
435 depends on X86 && PCI
437 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
438 (Total Cost of Ownership) timer is a watchdog timer that will reboot
439 the machine after its expiration. The expiration time can be
440 configured with the "heartbeat" parameter.
442 To compile this driver as a module, choose M here: the
443 module will be called sp5100_tco.
446 tristate "AMD Geode CS5535/CS5536 Watchdog"
447 depends on CS5535_MFGPT
449 This driver enables a watchdog capability built into the
450 CS5535/CS5536 companion chips for the AMD Geode GX and LX
451 processors. This watchdog watches your kernel to make sure
452 it doesn't freeze, and if it does, it reboots your computer after
453 a certain amount of time.
455 You can compile this driver directly into the kernel, or use
456 it as a module. The module will be called geodewdt.
459 tristate "AMD Elan SC520 processor Watchdog"
462 This is the driver for the hardware watchdog built in to the
463 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
464 This watchdog simply watches your kernel to make sure it doesn't
465 freeze, and if it does, it reboots your computer after a certain
468 You can compile this driver directly into the kernel, or use
469 it as a module. The module will be called sc520_wdt.
471 config SBC_FITPC2_WATCHDOG
472 tristate "Compulab SBC-FITPC2 watchdog"
475 This is the driver for the built-in watchdog timer on the fit-PC2,
476 fit-PC2i, CM-iAM single-board computers made by Compulab.
478 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
479 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
481 Entering BIOS setup temporary disables watchdog operation regardless to current state,
482 so system will not be restarted while user in BIOS setup.
484 Once watchdog was enabled the system will be restarted every
485 "Watchdog Timer Value" period, so to prevent it user can restart or
486 disable the watchdog.
488 To compile this driver as a module, choose M here: the
489 module will be called sbc_fitpc2_wdt.
491 Most people will say N.
494 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
497 Enable support for the watchdog timer on the Eurotech CPU-1220 and
498 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
499 information are at <http://www.eurotech.it/>.
502 tristate "IB700 SBC Watchdog Timer"
505 This is the driver for the hardware watchdog on the IB700 Single
506 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
507 simply watches your kernel to make sure it doesn't freeze, and if
508 it does, it reboots your computer after a certain amount of time.
510 This driver is like the WDT501 driver but for slightly different hardware.
512 To compile this driver as a module, choose M here: the
513 module will be called ib700wdt.
515 Most people will say N.
518 tristate "IBM Automatic Server Restart"
521 This is the driver for the IBM Automatic Server Restart watchdog
522 timer built-in into some eServer xSeries machines.
524 To compile this driver as a module, choose M here: the
525 module will be called ibmasr.
528 tristate "ICP Single Board Computer Watchdog Timer"
531 This is a driver for the hardware watchdog on the ICP Single
532 Board Computer. This driver is working on (at least) the following
533 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
535 To compile this driver as a module, choose M here: the
536 module will be called wafer5823wdt.
539 tristate "Intel 6300ESB Timer/Watchdog"
540 depends on X86 && PCI
542 Hardware driver for the watchdog timer built into the Intel
543 6300ESB controller hub.
545 To compile this driver as a module, choose M here: the
546 module will be called i6300esb.
548 config INTEL_SCU_WATCHDOG
549 bool "Intel SCU Watchdog for Mobile Platforms"
552 Hardware driver for the watchdog time built into the Intel SCU
553 for Intel Mobile Platforms.
555 To compile this driver as a module, choose M here.
558 tristate "Intel TCO Timer/Watchdog"
559 depends on (X86 || IA64) && PCI
561 Hardware driver for the intel TCO timer based watchdog devices.
562 These drivers are included in the Intel 82801 I/O Controller
563 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
566 The TCO (Total Cost of Ownership) timer is a watchdog timer
567 that will reboot the machine after its second expiration. The
568 expiration time can be configured with the "heartbeat" parameter.
570 On some motherboards the driver may fail to reset the chipset's
571 NO_REBOOT flag which prevents the watchdog from rebooting the
572 machine. If this is the case you will get a kernel message like
573 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
575 To compile this driver as a module, choose M here: the
576 module will be called iTCO_wdt.
578 config ITCO_VENDOR_SUPPORT
579 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
582 Add vendor specific support to the intel TCO timer based watchdog
583 devices. At this moment we only have additional support for some
584 SuperMicro Inc. motherboards.
587 tristate "IT8712F (Smart Guardian) Watchdog Timer"
590 This is the driver for the built-in watchdog timer on the IT8712F
591 Super I/0 chipset used on many motherboards.
593 If the driver does not work, then make sure that the game port in
596 To compile this driver as a module, choose M here: the
597 module will be called it8712f_wdt.
600 tristate "IT87 Watchdog Timer"
601 depends on X86 && EXPERIMENTAL
603 This is the driver for the hardware watchdog on the ITE IT8702,
604 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
605 This watchdog simply watches your kernel to make sure it doesn't
606 freeze, and if it does, it reboots your computer after a certain
609 To compile this driver as a module, choose M here: the module will
613 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
614 depends on X86 && PCI
616 A software monitoring watchdog and NMI sourcing driver. This driver
617 will detect lockups and provide a stack trace. This is a driver that
618 will only load on an HP ProLiant system with a minimum of iLO2 support.
619 To compile this driver as a module, choose M here: the module will be
622 config HPWDT_NMI_DECODING
623 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
624 depends on HP_WATCHDOG
627 When an NMI occurs this feature will make the necessary BIOS calls to
628 log the cause of the NMI.
631 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
634 This is a driver for National Semiconductor PC87307/PC97307 hardware
635 watchdog cards as found on the SC1200. This watchdog is mainly used
636 for power management purposes and can be used to power down the device
637 during inactivity periods (includes interrupt activity monitoring).
639 To compile this driver as a module, choose M here: the
640 module will be called sc1200wdt.
642 Most people will say N.
645 tristate "National Semiconductor SCx200 Watchdog"
646 depends on SCx200 && PCI
648 Enable the built-in watchdog timer support on the National
649 Semiconductor SCx200 processors.
651 If compiled as a module, it will be called scx200_wdt.
654 tristate "NS PC87413 watchdog"
657 This is the driver for the hardware watchdog on the PC87413 chipset
658 This watchdog simply watches your kernel to make sure it doesn't
659 freeze, and if it does, it reboots your computer after a certain
662 To compile this driver as a module, choose M here: the
663 module will be called pc87413_wdt.
665 Most people will say N.
668 tristate "nVidia TCO Timer/Watchdog"
669 depends on X86 && PCI
671 Hardware driver for the TCO timer built into the nVidia Hub family
672 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
673 watchdog timer that will reboot the machine after its second
674 expiration. The expiration time can be configured with the
675 "heartbeat" parameter.
677 On some motherboards the driver may fail to reset the chipset's
678 NO_REBOOT flag which prevents the watchdog from rebooting the
679 machine. If this is the case you will get a kernel message like
680 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
682 To compile this driver as a module, choose M here: the
683 module will be called nv_tco.
686 tristate "RDC R-321x SoC watchdog"
687 depends on X86_RDC321X
689 This is the driver for the built in hardware watchdog
690 in the RDC R-321x SoC.
692 To compile this driver as a module, choose M here: the
693 module will be called rdc321x_wdt.
696 tristate "SBC-60XX Watchdog Timer"
699 This driver can be used with the watchdog timer found on some
700 single board computers, namely the 6010 PII based computer.
701 It may well work with other cards. It reads port 0x443 to enable
702 and re-set the watchdog timer, and reads port 0x45 to disable
703 the watchdog. If you have a card that behave in similar ways,
704 you can probably make this driver work with your card as well.
706 You can compile this driver directly into the kernel, or use
707 it as a module. The module will be called sbc60xxwdt.
710 tristate "SBC8360 Watchdog Timer"
714 This is the driver for the hardware watchdog on the SBC8360 Single
715 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
717 To compile this driver as a module, choose M here: the
718 module will be called sbc8360.
720 Most people will say N.
723 tristate "SBC Nano 7240 Watchdog Timer"
724 depends on X86_32 && !UML
726 This is the driver for the hardware watchdog found on the IEI
727 single board computers EPIC Nano 7240 (and likely others). This
728 watchdog simply watches your kernel to make sure it doesn't freeze,
729 and if it does, it reboots your computer after a certain amount of
732 To compile this driver as a module, choose M here: the
733 module will be called sbc7240_wdt.
736 tristate "SMA CPU5 Watchdog"
740 To compile this driver as a module, choose M here: the
741 module will be called cpu5wdt.
743 config SMSC_SCH311X_WDT
744 tristate "SMSC SCH311X Watchdog Timer"
747 This is the driver for the hardware watchdog timer on the
748 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
749 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
752 To compile this driver as a module, choose M here: the
753 module will be called sch311x_wdt.
755 config SMSC37B787_WDT
756 tristate "Winbond SMsC37B787 Watchdog Timer"
759 This is the driver for the hardware watchdog component on the
760 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
761 from Vision Systems and maybe others.
763 This watchdog simply watches your kernel to make sure it doesn't
764 freeze, and if it does, it reboots your computer after a certain
767 Usually a userspace daemon will notify the kernel WDT driver that
768 userspace is still alive, at regular intervals.
770 To compile this driver as a module, choose M here: the
771 module will be called smsc37b787_wdt.
773 Most people will say N.
776 tristate "W83627HF/W83627DHG Watchdog Timer"
779 This is the driver for the hardware watchdog on the W83627HF chipset
780 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
781 (and likely others). The driver also supports the W83627DHG chip.
782 This watchdog simply watches your kernel to make sure it doesn't
783 freeze, and if it does, it reboots your computer after a certain
786 To compile this driver as a module, choose M here: the
787 module will be called w83627hf_wdt.
789 Most people will say N.
792 tristate "W83697HF/W83697HG Watchdog Timer"
795 This is the driver for the hardware watchdog on the W83697HF/HG
796 chipset as used in Dedibox/VIA motherboards (and likely others).
797 This watchdog simply watches your kernel to make sure it doesn't
798 freeze, and if it does, it reboots your computer after a certain
801 To compile this driver as a module, choose M here: the
802 module will be called w83697hf_wdt.
804 Most people will say N.
807 tristate "W83697UG/W83697UF Watchdog Timer"
810 This is the driver for the hardware watchdog on the W83697UG/UF
811 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
812 This watchdog simply watches your kernel to make sure it doesn't
813 freeze, and if it does, it reboots your computer after a certain
816 To compile this driver as a module, choose M here: the
817 module will be called w83697ug_wdt.
819 Most people will say N.
822 tristate "W83877F (EMACS) Watchdog Timer"
825 This is the driver for the hardware watchdog on the W83877F chipset
826 as used in EMACS PC-104 motherboards (and likely others). This
827 watchdog simply watches your kernel to make sure it doesn't freeze,
828 and if it does, it reboots your computer after a certain amount of
831 To compile this driver as a module, choose M here: the
832 module will be called w83877f_wdt.
834 Most people will say N.
837 tristate "W83977F (PCM-5335) Watchdog Timer"
840 This is the driver for the hardware watchdog on the W83977F I/O chip
841 as used in AAEON's PCM-5335 SBC (and likely others). This
842 watchdog simply watches your kernel to make sure it doesn't freeze,
843 and if it does, it reboots your computer after a certain amount of
846 To compile this driver as a module, choose M here: the
847 module will be called w83977f_wdt.
850 tristate "ZF MachZ Watchdog"
853 If you are using a ZF Micro MachZ processor, say Y here, otherwise
854 N. This is the driver for the watchdog timer built-in on that
855 processor using ZF-Logic interface. This watchdog simply watches
856 your kernel to make sure it doesn't freeze, and if it does, it
857 reboots your computer after a certain amount of time.
859 To compile this driver as a module, choose M here: the
860 module will be called machzwd.
862 config SBC_EPX_C3_WATCHDOG
863 tristate "Winsystems SBC EPX-C3 watchdog"
866 This is the driver for the built-in watchdog timer on the EPX-C3
867 Single-board computer made by Winsystems, Inc.
869 *Note*: This hardware watchdog is not probeable and thus there
870 is no way to know if writing to its IO address will corrupt
871 your system or have any real effect. The only way to be sure
872 that this driver does what you want is to make sure you
873 are running it on an EPX-C3 from Winsystems with the watchdog
874 timer at IO address 0x1ee and 0x1ef. It will write to both those
875 IO ports. Basically, the assumption is made that if you compile
876 this driver into your kernel and/or load it as a module, that you
877 know what you are doing and that you are in fact running on an
880 To compile this driver as a module, choose M here: the
881 module will be called sbc_epx_c3.
887 config M54xx_WATCHDOG
888 tristate "MCF54xx watchdog support"
891 To compile this driver as a module, choose M here: the
892 module will be called m54xx_wdt.
894 # MicroBlaze Architecture
896 config XILINX_WATCHDOG
897 tristate "Xilinx Watchdog timer"
898 depends on MICROBLAZE
900 Watchdog driver for the xps_timebase_wdt ip core.
902 IMPORTANT: The xps_timebase_wdt parent must have the property
903 "clock-frequency" at device tree.
905 To compile this driver as a module, choose M here: the
906 module will be called of_xilinx_wdt.
911 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
914 Hardware driver for the built-in watchdog timer on the Atheros
915 AR71XX/AR724X/AR913X SoCs.
918 tristate "Broadcom BCM47xx Watchdog Timer"
921 Hardware driver for the Broadcom BCM47xx Watchog Timer.
924 tristate "IDT RC32434 SoC Watchdog Timer"
925 depends on MIKROTIK_RB532
927 Hardware driver for the IDT RC32434 SoC built-in
930 To compile this driver as a module, choose M here: the
931 module will be called rc32434_wdt.
934 tristate "Indy/I2 Hardware Watchdog"
935 depends on SGI_HAS_INDYDOG
937 Hardware driver for the Indy's/I2's watchdog. This is a
938 watchdog timer that will reboot the machine after a 60 second
939 timer expired and no process has written to /dev/watchdog during
943 tristate "Ingenic jz4740 SoC hardware watchdog"
944 depends on MACH_JZ4740
946 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
949 tristate "MTX-1 Hardware Watchdog"
952 Hardware driver for the MTX-1 boards. This is a watchdog timer that
953 will reboot the machine after a 100 seconds timer expired.
956 tristate "PNX833x Hardware Watchdog"
957 depends on SOC_PNX8335
959 Hardware driver for the PNX833x's watchdog. This is a
960 watchdog timer that will reboot the machine after a programmable
961 timer has expired and no process has written to /dev/watchdog during
965 tristate "Sibyte SoC hardware watchdog"
968 Watchdog driver for the built in watchdog hardware in Sibyte
969 SoC processors. There are apparently two watchdog timers
970 on such processors; this driver supports only the first one,
971 because currently Linux only supports exporting one watchdog
974 To compile this driver as a loadable module, choose M here.
975 The module will be called sb_wdog.
978 tristate "TI AR7 Watchdog Timer"
981 Hardware driver for the TI AR7 Watchdog Timer.
984 tristate "Toshiba TXx9 Watchdog Timer"
985 depends on CPU_TX39XX || CPU_TX49XX
987 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
990 tristate "Cavium OCTEON SOC family Watchdog Timer"
991 depends on CPU_CAVIUM_OCTEON
993 select EXPORT_UASM if OCTEON_WDT = m
995 Hardware driver for OCTEON's on chip watchdog timer.
996 Enables the watchdog for all cores running Linux. It
997 installs a NMI handler and pokes the watchdog based on an
998 interrupt. On first expiration of the watchdog, the
999 interrupt handler pokes it. The second expiration causes an
1000 NMI that prints a message. The third expiration causes a
1003 When userspace has /dev/watchdog open, no poking is done
1004 from the first interrupt, it is then only poked when the
1008 tristate "Broadcom BCM63xx hardware watchdog"
1011 Watchdog driver for the built in watchdog hardware in Broadcom
1014 To compile this driver as a loadable module, choose M here.
1015 The module will be called bcm63xx_wdt.
1018 tristate "Lantiq SoC watchdog"
1021 Hardware driver for the Lantiq SoC Watchdog Timer.
1023 # PARISC Architecture
1025 # POWERPC Architecture
1028 tristate "GE Watchdog Timer"
1029 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
1031 Watchdog timer found in a number of GE single board computers.
1034 bool "MPC52xx Watchdog Timer"
1035 depends on PPC_MPC52xx
1037 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1040 tristate "MPC8xxx Platform Watchdog Timer"
1041 depends on PPC_8xx || PPC_83xx || PPC_86xx
1043 This driver is for a SoC level watchdog that exists on some
1044 Freescale PowerPC processors. So far this driver supports:
1049 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1052 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1056 tristate "PIKA FPGA Watchdog"
1060 This enables the watchdog in the PIKA FPGA. Currently used on
1064 tristate "PowerPC Book-E Watchdog Timer"
1065 depends on BOOKE || 4xx
1067 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1068 MPC85xx SOCs and the IBM PowerPC 440.
1070 Please see Documentation/watchdog/watchdog-api.txt for
1073 config BOOKE_WDT_DEFAULT_TIMEOUT
1074 int "PowerPC Book-E Watchdog Timer Default Timeout"
1075 depends on BOOKE_WDT
1076 default 38 if FSL_BOOKE
1077 range 0 63 if FSL_BOOKE
1078 default 3 if !FSL_BOOKE
1079 range 0 3 if !FSL_BOOKE
1081 Select the default watchdog timer period to be used by the PowerPC
1082 Book-E watchdog driver. A watchdog "event" occurs when the bit
1083 position represented by this number transitions from zero to one.
1085 For Freescale Book-E processors, this is a number between 0 and 63.
1086 For other Book-E processors, this is a number between 0 and 3.
1088 The value can be overidden by the wdt_period command-line parameter.
1090 # PPC64 Architecture
1092 config WATCHDOG_RTAS
1093 tristate "RTAS watchdog"
1096 This driver adds watchdog support for the RTAS watchdog.
1098 To compile this driver as a module, choose M here. The module
1099 will be called wdrtas.
1104 tristate "z/VM Watchdog Timer"
1107 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1108 provide a virtual watchdog timer to their guest that cause a
1109 user define Control Program command to be executed after a
1112 To compile this driver as a module, choose M here. The module
1113 will be called vmwatchdog.
1115 # SUPERH (sh + sh64) Architecture
1118 tristate "SuperH Watchdog"
1119 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1121 This driver adds watchdog support for the integrated watchdog in the
1122 SuperH processors. If you have one of these processors and wish
1123 to have watchdog support enabled, say Y, otherwise say N.
1125 As a side note, saying Y here will automatically boost HZ to 1000
1126 so that the timer has a chance to clear the overflow counter. On
1127 slower systems (such as the SH-2 and SH-3) this will likely yield
1128 some performance issues. As such, the WDT should be avoided here
1129 unless it is absolutely necessary.
1131 To compile this driver as a module, choose M here: the
1132 module will be called shwdt.
1134 # SPARC Architecture
1136 # SPARC64 Architecture
1138 config WATCHDOG_CP1XXX
1139 tristate "CP1XXX Hardware Watchdog support"
1140 depends on SPARC64 && PCI
1142 This is the driver for the hardware watchdog timers present on
1143 Sun Microsystems CompactPCI models CP1400 and CP1500.
1145 To compile this driver as a module, choose M here: the
1146 module will be called cpwatchdog.
1148 If you do not have a CompactPCI model CP1400 or CP1500, or
1149 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1150 you should say N to this option.
1153 tristate "RIO Hardware Watchdog support"
1154 depends on SPARC64 && PCI
1156 Say Y here to support the hardware watchdog capability on Sun RIO
1157 machines. The watchdog timeout period is normally one minute but
1158 can be changed with a boot-time parameter.
1160 # XTENSA Architecture
1165 tristate "Xen Watchdog support"
1168 Say Y here to support the hypervisor watchdog capability provided
1169 by Xen 4.0 and newer. The watchdog timeout period is normally one
1170 minute but can be changed with a boot-time parameter.
1173 tristate "UML watchdog"
1177 # ISA-based Watchdog Cards
1180 comment "ISA-based Watchdog Cards"
1184 tristate "Berkshire Products ISA-PC Watchdog"
1187 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1188 This card simply watches your kernel to make sure it doesn't freeze,
1189 and if it does, it reboots your computer after a certain amount of
1190 time. This driver is like the WDT501 driver but for different
1191 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1192 watchdog cards can be ordered from <http://www.berkprod.com/>.
1194 To compile this driver as a module, choose M here: the
1195 module will be called pcwd.
1197 Most people will say N.
1200 tristate "Mixcom Watchdog"
1203 This is a driver for the Mixcom hardware watchdog cards. This
1204 watchdog simply watches your kernel to make sure it doesn't freeze,
1205 and if it does, it reboots your computer after a certain amount of
1208 To compile this driver as a module, choose M here: the
1209 module will be called mixcomwd.
1211 Most people will say N.
1214 tristate "WDT Watchdog timer"
1217 If you have a WDT500P or WDT501P watchdog board, say Y here,
1218 otherwise N. It is not possible to probe for this board, which means
1219 that you have to inform the kernel about the IO port and IRQ that
1220 is needed (you can do this via the io and irq parameters)
1222 To compile this driver as a module, choose M here: the
1223 module will be called wdt.
1226 # PCI-based Watchdog Cards
1229 comment "PCI-based Watchdog Cards"
1232 config PCIPCWATCHDOG
1233 tristate "Berkshire Products PCI-PC Watchdog"
1236 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1237 This card simply watches your kernel to make sure it doesn't freeze,
1238 and if it does, it reboots your computer after a certain amount of
1239 time. The card can also monitor the internal temperature of the PC.
1240 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1242 To compile this driver as a module, choose M here: the
1243 module will be called pcwd_pci.
1245 Most people will say N.
1248 tristate "PCI-WDT500/501 Watchdog timer"
1251 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1253 If you have a PCI-WDT501 watchdog board then you can enable the
1254 temperature sensor by setting the type parameter to 501.
1256 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1257 can do this via the tachometer parameter. Only do this if you have a
1258 fan tachometer actually set up.
1260 To compile this driver as a module, choose M here: the
1261 module will be called wdt_pci.
1264 # USB-based Watchdog Cards
1267 comment "USB-based Watchdog Cards"
1270 config USBPCWATCHDOG
1271 tristate "Berkshire Products USB-PC Watchdog"
1274 This is the driver for the Berkshire Products USB-PC Watchdog card.
1275 This card simply watches your kernel to make sure it doesn't freeze,
1276 and if it does, it reboots your computer after a certain amount of
1277 time. The card can also monitor the internal temperature of the PC.
1278 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1280 To compile this driver as a module, choose M here: the
1281 module will be called pcwd_usb.
1283 Most people will say N.