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.
206 config DAVINCI_WATCHDOG
207 tristate "DaVinci watchdog"
208 depends on WATCHDOG && ARCH_DAVINCI
210 Say Y here if to include support for the watchdog timer
211 in the DaVinci DM644x/DM646x processors.
212 To compile this driver as a module, choose M here: the
213 module will be called davinci_wdt.
215 NOTE: once enabled, this timer cannot be disabled.
216 Say N if you are unsure.
220 config AT32AP700X_WDT
221 tristate "AT32AP700x watchdog"
222 depends on WATCHDOG && CPU_AT32AP7000
224 Watchdog timer embedded into AT32AP700x devices. This will reboot
225 your system when the timeout is reached.
227 # Blackfin Architecture
230 tristate "Blackfin On-Chip Watchdog Timer"
231 depends on WATCHDOG && BLACKFIN
233 If you say yes here you will get support for the Blackfin On-Chip
234 Watchdog Timer. If you have one of these processors and wish to
235 have watchdog support enabled, say Y, otherwise say N.
237 To compile this driver as a module, choose M here: the
238 module will be called bfin_wdt.
240 # X86 (i386 + ia64 + x86_64) Architecture
243 tristate "Acquire SBC Watchdog Timer"
246 This is the driver for the hardware watchdog on Single Board
247 Computers produced by Acquire Inc (and others). This watchdog
248 simply watches your kernel to make sure it doesn't freeze, and if
249 it does, it reboots your computer after a certain amount of time.
251 To compile this driver as a module, choose M here: the
252 module will be called acquirewdt.
254 Most people will say N.
257 tristate "Advantech SBC Watchdog Timer"
260 If you are configuring a Linux kernel for the Advantech single-board
261 computer, say `Y' here to support its built-in watchdog timer
262 feature. More information can be found at
263 <http://www.advantech.com.tw/products/>
266 tristate "ALi M1535 PMU Watchdog Timer"
267 depends on X86 && PCI
269 This is the driver for the hardware watchdog on the ALi M1535 PMU.
271 To compile this driver as a module, choose M here: the
272 module will be called alim1535_wdt.
274 Most people will say N.
277 tristate "ALi M7101 PMU Computer Watchdog"
278 depends on X86 && PCI
280 This is the driver for the hardware watchdog on the ALi M7101 PMU
281 as used in the x86 Cobalt servers.
283 To compile this driver as a module, choose M here: the
284 module will be called alim7101_wdt.
286 Most people will say N.
289 tristate "AMD Elan SC520 processor Watchdog"
292 This is the driver for the hardware watchdog built in to the
293 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
294 This watchdog simply watches your kernel to make sure it doesn't
295 freeze, and if it does, it reboots your computer after a certain
298 You can compile this driver directly into the kernel, or use
299 it as a module. The module will be called sc520_wdt.
302 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
305 Enable support for the watchdog timer on the Eurotech CPU-1220 and
306 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
307 information are at <http://www.eurotech.it/>.
310 tristate "IB700 SBC Watchdog Timer"
313 This is the driver for the hardware watchdog on the IB700 Single
314 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
315 simply watches your kernel to make sure it doesn't freeze, and if
316 it does, it reboots your computer after a certain amount of time.
318 This driver is like the WDT501 driver but for slightly different hardware.
320 To compile this driver as a module, choose M here: the
321 module will be called ib700wdt.
323 Most people will say N.
326 tristate "IBM Automatic Server Restart"
329 This is the driver for the IBM Automatic Server Restart watchdog
330 timer built-in into some eServer xSeries machines.
332 To compile this driver as a module, choose M here: the
333 module will be called ibmasr.
336 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
339 This is a driver for the hardware watchdog on the ICP Wafer 5823
340 Single Board Computer (and probably other similar models).
342 To compile this driver as a module, choose M here: the
343 module will be called wafer5823wdt.
346 tristate "Intel 6300ESB Timer/Watchdog"
347 depends on X86 && PCI
349 Hardware driver for the watchdog timer built into the Intel
350 6300ESB controller hub.
352 To compile this driver as a module, choose M here: the
353 module will be called i6300esb.
356 tristate "Intel TCO Timer/Watchdog"
357 depends on (X86 || IA64) && PCI
359 Hardware driver for the intel TCO timer based watchdog devices.
360 These drivers are included in the Intel 82801 I/O Controller
361 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
364 The TCO (Total Cost of Ownership) timer is a watchdog timer
365 that will reboot the machine after its second expiration. The
366 expiration time can be configured with the "heartbeat" parameter.
368 On some motherboards the driver may fail to reset the chipset's
369 NO_REBOOT flag which prevents the watchdog from rebooting the
370 machine. If this is the case you will get a kernel message like
371 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
373 To compile this driver as a module, choose M here: the
374 module will be called iTCO_wdt.
376 config ITCO_VENDOR_SUPPORT
377 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
380 Add vendor specific support to the intel TCO timer based watchdog
381 devices. At this moment we only have additional support for some
382 SuperMicro Inc. motherboards.
385 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
388 This is a driver for National Semiconductor PC87307/PC97307 hardware
389 watchdog cards as found on the SC1200. This watchdog is mainly used
390 for power management purposes and can be used to power down the device
391 during inactivity periods (includes interrupt activity monitoring).
393 To compile this driver as a module, choose M here: the
394 module will be called sc1200wdt.
396 Most people will say N.
399 tristate "National Semiconductor SCx200 Watchdog"
400 depends on SCx200 && PCI
402 Enable the built-in watchdog timer support on the National
403 Semiconductor SCx200 processors.
405 If compiled as a module, it will be called scx200_wdt.
408 tristate "NS PC87413 watchdog"
411 This is the driver for the hardware watchdog on the PC87413 chipset
412 This watchdog simply watches your kernel to make sure it doesn't
413 freeze, and if it does, it reboots your computer after a certain
416 To compile this driver as a module, choose M here: the
417 module will be called pc87413_wdt.
419 Most people will say N.
422 tristate "SBC-60XX Watchdog Timer"
425 This driver can be used with the watchdog timer found on some
426 single board computers, namely the 6010 PII based computer.
427 It may well work with other cards. It reads port 0x443 to enable
428 and re-set the watchdog timer, and reads port 0x45 to disable
429 the watchdog. If you have a card that behave in similar ways,
430 you can probably make this driver work with your card as well.
432 You can compile this driver directly into the kernel, or use
433 it as a module. The module will be called sbc60xxwdt.
436 tristate "SBC8360 Watchdog Timer"
440 This is the driver for the hardware watchdog on the SBC8360 Single
441 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
443 To compile this driver as a module, choose M here: the
444 module will be called sbc8360.ko.
446 Most people will say N.
449 tristate "SMA CPU5 Watchdog"
453 To compile this driver as a module, choose M here: the
454 module will be called cpu5wdt.
456 config SMSC37B787_WDT
457 tristate "Winbond SMsC37B787 Watchdog Timer"
460 This is the driver for the hardware watchdog component on the
461 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
462 from Vision Systems and maybe others.
464 This watchdog simply watches your kernel to make sure it doesn't
465 freeze, and if it does, it reboots your computer after a certain
468 Usually a userspace daemon will notify the kernel WDT driver that
469 userspace is still alive, at regular intervals.
471 To compile this driver as a module, choose M here: the
472 module will be called smsc37b787_wdt.
474 Most people will say N.
477 tristate "W83627HF Watchdog Timer"
480 This is the driver for the hardware watchdog on the W83627HF chipset
481 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
482 (and likely others). This watchdog simply watches your kernel to
483 make sure it doesn't freeze, and if it does, it reboots your computer
484 after a certain amount of time.
486 To compile this driver as a module, choose M here: the
487 module will be called w83627hf_wdt.
489 Most people will say N.
492 tristate "W83697HF/W83697HG Watchdog Timer"
495 This is the driver for the hardware watchdog on the W83697HF/HG
496 chipset as used in Dedibox/VIA motherboards (and likely others).
497 This watchdog simply watches your kernel to make sure it doesn't
498 freeze, and if it does, it reboots your computer after a certain
501 To compile this driver as a module, choose M here: the
502 module will be called w83697hf_wdt.
504 Most people will say N.
507 tristate "W83877F (EMACS) Watchdog Timer"
510 This is the driver for the hardware watchdog on the W83877F chipset
511 as used in EMACS PC-104 motherboards (and likely others). This
512 watchdog simply watches your kernel to make sure it doesn't freeze,
513 and if it does, it reboots your computer after a certain amount of
516 To compile this driver as a module, choose M here: the
517 module will be called w83877f_wdt.
519 Most people will say N.
522 tristate "W83977F (PCM-5335) Watchdog Timer"
525 This is the driver for the hardware watchdog on the W83977F I/O chip
526 as used in AAEON's PCM-5335 SBC (and likely others). This
527 watchdog simply watches your kernel to make sure it doesn't freeze,
528 and if it does, it reboots your computer after a certain amount of
531 To compile this driver as a module, choose M here: the
532 module will be called w83977f_wdt.
535 tristate "ZF MachZ Watchdog"
538 If you are using a ZF Micro MachZ processor, say Y here, otherwise
539 N. This is the driver for the watchdog timer built-in on that
540 processor using ZF-Logic interface. This watchdog simply watches
541 your kernel to make sure it doesn't freeze, and if it does, it
542 reboots your computer after a certain amount of time.
544 To compile this driver as a module, choose M here: the
545 module will be called machzwd.
547 config SBC_EPX_C3_WATCHDOG
548 tristate "Winsystems SBC EPX-C3 watchdog"
551 This is the driver for the built-in watchdog timer on the EPX-C3
552 Single-board computer made by Winsystems, Inc.
554 *Note*: This hardware watchdog is not probeable and thus there
555 is no way to know if writing to its IO address will corrupt
556 your system or have any real effect. The only way to be sure
557 that this driver does what you want is to make sure you
558 are running it on an EPX-C3 from Winsystems with the watchdog
559 timer at IO address 0x1ee and 0x1ef. It will write to both those
560 IO ports. Basically, the assumption is made that if you compile
561 this driver into your kernel and/or load it as a module, that you
562 know what you are doing and that you are in fact running on an
565 To compile this driver as a module, choose M here: the
566 module will be called sbc_epx_c3.
568 # PowerPC Architecture
571 tristate "MPC8xx Watchdog Timer"
575 tristate "MPC5200 Watchdog Timer"
576 depends on PPC_MPC52xx
579 tristate "MPC83xx Watchdog Timer"
583 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
587 bool "PowerPC Book-E Watchdog Timer"
588 depends on BOOKE || 4xx
590 Please see Documentation/watchdog/watchdog-api.txt for
596 tristate "RTAS watchdog"
599 This driver adds watchdog support for the RTAS watchdog.
601 To compile this driver as a module, choose M here. The module
602 will be called wdrtas.
607 tristate "Indy/I2 Hardware Watchdog"
610 Hardware driver for the Indy's/I2's watchdog. This is a
611 watchdog timer that will reboot the machine after a 60 second
612 timer expired and no process has written to /dev/watchdog during
616 tristate "MTX-1 Hardware Watchdog"
619 Hardware driver for the MTX-1 boards. This is a watchdog timer that
620 will reboot the machine after a 100 seconds timer expired.
623 tristate "RM9000/GPI hardware watchdog"
624 depends on CPU_RM9000
626 Watchdog implementation using the GPI hardware found on
627 PMC-Sierra RM9xxx CPUs.
629 To compile this driver as a module, choose M here: the
630 module will be called rm9k_wdt.
635 tristate "z/VM Watchdog Timer"
638 IBM s/390 and zSeries machines running under z/VM 5.1 or later
639 provide a virtual watchdog timer to their guest that cause a
640 user define Control Program command to be executed after a
643 To compile this driver as a module, choose M here. The module
644 will be called vmwatchdog.
646 # SUPERH Architecture
649 tristate "SuperH Watchdog"
650 depends on SUPERH && (CPU_SH3 || CPU_SH4)
652 This driver adds watchdog support for the integrated watchdog in the
653 SuperH processors. If you have one of these processors and wish
654 to have watchdog support enabled, say Y, otherwise say N.
656 As a side note, saying Y here will automatically boost HZ to 1000
657 so that the timer has a chance to clear the overflow counter. On
658 slower systems (such as the SH-2 and SH-3) this will likely yield
659 some performance issues. As such, the WDT should be avoided here
660 unless it is absolutely necessary.
662 To compile this driver as a module, choose M here: the
663 module will be called shwdt.
666 bool "Allow mmap of SH WDT"
670 If you say Y here, user applications will be able to mmap the
673 # SPARC64 Architecture
675 config WATCHDOG_CP1XXX
676 tristate "CP1XXX Hardware Watchdog support"
677 depends on SPARC64 && PCI
679 This is the driver for the hardware watchdog timers present on
680 Sun Microsystems CompactPCI models CP1400 and CP1500.
682 To compile this driver as a module, choose M here: the
683 module will be called cpwatchdog.
685 If you do not have a CompactPCI model CP1400 or CP1500, or
686 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
687 you should say N to this option.
690 tristate "RIO Hardware Watchdog support"
691 depends on SPARC64 && PCI
693 Say Y here to support the hardware watchdog capability on Sun RIO
694 machines. The watchdog timeout period is normally one minute but
695 can be changed with a boot-time parameter.
698 # ISA-based Watchdog Cards
701 comment "ISA-based Watchdog Cards"
705 tristate "Berkshire Products ISA-PC Watchdog"
708 This is the driver for the Berkshire Products ISA-PC Watchdog card.
709 This card simply watches your kernel to make sure it doesn't freeze,
710 and if it does, it reboots your computer after a certain amount of
711 time. This driver is like the WDT501 driver but for different
712 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
713 watchdog cards can be ordered from <http://www.berkprod.com/>.
715 To compile this driver as a module, choose M here: the
716 module will be called pcwd.
718 Most people will say N.
721 tristate "Mixcom Watchdog"
724 This is a driver for the Mixcom hardware watchdog cards. This
725 watchdog simply watches your kernel to make sure it doesn't freeze,
726 and if it does, it reboots your computer after a certain amount of
729 To compile this driver as a module, choose M here: the
730 module will be called mixcomwd.
732 Most people will say N.
735 tristate "WDT Watchdog timer"
738 If you have a WDT500P or WDT501P watchdog board, say Y here,
739 otherwise N. It is not possible to probe for this board, which means
740 that you have to inform the kernel about the IO port and IRQ that
741 is needed (you can do this via the io and irq parameters)
743 To compile this driver as a module, choose M here: the
744 module will be called wdt.
747 bool "WDT501 features"
750 Saying Y here and creating a character special file /dev/temperature
751 with major number 10 and minor number 131 ("man mknod") will give
752 you a thermometer inside your computer: reading from
753 /dev/temperature yields one byte, the temperature in degrees
754 Fahrenheit. This works only if you have a WDT501P watchdog board
757 If you want to enable the Fan Tachometer on the WDT501P, then you
758 can do this via the tachometer parameter. Only do this if you have a
759 fan tachometer actually set up.
762 # PCI-based Watchdog Cards
765 comment "PCI-based Watchdog Cards"
769 tristate "Berkshire Products PCI-PC Watchdog"
772 This is the driver for the Berkshire Products PCI-PC Watchdog card.
773 This card simply watches your kernel to make sure it doesn't freeze,
774 and if it does, it reboots your computer after a certain amount of
775 time. The card can also monitor the internal temperature of the PC.
776 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
778 To compile this driver as a module, choose M here: the
779 module will be called pcwd_pci.
781 Most people will say N.
784 tristate "PCI-WDT500/501 Watchdog timer"
787 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
789 To compile this driver as a module, choose M here: the
790 module will be called wdt_pci.
793 bool "PCI-WDT501 features"
796 Saying Y here and creating a character special file /dev/temperature
797 with major number 10 and minor number 131 ("man mknod") will give
798 you a thermometer inside your computer: reading from
799 /dev/temperature yields one byte, the temperature in degrees
800 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
803 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
804 can do this via the tachometer parameter. Only do this if you have a
805 fan tachometer actually set up.
808 # USB-based Watchdog Cards
811 comment "USB-based Watchdog Cards"
815 tristate "Berkshire Products USB-PC Watchdog"
818 This is the driver for the Berkshire Products USB-PC Watchdog card.
819 This card simply watches your kernel to make sure it doesn't freeze,
820 and if it does, it reboots your computer after a certain amount of
821 time. The card can also monitor the internal temperature of the PC.
822 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
824 To compile this driver as a module, choose M here: the
825 module will be called pcwd_usb.
827 Most people will say N.