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 online 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.
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 builtin 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 # X86 (i386 + ia64 + x86_64) Architecture
178 tristate "Acquire SBC Watchdog Timer"
179 depends on WATCHDOG && X86
181 This is the driver for the hardware watchdog on Single Board
182 Computers produced by Acquire Inc (and others). This watchdog
183 simply watches your kernel to make sure it doesn't freeze, and if
184 it does, it reboots your computer after a certain amount of time.
186 To compile this driver as a module, choose M here: the
187 module will be called acquirewdt.
189 Most people will say N.
192 tristate "Advantech SBC Watchdog Timer"
193 depends on WATCHDOG && X86
195 If you are configuring a Linux kernel for the Advantech single-board
196 computer, say `Y' here to support its built-in watchdog timer
197 feature. More information can be found at
198 <http://www.advantech.com.tw/products/>
201 tristate "ALi M1535 PMU Watchdog Timer"
202 depends on WATCHDOG && X86 && PCI
204 This is the driver for the hardware watchdog on the ALi M1535 PMU.
206 To compile this driver as a module, choose M here: the
207 module will be called alim1535_wdt.
209 Most people will say N.
212 tristate "ALi M7101 PMU Computer Watchdog"
213 depends on WATCHDOG && X86 && PCI
215 This is the driver for the hardware watchdog on the ALi M7101 PMU
216 as used in the x86 Cobalt servers.
218 To compile this driver as a module, choose M here: the
219 module will be called alim7101_wdt.
221 Most people will say N.
224 tristate "AMD Elan SC520 processor Watchdog"
225 depends on WATCHDOG && X86
227 This is the driver for the hardware watchdog built in to the
228 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
229 This watchdog simply watches your kernel to make sure it doesn't
230 freeze, and if it does, it reboots your computer after a certain
233 You can compile this driver directly into the kernel, or use
234 it as a module. The module will be called sc520_wdt.
237 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
238 depends on WATCHDOG && X86
240 Enable support for the watchdog timer on the Eurotech CPU-1220 and
241 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
242 information are at <http://www.eurotech.it/>.
245 tristate "IB700 SBC Watchdog Timer"
246 depends on WATCHDOG && X86
248 This is the driver for the hardware watchdog on the IB700 Single
249 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
250 simply watches your kernel to make sure it doesn't freeze, and if
251 it does, it reboots your computer after a certain amount of time.
253 This driver is like the WDT501 driver but for slightly different hardware.
255 To compile this driver as a module, choose M here: the
256 module will be called ib700wdt.
258 Most people will say N.
261 tristate "IBM Automatic Server Restart"
262 depends on WATCHDOG && X86
264 This is the driver for the IBM Automatic Server Restart watchdog
265 timer builtin into some eServer xSeries machines.
267 To compile this driver as a module, choose M here: the
268 module will be called ibmasr.
271 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
272 depends on WATCHDOG && X86
274 This is a driver for the hardware watchdog on the ICP Wafer 5823
275 Single Board Computer (and probably other similar models).
277 To compile this driver as a module, choose M here: the
278 module will be called wafer5823wdt.
281 tristate "Intel 6300ESB Timer/Watchdog"
282 depends on WATCHDOG && X86 && PCI
284 Hardware driver for the watchdog timer built into the Intel
285 6300ESB controller hub.
287 To compile this driver as a module, choose M here: the
288 module will be called i6300esb.
291 tristate "Intel i8xx TCO Timer/Watchdog"
292 depends on WATCHDOG && (X86 || IA64) && PCI
294 Hardware driver for the TCO timer built into the Intel 82801
295 I/O Controller Hub family. The TCO (Total Cost of Ownership)
296 timer is a watchdog timer that will reboot the machine after
297 its second expiration. The expiration time can be configured
298 with the "heartbeat" parameter.
300 On some motherboards the driver may fail to reset the chipset's
301 NO_REBOOT flag which prevents the watchdog from rebooting the
302 machine. If this is the case you will get a kernel message like
303 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
305 To compile this driver as a module, choose M here: the
306 module will be called i8xx_tco.
309 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
310 depends on WATCHDOG && X86
312 This is a driver for National Semiconductor PC87307/PC97307 hardware
313 watchdog cards as found on the SC1200. This watchdog is mainly used
314 for power management purposes and can be used to power down the device
315 during inactivity periods (includes interrupt activity monitoring).
317 To compile this driver as a module, choose M here: the
318 module will be called sc1200wdt.
320 Most people will say N.
323 tristate "National Semiconductor SCx200 Watchdog"
324 depends on WATCHDOG && SCx200 && PCI
326 Enable the built-in watchdog timer support on the National
327 Semiconductor SCx200 processors.
329 If compiled as a module, it will be called scx200_wdt.
332 tristate "SBC-60XX Watchdog Timer"
333 depends on WATCHDOG && X86
335 This driver can be used with the watchdog timer found on some
336 single board computers, namely the 6010 PII based computer.
337 It may well work with other cards. It reads port 0x443 to enable
338 and re-set the watchdog timer, and reads port 0x45 to disable
339 the watchdog. If you have a card that behave in similar ways,
340 you can probably make this driver work with your card as well.
342 You can compile this driver directly into the kernel, or use
343 it as a module. The module will be called sbc60xxwdt.
346 tristate "SBC8360 Watchdog Timer"
347 depends on WATCHDOG && X86
350 This is the driver for the hardware watchdog on the SBC8360 Single
351 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
353 To compile this driver as a module, choose M here: the
354 module will be called sbc8360.ko.
356 Most people will say N.
359 tristate "SMA CPU5 Watchdog"
360 depends on WATCHDOG && X86
363 To compile this driver as a module, choose M here: the
364 module will be called cpu5wdt.
367 tristate "W83627HF Watchdog Timer"
368 depends on WATCHDOG && X86
370 This is the driver for the hardware watchdog on the W83627HF chipset
371 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
372 (and likely others). This watchdog simply watches your kernel to
373 make sure it doesn't freeze, and if it does, it reboots your computer
374 after a certain amount of time.
376 To compile this driver as a module, choose M here: the
377 module will be called w83627hf_wdt.
379 Most people will say N.
382 tristate "W83877F (EMACS) Watchdog Timer"
383 depends on WATCHDOG && X86
385 This is the driver for the hardware watchdog on the W83877F chipset
386 as used in EMACS PC-104 motherboards (and likely others). This
387 watchdog simply watches your kernel to make sure it doesn't freeze,
388 and if it does, it reboots your computer after a certain amount of
391 To compile this driver as a module, choose M here: the
392 module will be called w83877f_wdt.
394 Most people will say N.
397 tristate "W83977F (PCM-5335) Watchdog Timer"
398 depends on WATCHDOG && X86
400 This is the driver for the hardware watchdog on the W83977F I/O chip
401 as used in AAEON's PCM-5335 SBC (and likely others). This
402 watchdog simply watches your kernel to make sure it doesn't freeze,
403 and if it does, it reboots your computer after a certain amount of
406 To compile this driver as a module, choose M here: the
407 module will be called w83977f_wdt.
410 tristate "ZF MachZ Watchdog"
411 depends on WATCHDOG && X86
413 If you are using a ZF Micro MachZ processor, say Y here, otherwise
414 N. This is the driver for the watchdog timer builtin on that
415 processor using ZF-Logic interface. This watchdog simply watches
416 your kernel to make sure it doesn't freeze, and if it does, it
417 reboots your computer after a certain amount of time.
419 To compile this driver as a module, choose M here: the
420 module will be called machzwd.
422 config SBC_EPX_C3_WATCHDOG
423 tristate "Winsystems SBC EPX-C3 watchdog"
424 depends on WATCHDOG && X86
426 This is the driver for the built-in watchdog timer on the EPX-C3
427 Single-board computer made by Winsystems, Inc.
429 *Note*: This hardware watchdog is not probeable and thus there
430 is no way to know if writing to its IO address will corrupt
431 your system or have any real effect. The only way to be sure
432 that this driver does what you want is to make sure you
433 are running it on an EPX-C3 from Winsystems with the watchdog
434 timer at IO address 0x1ee and 0x1ef. It will write to both those
435 IO ports. Basically, the assumption is made that if you compile
436 this driver into your kernel and/or load it as a module, that you
437 know what you are doing and that you are in fact running on an
440 To compile this driver as a module, choose M here: the
441 module will be called sbc_epx_c3.
444 # PowerPC Architecture
447 tristate "MPC8xx Watchdog Timer"
448 depends on WATCHDOG && 8xx
451 tristate "MPC83xx Watchdog Timer"
452 depends on WATCHDOG && PPC_83xx
455 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
456 depends on WATCHDOG && MV64X60
459 tristate "PowerPC Book-E Watchdog Timer"
460 depends on WATCHDOG && (BOOKE || 4xx)
462 Please see Documentation/watchdog/watchdog-api.txt for
468 tristate "RTAS watchdog"
469 depends on WATCHDOG && PPC_RTAS
471 This driver adds watchdog support for the RTAS watchdog.
473 To compile this driver as a module, choose M here. The module
474 will be called wdrtas.
479 tristate "Indy/I2 Hardware Watchdog"
480 depends on WATCHDOG && SGI_IP22
482 Hardware driver for the Indy's/I2's watchdog. This is a
483 watchdog timer that will reboot the machine after a 60 second
484 timer expired and no process has written to /dev/watchdog during
490 tristate "z/VM Watchdog Timer"
491 depends on WATCHDOG && S390
493 IBM s/390 and zSeries machines running under z/VM 5.1 or later
494 provide a virtual watchdog timer to their guest that cause a
495 user define Control Program command to be executed after a
498 To compile this driver as a module, choose M here. The module
499 will be called vmwatchdog.
501 # SUPERH Architecture
504 tristate "SuperH Watchdog"
505 depends on WATCHDOG && SUPERH
507 This driver adds watchdog support for the integrated watchdog in the
508 SuperH processors. If you have one of these processors and wish
509 to have watchdog support enabled, say Y, otherwise say N.
511 As a side note, saying Y here will automatically boost HZ to 1000
512 so that the timer has a chance to clear the overflow counter. On
513 slower systems (such as the SH-2 and SH-3) this will likely yield
514 some performance issues. As such, the WDT should be avoided here
515 unless it is absolutely necessary.
517 To compile this driver as a module, choose M here: the
518 module will be called shwdt.
521 bool "Allow mmap of SH WDT"
525 If you say Y here, user applications will be able to mmap the
528 # SPARC64 Architecture
530 config WATCHDOG_CP1XXX
531 tristate "CP1XXX Hardware Watchdog support"
532 depends on WATCHDOG && SPARC64 && PCI
534 This is the driver for the hardware watchdog timers present on
535 Sun Microsystems CompactPCI models CP1400 and CP1500.
537 To compile this driver as a module, choose M here: the
538 module will be called cpwatchdog.
540 If you do not have a CompactPCI model CP1400 or CP1500, or
541 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
542 you should say N to this option.
545 tristate "RIO Hardware Watchdog support"
546 depends on WATCHDOG && SPARC64 && PCI
548 Say Y here to support the hardware watchdog capability on Sun RIO
549 machines. The watchdog timeout period is normally one minute but
550 can be changed with a boot-time parameter.
553 # ISA-based Watchdog Cards
556 comment "ISA-based Watchdog Cards"
557 depends on WATCHDOG && ISA
560 tristate "Berkshire Products ISA-PC Watchdog"
561 depends on WATCHDOG && ISA
563 This is the driver for the Berkshire Products ISA-PC Watchdog card.
564 This card simply watches your kernel to make sure it doesn't freeze,
565 and if it does, it reboots your computer after a certain amount of
566 time. This driver is like the WDT501 driver but for different
567 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
568 watchdog cards can be ordered from <http://www.berkprod.com/>.
570 To compile this driver as a module, choose M here: the
571 module will be called pcwd.
573 Most people will say N.
576 tristate "Mixcom Watchdog"
577 depends on WATCHDOG && ISA
579 This is a driver for the Mixcom hardware watchdog cards. This
580 watchdog simply watches your kernel to make sure it doesn't freeze,
581 and if it does, it reboots your computer after a certain amount of
584 To compile this driver as a module, choose M here: the
585 module will be called mixcomwd.
587 Most people will say N.
590 tristate "WDT Watchdog timer"
591 depends on WATCHDOG && ISA
593 If you have a WDT500P or WDT501P watchdog board, say Y here,
594 otherwise N. It is not possible to probe for this board, which means
595 that you have to inform the kernel about the IO port and IRQ that
596 is needed (you can do this via the io and irq parameters)
598 To compile this driver as a module, choose M here: the
599 module will be called wdt.
602 bool "WDT501 features"
605 Saying Y here and creating a character special file /dev/temperature
606 with major number 10 and minor number 131 ("man mknod") will give
607 you a thermometer inside your computer: reading from
608 /dev/temperature yields one byte, the temperature in degrees
609 Fahrenheit. This works only if you have a WDT501P watchdog board
612 If you want to enable the Fan Tachometer on the WDT501P, then you
613 can do this via the tachometer parameter. Only do this if you have a
614 fan tachometer actually set up.
617 # PCI-based Watchdog Cards
620 comment "PCI-based Watchdog Cards"
621 depends on WATCHDOG && PCI
624 tristate "Berkshire Products PCI-PC Watchdog"
625 depends on WATCHDOG && PCI
627 This is the driver for the Berkshire Products PCI-PC Watchdog card.
628 This card simply watches your kernel to make sure it doesn't freeze,
629 and if it does, it reboots your computer after a certain amount of
630 time. The card can also monitor the internal temperature of the PC.
631 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
633 To compile this driver as a module, choose M here: the
634 module will be called pcwd_pci.
636 Most people will say N.
639 tristate "PCI-WDT500/501 Watchdog timer"
640 depends on WATCHDOG && PCI
642 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
644 To compile this driver as a module, choose M here: the
645 module will be called wdt_pci.
648 bool "PCI-WDT501 features"
651 Saying Y here and creating a character special file /dev/temperature
652 with major number 10 and minor number 131 ("man mknod") will give
653 you a thermometer inside your computer: reading from
654 /dev/temperature yields one byte, the temperature in degrees
655 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
658 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
659 can do this via the tachometer parameter. Only do this if you have a
660 fan tachometer actually set up.
663 # USB-based Watchdog Cards
666 comment "USB-based Watchdog Cards"
667 depends on WATCHDOG && USB
670 tristate "Berkshire Products USB-PC Watchdog"
671 depends on WATCHDOG && USB
673 This is the driver for the Berkshire Products USB-PC Watchdog card.
674 This card simply watches your kernel to make sure it doesn't freeze,
675 and if it does, it reboots your computer after a certain amount of
676 time. The card can also monitor the internal temperature of the PC.
677 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
679 To compile this driver as a module, choose M here: the
680 module will be called pcwd_usb.
682 Most people will say N.