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
31 config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
34 The default watchdog behaviour (which you get if you say N here) is
35 to stop the timer if the process managing it closes the file
36 /dev/watchdog. It's always remotely possible that this process might
37 get killed. If you say Y here, the watchdog cannot be stopped once
41 # General Watchdog drivers
44 comment "Watchdog Device Drivers"
46 # Architecture Independent
49 tristate "Software watchdog"
51 A software monitoring watchdog. This will fail to reboot your system
52 from some situations that the hardware watchdog will recover
53 from. Equally it's a lot cheaper to install.
55 To compile this driver as a module, choose M here: the
56 module will be called softdog.
58 config WM831X_WATCHDOG
59 tristate "WM831x watchdog"
62 Support for the watchdog in the WM831x AudioPlus PMICs. When
63 the watchdog triggers the system will be reset.
65 config WM8350_WATCHDOG
66 tristate "WM8350 watchdog"
69 Support for the watchdog in the WM8350 AudioPlus PMIC. When
70 the watchdog triggers the system will be reset.
76 config ARM_SP805_WATCHDOG
77 tristate "ARM SP805 Watchdog"
80 ARM Primecell SP805 Watchdog timer. This will reboot your system when
81 the timeout is reached.
83 config AT91RM9200_WATCHDOG
84 tristate "AT91RM9200 watchdog"
85 depends on ARCH_AT91RM9200
87 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
88 system when the timeout is reached.
90 config AT91SAM9X_WATCHDOG
91 tristate "AT91SAM9X / AT91CAP9 watchdog"
92 depends on ARCH_AT91 && !ARCH_AT91RM9200
94 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
95 reboot your system when the timeout is reached.
98 tristate "DC21285 watchdog"
101 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
102 here if you wish to use this. Alternatively say M to compile the
103 driver as a module, which will be called wdt285.
105 This driver does not work on all machines. In particular, early CATS
106 boards have hardware problems that will cause the machine to simply
107 lock up if the watchdog fires.
109 "If in doubt, leave it out" - say N.
112 tristate "NetWinder WB83C977 watchdog"
113 depends on FOOTBRIDGE && ARCH_NETWINDER
115 Say Y here to include support for the WB977 watchdog included in
116 NetWinder machines. Alternatively say M to compile the driver as
117 a module, which will be called wdt977.
119 Not sure? It's safe to say N.
121 config IXP2000_WATCHDOG
122 tristate "IXP2000 Watchdog"
123 depends on ARCH_IXP2000
125 Say Y here if to include support for the watchdog timer
126 in the Intel IXP2000(2400, 2800, 2850) network processors.
127 This driver can be built as a module by choosing M. The module
128 will be called ixp2000_wdt.
130 Say N if you are unsure.
132 config IXP4XX_WATCHDOG
133 tristate "IXP4xx Watchdog"
134 depends on ARCH_IXP4XX
136 Say Y here if to include support for the watchdog timer
137 in the Intel IXP4xx network processors. This driver can
138 be built as a module by choosing M. The module will
139 be called ixp4xx_wdt.
141 Note: The internal IXP4xx watchdog does a soft CPU reset
142 which doesn't reset any peripherals. There are circumstances
143 where the watchdog will fail to reset the board correctly
144 (e.g., if the boot ROM is in an unreadable state).
146 Say N if you are unsure.
148 config KS8695_WATCHDOG
149 tristate "KS8695 watchdog"
150 depends on ARCH_KS8695
152 Watchdog timer embedded into KS8695 processor. This will reboot your
153 system when the timeout is reached.
155 config HAVE_S3C2410_WATCHDOG
158 This will include watchdog timer support for Samsung SoCs. If
159 you want to include watchdog support for any machine, kindly
160 select this in the respective mach-XXXX/Kconfig file.
162 config S3C2410_WATCHDOG
163 tristate "S3C2410 Watchdog"
164 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
166 Watchdog timer block in the Samsung SoCs. This will reboot
167 the system when the timer expires with the watchdog enabled.
169 The driver is limited by the speed of the system's PCLK
170 signal, so with reasonably fast systems (PCLK around 50-66MHz)
171 then watchdog intervals of over approximately 20seconds are
174 The driver can be built as a module by choosing M, and will
175 be called s3c2410_wdt
179 config SAMSUNG_WATCHDOG_RESET_BOOT
180 bool "Enable watchdog reset for debugging"
182 Watchdog reset system when occur system delay. and goto watchdog reset boot mode.
183 If you get reset debugging log, enable WTD_RESET_BOOT on boot config.
185 endif #S3C2410_WATCHDOG
187 if SAMSUNG_WATCHDOG_RESET_BOOT
189 config WTD_RESET_BOOT_USE_MAGIC_CODE
190 bool "Using magic code when reset by watchdog"
192 Check "INFORM6" bit to distinguish between watchdog reset because of lockup and intentional watchdog reset.
193 endif #SAMSUNG_WATCHDOG_RESET_BOOT
195 config SA1100_WATCHDOG
196 tristate "SA1100/PXA2xx watchdog"
197 depends on ARCH_SA1100 || ARCH_PXA
199 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
200 reboot your system when timeout is reached.
202 NOTE: once enabled, this timer cannot be disabled.
204 To compile this driver as a module, choose M here: the
205 module will be called sa1100_wdt.
207 config MPCORE_WATCHDOG
208 tristate "MPcore watchdog"
209 depends on HAVE_ARM_TWD
211 Watchdog timer embedded into the MPcore system.
213 To compile this driver as a module, choose M here: the
214 module will be called mpcore_wdt.
216 config EP93XX_WATCHDOG
217 tristate "EP93xx Watchdog"
218 depends on ARCH_EP93XX
220 Say Y here if to include support for the watchdog timer
221 embedded in the Cirrus Logic EP93xx family of devices.
223 To compile this driver as a module, choose M here: the
224 module will be called ep93xx_wdt.
227 tristate "OMAP Watchdog"
228 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
230 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
231 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
233 config PNX4008_WATCHDOG
234 tristate "PNX4008 and LPC32XX Watchdog"
235 depends on ARCH_PNX4008 || ARCH_LPC32XX
237 Say Y here if to include support for the watchdog timer
238 in the PNX4008 or LPC32XX processor.
239 This driver can be built as a module by choosing M. The module
240 will be called pnx4008_wdt.
242 Say N if you are unsure.
245 tristate "IOP Watchdog"
247 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
249 Say Y here if to include support for the watchdog timer
250 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
251 be built as a module by choosing M. The module will
254 Note: The IOP13XX watchdog does an Internal Bus Reset which will
255 affect both cores and the peripherals of the IOP. The ATU-X
256 and/or ATUe configuration registers will remain intact, but if
257 operating as an Root Complex and/or Central Resource, the PCI-X
258 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
260 config DAVINCI_WATCHDOG
261 tristate "DaVinci watchdog"
262 depends on ARCH_DAVINCI
264 Say Y here if to include support for the watchdog timer
265 in the DaVinci DM644x/DM646x processors.
266 To compile this driver as a module, choose M here: the
267 module will be called davinci_wdt.
269 NOTE: once enabled, this timer cannot be disabled.
270 Say N if you are unsure.
272 config ORION_WATCHDOG
273 tristate "Orion watchdog"
274 depends on ARCH_ORION5X || ARCH_KIRKWOOD
276 Say Y here if to include support for the watchdog timer
277 in the Marvell Orion5x and Kirkwood ARM SoCs.
278 To compile this driver as a module, choose M here: the
279 module will be called orion_wdt.
281 config COH901327_WATCHDOG
282 bool "ST-Ericsson COH 901 327 watchdog"
284 default y if MACH_U300
286 Say Y here to include Watchdog timer support for the
287 watchdog embedded into the ST-Ericsson U300 series platforms.
288 This watchdog is used to reset the system and thus cannot be
289 compiled as a module.
291 config TWL4030_WATCHDOG
292 tristate "TWL4030 Watchdog"
293 depends on TWL4030_CORE
295 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
296 watchdog timer support for TWL4030 chips.
298 config STMP3XXX_WATCHDOG
299 tristate "Freescale STMP3XXX watchdog"
300 depends on ARCH_STMP3XXX
302 Say Y here if to include support for the watchdog timer
303 for the Sigmatel STMP37XX/378X SoC.
304 To compile this driver as a module, choose M here: the
305 module will be called stmp3xxx_wdt.
307 config NUC900_WATCHDOG
308 tristate "Nuvoton NUC900 watchdog"
309 depends on ARCH_W90X900
311 Say Y here if to include support for the watchdog timer
312 for the Nuvoton NUC900 series SoCs.
313 To compile this driver as a module, choose M here: the
314 module will be called nuc900_wdt.
317 tristate "Avionic Design Xanthos watchdog"
318 depends on ARCH_PXA_ADX
320 Say Y here if you want support for the watchdog timer on Avionic
321 Design Xanthos boards.
323 config TS72XX_WATCHDOG
324 tristate "TS-72XX SBC Watchdog"
325 depends on MACH_TS72XX
327 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
328 watchdog timer implemented in a external CPLD chip. Say Y here
329 if you want to support for the watchdog timer on TS-72XX boards.
331 To compile this driver as a module, choose M here: the
332 module will be called ts72xx_wdt.
334 config MAX63XX_WATCHDOG
335 tristate "Max63xx watchdog"
336 depends on ARM && HAS_IOMEM
338 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
341 tristate "IMX2+ Watchdog"
342 depends on ARCH_MX2 || ARCH_MX25 || ARCH_MX3 || ARCH_MX5
344 This is the driver for the hardware watchdog
345 on the Freescale IMX2 and later processors.
346 If you have one of these processors and wish to have
347 watchdog support enabled, say Y, otherwise say N.
349 To compile this driver as a module, choose M here: the
350 module will be called imx2_wdt.
354 config AT32AP700X_WDT
355 tristate "AT32AP700x watchdog"
356 depends on CPU_AT32AP700X
358 Watchdog timer embedded into AT32AP700x devices. This will reboot
359 your system when the timeout is reached.
361 # BLACKFIN Architecture
364 tristate "Blackfin On-Chip Watchdog Timer"
367 If you say yes here you will get support for the Blackfin On-Chip
368 Watchdog Timer. If you have one of these processors and wish to
369 have watchdog support enabled, say Y, otherwise say N.
371 To compile this driver as a module, choose M here: the
372 module will be called bfin_wdt.
380 # X86 (i386 + ia64 + x86_64) Architecture
383 tristate "Acquire SBC Watchdog Timer"
386 This is the driver for the hardware watchdog on Single Board
387 Computers produced by Acquire Inc (and others). This watchdog
388 simply watches your kernel to make sure it doesn't freeze, and if
389 it does, it reboots your computer after a certain amount of time.
391 To compile this driver as a module, choose M here: the
392 module will be called acquirewdt.
394 Most people will say N.
397 tristate "Advantech SBC Watchdog Timer"
400 If you are configuring a Linux kernel for the Advantech single-board
401 computer, say `Y' here to support its built-in watchdog timer
402 feature. More information can be found at
403 <http://www.advantech.com.tw/products/>
406 tristate "ALi M1535 PMU Watchdog Timer"
407 depends on X86 && PCI
409 This is the driver for the hardware watchdog on the ALi M1535 PMU.
411 To compile this driver as a module, choose M here: the
412 module will be called alim1535_wdt.
414 Most people will say N.
417 tristate "ALi M7101 PMU Computer Watchdog"
420 This is the driver for the hardware watchdog on the ALi M7101 PMU
421 as used in the x86 Cobalt servers and also found in some
422 SPARC Netra servers too.
424 To compile this driver as a module, choose M here: the
425 module will be called alim7101_wdt.
427 Most people will say N.
430 tristate "Fintek F71808E and F71882FG Watchdog"
431 depends on X86 && EXPERIMENTAL
433 This is the driver for the hardware watchdog on the Fintek
434 F71808E and F71882FG Super I/O controllers.
436 You can compile this driver directly into the kernel, or use
437 it as a module. The module will be called f71808e_wdt.
441 tristate "AMD Geode CS5535/CS5536 Watchdog"
442 depends on CS5535_MFGPT
444 This driver enables a watchdog capability built into the
445 CS5535/CS5536 companion chips for the AMD Geode GX and LX
446 processors. This watchdog watches your kernel to make sure
447 it doesn't freeze, and if it does, it reboots your computer after
448 a certain amount of time.
450 You can compile this driver directly into the kernel, or use
451 it as a module. The module will be called geodewdt.
454 tristate "AMD Elan SC520 processor Watchdog"
457 This is the driver for the hardware watchdog built in to the
458 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
459 This watchdog simply watches your kernel to make sure it doesn't
460 freeze, and if it does, it reboots your computer after a certain
463 You can compile this driver directly into the kernel, or use
464 it as a module. The module will be called sc520_wdt.
466 config SBC_FITPC2_WATCHDOG
467 tristate "Compulab SBC-FITPC2 watchdog"
470 This is the driver for the built-in watchdog timer on the fit-PC2,
471 fit-PC2i, CM-iAM single-board computers made by Compulab.
473 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
474 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
476 Entering BIOS setup temporary disables watchdog operation regardless to current state,
477 so system will not be restarted while user in BIOS setup.
479 Once watchdog was enabled the system will be restarted every
480 "Watchdog Timer Value" period, so to prevent it user can restart or
481 disable the watchdog.
483 To compile this driver as a module, choose M here: the
484 module will be called sbc_fitpc2_wdt.
486 Most people will say N.
489 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
492 Enable support for the watchdog timer on the Eurotech CPU-1220 and
493 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
494 information are at <http://www.eurotech.it/>.
497 tristate "IB700 SBC Watchdog Timer"
500 This is the driver for the hardware watchdog on the IB700 Single
501 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
502 simply watches your kernel to make sure it doesn't freeze, and if
503 it does, it reboots your computer after a certain amount of time.
505 This driver is like the WDT501 driver but for slightly different hardware.
507 To compile this driver as a module, choose M here: the
508 module will be called ib700wdt.
510 Most people will say N.
513 tristate "IBM Automatic Server Restart"
516 This is the driver for the IBM Automatic Server Restart watchdog
517 timer built-in into some eServer xSeries machines.
519 To compile this driver as a module, choose M here: the
520 module will be called ibmasr.
523 tristate "ICP Single Board Computer Watchdog Timer"
526 This is a driver for the hardware watchdog on the ICP Single
527 Board Computer. This driver is working on (at least) the following
528 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
530 To compile this driver as a module, choose M here: the
531 module will be called wafer5823wdt.
534 tristate "Intel 6300ESB Timer/Watchdog"
535 depends on X86 && PCI
537 Hardware driver for the watchdog timer built into the Intel
538 6300ESB controller hub.
540 To compile this driver as a module, choose M here: the
541 module will be called i6300esb.
544 tristate "Intel TCO Timer/Watchdog"
545 depends on (X86 || IA64) && PCI
547 Hardware driver for the intel TCO timer based watchdog devices.
548 These drivers are included in the Intel 82801 I/O Controller
549 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
552 The TCO (Total Cost of Ownership) timer is a watchdog timer
553 that will reboot the machine after its second expiration. The
554 expiration time can be configured with the "heartbeat" parameter.
556 On some motherboards the driver may fail to reset the chipset's
557 NO_REBOOT flag which prevents the watchdog from rebooting the
558 machine. If this is the case you will get a kernel message like
559 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
561 To compile this driver as a module, choose M here: the
562 module will be called iTCO_wdt.
564 config ITCO_VENDOR_SUPPORT
565 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
568 Add vendor specific support to the intel TCO timer based watchdog
569 devices. At this moment we only have additional support for some
570 SuperMicro Inc. motherboards.
573 tristate "IT8712F (Smart Guardian) Watchdog Timer"
576 This is the driver for the built-in watchdog timer on the IT8712F
577 Super I/0 chipset used on many motherboards.
579 To compile this driver as a module, choose M here: the
580 module will be called it8712f_wdt.
583 tristate "IT87 Watchdog Timer"
584 depends on X86 && EXPERIMENTAL
586 This is the driver for the hardware watchdog on the ITE IT8716,
587 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
588 simply watches your kernel to make sure it doesn't freeze, and if
589 it does, it reboots your computer after a certain amount of time.
591 To compile this driver as a module, choose M here: the module will
595 tristate "HP Proliant iLO2+ Hardware Watchdog Timer"
598 A software monitoring watchdog and NMI sourcing driver. This driver
599 will detect lockups and provide a stack trace. This is a driver that
600 will only load on a HP ProLiant system with a minimum of iLO2 support.
601 To compile this driver as a module, choose M here: the module will be
604 config HPWDT_NMI_DECODING
605 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
606 depends on HP_WATCHDOG
608 When an NMI occurs this feature will make the necessary BIOS calls to
609 log the cause of the NMI.
612 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
615 This is a driver for National Semiconductor PC87307/PC97307 hardware
616 watchdog cards as found on the SC1200. This watchdog is mainly used
617 for power management purposes and can be used to power down the device
618 during inactivity periods (includes interrupt activity monitoring).
620 To compile this driver as a module, choose M here: the
621 module will be called sc1200wdt.
623 Most people will say N.
626 tristate "National Semiconductor SCx200 Watchdog"
627 depends on SCx200 && PCI
629 Enable the built-in watchdog timer support on the National
630 Semiconductor SCx200 processors.
632 If compiled as a module, it will be called scx200_wdt.
635 tristate "NS PC87413 watchdog"
638 This is the driver for the hardware watchdog on the PC87413 chipset
639 This watchdog simply watches your kernel to make sure it doesn't
640 freeze, and if it does, it reboots your computer after a certain
643 To compile this driver as a module, choose M here: the
644 module will be called pc87413_wdt.
646 Most people will say N.
649 tristate "RDC R-321x SoC watchdog"
650 depends on X86_RDC321X
652 This is the driver for the built in hardware watchdog
653 in the RDC R-321x SoC.
655 To compile this driver as a module, choose M here: the
656 module will be called rdc321x_wdt.
659 tristate "SBC-60XX Watchdog Timer"
662 This driver can be used with the watchdog timer found on some
663 single board computers, namely the 6010 PII based computer.
664 It may well work with other cards. It reads port 0x443 to enable
665 and re-set the watchdog timer, and reads port 0x45 to disable
666 the watchdog. If you have a card that behave in similar ways,
667 you can probably make this driver work with your card as well.
669 You can compile this driver directly into the kernel, or use
670 it as a module. The module will be called sbc60xxwdt.
673 tristate "SBC8360 Watchdog Timer"
677 This is the driver for the hardware watchdog on the SBC8360 Single
678 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
680 To compile this driver as a module, choose M here: the
681 module will be called sbc8360.
683 Most people will say N.
686 tristate "SBC Nano 7240 Watchdog Timer"
689 This is the driver for the hardware watchdog found on the IEI
690 single board computers EPIC Nano 7240 (and likely others). This
691 watchdog simply watches your kernel to make sure it doesn't freeze,
692 and if it does, it reboots your computer after a certain amount of
695 To compile this driver as a module, choose M here: the
696 module will be called sbc7240_wdt.
699 tristate "SMA CPU5 Watchdog"
703 To compile this driver as a module, choose M here: the
704 module will be called cpu5wdt.
706 config SMSC_SCH311X_WDT
707 tristate "SMSC SCH311X Watchdog Timer"
710 This is the driver for the hardware watchdog timer on the
711 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
712 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
715 To compile this driver as a module, choose M here: the
716 module will be called sch311x_wdt.
718 config SMSC37B787_WDT
719 tristate "Winbond SMsC37B787 Watchdog Timer"
722 This is the driver for the hardware watchdog component on the
723 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
724 from Vision Systems and maybe others.
726 This watchdog simply watches your kernel to make sure it doesn't
727 freeze, and if it does, it reboots your computer after a certain
730 Usually a userspace daemon will notify the kernel WDT driver that
731 userspace is still alive, at regular intervals.
733 To compile this driver as a module, choose M here: the
734 module will be called smsc37b787_wdt.
736 Most people will say N.
739 tristate "W83627HF Watchdog Timer"
742 This is the driver for the hardware watchdog on the W83627HF chipset
743 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
744 (and likely others). This watchdog simply watches your kernel to
745 make sure it doesn't freeze, and if it does, it reboots your computer
746 after a certain amount of time.
748 To compile this driver as a module, choose M here: the
749 module will be called w83627hf_wdt.
751 Most people will say N.
754 tristate "W83697HF/W83697HG Watchdog Timer"
757 This is the driver for the hardware watchdog on the W83697HF/HG
758 chipset as used in Dedibox/VIA motherboards (and likely others).
759 This watchdog simply watches your kernel to make sure it doesn't
760 freeze, and if it does, it reboots your computer after a certain
763 To compile this driver as a module, choose M here: the
764 module will be called w83697hf_wdt.
766 Most people will say N.
769 tristate "W83697UG/W83697UF Watchdog Timer"
772 This is the driver for the hardware watchdog on the W83697UG/UF
773 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
774 This watchdog simply watches your kernel to make sure it doesn't
775 freeze, and if it does, it reboots your computer after a certain
778 To compile this driver as a module, choose M here: the
779 module will be called w83697ug_wdt.
781 Most people will say N.
784 tristate "W83877F (EMACS) Watchdog Timer"
787 This is the driver for the hardware watchdog on the W83877F chipset
788 as used in EMACS PC-104 motherboards (and likely others). This
789 watchdog simply watches your kernel to make sure it doesn't freeze,
790 and if it does, it reboots your computer after a certain amount of
793 To compile this driver as a module, choose M here: the
794 module will be called w83877f_wdt.
796 Most people will say N.
799 tristate "W83977F (PCM-5335) Watchdog Timer"
802 This is the driver for the hardware watchdog on the W83977F I/O chip
803 as used in AAEON's PCM-5335 SBC (and likely others). This
804 watchdog simply watches your kernel to make sure it doesn't freeze,
805 and if it does, it reboots your computer after a certain amount of
808 To compile this driver as a module, choose M here: the
809 module will be called w83977f_wdt.
812 tristate "ZF MachZ Watchdog"
815 If you are using a ZF Micro MachZ processor, say Y here, otherwise
816 N. This is the driver for the watchdog timer built-in on that
817 processor using ZF-Logic interface. This watchdog simply watches
818 your kernel to make sure it doesn't freeze, and if it does, it
819 reboots your computer after a certain amount of time.
821 To compile this driver as a module, choose M here: the
822 module will be called machzwd.
824 config SBC_EPX_C3_WATCHDOG
825 tristate "Winsystems SBC EPX-C3 watchdog"
828 This is the driver for the built-in watchdog timer on the EPX-C3
829 Single-board computer made by Winsystems, Inc.
831 *Note*: This hardware watchdog is not probeable and thus there
832 is no way to know if writing to its IO address will corrupt
833 your system or have any real effect. The only way to be sure
834 that this driver does what you want is to make sure you
835 are running it on an EPX-C3 from Winsystems with the watchdog
836 timer at IO address 0x1ee and 0x1ef. It will write to both those
837 IO ports. Basically, the assumption is made that if you compile
838 this driver into your kernel and/or load it as a module, that you
839 know what you are doing and that you are in fact running on an
842 To compile this driver as a module, choose M here: the
843 module will be called sbc_epx_c3.
849 # M68KNOMMU Architecture
854 tristate "Broadcom BCM47xx Watchdog Timer"
857 Hardware driver for the Broadcom BCM47xx Watchog Timer.
860 tristate "IDT RC32434 SoC Watchdog Timer"
861 depends on MIKROTIK_RB532
863 Hardware driver for the IDT RC32434 SoC built-in
866 To compile this driver as a module, choose M here: the
867 module will be called rc32434_wdt.
870 tristate "Indy/I2 Hardware Watchdog"
871 depends on SGI_HAS_INDYDOG
873 Hardware driver for the Indy's/I2's watchdog. This is a
874 watchdog timer that will reboot the machine after a 60 second
875 timer expired and no process has written to /dev/watchdog during
879 tristate "MTX-1 Hardware Watchdog"
882 Hardware driver for the MTX-1 boards. This is a watchdog timer that
883 will reboot the machine after a 100 seconds timer expired.
886 tristate "PNX833x Hardware Watchdog"
887 depends on SOC_PNX8335
889 Hardware driver for the PNX833x's watchdog. This is a
890 watchdog timer that will reboot the machine after a programable
891 timer has expired and no process has written to /dev/watchdog during
895 tristate "Sibyte SoC hardware watchdog"
898 Watchdog driver for the built in watchdog hardware in Sibyte
899 SoC processors. There are apparently two watchdog timers
900 on such processors; this driver supports only the first one,
901 because currently Linux only supports exporting one watchdog
904 To compile this driver as a loadable module, choose M here.
905 The module will be called sb_wdog.
908 tristate "TI AR7 Watchdog Timer"
911 Hardware driver for the TI AR7 Watchdog Timer.
914 tristate "Toshiba TXx9 Watchdog Timer"
915 depends on CPU_TX39XX || CPU_TX49XX
917 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
920 tristate "Cavium OCTEON SOC family Watchdog Timer"
921 depends on CPU_CAVIUM_OCTEON
923 select EXPORT_UASM if OCTEON_WDT = m
925 Hardware driver for OCTEON's on chip watchdog timer.
926 Enables the watchdog for all cores running Linux. It
927 installs a NMI handler and pokes the watchdog based on an
928 interrupt. On first expiration of the watchdog, the
929 interrupt handler pokes it. The second expiration causes an
930 NMI that prints a message. The third expiration causes a
933 When userspace has /dev/watchdog open, no poking is done
934 from the first interrupt, it is then only poked when the
937 # PARISC Architecture
939 # POWERPC Architecture
942 tristate "GE Watchdog Timer"
943 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
945 Watchdog timer found in a number of GE single board computers.
948 bool "MPC52xx Watchdog Timer"
949 depends on PPC_MPC52xx
951 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
954 tristate "MPC8xxx Platform Watchdog Timer"
955 depends on PPC_8xx || PPC_83xx || PPC_86xx
957 This driver is for a SoC level watchdog that exists on some
958 Freescale PowerPC processors. So far this driver supports:
963 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
966 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
970 tristate "PIKA FPGA Watchdog"
974 This enables the watchdog in the PIKA FPGA. Currently used on
978 bool "PowerPC Book-E Watchdog Timer"
979 depends on BOOKE || 4xx
981 Please see Documentation/watchdog/watchdog-api.txt for
987 tristate "RTAS watchdog"
990 This driver adds watchdog support for the RTAS watchdog.
992 To compile this driver as a module, choose M here. The module
993 will be called wdrtas.
998 tristate "z/VM Watchdog Timer"
1001 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1002 provide a virtual watchdog timer to their guest that cause a
1003 user define Control Program command to be executed after a
1006 To compile this driver as a module, choose M here. The module
1007 will be called vmwatchdog.
1009 # SUPERH (sh + sh64) Architecture
1012 tristate "SuperH Watchdog"
1013 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1015 This driver adds watchdog support for the integrated watchdog in the
1016 SuperH processors. If you have one of these processors and wish
1017 to have watchdog support enabled, say Y, otherwise say N.
1019 As a side note, saying Y here will automatically boost HZ to 1000
1020 so that the timer has a chance to clear the overflow counter. On
1021 slower systems (such as the SH-2 and SH-3) this will likely yield
1022 some performance issues. As such, the WDT should be avoided here
1023 unless it is absolutely necessary.
1025 To compile this driver as a module, choose M here: the
1026 module will be called shwdt.
1029 bool "Allow mmap of SH WDT"
1033 If you say Y here, user applications will be able to mmap the
1036 # SPARC Architecture
1038 # SPARC64 Architecture
1040 config WATCHDOG_CP1XXX
1041 tristate "CP1XXX Hardware Watchdog support"
1042 depends on SPARC64 && PCI
1044 This is the driver for the hardware watchdog timers present on
1045 Sun Microsystems CompactPCI models CP1400 and CP1500.
1047 To compile this driver as a module, choose M here: the
1048 module will be called cpwatchdog.
1050 If you do not have a CompactPCI model CP1400 or CP1500, or
1051 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1052 you should say N to this option.
1055 tristate "RIO Hardware Watchdog support"
1056 depends on SPARC64 && PCI
1058 Say Y here to support the hardware watchdog capability on Sun RIO
1059 machines. The watchdog timeout period is normally one minute but
1060 can be changed with a boot-time parameter.
1062 # XTENSA Architecture
1065 # ISA-based Watchdog Cards
1068 comment "ISA-based Watchdog Cards"
1072 tristate "Berkshire Products ISA-PC Watchdog"
1075 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1076 This card simply watches your kernel to make sure it doesn't freeze,
1077 and if it does, it reboots your computer after a certain amount of
1078 time. This driver is like the WDT501 driver but for different
1079 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1080 watchdog cards can be ordered from <http://www.berkprod.com/>.
1082 To compile this driver as a module, choose M here: the
1083 module will be called pcwd.
1085 Most people will say N.
1088 tristate "Mixcom Watchdog"
1091 This is a driver for the Mixcom hardware watchdog cards. This
1092 watchdog simply watches your kernel to make sure it doesn't freeze,
1093 and if it does, it reboots your computer after a certain amount of
1096 To compile this driver as a module, choose M here: the
1097 module will be called mixcomwd.
1099 Most people will say N.
1102 tristate "WDT Watchdog timer"
1105 If you have a WDT500P or WDT501P watchdog board, say Y here,
1106 otherwise N. It is not possible to probe for this board, which means
1107 that you have to inform the kernel about the IO port and IRQ that
1108 is needed (you can do this via the io and irq parameters)
1110 To compile this driver as a module, choose M here: the
1111 module will be called wdt.
1114 # PCI-based Watchdog Cards
1117 comment "PCI-based Watchdog Cards"
1120 config PCIPCWATCHDOG
1121 tristate "Berkshire Products PCI-PC Watchdog"
1124 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1125 This card simply watches your kernel to make sure it doesn't freeze,
1126 and if it does, it reboots your computer after a certain amount of
1127 time. The card can also monitor the internal temperature of the PC.
1128 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1130 To compile this driver as a module, choose M here: the
1131 module will be called pcwd_pci.
1133 Most people will say N.
1136 tristate "PCI-WDT500/501 Watchdog timer"
1139 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1141 If you have a PCI-WDT501 watchdog board then you can enable the
1142 temperature sensor by setting the type parameter to 501.
1144 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1145 can do this via the tachometer parameter. Only do this if you have a
1146 fan tachometer actually set up.
1148 To compile this driver as a module, choose M here: the
1149 module will be called wdt_pci.
1152 # USB-based Watchdog Cards
1155 comment "USB-based Watchdog Cards"
1158 config USBPCWATCHDOG
1159 tristate "Berkshire Products USB-PC Watchdog"
1162 This is the driver for the Berkshire Products USB-PC Watchdog card.
1163 This card simply watches your kernel to make sure it doesn't freeze,
1164 and if it does, it reboots your computer after a certain amount of
1165 time. The card can also monitor the internal temperature of the PC.
1166 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1168 To compile this driver as a module, choose M here: the
1169 module will be called pcwd_usb.
1171 Most people will say N.