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.
208 config AT32AP700X_WDT
209 tristate "AT32AP700x watchdog"
210 depends on WATCHDOG && CPU_AT32AP7000
212 Watchdog timer embedded into AT32AP700x devices. This will reboot
213 your system when the timeout is reached.
215 # Blackfin Architecture
218 tristate "Blackfin On-Chip Watchdog Timer"
219 depends on WATCHDOG && BLACKFIN
221 If you say yes here you will get support for the Blackfin On-Chip
222 Watchdog Timer. If you have one of these processors and wish to
223 have watchdog support enabled, say Y, otherwise say N.
225 To compile this driver as a module, choose M here: the
226 module will be called bfin_wdt.
228 # X86 (i386 + ia64 + x86_64) Architecture
231 tristate "Acquire SBC Watchdog Timer"
234 This is the driver for the hardware watchdog on Single Board
235 Computers produced by Acquire Inc (and others). This watchdog
236 simply watches your kernel to make sure it doesn't freeze, and if
237 it does, it reboots your computer after a certain amount of time.
239 To compile this driver as a module, choose M here: the
240 module will be called acquirewdt.
242 Most people will say N.
245 tristate "Advantech SBC Watchdog Timer"
248 If you are configuring a Linux kernel for the Advantech single-board
249 computer, say `Y' here to support its built-in watchdog timer
250 feature. More information can be found at
251 <http://www.advantech.com.tw/products/>
254 tristate "ALi M1535 PMU Watchdog Timer"
255 depends on X86 && PCI
257 This is the driver for the hardware watchdog on the ALi M1535 PMU.
259 To compile this driver as a module, choose M here: the
260 module will be called alim1535_wdt.
262 Most people will say N.
265 tristate "ALi M7101 PMU Computer Watchdog"
266 depends on X86 && PCI
268 This is the driver for the hardware watchdog on the ALi M7101 PMU
269 as used in the x86 Cobalt servers.
271 To compile this driver as a module, choose M here: the
272 module will be called alim7101_wdt.
274 Most people will say N.
277 tristate "AMD Elan SC520 processor Watchdog"
280 This is the driver for the hardware watchdog built in to the
281 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
282 This watchdog simply watches your kernel to make sure it doesn't
283 freeze, and if it does, it reboots your computer after a certain
286 You can compile this driver directly into the kernel, or use
287 it as a module. The module will be called sc520_wdt.
290 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
293 Enable support for the watchdog timer on the Eurotech CPU-1220 and
294 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
295 information are at <http://www.eurotech.it/>.
298 tristate "IB700 SBC Watchdog Timer"
301 This is the driver for the hardware watchdog on the IB700 Single
302 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
303 simply watches your kernel to make sure it doesn't freeze, and if
304 it does, it reboots your computer after a certain amount of time.
306 This driver is like the WDT501 driver but for slightly different hardware.
308 To compile this driver as a module, choose M here: the
309 module will be called ib700wdt.
311 Most people will say N.
314 tristate "IBM Automatic Server Restart"
317 This is the driver for the IBM Automatic Server Restart watchdog
318 timer built-in into some eServer xSeries machines.
320 To compile this driver as a module, choose M here: the
321 module will be called ibmasr.
324 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
327 This is a driver for the hardware watchdog on the ICP Wafer 5823
328 Single Board Computer (and probably other similar models).
330 To compile this driver as a module, choose M here: the
331 module will be called wafer5823wdt.
334 tristate "Intel 6300ESB Timer/Watchdog"
335 depends on X86 && PCI
337 Hardware driver for the watchdog timer built into the Intel
338 6300ESB controller hub.
340 To compile this driver as a module, choose M here: the
341 module will be called i6300esb.
344 tristate "Intel TCO Timer/Watchdog"
345 depends on (X86 || IA64) && PCI
347 Hardware driver for the intel TCO timer based watchdog devices.
348 These drivers are included in the Intel 82801 I/O Controller
349 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
352 The TCO (Total Cost of Ownership) timer is a watchdog timer
353 that will reboot the machine after its second expiration. The
354 expiration time can be configured with the "heartbeat" parameter.
356 On some motherboards the driver may fail to reset the chipset's
357 NO_REBOOT flag which prevents the watchdog from rebooting the
358 machine. If this is the case you will get a kernel message like
359 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
361 To compile this driver as a module, choose M here: the
362 module will be called iTCO_wdt.
364 config ITCO_VENDOR_SUPPORT
365 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
368 Add vendor specific support to the intel TCO timer based watchdog
369 devices. At this moment we only have additional support for some
370 SuperMicro Inc. motherboards.
373 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
376 This is a driver for National Semiconductor PC87307/PC97307 hardware
377 watchdog cards as found on the SC1200. This watchdog is mainly used
378 for power management purposes and can be used to power down the device
379 during inactivity periods (includes interrupt activity monitoring).
381 To compile this driver as a module, choose M here: the
382 module will be called sc1200wdt.
384 Most people will say N.
387 tristate "National Semiconductor SCx200 Watchdog"
388 depends on SCx200 && PCI
390 Enable the built-in watchdog timer support on the National
391 Semiconductor SCx200 processors.
393 If compiled as a module, it will be called scx200_wdt.
396 tristate "NS PC87413 watchdog"
399 This is the driver for the hardware watchdog on the PC87413 chipset
400 This watchdog simply watches your kernel to make sure it doesn't
401 freeze, and if it does, it reboots your computer after a certain
404 To compile this driver as a module, choose M here: the
405 module will be called pc87413_wdt.
407 Most people will say N.
410 tristate "SBC-60XX Watchdog Timer"
413 This driver can be used with the watchdog timer found on some
414 single board computers, namely the 6010 PII based computer.
415 It may well work with other cards. It reads port 0x443 to enable
416 and re-set the watchdog timer, and reads port 0x45 to disable
417 the watchdog. If you have a card that behave in similar ways,
418 you can probably make this driver work with your card as well.
420 You can compile this driver directly into the kernel, or use
421 it as a module. The module will be called sbc60xxwdt.
424 tristate "SBC8360 Watchdog Timer"
428 This is the driver for the hardware watchdog on the SBC8360 Single
429 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
431 To compile this driver as a module, choose M here: the
432 module will be called sbc8360.ko.
434 Most people will say N.
437 tristate "SMA CPU5 Watchdog"
441 To compile this driver as a module, choose M here: the
442 module will be called cpu5wdt.
444 config SMSC37B787_WDT
445 tristate "Winbond SMsC37B787 Watchdog Timer"
448 This is the driver for the hardware watchdog component on the
449 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
450 from Vision Systems and maybe others.
452 This watchdog simply watches your kernel to make sure it doesn't
453 freeze, and if it does, it reboots your computer after a certain
456 Usually a userspace daemon will notify the kernel WDT driver that
457 userspace is still alive, at regular intervals.
459 To compile this driver as a module, choose M here: the
460 module will be called smsc37b787_wdt.
462 Most people will say N.
465 tristate "W83627HF Watchdog Timer"
468 This is the driver for the hardware watchdog on the W83627HF chipset
469 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
470 (and likely others). This watchdog simply watches your kernel to
471 make sure it doesn't freeze, and if it does, it reboots your computer
472 after a certain amount of time.
474 To compile this driver as a module, choose M here: the
475 module will be called w83627hf_wdt.
477 Most people will say N.
480 tristate "W83697HF/W83697HG Watchdog Timer"
483 This is the driver for the hardware watchdog on the W83697HF/HG
484 chipset as used in Dedibox/VIA motherboards (and likely others).
485 This watchdog simply watches your kernel to make sure it doesn't
486 freeze, and if it does, it reboots your computer after a certain
489 To compile this driver as a module, choose M here: the
490 module will be called w83697hf_wdt.
492 Most people will say N.
495 tristate "W83877F (EMACS) Watchdog Timer"
498 This is the driver for the hardware watchdog on the W83877F chipset
499 as used in EMACS PC-104 motherboards (and likely others). This
500 watchdog simply watches your kernel to make sure it doesn't freeze,
501 and if it does, it reboots your computer after a certain amount of
504 To compile this driver as a module, choose M here: the
505 module will be called w83877f_wdt.
507 Most people will say N.
510 tristate "W83977F (PCM-5335) Watchdog Timer"
513 This is the driver for the hardware watchdog on the W83977F I/O chip
514 as used in AAEON's PCM-5335 SBC (and likely others). This
515 watchdog simply watches your kernel to make sure it doesn't freeze,
516 and if it does, it reboots your computer after a certain amount of
519 To compile this driver as a module, choose M here: the
520 module will be called w83977f_wdt.
523 tristate "ZF MachZ Watchdog"
526 If you are using a ZF Micro MachZ processor, say Y here, otherwise
527 N. This is the driver for the watchdog timer built-in on that
528 processor using ZF-Logic interface. This watchdog simply watches
529 your kernel to make sure it doesn't freeze, and if it does, it
530 reboots your computer after a certain amount of time.
532 To compile this driver as a module, choose M here: the
533 module will be called machzwd.
535 config SBC_EPX_C3_WATCHDOG
536 tristate "Winsystems SBC EPX-C3 watchdog"
539 This is the driver for the built-in watchdog timer on the EPX-C3
540 Single-board computer made by Winsystems, Inc.
542 *Note*: This hardware watchdog is not probeable and thus there
543 is no way to know if writing to its IO address will corrupt
544 your system or have any real effect. The only way to be sure
545 that this driver does what you want is to make sure you
546 are running it on an EPX-C3 from Winsystems with the watchdog
547 timer at IO address 0x1ee and 0x1ef. It will write to both those
548 IO ports. Basically, the assumption is made that if you compile
549 this driver into your kernel and/or load it as a module, that you
550 know what you are doing and that you are in fact running on an
553 To compile this driver as a module, choose M here: the
554 module will be called sbc_epx_c3.
556 # PowerPC Architecture
559 tristate "MPC8xx Watchdog Timer"
563 tristate "MPC5200 Watchdog Timer"
564 depends on PPC_MPC52xx
567 tristate "MPC83xx Watchdog Timer"
571 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
575 bool "PowerPC Book-E Watchdog Timer"
576 depends on BOOKE || 4xx
578 Please see Documentation/watchdog/watchdog-api.txt for
584 tristate "RTAS watchdog"
587 This driver adds watchdog support for the RTAS watchdog.
589 To compile this driver as a module, choose M here. The module
590 will be called wdrtas.
595 tristate "Indy/I2 Hardware Watchdog"
598 Hardware driver for the Indy's/I2's watchdog. This is a
599 watchdog timer that will reboot the machine after a 60 second
600 timer expired and no process has written to /dev/watchdog during
604 tristate "MTX-1 Hardware Watchdog"
607 Hardware driver for the MTX-1 boards. This is a watchdog timer that
608 will reboot the machine after a 100 seconds timer expired.
611 tristate "RM9000/GPI hardware watchdog"
612 depends on CPU_RM9000
614 Watchdog implementation using the GPI hardware found on
615 PMC-Sierra RM9xxx CPUs.
617 To compile this driver as a module, choose M here: the
618 module will be called rm9k_wdt.
623 tristate "z/VM Watchdog Timer"
626 IBM s/390 and zSeries machines running under z/VM 5.1 or later
627 provide a virtual watchdog timer to their guest that cause a
628 user define Control Program command to be executed after a
631 To compile this driver as a module, choose M here. The module
632 will be called vmwatchdog.
634 # SUPERH Architecture
637 tristate "SuperH Watchdog"
638 depends on SUPERH && (CPU_SH3 || CPU_SH4)
640 This driver adds watchdog support for the integrated watchdog in the
641 SuperH processors. If you have one of these processors and wish
642 to have watchdog support enabled, say Y, otherwise say N.
644 As a side note, saying Y here will automatically boost HZ to 1000
645 so that the timer has a chance to clear the overflow counter. On
646 slower systems (such as the SH-2 and SH-3) this will likely yield
647 some performance issues. As such, the WDT should be avoided here
648 unless it is absolutely necessary.
650 To compile this driver as a module, choose M here: the
651 module will be called shwdt.
654 bool "Allow mmap of SH WDT"
658 If you say Y here, user applications will be able to mmap the
661 # SPARC64 Architecture
663 config WATCHDOG_CP1XXX
664 tristate "CP1XXX Hardware Watchdog support"
665 depends on SPARC64 && PCI
667 This is the driver for the hardware watchdog timers present on
668 Sun Microsystems CompactPCI models CP1400 and CP1500.
670 To compile this driver as a module, choose M here: the
671 module will be called cpwatchdog.
673 If you do not have a CompactPCI model CP1400 or CP1500, or
674 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
675 you should say N to this option.
678 tristate "RIO Hardware Watchdog support"
679 depends on SPARC64 && PCI
681 Say Y here to support the hardware watchdog capability on Sun RIO
682 machines. The watchdog timeout period is normally one minute but
683 can be changed with a boot-time parameter.
686 # ISA-based Watchdog Cards
689 comment "ISA-based Watchdog Cards"
693 tristate "Berkshire Products ISA-PC Watchdog"
696 This is the driver for the Berkshire Products ISA-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. This driver is like the WDT501 driver but for different
700 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
701 watchdog cards can be ordered from <http://www.berkprod.com/>.
703 To compile this driver as a module, choose M here: the
704 module will be called pcwd.
706 Most people will say N.
709 tristate "Mixcom Watchdog"
712 This is a driver for the Mixcom hardware watchdog cards. This
713 watchdog simply watches your kernel to make sure it doesn't freeze,
714 and if it does, it reboots your computer after a certain amount of
717 To compile this driver as a module, choose M here: the
718 module will be called mixcomwd.
720 Most people will say N.
723 tristate "WDT Watchdog timer"
726 If you have a WDT500P or WDT501P watchdog board, say Y here,
727 otherwise N. It is not possible to probe for this board, which means
728 that you have to inform the kernel about the IO port and IRQ that
729 is needed (you can do this via the io and irq parameters)
731 To compile this driver as a module, choose M here: the
732 module will be called wdt.
735 bool "WDT501 features"
738 Saying Y here and creating a character special file /dev/temperature
739 with major number 10 and minor number 131 ("man mknod") will give
740 you a thermometer inside your computer: reading from
741 /dev/temperature yields one byte, the temperature in degrees
742 Fahrenheit. This works only if you have a WDT501P watchdog board
745 If you want to enable the Fan Tachometer on the WDT501P, then you
746 can do this via the tachometer parameter. Only do this if you have a
747 fan tachometer actually set up.
750 # PCI-based Watchdog Cards
753 comment "PCI-based Watchdog Cards"
757 tristate "Berkshire Products PCI-PC Watchdog"
760 This is the driver for the Berkshire Products PCI-PC Watchdog card.
761 This card simply watches your kernel to make sure it doesn't freeze,
762 and if it does, it reboots your computer after a certain amount of
763 time. The card can also monitor the internal temperature of the PC.
764 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
766 To compile this driver as a module, choose M here: the
767 module will be called pcwd_pci.
769 Most people will say N.
772 tristate "PCI-WDT500/501 Watchdog timer"
775 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
777 To compile this driver as a module, choose M here: the
778 module will be called wdt_pci.
781 bool "PCI-WDT501 features"
784 Saying Y here and creating a character special file /dev/temperature
785 with major number 10 and minor number 131 ("man mknod") will give
786 you a thermometer inside your computer: reading from
787 /dev/temperature yields one byte, the temperature in degrees
788 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
791 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
792 can do this via the tachometer parameter. Only do this if you have a
793 fan tachometer actually set up.
796 # USB-based Watchdog Cards
799 comment "USB-based Watchdog Cards"
803 tristate "Berkshire Products USB-PC Watchdog"
806 This is the driver for the Berkshire Products USB-PC Watchdog card.
807 This card simply watches your kernel to make sure it doesn't freeze,
808 and if it does, it reboots your computer after a certain amount of
809 time. The card can also monitor the internal temperature of the PC.
810 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
812 To compile this driver as a module, choose M here: the
813 module will be called pcwd_usb.
815 Most people will say N.