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.
190 # X86 (i386 + ia64 + x86_64) Architecture
193 tristate "Acquire SBC Watchdog Timer"
196 This is the driver for the hardware watchdog on Single Board
197 Computers produced by Acquire Inc (and others). This watchdog
198 simply watches your kernel to make sure it doesn't freeze, and if
199 it does, it reboots your computer after a certain amount of time.
201 To compile this driver as a module, choose M here: the
202 module will be called acquirewdt.
204 Most people will say N.
207 tristate "Advantech SBC Watchdog Timer"
210 If you are configuring a Linux kernel for the Advantech single-board
211 computer, say `Y' here to support its built-in watchdog timer
212 feature. More information can be found at
213 <http://www.advantech.com.tw/products/>
216 tristate "ALi M1535 PMU Watchdog Timer"
217 depends on X86 && PCI
219 This is the driver for the hardware watchdog on the ALi M1535 PMU.
221 To compile this driver as a module, choose M here: the
222 module will be called alim1535_wdt.
224 Most people will say N.
227 tristate "ALi M7101 PMU Computer Watchdog"
228 depends on X86 && PCI
230 This is the driver for the hardware watchdog on the ALi M7101 PMU
231 as used in the x86 Cobalt servers.
233 To compile this driver as a module, choose M here: the
234 module will be called alim7101_wdt.
236 Most people will say N.
239 tristate "AMD Elan SC520 processor Watchdog"
242 This is the driver for the hardware watchdog built in to the
243 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
244 This watchdog simply watches your kernel to make sure it doesn't
245 freeze, and if it does, it reboots your computer after a certain
248 You can compile this driver directly into the kernel, or use
249 it as a module. The module will be called sc520_wdt.
252 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
255 Enable support for the watchdog timer on the Eurotech CPU-1220 and
256 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
257 information are at <http://www.eurotech.it/>.
260 tristate "IB700 SBC Watchdog Timer"
263 This is the driver for the hardware watchdog on the IB700 Single
264 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
265 simply watches your kernel to make sure it doesn't freeze, and if
266 it does, it reboots your computer after a certain amount of time.
268 This driver is like the WDT501 driver but for slightly different hardware.
270 To compile this driver as a module, choose M here: the
271 module will be called ib700wdt.
273 Most people will say N.
276 tristate "IBM Automatic Server Restart"
279 This is the driver for the IBM Automatic Server Restart watchdog
280 timer built-in into some eServer xSeries machines.
282 To compile this driver as a module, choose M here: the
283 module will be called ibmasr.
286 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
289 This is a driver for the hardware watchdog on the ICP Wafer 5823
290 Single Board Computer (and probably other similar models).
292 To compile this driver as a module, choose M here: the
293 module will be called wafer5823wdt.
296 tristate "Intel 6300ESB Timer/Watchdog"
297 depends on X86 && PCI
299 Hardware driver for the watchdog timer built into the Intel
300 6300ESB controller hub.
302 To compile this driver as a module, choose M here: the
303 module will be called i6300esb.
306 tristate "Intel TCO Timer/Watchdog"
307 depends on (X86 || IA64) && PCI
309 Hardware driver for the intel TCO timer based watchdog devices.
310 These drivers are included in the Intel 82801 I/O Controller
311 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
314 The TCO (Total Cost of Ownership) timer is a watchdog timer
315 that will reboot the machine after its second expiration. The
316 expiration time can be configured with the "heartbeat" parameter.
318 On some motherboards the driver may fail to reset the chipset's
319 NO_REBOOT flag which prevents the watchdog from rebooting the
320 machine. If this is the case you will get a kernel message like
321 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
323 To compile this driver as a module, choose M here: the
324 module will be called iTCO_wdt.
326 config ITCO_VENDOR_SUPPORT
327 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
330 Add vendor specific support to the intel TCO timer based watchdog
331 devices. At this moment we only have additional support for some
332 SuperMicro Inc. motherboards.
335 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
338 This is a driver for National Semiconductor PC87307/PC97307 hardware
339 watchdog cards as found on the SC1200. This watchdog is mainly used
340 for power management purposes and can be used to power down the device
341 during inactivity periods (includes interrupt activity monitoring).
343 To compile this driver as a module, choose M here: the
344 module will be called sc1200wdt.
346 Most people will say N.
349 tristate "National Semiconductor SCx200 Watchdog"
350 depends on SCx200 && PCI
352 Enable the built-in watchdog timer support on the National
353 Semiconductor SCx200 processors.
355 If compiled as a module, it will be called scx200_wdt.
358 tristate "NS PC87413 watchdog"
361 This is the driver for the hardware watchdog on the PC87413 chipset
362 This watchdog simply watches your kernel to make sure it doesn't
363 freeze, and if it does, it reboots your computer after a certain
366 To compile this driver as a module, choose M here: the
367 module will be called pc87413_wdt.
369 Most people will say N.
372 tristate "SBC-60XX Watchdog Timer"
375 This driver can be used with the watchdog timer found on some
376 single board computers, namely the 6010 PII based computer.
377 It may well work with other cards. It reads port 0x443 to enable
378 and re-set the watchdog timer, and reads port 0x45 to disable
379 the watchdog. If you have a card that behave in similar ways,
380 you can probably make this driver work with your card as well.
382 You can compile this driver directly into the kernel, or use
383 it as a module. The module will be called sbc60xxwdt.
386 tristate "SBC8360 Watchdog Timer"
390 This is the driver for the hardware watchdog on the SBC8360 Single
391 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
393 To compile this driver as a module, choose M here: the
394 module will be called sbc8360.ko.
396 Most people will say N.
399 tristate "SMA CPU5 Watchdog"
403 To compile this driver as a module, choose M here: the
404 module will be called cpu5wdt.
406 config SMSC37B787_WDT
407 tristate "Winbond SMsC37B787 Watchdog Timer"
410 This is the driver for the hardware watchdog component on the
411 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
412 from Vision Systems and maybe others.
414 This watchdog simply watches your kernel to make sure it doesn't
415 freeze, and if it does, it reboots your computer after a certain
418 Usually a userspace daemon will notify the kernel WDT driver that
419 userspace is still alive, at regular intervals.
421 To compile this driver as a module, choose M here: the
422 module will be called smsc37b787_wdt.
424 Most people will say N.
427 tristate "W83627HF Watchdog Timer"
430 This is the driver for the hardware watchdog on the W83627HF chipset
431 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
432 (and likely others). This watchdog simply watches your kernel to
433 make sure it doesn't freeze, and if it does, it reboots your computer
434 after a certain amount of time.
436 To compile this driver as a module, choose M here: the
437 module will be called w83627hf_wdt.
439 Most people will say N.
442 tristate "W83697HF/W83697HG Watchdog Timer"
445 This is the driver for the hardware watchdog on the W83697HF/HG
446 chipset as used in Dedibox/VIA motherboards (and likely others).
447 This watchdog simply watches your kernel to make sure it doesn't
448 freeze, and if it does, it reboots your computer after a certain
451 To compile this driver as a module, choose M here: the
452 module will be called w83697hf_wdt.
454 Most people will say N.
457 tristate "W83877F (EMACS) Watchdog Timer"
460 This is the driver for the hardware watchdog on the W83877F chipset
461 as used in EMACS PC-104 motherboards (and likely others). This
462 watchdog simply watches your kernel to make sure it doesn't freeze,
463 and if it does, it reboots your computer after a certain amount of
466 To compile this driver as a module, choose M here: the
467 module will be called w83877f_wdt.
469 Most people will say N.
472 tristate "W83977F (PCM-5335) Watchdog Timer"
475 This is the driver for the hardware watchdog on the W83977F I/O chip
476 as used in AAEON's PCM-5335 SBC (and likely others). This
477 watchdog simply watches your kernel to make sure it doesn't freeze,
478 and if it does, it reboots your computer after a certain amount of
481 To compile this driver as a module, choose M here: the
482 module will be called w83977f_wdt.
485 tristate "ZF MachZ Watchdog"
488 If you are using a ZF Micro MachZ processor, say Y here, otherwise
489 N. This is the driver for the watchdog timer built-in on that
490 processor using ZF-Logic interface. This watchdog simply watches
491 your kernel to make sure it doesn't freeze, and if it does, it
492 reboots your computer after a certain amount of time.
494 To compile this driver as a module, choose M here: the
495 module will be called machzwd.
497 config SBC_EPX_C3_WATCHDOG
498 tristate "Winsystems SBC EPX-C3 watchdog"
501 This is the driver for the built-in watchdog timer on the EPX-C3
502 Single-board computer made by Winsystems, Inc.
504 *Note*: This hardware watchdog is not probeable and thus there
505 is no way to know if writing to its IO address will corrupt
506 your system or have any real effect. The only way to be sure
507 that this driver does what you want is to make sure you
508 are running it on an EPX-C3 from Winsystems with the watchdog
509 timer at IO address 0x1ee and 0x1ef. It will write to both those
510 IO ports. Basically, the assumption is made that if you compile
511 this driver into your kernel and/or load it as a module, that you
512 know what you are doing and that you are in fact running on an
515 To compile this driver as a module, choose M here: the
516 module will be called sbc_epx_c3.
518 # PowerPC Architecture
521 tristate "MPC8xx Watchdog Timer"
525 tristate "MPC83xx Watchdog Timer"
529 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
533 bool "PowerPC Book-E Watchdog Timer"
534 depends on BOOKE || 4xx
536 Please see Documentation/watchdog/watchdog-api.txt for
542 tristate "RTAS watchdog"
545 This driver adds watchdog support for the RTAS watchdog.
547 To compile this driver as a module, choose M here. The module
548 will be called wdrtas.
553 tristate "Indy/I2 Hardware Watchdog"
556 Hardware driver for the Indy's/I2's watchdog. This is a
557 watchdog timer that will reboot the machine after a 60 second
558 timer expired and no process has written to /dev/watchdog during
562 tristate "MTX-1 Hardware Watchdog"
565 Hardware driver for the MTX-1 boards. This is a watchdog timer that
566 will reboot the machine after a 100 seconds timer expired.
569 tristate "RM9000/GPI hardware watchdog"
570 depends on CPU_RM9000
572 Watchdog implementation using the GPI hardware found on
573 PMC-Sierra RM9xxx CPUs.
575 To compile this driver as a module, choose M here: the
576 module will be called rm9k_wdt.
581 tristate "z/VM Watchdog Timer"
584 IBM s/390 and zSeries machines running under z/VM 5.1 or later
585 provide a virtual watchdog timer to their guest that cause a
586 user define Control Program command to be executed after a
589 To compile this driver as a module, choose M here. The module
590 will be called vmwatchdog.
592 # SUPERH Architecture
595 tristate "SuperH Watchdog"
598 This driver adds watchdog support for the integrated watchdog in the
599 SuperH processors. If you have one of these processors and wish
600 to have watchdog support enabled, say Y, otherwise say N.
602 As a side note, saying Y here will automatically boost HZ to 1000
603 so that the timer has a chance to clear the overflow counter. On
604 slower systems (such as the SH-2 and SH-3) this will likely yield
605 some performance issues. As such, the WDT should be avoided here
606 unless it is absolutely necessary.
608 To compile this driver as a module, choose M here: the
609 module will be called shwdt.
612 bool "Allow mmap of SH WDT"
616 If you say Y here, user applications will be able to mmap the
619 # SPARC64 Architecture
621 config WATCHDOG_CP1XXX
622 tristate "CP1XXX Hardware Watchdog support"
623 depends on SPARC64 && PCI
625 This is the driver for the hardware watchdog timers present on
626 Sun Microsystems CompactPCI models CP1400 and CP1500.
628 To compile this driver as a module, choose M here: the
629 module will be called cpwatchdog.
631 If you do not have a CompactPCI model CP1400 or CP1500, or
632 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
633 you should say N to this option.
636 tristate "RIO Hardware Watchdog support"
637 depends on SPARC64 && PCI
639 Say Y here to support the hardware watchdog capability on Sun RIO
640 machines. The watchdog timeout period is normally one minute but
641 can be changed with a boot-time parameter.
644 # ISA-based Watchdog Cards
647 comment "ISA-based Watchdog Cards"
651 tristate "Berkshire Products ISA-PC Watchdog"
654 This is the driver for the Berkshire Products ISA-PC Watchdog card.
655 This card simply watches your kernel to make sure it doesn't freeze,
656 and if it does, it reboots your computer after a certain amount of
657 time. This driver is like the WDT501 driver but for different
658 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
659 watchdog cards can be ordered from <http://www.berkprod.com/>.
661 To compile this driver as a module, choose M here: the
662 module will be called pcwd.
664 Most people will say N.
667 tristate "Mixcom Watchdog"
670 This is a driver for the Mixcom hardware watchdog cards. This
671 watchdog simply watches your kernel to make sure it doesn't freeze,
672 and if it does, it reboots your computer after a certain amount of
675 To compile this driver as a module, choose M here: the
676 module will be called mixcomwd.
678 Most people will say N.
681 tristate "WDT Watchdog timer"
684 If you have a WDT500P or WDT501P watchdog board, say Y here,
685 otherwise N. It is not possible to probe for this board, which means
686 that you have to inform the kernel about the IO port and IRQ that
687 is needed (you can do this via the io and irq parameters)
689 To compile this driver as a module, choose M here: the
690 module will be called wdt.
693 bool "WDT501 features"
696 Saying Y here and creating a character special file /dev/temperature
697 with major number 10 and minor number 131 ("man mknod") will give
698 you a thermometer inside your computer: reading from
699 /dev/temperature yields one byte, the temperature in degrees
700 Fahrenheit. This works only if you have a WDT501P watchdog board
703 If you want to enable the Fan Tachometer on the WDT501P, then you
704 can do this via the tachometer parameter. Only do this if you have a
705 fan tachometer actually set up.
708 # PCI-based Watchdog Cards
711 comment "PCI-based Watchdog Cards"
715 tristate "Berkshire Products PCI-PC Watchdog"
718 This is the driver for the Berkshire Products PCI-PC Watchdog card.
719 This card simply watches your kernel to make sure it doesn't freeze,
720 and if it does, it reboots your computer after a certain amount of
721 time. The card can also monitor the internal temperature of the PC.
722 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
724 To compile this driver as a module, choose M here: the
725 module will be called pcwd_pci.
727 Most people will say N.
730 tristate "PCI-WDT500/501 Watchdog timer"
733 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
735 To compile this driver as a module, choose M here: the
736 module will be called wdt_pci.
739 bool "PCI-WDT501 features"
742 Saying Y here and creating a character special file /dev/temperature
743 with major number 10 and minor number 131 ("man mknod") will give
744 you a thermometer inside your computer: reading from
745 /dev/temperature yields one byte, the temperature in degrees
746 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
749 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
750 can do this via the tachometer parameter. Only do this if you have a
751 fan tachometer actually set up.
754 # USB-based Watchdog Cards
757 comment "USB-based Watchdog Cards"
761 tristate "Berkshire Products USB-PC Watchdog"
764 This is the driver for the Berkshire Products USB-PC Watchdog card.
765 This card simply watches your kernel to make sure it doesn't freeze,
766 and if it does, it reboots your computer after a certain amount of
767 time. The card can also monitor the internal temperature of the PC.
768 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
770 To compile this driver as a module, choose M here: the
771 module will be called pcwd_usb.
773 Most people will say N.