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.
192 config AT32AP700X_WDT
193 tristate "AT32AP700x watchdog"
194 depends on WATCHDOG && CPU_AT32AP7000
196 Watchdog timer embedded into AT32AP700x devices. This will reboot
197 your system when the timeout is reached.
199 # X86 (i386 + ia64 + x86_64) Architecture
202 tristate "Acquire SBC Watchdog Timer"
205 This is the driver for the hardware watchdog on Single Board
206 Computers produced by Acquire Inc (and others). This watchdog
207 simply watches your kernel to make sure it doesn't freeze, and if
208 it does, it reboots your computer after a certain amount of time.
210 To compile this driver as a module, choose M here: the
211 module will be called acquirewdt.
213 Most people will say N.
216 tristate "Advantech SBC Watchdog Timer"
219 If you are configuring a Linux kernel for the Advantech single-board
220 computer, say `Y' here to support its built-in watchdog timer
221 feature. More information can be found at
222 <http://www.advantech.com.tw/products/>
225 tristate "ALi M1535 PMU Watchdog Timer"
226 depends on X86 && PCI
228 This is the driver for the hardware watchdog on the ALi M1535 PMU.
230 To compile this driver as a module, choose M here: the
231 module will be called alim1535_wdt.
233 Most people will say N.
236 tristate "ALi M7101 PMU Computer Watchdog"
237 depends on X86 && PCI
239 This is the driver for the hardware watchdog on the ALi M7101 PMU
240 as used in the x86 Cobalt servers.
242 To compile this driver as a module, choose M here: the
243 module will be called alim7101_wdt.
245 Most people will say N.
248 tristate "AMD Elan SC520 processor Watchdog"
251 This is the driver for the hardware watchdog built in to the
252 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
253 This watchdog simply watches your kernel to make sure it doesn't
254 freeze, and if it does, it reboots your computer after a certain
257 You can compile this driver directly into the kernel, or use
258 it as a module. The module will be called sc520_wdt.
261 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
264 Enable support for the watchdog timer on the Eurotech CPU-1220 and
265 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
266 information are at <http://www.eurotech.it/>.
269 tristate "IB700 SBC Watchdog Timer"
272 This is the driver for the hardware watchdog on the IB700 Single
273 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
274 simply watches your kernel to make sure it doesn't freeze, and if
275 it does, it reboots your computer after a certain amount of time.
277 This driver is like the WDT501 driver but for slightly different hardware.
279 To compile this driver as a module, choose M here: the
280 module will be called ib700wdt.
282 Most people will say N.
285 tristate "IBM Automatic Server Restart"
288 This is the driver for the IBM Automatic Server Restart watchdog
289 timer built-in into some eServer xSeries machines.
291 To compile this driver as a module, choose M here: the
292 module will be called ibmasr.
295 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
298 This is a driver for the hardware watchdog on the ICP Wafer 5823
299 Single Board Computer (and probably other similar models).
301 To compile this driver as a module, choose M here: the
302 module will be called wafer5823wdt.
305 tristate "Intel 6300ESB Timer/Watchdog"
306 depends on X86 && PCI
308 Hardware driver for the watchdog timer built into the Intel
309 6300ESB controller hub.
311 To compile this driver as a module, choose M here: the
312 module will be called i6300esb.
315 tristate "Intel TCO Timer/Watchdog"
316 depends on (X86 || IA64) && PCI
318 Hardware driver for the intel TCO timer based watchdog devices.
319 These drivers are included in the Intel 82801 I/O Controller
320 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
323 The TCO (Total Cost of Ownership) timer is a watchdog timer
324 that will reboot the machine after its second expiration. The
325 expiration time can be configured with the "heartbeat" parameter.
327 On some motherboards the driver may fail to reset the chipset's
328 NO_REBOOT flag which prevents the watchdog from rebooting the
329 machine. If this is the case you will get a kernel message like
330 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
332 To compile this driver as a module, choose M here: the
333 module will be called iTCO_wdt.
335 config ITCO_VENDOR_SUPPORT
336 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
339 Add vendor specific support to the intel TCO timer based watchdog
340 devices. At this moment we only have additional support for some
341 SuperMicro Inc. motherboards.
344 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
347 This is a driver for National Semiconductor PC87307/PC97307 hardware
348 watchdog cards as found on the SC1200. This watchdog is mainly used
349 for power management purposes and can be used to power down the device
350 during inactivity periods (includes interrupt activity monitoring).
352 To compile this driver as a module, choose M here: the
353 module will be called sc1200wdt.
355 Most people will say N.
358 tristate "National Semiconductor SCx200 Watchdog"
359 depends on SCx200 && PCI
361 Enable the built-in watchdog timer support on the National
362 Semiconductor SCx200 processors.
364 If compiled as a module, it will be called scx200_wdt.
367 tristate "NS PC87413 watchdog"
370 This is the driver for the hardware watchdog on the PC87413 chipset
371 This watchdog simply watches your kernel to make sure it doesn't
372 freeze, and if it does, it reboots your computer after a certain
375 To compile this driver as a module, choose M here: the
376 module will be called pc87413_wdt.
378 Most people will say N.
381 tristate "SBC-60XX Watchdog Timer"
384 This driver can be used with the watchdog timer found on some
385 single board computers, namely the 6010 PII based computer.
386 It may well work with other cards. It reads port 0x443 to enable
387 and re-set the watchdog timer, and reads port 0x45 to disable
388 the watchdog. If you have a card that behave in similar ways,
389 you can probably make this driver work with your card as well.
391 You can compile this driver directly into the kernel, or use
392 it as a module. The module will be called sbc60xxwdt.
395 tristate "SBC8360 Watchdog Timer"
399 This is the driver for the hardware watchdog on the SBC8360 Single
400 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
402 To compile this driver as a module, choose M here: the
403 module will be called sbc8360.ko.
405 Most people will say N.
408 tristate "SMA CPU5 Watchdog"
412 To compile this driver as a module, choose M here: the
413 module will be called cpu5wdt.
415 config SMSC37B787_WDT
416 tristate "Winbond SMsC37B787 Watchdog Timer"
419 This is the driver for the hardware watchdog component on the
420 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
421 from Vision Systems and maybe others.
423 This watchdog simply watches your kernel to make sure it doesn't
424 freeze, and if it does, it reboots your computer after a certain
427 Usually a userspace daemon will notify the kernel WDT driver that
428 userspace is still alive, at regular intervals.
430 To compile this driver as a module, choose M here: the
431 module will be called smsc37b787_wdt.
433 Most people will say N.
436 tristate "W83627HF Watchdog Timer"
439 This is the driver for the hardware watchdog on the W83627HF chipset
440 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
441 (and likely others). This watchdog simply watches your kernel to
442 make sure it doesn't freeze, and if it does, it reboots your computer
443 after a certain amount of time.
445 To compile this driver as a module, choose M here: the
446 module will be called w83627hf_wdt.
448 Most people will say N.
451 tristate "W83697HF/W83697HG Watchdog Timer"
454 This is the driver for the hardware watchdog on the W83697HF/HG
455 chipset as used in Dedibox/VIA motherboards (and likely others).
456 This watchdog simply watches your kernel to make sure it doesn't
457 freeze, and if it does, it reboots your computer after a certain
460 To compile this driver as a module, choose M here: the
461 module will be called w83697hf_wdt.
463 Most people will say N.
466 tristate "W83877F (EMACS) Watchdog Timer"
469 This is the driver for the hardware watchdog on the W83877F chipset
470 as used in EMACS PC-104 motherboards (and likely others). This
471 watchdog simply watches your kernel to make sure it doesn't freeze,
472 and if it does, it reboots your computer after a certain amount of
475 To compile this driver as a module, choose M here: the
476 module will be called w83877f_wdt.
478 Most people will say N.
481 tristate "W83977F (PCM-5335) Watchdog Timer"
484 This is the driver for the hardware watchdog on the W83977F I/O chip
485 as used in AAEON's PCM-5335 SBC (and likely others). This
486 watchdog simply watches your kernel to make sure it doesn't freeze,
487 and if it does, it reboots your computer after a certain amount of
490 To compile this driver as a module, choose M here: the
491 module will be called w83977f_wdt.
494 tristate "ZF MachZ Watchdog"
497 If you are using a ZF Micro MachZ processor, say Y here, otherwise
498 N. This is the driver for the watchdog timer built-in on that
499 processor using ZF-Logic interface. This watchdog simply watches
500 your kernel to make sure it doesn't freeze, and if it does, it
501 reboots your computer after a certain amount of time.
503 To compile this driver as a module, choose M here: the
504 module will be called machzwd.
506 config SBC_EPX_C3_WATCHDOG
507 tristate "Winsystems SBC EPX-C3 watchdog"
510 This is the driver for the built-in watchdog timer on the EPX-C3
511 Single-board computer made by Winsystems, Inc.
513 *Note*: This hardware watchdog is not probeable and thus there
514 is no way to know if writing to its IO address will corrupt
515 your system or have any real effect. The only way to be sure
516 that this driver does what you want is to make sure you
517 are running it on an EPX-C3 from Winsystems with the watchdog
518 timer at IO address 0x1ee and 0x1ef. It will write to both those
519 IO ports. Basically, the assumption is made that if you compile
520 this driver into your kernel and/or load it as a module, that you
521 know what you are doing and that you are in fact running on an
524 To compile this driver as a module, choose M here: the
525 module will be called sbc_epx_c3.
527 # PowerPC Architecture
530 tristate "MPC8xx Watchdog Timer"
534 tristate "MPC83xx Watchdog Timer"
538 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
542 bool "PowerPC Book-E Watchdog Timer"
543 depends on BOOKE || 4xx
545 Please see Documentation/watchdog/watchdog-api.txt for
551 tristate "RTAS watchdog"
554 This driver adds watchdog support for the RTAS watchdog.
556 To compile this driver as a module, choose M here. The module
557 will be called wdrtas.
562 tristate "Indy/I2 Hardware Watchdog"
565 Hardware driver for the Indy's/I2's watchdog. This is a
566 watchdog timer that will reboot the machine after a 60 second
567 timer expired and no process has written to /dev/watchdog during
571 tristate "MTX-1 Hardware Watchdog"
574 Hardware driver for the MTX-1 boards. This is a watchdog timer that
575 will reboot the machine after a 100 seconds timer expired.
578 tristate "RM9000/GPI hardware watchdog"
579 depends on CPU_RM9000
581 Watchdog implementation using the GPI hardware found on
582 PMC-Sierra RM9xxx CPUs.
584 To compile this driver as a module, choose M here: the
585 module will be called rm9k_wdt.
590 tristate "z/VM Watchdog Timer"
593 IBM s/390 and zSeries machines running under z/VM 5.1 or later
594 provide a virtual watchdog timer to their guest that cause a
595 user define Control Program command to be executed after a
598 To compile this driver as a module, choose M here. The module
599 will be called vmwatchdog.
601 # SUPERH Architecture
604 tristate "SuperH Watchdog"
607 This driver adds watchdog support for the integrated watchdog in the
608 SuperH processors. If you have one of these processors and wish
609 to have watchdog support enabled, say Y, otherwise say N.
611 As a side note, saying Y here will automatically boost HZ to 1000
612 so that the timer has a chance to clear the overflow counter. On
613 slower systems (such as the SH-2 and SH-3) this will likely yield
614 some performance issues. As such, the WDT should be avoided here
615 unless it is absolutely necessary.
617 To compile this driver as a module, choose M here: the
618 module will be called shwdt.
621 bool "Allow mmap of SH WDT"
625 If you say Y here, user applications will be able to mmap the
628 # SPARC64 Architecture
630 config WATCHDOG_CP1XXX
631 tristate "CP1XXX Hardware Watchdog support"
632 depends on SPARC64 && PCI
634 This is the driver for the hardware watchdog timers present on
635 Sun Microsystems CompactPCI models CP1400 and CP1500.
637 To compile this driver as a module, choose M here: the
638 module will be called cpwatchdog.
640 If you do not have a CompactPCI model CP1400 or CP1500, or
641 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
642 you should say N to this option.
645 tristate "RIO Hardware Watchdog support"
646 depends on SPARC64 && PCI
648 Say Y here to support the hardware watchdog capability on Sun RIO
649 machines. The watchdog timeout period is normally one minute but
650 can be changed with a boot-time parameter.
653 # ISA-based Watchdog Cards
656 comment "ISA-based Watchdog Cards"
660 tristate "Berkshire Products ISA-PC Watchdog"
663 This is the driver for the Berkshire Products ISA-PC Watchdog card.
664 This card simply watches your kernel to make sure it doesn't freeze,
665 and if it does, it reboots your computer after a certain amount of
666 time. This driver is like the WDT501 driver but for different
667 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
668 watchdog cards can be ordered from <http://www.berkprod.com/>.
670 To compile this driver as a module, choose M here: the
671 module will be called pcwd.
673 Most people will say N.
676 tristate "Mixcom Watchdog"
679 This is a driver for the Mixcom hardware watchdog cards. This
680 watchdog simply watches your kernel to make sure it doesn't freeze,
681 and if it does, it reboots your computer after a certain amount of
684 To compile this driver as a module, choose M here: the
685 module will be called mixcomwd.
687 Most people will say N.
690 tristate "WDT Watchdog timer"
693 If you have a WDT500P or WDT501P watchdog board, say Y here,
694 otherwise N. It is not possible to probe for this board, which means
695 that you have to inform the kernel about the IO port and IRQ that
696 is needed (you can do this via the io and irq parameters)
698 To compile this driver as a module, choose M here: the
699 module will be called wdt.
702 bool "WDT501 features"
705 Saying Y here and creating a character special file /dev/temperature
706 with major number 10 and minor number 131 ("man mknod") will give
707 you a thermometer inside your computer: reading from
708 /dev/temperature yields one byte, the temperature in degrees
709 Fahrenheit. This works only if you have a WDT501P watchdog board
712 If you want to enable the Fan Tachometer on the WDT501P, then you
713 can do this via the tachometer parameter. Only do this if you have a
714 fan tachometer actually set up.
717 # PCI-based Watchdog Cards
720 comment "PCI-based Watchdog Cards"
724 tristate "Berkshire Products PCI-PC Watchdog"
727 This is the driver for the Berkshire Products PCI-PC Watchdog card.
728 This card 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
730 time. The card can also monitor the internal temperature of the PC.
731 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
733 To compile this driver as a module, choose M here: the
734 module will be called pcwd_pci.
736 Most people will say N.
739 tristate "PCI-WDT500/501 Watchdog timer"
742 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
744 To compile this driver as a module, choose M here: the
745 module will be called wdt_pci.
748 bool "PCI-WDT501 features"
751 Saying Y here and creating a character special file /dev/temperature
752 with major number 10 and minor number 131 ("man mknod") will give
753 you a thermometer inside your computer: reading from
754 /dev/temperature yields one byte, the temperature in degrees
755 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
758 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
759 can do this via the tachometer parameter. Only do this if you have a
760 fan tachometer actually set up.
763 # USB-based Watchdog Cards
766 comment "USB-based Watchdog Cards"
770 tristate "Berkshire Products USB-PC Watchdog"
773 This is the driver for the Berkshire Products USB-PC Watchdog card.
774 This card simply watches your kernel to make sure it doesn't freeze,
775 and if it does, it reboots your computer after a certain amount of
776 time. The card can also monitor the internal temperature of the PC.
777 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
779 To compile this driver as a module, choose M here: the
780 module will be called pcwd_usb.
782 Most people will say N.