2 # Watchdog device configuration
8 bool "Watchdog Timer Support"
10 If you say Y here (and to one of the following options) and create a
11 character special file /dev/watchdog with major number 10 and minor
12 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13 subsequently opening the file and then failing to write to it for
14 longer than 1 minute will result in rebooting the machine. This
15 could be useful for a networked machine that needs to come back
16 on-line as fast as possible after a lock-up. There's both a watchdog
17 implementation entirely in software (which can sometimes fail to
18 reboot the machine) and a driver for hardware watchdog boards, which
19 are more robust and can also keep track of the temperature inside
20 your computer. For details, read <file:Documentation/watchdog/watchdog.txt>
23 The watchdog is usually used together with the watchdog daemon
24 which is available from
25 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
26 also monitor NFS connections and can reboot the machine when the process
31 config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
35 The default watchdog behaviour (which you get if you say N here) is
36 to stop the timer if the process managing it closes the file
37 /dev/watchdog. It's always remotely possible that this process might
38 get killed. If you say Y here, the watchdog cannot be stopped once
42 # General Watchdog drivers
45 comment "Watchdog Device Drivers"
48 # Architecture Independent
51 tristate "Software watchdog"
54 A software monitoring watchdog. This will fail to reboot your system
55 from some situations that the hardware watchdog will recover
56 from. Equally it's a lot cheaper to install.
58 To compile this driver as a module, choose M here: the
59 module will be called softdog.
63 config AT91RM9200_WATCHDOG
64 tristate "AT91RM9200 watchdog"
65 depends on WATCHDOG && ARCH_AT91RM9200
67 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
68 system when the timeout is reached.
71 tristate "DC21285 watchdog"
72 depends on WATCHDOG && FOOTBRIDGE
74 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
75 here if you wish to use this. Alternatively say M to compile the
76 driver as a module, which will be called wdt285.
78 This driver does not work on all machines. In particular, early CATS
79 boards have hardware problems that will cause the machine to simply
80 lock up if the watchdog fires.
82 "If in doubt, leave it out" - say N.
85 tristate "NetWinder WB83C977 watchdog"
86 depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER
88 Say Y here to include support for the WB977 watchdog included in
89 NetWinder machines. Alternatively say M to compile the driver as
90 a module, which will be called wdt977.
92 Not sure? It's safe to say N.
94 config IXP2000_WATCHDOG
95 tristate "IXP2000 Watchdog"
96 depends on WATCHDOG && ARCH_IXP2000
98 Say Y here if to include support for the watchdog timer
99 in the Intel IXP2000(2400, 2800, 2850) network processors.
100 This driver can be built as a module by choosing M. The module
101 will be called ixp2000_wdt.
103 Say N if you are unsure.
105 config IXP4XX_WATCHDOG
106 tristate "IXP4xx Watchdog"
107 depends on WATCHDOG && ARCH_IXP4XX
109 Say Y here if to include support for the watchdog timer
110 in the Intel IXP4xx network processors. This driver can
111 be built as a module by choosing M. The module will
112 be called ixp4xx_wdt.
114 Note: The internal IXP4xx watchdog does a soft CPU reset
115 which doesn't reset any peripherals. There are circumstances
116 where the watchdog will fail to reset the board correctly
117 (e.g., if the boot ROM is in an unreadable state).
119 Say N if you are unsure.
121 config S3C2410_WATCHDOG
122 tristate "S3C2410 Watchdog"
123 depends on WATCHDOG && ARCH_S3C2410
125 Watchdog timer block in the Samsung S3C2410 chips. This will
126 reboot the system when the timer expires with the watchdog
129 The driver is limited by the speed of the system's PCLK
130 signal, so with reasonably fast systems (PCLK around 50-66MHz)
131 then watchdog intervals of over approximately 20seconds are
134 The driver can be built as a module by choosing M, and will
135 be called s3c2410_wdt
137 config SA1100_WATCHDOG
138 tristate "SA1100/PXA2xx watchdog"
139 depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA )
141 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
142 reboot your system when timeout is reached.
144 NOTE: once enabled, this timer cannot be disabled.
146 To compile this driver as a module, choose M here: the
147 module will be called sa1100_wdt.
149 config MPCORE_WATCHDOG
150 tristate "MPcore watchdog"
151 depends on WATCHDOG && ARM_MPCORE_PLATFORM && LOCAL_TIMERS
153 Watchdog timer embedded into the MPcore system.
155 To compile this driver as a module, choose M here: the
156 module will be called mpcore_wdt.
158 config EP93XX_WATCHDOG
159 tristate "EP93xx Watchdog"
160 depends on WATCHDOG && ARCH_EP93XX
162 Say Y here if to include support for the watchdog timer
163 embedded in the Cirrus Logic EP93xx family of devices.
165 To compile this driver as a module, choose M here: the
166 module will be called ep93xx_wdt.
169 tristate "OMAP Watchdog"
170 depends on WATCHDOG && (ARCH_OMAP16XX || ARCH_OMAP24XX)
172 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
173 enable the OMAP1610/OMAP1710 watchdog timer.
175 config PNX4008_WATCHDOG
176 tristate "PNX4008 Watchdog"
177 depends on WATCHDOG && ARCH_PNX4008
179 Say Y here if to include support for the watchdog timer
180 in the PNX4008 processor.
181 This driver can be built as a module by choosing M. The module
182 will be called pnx4008_wdt.
184 Say N if you are unsure.
186 # X86 (i386 + ia64 + x86_64) Architecture
189 tristate "Acquire SBC Watchdog Timer"
190 depends on WATCHDOG && X86
192 This is the driver for the hardware watchdog on Single Board
193 Computers produced by Acquire Inc (and others). This watchdog
194 simply watches your kernel to make sure it doesn't freeze, and if
195 it does, it reboots your computer after a certain amount of time.
197 To compile this driver as a module, choose M here: the
198 module will be called acquirewdt.
200 Most people will say N.
203 tristate "Advantech SBC Watchdog Timer"
204 depends on WATCHDOG && X86
206 If you are configuring a Linux kernel for the Advantech single-board
207 computer, say `Y' here to support its built-in watchdog timer
208 feature. More information can be found at
209 <http://www.advantech.com.tw/products/>
212 tristate "ALi M1535 PMU Watchdog Timer"
213 depends on WATCHDOG && X86 && PCI
215 This is the driver for the hardware watchdog on the ALi M1535 PMU.
217 To compile this driver as a module, choose M here: the
218 module will be called alim1535_wdt.
220 Most people will say N.
223 tristate "ALi M7101 PMU Computer Watchdog"
224 depends on WATCHDOG && X86 && PCI
226 This is the driver for the hardware watchdog on the ALi M7101 PMU
227 as used in the x86 Cobalt servers.
229 To compile this driver as a module, choose M here: the
230 module will be called alim7101_wdt.
232 Most people will say N.
235 tristate "AMD Elan SC520 processor Watchdog"
236 depends on WATCHDOG && X86
238 This is the driver for the hardware watchdog built in to the
239 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
240 This watchdog simply watches your kernel to make sure it doesn't
241 freeze, and if it does, it reboots your computer after a certain
244 You can compile this driver directly into the kernel, or use
245 it as a module. The module will be called sc520_wdt.
248 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
249 depends on WATCHDOG && X86
251 Enable support for the watchdog timer on the Eurotech CPU-1220 and
252 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
253 information are at <http://www.eurotech.it/>.
256 tristate "IB700 SBC Watchdog Timer"
257 depends on WATCHDOG && X86
259 This is the driver for the hardware watchdog on the IB700 Single
260 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
261 simply watches your kernel to make sure it doesn't freeze, and if
262 it does, it reboots your computer after a certain amount of time.
264 This driver is like the WDT501 driver but for slightly different hardware.
266 To compile this driver as a module, choose M here: the
267 module will be called ib700wdt.
269 Most people will say N.
272 tristate "IBM Automatic Server Restart"
273 depends on WATCHDOG && X86
275 This is the driver for the IBM Automatic Server Restart watchdog
276 timer built-in into some eServer xSeries machines.
278 To compile this driver as a module, choose M here: the
279 module will be called ibmasr.
282 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
283 depends on WATCHDOG && X86
285 This is a driver for the hardware watchdog on the ICP Wafer 5823
286 Single Board Computer (and probably other similar models).
288 To compile this driver as a module, choose M here: the
289 module will be called wafer5823wdt.
292 tristate "Intel 6300ESB Timer/Watchdog"
293 depends on WATCHDOG && X86 && PCI
295 Hardware driver for the watchdog timer built into the Intel
296 6300ESB controller hub.
298 To compile this driver as a module, choose M here: the
299 module will be called i6300esb.
302 tristate "Intel i8xx TCO Timer/Watchdog"
303 depends on WATCHDOG && (X86 || IA64) && PCI
305 Hardware driver for the TCO timer built into the Intel 82801
306 I/O Controller Hub family. The TCO (Total Cost of Ownership)
307 timer is a watchdog timer that will reboot the machine after
308 its second expiration. The expiration time can be configured
309 with the "heartbeat" parameter.
311 On some motherboards the driver may fail to reset the chipset's
312 NO_REBOOT flag which prevents the watchdog from rebooting the
313 machine. If this is the case you will get a kernel message like
314 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
316 To compile this driver as a module, choose M here: the
317 module will be called i8xx_tco.
319 Note: This driver will be removed in the near future. Please
320 use the Intel TCO Timer/Watchdog driver.
323 tristate "Intel TCO Timer/Watchdog"
324 depends on WATCHDOG && (X86 || IA64) && PCI
326 Hardware driver for the intel TCO timer based watchdog devices.
327 These drivers are included in the Intel 82801 I/O Controller
328 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
331 The TCO (Total Cost of Ownership) timer is a watchdog timer
332 that will reboot the machine after its second expiration. The
333 expiration time can be configured with the "heartbeat" parameter.
335 On some motherboards the driver may fail to reset the chipset's
336 NO_REBOOT flag which prevents the watchdog from rebooting the
337 machine. If this is the case you will get a kernel message like
338 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
340 To compile this driver as a module, choose M here: the
341 module will be called iTCO_wdt.
344 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
345 depends on WATCHDOG && X86
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 WATCHDOG && 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 "SBC-60XX Watchdog Timer"
368 depends on WATCHDOG && X86
370 This driver can be used with the watchdog timer found on some
371 single board computers, namely the 6010 PII based computer.
372 It may well work with other cards. It reads port 0x443 to enable
373 and re-set the watchdog timer, and reads port 0x45 to disable
374 the watchdog. If you have a card that behave in similar ways,
375 you can probably make this driver work with your card as well.
377 You can compile this driver directly into the kernel, or use
378 it as a module. The module will be called sbc60xxwdt.
381 tristate "SBC8360 Watchdog Timer"
382 depends on WATCHDOG && X86
385 This is the driver for the hardware watchdog on the SBC8360 Single
386 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
388 To compile this driver as a module, choose M here: the
389 module will be called sbc8360.ko.
391 Most people will say N.
394 tristate "SMA CPU5 Watchdog"
395 depends on WATCHDOG && X86
398 To compile this driver as a module, choose M here: the
399 module will be called cpu5wdt.
401 config SMSC37B787_WDT
402 tristate "Winbond SMsC37B787 Watchdog Timer"
403 depends on WATCHDOG && X86
405 This is the driver for the hardware watchdog component on the
406 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
407 from Vision Systems and maybe others.
409 This watchdog simply watches your kernel to make sure it doesn't
410 freeze, and if it does, it reboots your computer after a certain
413 Usually a userspace daemon will notify the kernel WDT driver that
414 userspace is still alive, at regular intervals.
416 To compile this driver as a module, choose M here: the
417 module will be called smsc37b787_wdt.
419 Most people will say N.
422 tristate "W83627HF Watchdog Timer"
423 depends on WATCHDOG && X86
425 This is the driver for the hardware watchdog on the W83627HF chipset
426 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
427 (and likely others). This watchdog simply watches your kernel to
428 make sure it doesn't freeze, and if it does, it reboots your computer
429 after a certain amount of time.
431 To compile this driver as a module, choose M here: the
432 module will be called w83627hf_wdt.
434 Most people will say N.
437 tristate "W83697HF/W83697HG Watchdog Timer"
438 depends on WATCHDOG && X86
440 This is the driver for the hardware watchdog on the W83697HF/HG
441 chipset as used in Dedibox/VIA motherboards (and likely others).
442 This watchdog simply watches your kernel to make sure it doesn't
443 freeze, and if it does, it reboots your computer after a certain
446 To compile this driver as a module, choose M here: the
447 module will be called w83697hf_wdt.
449 Most people will say N.
452 tristate "W83877F (EMACS) Watchdog Timer"
453 depends on WATCHDOG && X86
455 This is the driver for the hardware watchdog on the W83877F chipset
456 as used in EMACS PC-104 motherboards (and likely others). This
457 watchdog simply watches your kernel to make sure it doesn't freeze,
458 and if it does, it reboots your computer after a certain amount of
461 To compile this driver as a module, choose M here: the
462 module will be called w83877f_wdt.
464 Most people will say N.
467 tristate "W83977F (PCM-5335) Watchdog Timer"
468 depends on WATCHDOG && X86
470 This is the driver for the hardware watchdog on the W83977F I/O chip
471 as used in AAEON's PCM-5335 SBC (and likely others). This
472 watchdog simply watches your kernel to make sure it doesn't freeze,
473 and if it does, it reboots your computer after a certain amount of
476 To compile this driver as a module, choose M here: the
477 module will be called w83977f_wdt.
480 tristate "ZF MachZ Watchdog"
481 depends on WATCHDOG && X86
483 If you are using a ZF Micro MachZ processor, say Y here, otherwise
484 N. This is the driver for the watchdog timer built-in on that
485 processor using ZF-Logic interface. This watchdog simply watches
486 your kernel to make sure it doesn't freeze, and if it does, it
487 reboots your computer after a certain amount of time.
489 To compile this driver as a module, choose M here: the
490 module will be called machzwd.
492 config SBC_EPX_C3_WATCHDOG
493 tristate "Winsystems SBC EPX-C3 watchdog"
494 depends on WATCHDOG && X86
496 This is the driver for the built-in watchdog timer on the EPX-C3
497 Single-board computer made by Winsystems, Inc.
499 *Note*: This hardware watchdog is not probeable and thus there
500 is no way to know if writing to its IO address will corrupt
501 your system or have any real effect. The only way to be sure
502 that this driver does what you want is to make sure you
503 are running it on an EPX-C3 from Winsystems with the watchdog
504 timer at IO address 0x1ee and 0x1ef. It will write to both those
505 IO ports. Basically, the assumption is made that if you compile
506 this driver into your kernel and/or load it as a module, that you
507 know what you are doing and that you are in fact running on an
510 To compile this driver as a module, choose M here: the
511 module will be called sbc_epx_c3.
513 # PowerPC Architecture
516 tristate "MPC8xx Watchdog Timer"
517 depends on WATCHDOG && 8xx
520 tristate "MPC83xx Watchdog Timer"
521 depends on WATCHDOG && PPC_83xx
524 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
525 depends on WATCHDOG && MV64X60
528 tristate "PowerPC Book-E Watchdog Timer"
529 depends on WATCHDOG && (BOOKE || 4xx)
531 Please see Documentation/watchdog/watchdog-api.txt for
537 tristate "RTAS watchdog"
538 depends on WATCHDOG && PPC_RTAS
540 This driver adds watchdog support for the RTAS watchdog.
542 To compile this driver as a module, choose M here. The module
543 will be called wdrtas.
548 tristate "Indy/I2 Hardware Watchdog"
549 depends on WATCHDOG && SGI_IP22
551 Hardware driver for the Indy's/I2's watchdog. This is a
552 watchdog timer that will reboot the machine after a 60 second
553 timer expired and no process has written to /dev/watchdog during
559 tristate "z/VM Watchdog Timer"
560 depends on WATCHDOG && S390
562 IBM s/390 and zSeries machines running under z/VM 5.1 or later
563 provide a virtual watchdog timer to their guest that cause a
564 user define Control Program command to be executed after a
567 To compile this driver as a module, choose M here. The module
568 will be called vmwatchdog.
570 # SUPERH Architecture
573 tristate "SuperH Watchdog"
574 depends on WATCHDOG && SUPERH
576 This driver adds watchdog support for the integrated watchdog in the
577 SuperH processors. If you have one of these processors and wish
578 to have watchdog support enabled, say Y, otherwise say N.
580 As a side note, saying Y here will automatically boost HZ to 1000
581 so that the timer has a chance to clear the overflow counter. On
582 slower systems (such as the SH-2 and SH-3) this will likely yield
583 some performance issues. As such, the WDT should be avoided here
584 unless it is absolutely necessary.
586 To compile this driver as a module, choose M here: the
587 module will be called shwdt.
590 bool "Allow mmap of SH WDT"
594 If you say Y here, user applications will be able to mmap the
597 # SPARC64 Architecture
599 config WATCHDOG_CP1XXX
600 tristate "CP1XXX Hardware Watchdog support"
601 depends on WATCHDOG && SPARC64 && PCI
603 This is the driver for the hardware watchdog timers present on
604 Sun Microsystems CompactPCI models CP1400 and CP1500.
606 To compile this driver as a module, choose M here: the
607 module will be called cpwatchdog.
609 If you do not have a CompactPCI model CP1400 or CP1500, or
610 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
611 you should say N to this option.
614 tristate "RIO Hardware Watchdog support"
615 depends on WATCHDOG && SPARC64 && PCI
617 Say Y here to support the hardware watchdog capability on Sun RIO
618 machines. The watchdog timeout period is normally one minute but
619 can be changed with a boot-time parameter.
622 # ISA-based Watchdog Cards
625 comment "ISA-based Watchdog Cards"
626 depends on WATCHDOG && ISA
629 tristate "Berkshire Products ISA-PC Watchdog"
630 depends on WATCHDOG && ISA
632 This is the driver for the Berkshire Products ISA-PC Watchdog card.
633 This card simply watches your kernel to make sure it doesn't freeze,
634 and if it does, it reboots your computer after a certain amount of
635 time. This driver is like the WDT501 driver but for different
636 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
637 watchdog cards can be ordered from <http://www.berkprod.com/>.
639 To compile this driver as a module, choose M here: the
640 module will be called pcwd.
642 Most people will say N.
645 tristate "Mixcom Watchdog"
646 depends on WATCHDOG && ISA
648 This is a driver for the Mixcom hardware watchdog cards. This
649 watchdog simply watches your kernel to make sure it doesn't freeze,
650 and if it does, it reboots your computer after a certain amount of
653 To compile this driver as a module, choose M here: the
654 module will be called mixcomwd.
656 Most people will say N.
659 tristate "WDT Watchdog timer"
660 depends on WATCHDOG && ISA
662 If you have a WDT500P or WDT501P watchdog board, say Y here,
663 otherwise N. It is not possible to probe for this board, which means
664 that you have to inform the kernel about the IO port and IRQ that
665 is needed (you can do this via the io and irq parameters)
667 To compile this driver as a module, choose M here: the
668 module will be called wdt.
671 bool "WDT501 features"
674 Saying Y here and creating a character special file /dev/temperature
675 with major number 10 and minor number 131 ("man mknod") will give
676 you a thermometer inside your computer: reading from
677 /dev/temperature yields one byte, the temperature in degrees
678 Fahrenheit. This works only if you have a WDT501P watchdog board
681 If you want to enable the Fan Tachometer on the WDT501P, then you
682 can do this via the tachometer parameter. Only do this if you have a
683 fan tachometer actually set up.
686 # PCI-based Watchdog Cards
689 comment "PCI-based Watchdog Cards"
690 depends on WATCHDOG && PCI
693 tristate "Berkshire Products PCI-PC Watchdog"
694 depends on WATCHDOG && PCI
696 This is the driver for the Berkshire Products PCI-PC Watchdog card.
697 This card simply watches your kernel to make sure it doesn't freeze,
698 and if it does, it reboots your computer after a certain amount of
699 time. The card can also monitor the internal temperature of the PC.
700 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
702 To compile this driver as a module, choose M here: the
703 module will be called pcwd_pci.
705 Most people will say N.
708 tristate "PCI-WDT500/501 Watchdog timer"
709 depends on WATCHDOG && PCI
711 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
713 To compile this driver as a module, choose M here: the
714 module will be called wdt_pci.
717 bool "PCI-WDT501 features"
720 Saying Y here and creating a character special file /dev/temperature
721 with major number 10 and minor number 131 ("man mknod") will give
722 you a thermometer inside your computer: reading from
723 /dev/temperature yields one byte, the temperature in degrees
724 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
727 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
728 can do this via the tachometer parameter. Only do this if you have a
729 fan tachometer actually set up.
732 # USB-based Watchdog Cards
735 comment "USB-based Watchdog Cards"
736 depends on WATCHDOG && USB
739 tristate "Berkshire Products USB-PC Watchdog"
740 depends on WATCHDOG && USB
742 This is the driver for the Berkshire Products USB-PC Watchdog card.
743 This card simply watches your kernel to make sure it doesn't freeze,
744 and if it does, it reboots your computer after a certain amount of
745 time. The card can also monitor the internal temperature of the PC.
746 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
748 To compile this driver as a module, choose M here: the
749 module will be called pcwd_usb.
751 Most people will say N.