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 <file:Documentation/watchdog/watchdog.txt>
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.
60 config AT91RM9200_WATCHDOG
61 tristate "AT91RM9200 watchdog"
62 depends on ARCH_AT91RM9200
64 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
65 system when the timeout is reached.
68 tristate "DC21285 watchdog"
71 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
72 here if you wish to use this. Alternatively say M to compile the
73 driver as a module, which will be called wdt285.
75 This driver does not work on all machines. In particular, early CATS
76 boards have hardware problems that will cause the machine to simply
77 lock up if the watchdog fires.
79 "If in doubt, leave it out" - say N.
82 tristate "NetWinder WB83C977 watchdog"
83 depends on FOOTBRIDGE && ARCH_NETWINDER
85 Say Y here to include support for the WB977 watchdog included in
86 NetWinder machines. Alternatively say M to compile the driver as
87 a module, which will be called wdt977.
89 Not sure? It's safe to say N.
91 config IXP2000_WATCHDOG
92 tristate "IXP2000 Watchdog"
93 depends on ARCH_IXP2000
95 Say Y here if to include support for the watchdog timer
96 in the Intel IXP2000(2400, 2800, 2850) network processors.
97 This driver can be built as a module by choosing M. The module
98 will be called ixp2000_wdt.
100 Say N if you are unsure.
102 config IXP4XX_WATCHDOG
103 tristate "IXP4xx Watchdog"
104 depends on ARCH_IXP4XX
106 Say Y here if to include support for the watchdog timer
107 in the Intel IXP4xx network processors. This driver can
108 be built as a module by choosing M. The module will
109 be called ixp4xx_wdt.
111 Note: The internal IXP4xx watchdog does a soft CPU reset
112 which doesn't reset any peripherals. There are circumstances
113 where the watchdog will fail to reset the board correctly
114 (e.g., if the boot ROM is in an unreadable state).
116 Say N if you are unsure.
118 config KS8695_WATCHDOG
119 tristate "KS8695 watchdog"
120 depends on ARCH_KS8695
122 Watchdog timer embedded into KS8695 processor. This will reboot your
123 system when the timeout is reached.
125 config S3C2410_WATCHDOG
126 tristate "S3C2410 Watchdog"
127 depends on ARCH_S3C2410
129 Watchdog timer block in the Samsung S3C2410 chips. This will
130 reboot the system when the timer expires with the watchdog
133 The driver is limited by the speed of the system's PCLK
134 signal, so with reasonably fast systems (PCLK around 50-66MHz)
135 then watchdog intervals of over approximately 20seconds are
138 The driver can be built as a module by choosing M, and will
139 be called s3c2410_wdt
141 config SA1100_WATCHDOG
142 tristate "SA1100/PXA2xx watchdog"
143 depends on ARCH_SA1100 || ARCH_PXA
145 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
146 reboot your system when timeout is reached.
148 NOTE: once enabled, this timer cannot be disabled.
150 To compile this driver as a module, choose M here: the
151 module will be called sa1100_wdt.
153 config MPCORE_WATCHDOG
154 tristate "MPcore watchdog"
155 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
157 Watchdog timer embedded into the MPcore system.
159 To compile this driver as a module, choose M here: the
160 module will be called mpcore_wdt.
162 config EP93XX_WATCHDOG
163 tristate "EP93xx Watchdog"
164 depends on ARCH_EP93XX
166 Say Y here if to include support for the watchdog timer
167 embedded in the Cirrus Logic EP93xx family of devices.
169 To compile this driver as a module, choose M here: the
170 module will be called ep93xx_wdt.
173 tristate "OMAP Watchdog"
174 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
176 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
177 enable the OMAP1610/OMAP1710 watchdog timer.
179 config PNX4008_WATCHDOG
180 tristate "PNX4008 Watchdog"
181 depends on ARCH_PNX4008
183 Say Y here if to include support for the watchdog timer
184 in the PNX4008 processor.
185 This driver can be built as a module by choosing M. The module
186 will be called pnx4008_wdt.
188 Say N if you are unsure.
191 tristate "IOP Watchdog"
192 depends on WATCHDOG && PLAT_IOP
193 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
195 Say Y here if to include support for the watchdog timer
196 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
197 be built as a module by choosing M. The module will
200 Note: The IOP13XX watchdog does an Internal Bus Reset which will
201 affect both cores and the peripherals of the IOP. The ATU-X
202 and/or ATUe configuration registers will remain intact, but if
203 operating as an Root Complex and/or Central Resource, the PCI-X
204 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
208 config AT32AP700X_WDT
209 tristate "AT32AP700x watchdog"
210 depends on WATCHDOG && CPU_AT32AP7000
212 Watchdog timer embedded into AT32AP700x devices. This will reboot
213 your system when the timeout is reached.
215 # X86 (i386 + ia64 + x86_64) Architecture
218 tristate "Acquire SBC Watchdog Timer"
221 This is the driver for the hardware watchdog on Single Board
222 Computers produced by Acquire Inc (and others). This watchdog
223 simply watches your kernel to make sure it doesn't freeze, and if
224 it does, it reboots your computer after a certain amount of time.
226 To compile this driver as a module, choose M here: the
227 module will be called acquirewdt.
229 Most people will say N.
232 tristate "Advantech SBC Watchdog Timer"
235 If you are configuring a Linux kernel for the Advantech single-board
236 computer, say `Y' here to support its built-in watchdog timer
237 feature. More information can be found at
238 <http://www.advantech.com.tw/products/>
241 tristate "ALi M1535 PMU Watchdog Timer"
242 depends on X86 && PCI
244 This is the driver for the hardware watchdog on the ALi M1535 PMU.
246 To compile this driver as a module, choose M here: the
247 module will be called alim1535_wdt.
249 Most people will say N.
252 tristate "ALi M7101 PMU Computer Watchdog"
253 depends on X86 && PCI
255 This is the driver for the hardware watchdog on the ALi M7101 PMU
256 as used in the x86 Cobalt servers.
258 To compile this driver as a module, choose M here: the
259 module will be called alim7101_wdt.
261 Most people will say N.
264 tristate "AMD Elan SC520 processor Watchdog"
267 This is the driver for the hardware watchdog built in to the
268 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
269 This watchdog simply watches your kernel to make sure it doesn't
270 freeze, and if it does, it reboots your computer after a certain
273 You can compile this driver directly into the kernel, or use
274 it as a module. The module will be called sc520_wdt.
277 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
280 Enable support for the watchdog timer on the Eurotech CPU-1220 and
281 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
282 information are at <http://www.eurotech.it/>.
285 tristate "IB700 SBC Watchdog Timer"
288 This is the driver for the hardware watchdog on the IB700 Single
289 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
290 simply watches your kernel to make sure it doesn't freeze, and if
291 it does, it reboots your computer after a certain amount of time.
293 This driver is like the WDT501 driver but for slightly different hardware.
295 To compile this driver as a module, choose M here: the
296 module will be called ib700wdt.
298 Most people will say N.
301 tristate "IBM Automatic Server Restart"
304 This is the driver for the IBM Automatic Server Restart watchdog
305 timer built-in into some eServer xSeries machines.
307 To compile this driver as a module, choose M here: the
308 module will be called ibmasr.
311 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
314 This is a driver for the hardware watchdog on the ICP Wafer 5823
315 Single Board Computer (and probably other similar models).
317 To compile this driver as a module, choose M here: the
318 module will be called wafer5823wdt.
321 tristate "Intel 6300ESB Timer/Watchdog"
322 depends on X86 && PCI
324 Hardware driver for the watchdog timer built into the Intel
325 6300ESB controller hub.
327 To compile this driver as a module, choose M here: the
328 module will be called i6300esb.
331 tristate "Intel TCO Timer/Watchdog"
332 depends on (X86 || IA64) && PCI
334 Hardware driver for the intel TCO timer based watchdog devices.
335 These drivers are included in the Intel 82801 I/O Controller
336 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
339 The TCO (Total Cost of Ownership) timer is a watchdog timer
340 that will reboot the machine after its second expiration. The
341 expiration time can be configured with the "heartbeat" parameter.
343 On some motherboards the driver may fail to reset the chipset's
344 NO_REBOOT flag which prevents the watchdog from rebooting the
345 machine. If this is the case you will get a kernel message like
346 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
348 To compile this driver as a module, choose M here: the
349 module will be called iTCO_wdt.
351 config ITCO_VENDOR_SUPPORT
352 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
355 Add vendor specific support to the intel TCO timer based watchdog
356 devices. At this moment we only have additional support for some
357 SuperMicro Inc. motherboards.
360 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
363 This is a driver for National Semiconductor PC87307/PC97307 hardware
364 watchdog cards as found on the SC1200. This watchdog is mainly used
365 for power management purposes and can be used to power down the device
366 during inactivity periods (includes interrupt activity monitoring).
368 To compile this driver as a module, choose M here: the
369 module will be called sc1200wdt.
371 Most people will say N.
374 tristate "National Semiconductor SCx200 Watchdog"
375 depends on SCx200 && PCI
377 Enable the built-in watchdog timer support on the National
378 Semiconductor SCx200 processors.
380 If compiled as a module, it will be called scx200_wdt.
383 tristate "NS PC87413 watchdog"
386 This is the driver for the hardware watchdog on the PC87413 chipset
387 This watchdog simply watches your kernel to make sure it doesn't
388 freeze, and if it does, it reboots your computer after a certain
391 To compile this driver as a module, choose M here: the
392 module will be called pc87413_wdt.
394 Most people will say N.
397 tristate "SBC-60XX Watchdog Timer"
400 This driver can be used with the watchdog timer found on some
401 single board computers, namely the 6010 PII based computer.
402 It may well work with other cards. It reads port 0x443 to enable
403 and re-set the watchdog timer, and reads port 0x45 to disable
404 the watchdog. If you have a card that behave in similar ways,
405 you can probably make this driver work with your card as well.
407 You can compile this driver directly into the kernel, or use
408 it as a module. The module will be called sbc60xxwdt.
411 tristate "SBC8360 Watchdog Timer"
415 This is the driver for the hardware watchdog on the SBC8360 Single
416 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
418 To compile this driver as a module, choose M here: the
419 module will be called sbc8360.ko.
421 Most people will say N.
424 tristate "SMA CPU5 Watchdog"
428 To compile this driver as a module, choose M here: the
429 module will be called cpu5wdt.
431 config SMSC37B787_WDT
432 tristate "Winbond SMsC37B787 Watchdog Timer"
435 This is the driver for the hardware watchdog component on the
436 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
437 from Vision Systems and maybe others.
439 This watchdog simply watches your kernel to make sure it doesn't
440 freeze, and if it does, it reboots your computer after a certain
443 Usually a userspace daemon will notify the kernel WDT driver that
444 userspace is still alive, at regular intervals.
446 To compile this driver as a module, choose M here: the
447 module will be called smsc37b787_wdt.
449 Most people will say N.
452 tristate "W83627HF Watchdog Timer"
455 This is the driver for the hardware watchdog on the W83627HF chipset
456 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
457 (and likely others). This watchdog simply watches your kernel to
458 make sure it doesn't freeze, and if it does, it reboots your computer
459 after a certain amount of time.
461 To compile this driver as a module, choose M here: the
462 module will be called w83627hf_wdt.
464 Most people will say N.
467 tristate "W83697HF/W83697HG Watchdog Timer"
470 This is the driver for the hardware watchdog on the W83697HF/HG
471 chipset as used in Dedibox/VIA motherboards (and likely others).
472 This watchdog simply watches your kernel to make sure it doesn't
473 freeze, and if it does, it reboots your computer after a certain
476 To compile this driver as a module, choose M here: the
477 module will be called w83697hf_wdt.
479 Most people will say N.
482 tristate "W83877F (EMACS) Watchdog Timer"
485 This is the driver for the hardware watchdog on the W83877F chipset
486 as used in EMACS PC-104 motherboards (and likely others). This
487 watchdog simply watches your kernel to make sure it doesn't freeze,
488 and if it does, it reboots your computer after a certain amount of
491 To compile this driver as a module, choose M here: the
492 module will be called w83877f_wdt.
494 Most people will say N.
497 tristate "W83977F (PCM-5335) Watchdog Timer"
500 This is the driver for the hardware watchdog on the W83977F I/O chip
501 as used in AAEON's PCM-5335 SBC (and likely others). This
502 watchdog simply watches your kernel to make sure it doesn't freeze,
503 and if it does, it reboots your computer after a certain amount of
506 To compile this driver as a module, choose M here: the
507 module will be called w83977f_wdt.
510 tristate "ZF MachZ Watchdog"
513 If you are using a ZF Micro MachZ processor, say Y here, otherwise
514 N. This is the driver for the watchdog timer built-in on that
515 processor using ZF-Logic interface. This watchdog simply watches
516 your kernel to make sure it doesn't freeze, and if it does, it
517 reboots your computer after a certain amount of time.
519 To compile this driver as a module, choose M here: the
520 module will be called machzwd.
522 config SBC_EPX_C3_WATCHDOG
523 tristate "Winsystems SBC EPX-C3 watchdog"
526 This is the driver for the built-in watchdog timer on the EPX-C3
527 Single-board computer made by Winsystems, Inc.
529 *Note*: This hardware watchdog is not probeable and thus there
530 is no way to know if writing to its IO address will corrupt
531 your system or have any real effect. The only way to be sure
532 that this driver does what you want is to make sure you
533 are running it on an EPX-C3 from Winsystems with the watchdog
534 timer at IO address 0x1ee and 0x1ef. It will write to both those
535 IO ports. Basically, the assumption is made that if you compile
536 this driver into your kernel and/or load it as a module, that you
537 know what you are doing and that you are in fact running on an
540 To compile this driver as a module, choose M here: the
541 module will be called sbc_epx_c3.
543 # PowerPC Architecture
546 tristate "MPC8xx Watchdog Timer"
550 tristate "MPC5200 Watchdog Timer"
551 depends on PPC_MPC52xx
554 tristate "MPC83xx Watchdog Timer"
558 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
562 bool "PowerPC Book-E Watchdog Timer"
563 depends on BOOKE || 4xx
565 Please see Documentation/watchdog/watchdog-api.txt for
571 tristate "RTAS watchdog"
574 This driver adds watchdog support for the RTAS watchdog.
576 To compile this driver as a module, choose M here. The module
577 will be called wdrtas.
582 tristate "Indy/I2 Hardware Watchdog"
585 Hardware driver for the Indy's/I2's watchdog. This is a
586 watchdog timer that will reboot the machine after a 60 second
587 timer expired and no process has written to /dev/watchdog during
591 tristate "MTX-1 Hardware Watchdog"
594 Hardware driver for the MTX-1 boards. This is a watchdog timer that
595 will reboot the machine after a 100 seconds timer expired.
598 tristate "RM9000/GPI hardware watchdog"
599 depends on CPU_RM9000
601 Watchdog implementation using the GPI hardware found on
602 PMC-Sierra RM9xxx CPUs.
604 To compile this driver as a module, choose M here: the
605 module will be called rm9k_wdt.
610 tristate "z/VM Watchdog Timer"
613 IBM s/390 and zSeries machines running under z/VM 5.1 or later
614 provide a virtual watchdog timer to their guest that cause a
615 user define Control Program command to be executed after a
618 To compile this driver as a module, choose M here. The module
619 will be called vmwatchdog.
621 # SUPERH Architecture
624 tristate "SuperH Watchdog"
625 depends on SUPERH && (CPU_SH3 || CPU_SH4)
627 This driver adds watchdog support for the integrated watchdog in the
628 SuperH processors. If you have one of these processors and wish
629 to have watchdog support enabled, say Y, otherwise say N.
631 As a side note, saying Y here will automatically boost HZ to 1000
632 so that the timer has a chance to clear the overflow counter. On
633 slower systems (such as the SH-2 and SH-3) this will likely yield
634 some performance issues. As such, the WDT should be avoided here
635 unless it is absolutely necessary.
637 To compile this driver as a module, choose M here: the
638 module will be called shwdt.
641 bool "Allow mmap of SH WDT"
645 If you say Y here, user applications will be able to mmap the
648 # SPARC64 Architecture
650 config WATCHDOG_CP1XXX
651 tristate "CP1XXX Hardware Watchdog support"
652 depends on SPARC64 && PCI
654 This is the driver for the hardware watchdog timers present on
655 Sun Microsystems CompactPCI models CP1400 and CP1500.
657 To compile this driver as a module, choose M here: the
658 module will be called cpwatchdog.
660 If you do not have a CompactPCI model CP1400 or CP1500, or
661 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
662 you should say N to this option.
665 tristate "RIO Hardware Watchdog support"
666 depends on SPARC64 && PCI
668 Say Y here to support the hardware watchdog capability on Sun RIO
669 machines. The watchdog timeout period is normally one minute but
670 can be changed with a boot-time parameter.
673 # ISA-based Watchdog Cards
676 comment "ISA-based Watchdog Cards"
680 tristate "Berkshire Products ISA-PC Watchdog"
683 This is the driver for the Berkshire Products ISA-PC Watchdog card.
684 This card simply watches your kernel to make sure it doesn't freeze,
685 and if it does, it reboots your computer after a certain amount of
686 time. This driver is like the WDT501 driver but for different
687 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
688 watchdog cards can be ordered from <http://www.berkprod.com/>.
690 To compile this driver as a module, choose M here: the
691 module will be called pcwd.
693 Most people will say N.
696 tristate "Mixcom Watchdog"
699 This is a driver for the Mixcom hardware watchdog cards. This
700 watchdog simply watches your kernel to make sure it doesn't freeze,
701 and if it does, it reboots your computer after a certain amount of
704 To compile this driver as a module, choose M here: the
705 module will be called mixcomwd.
707 Most people will say N.
710 tristate "WDT Watchdog timer"
713 If you have a WDT500P or WDT501P watchdog board, say Y here,
714 otherwise N. It is not possible to probe for this board, which means
715 that you have to inform the kernel about the IO port and IRQ that
716 is needed (you can do this via the io and irq parameters)
718 To compile this driver as a module, choose M here: the
719 module will be called wdt.
722 bool "WDT501 features"
725 Saying Y here and creating a character special file /dev/temperature
726 with major number 10 and minor number 131 ("man mknod") will give
727 you a thermometer inside your computer: reading from
728 /dev/temperature yields one byte, the temperature in degrees
729 Fahrenheit. This works only if you have a WDT501P watchdog board
732 If you want to enable the Fan Tachometer on the WDT501P, then you
733 can do this via the tachometer parameter. Only do this if you have a
734 fan tachometer actually set up.
737 # PCI-based Watchdog Cards
740 comment "PCI-based Watchdog Cards"
744 tristate "Berkshire Products PCI-PC Watchdog"
747 This is the driver for the Berkshire Products PCI-PC Watchdog card.
748 This card simply watches your kernel to make sure it doesn't freeze,
749 and if it does, it reboots your computer after a certain amount of
750 time. The card can also monitor the internal temperature of the PC.
751 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
753 To compile this driver as a module, choose M here: the
754 module will be called pcwd_pci.
756 Most people will say N.
759 tristate "PCI-WDT500/501 Watchdog timer"
762 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
764 To compile this driver as a module, choose M here: the
765 module will be called wdt_pci.
768 bool "PCI-WDT501 features"
771 Saying Y here and creating a character special file /dev/temperature
772 with major number 10 and minor number 131 ("man mknod") will give
773 you a thermometer inside your computer: reading from
774 /dev/temperature yields one byte, the temperature in degrees
775 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
778 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
779 can do this via the tachometer parameter. Only do this if you have a
780 fan tachometer actually set up.
783 # USB-based Watchdog Cards
786 comment "USB-based Watchdog Cards"
790 tristate "Berkshire Products USB-PC Watchdog"
793 This is the driver for the Berkshire Products USB-PC Watchdog card.
794 This card simply watches your kernel to make sure it doesn't freeze,
795 and if it does, it reboots your computer after a certain amount of
796 time. The card can also monitor the internal temperature of the PC.
797 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
799 To compile this driver as a module, choose M here: the
800 module will be called pcwd_usb.
802 Most people will say N.