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.
62 config AT91RM9200_WATCHDOG
63 tristate "AT91RM9200 watchdog"
64 depends on ARCH_AT91RM9200
66 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
67 system when the timeout is reached.
70 tristate "DC21285 watchdog"
73 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
74 here if you wish to use this. Alternatively say M to compile the
75 driver as a module, which will be called wdt285.
77 This driver does not work on all machines. In particular, early CATS
78 boards have hardware problems that will cause the machine to simply
79 lock up if the watchdog fires.
81 "If in doubt, leave it out" - say N.
84 tristate "NetWinder WB83C977 watchdog"
85 depends on FOOTBRIDGE && ARCH_NETWINDER
87 Say Y here to include support for the WB977 watchdog included in
88 NetWinder machines. Alternatively say M to compile the driver as
89 a module, which will be called wdt977.
91 Not sure? It's safe to say N.
93 config IXP2000_WATCHDOG
94 tristate "IXP2000 Watchdog"
95 depends on ARCH_IXP2000
97 Say Y here if to include support for the watchdog timer
98 in the Intel IXP2000(2400, 2800, 2850) network processors.
99 This driver can be built as a module by choosing M. The module
100 will be called ixp2000_wdt.
102 Say N if you are unsure.
104 config IXP4XX_WATCHDOG
105 tristate "IXP4xx Watchdog"
106 depends on ARCH_IXP4XX
108 Say Y here if to include support for the watchdog timer
109 in the Intel IXP4xx network processors. This driver can
110 be built as a module by choosing M. The module will
111 be called ixp4xx_wdt.
113 Note: The internal IXP4xx watchdog does a soft CPU reset
114 which doesn't reset any peripherals. There are circumstances
115 where the watchdog will fail to reset the board correctly
116 (e.g., if the boot ROM is in an unreadable state).
118 Say N if you are unsure.
120 config KS8695_WATCHDOG
121 tristate "KS8695 watchdog"
122 depends on ARCH_KS8695
124 Watchdog timer embedded into KS8695 processor. This will reboot your
125 system when the timeout is reached.
127 config S3C2410_WATCHDOG
128 tristate "S3C2410 Watchdog"
129 depends on ARCH_S3C2410
131 Watchdog timer block in the Samsung S3C2410 chips. This will
132 reboot the system when the timer expires with the watchdog
135 The driver is limited by the speed of the system's PCLK
136 signal, so with reasonably fast systems (PCLK around 50-66MHz)
137 then watchdog intervals of over approximately 20seconds are
140 The driver can be built as a module by choosing M, and will
141 be called s3c2410_wdt
143 config SA1100_WATCHDOG
144 tristate "SA1100/PXA2xx watchdog"
145 depends on ARCH_SA1100 || ARCH_PXA
147 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
148 reboot your system when timeout is reached.
150 NOTE: once enabled, this timer cannot be disabled.
152 To compile this driver as a module, choose M here: the
153 module will be called sa1100_wdt.
155 config MPCORE_WATCHDOG
156 tristate "MPcore watchdog"
157 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
159 Watchdog timer embedded into the MPcore system.
161 To compile this driver as a module, choose M here: the
162 module will be called mpcore_wdt.
164 config EP93XX_WATCHDOG
165 tristate "EP93xx Watchdog"
166 depends on ARCH_EP93XX
168 Say Y here if to include support for the watchdog timer
169 embedded in the Cirrus Logic EP93xx family of devices.
171 To compile this driver as a module, choose M here: the
172 module will be called ep93xx_wdt.
175 tristate "OMAP Watchdog"
176 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
178 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
179 enable the OMAP1610/OMAP1710 watchdog timer.
181 config PNX4008_WATCHDOG
182 tristate "PNX4008 Watchdog"
183 depends on ARCH_PNX4008
185 Say Y here if to include support for the watchdog timer
186 in the PNX4008 processor.
187 This driver can be built as a module by choosing M. The module
188 will be called pnx4008_wdt.
190 Say N if you are unsure.
193 tristate "IOP Watchdog"
195 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
197 Say Y here if to include support for the watchdog timer
198 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
199 be built as a module by choosing M. The module will
202 Note: The IOP13XX watchdog does an Internal Bus Reset which will
203 affect both cores and the peripherals of the IOP. The ATU-X
204 and/or ATUe configuration registers will remain intact, but if
205 operating as an Root Complex and/or Central Resource, the PCI-X
206 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
208 config DAVINCI_WATCHDOG
209 tristate "DaVinci watchdog"
210 depends on ARCH_DAVINCI
212 Say Y here if to include support for the watchdog timer
213 in the DaVinci DM644x/DM646x processors.
214 To compile this driver as a module, choose M here: the
215 module will be called davinci_wdt.
217 NOTE: once enabled, this timer cannot be disabled.
218 Say N if you are unsure.
224 config AT32AP700X_WDT
225 tristate "AT32AP700x watchdog"
226 depends on CPU_AT32AP7000
228 Watchdog timer embedded into AT32AP700x devices. This will reboot
229 your system when the timeout is reached.
231 # BLACKFIN Architecture
234 tristate "Blackfin On-Chip Watchdog Timer"
237 If you say yes here you will get support for the Blackfin On-Chip
238 Watchdog Timer. If you have one of these processors and wish to
239 have watchdog support enabled, say Y, otherwise say N.
241 To compile this driver as a module, choose M here: the
242 module will be called bfin_wdt.
250 # X86 (i386 + ia64 + x86_64) Architecture
253 tristate "Acquire SBC Watchdog Timer"
256 This is the driver for the hardware watchdog on Single Board
257 Computers produced by Acquire Inc (and others). This watchdog
258 simply watches your kernel to make sure it doesn't freeze, and if
259 it does, it reboots your computer after a certain amount of time.
261 To compile this driver as a module, choose M here: the
262 module will be called acquirewdt.
264 Most people will say N.
267 tristate "Advantech SBC Watchdog Timer"
270 If you are configuring a Linux kernel for the Advantech single-board
271 computer, say `Y' here to support its built-in watchdog timer
272 feature. More information can be found at
273 <http://www.advantech.com.tw/products/>
276 tristate "ALi M1535 PMU Watchdog Timer"
277 depends on X86 && PCI
279 This is the driver for the hardware watchdog on the ALi M1535 PMU.
281 To compile this driver as a module, choose M here: the
282 module will be called alim1535_wdt.
284 Most people will say N.
287 tristate "ALi M7101 PMU Computer Watchdog"
288 depends on X86 && PCI
290 This is the driver for the hardware watchdog on the ALi M7101 PMU
291 as used in the x86 Cobalt servers.
293 To compile this driver as a module, choose M here: the
294 module will be called alim7101_wdt.
296 Most people will say N.
299 tristate "AMD Elan SC520 processor Watchdog"
302 This is the driver for the hardware watchdog built in to the
303 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
304 This watchdog simply watches your kernel to make sure it doesn't
305 freeze, and if it does, it reboots your computer after a certain
308 You can compile this driver directly into the kernel, or use
309 it as a module. The module will be called sc520_wdt.
312 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
315 Enable support for the watchdog timer on the Eurotech CPU-1220 and
316 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
317 information are at <http://www.eurotech.it/>.
320 tristate "IB700 SBC Watchdog Timer"
323 This is the driver for the hardware watchdog on the IB700 Single
324 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
325 simply watches your kernel to make sure it doesn't freeze, and if
326 it does, it reboots your computer after a certain amount of time.
328 This driver is like the WDT501 driver but for slightly different hardware.
330 To compile this driver as a module, choose M here: the
331 module will be called ib700wdt.
333 Most people will say N.
336 tristate "IBM Automatic Server Restart"
339 This is the driver for the IBM Automatic Server Restart watchdog
340 timer built-in into some eServer xSeries machines.
342 To compile this driver as a module, choose M here: the
343 module will be called ibmasr.
346 tristate "ICP Single Board Computer Watchdog Timer"
349 This is a driver for the hardware watchdog on the ICP Single
350 Board Computer. This driver is working on (at least) the following
351 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
353 To compile this driver as a module, choose M here: the
354 module will be called wafer5823wdt.
357 tristate "Intel 6300ESB Timer/Watchdog"
358 depends on X86 && PCI
360 Hardware driver for the watchdog timer built into the Intel
361 6300ESB controller hub.
363 To compile this driver as a module, choose M here: the
364 module will be called i6300esb.
367 tristate "Intel TCO Timer/Watchdog"
368 depends on (X86 || IA64) && PCI
370 Hardware driver for the intel TCO timer based watchdog devices.
371 These drivers are included in the Intel 82801 I/O Controller
372 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
375 The TCO (Total Cost of Ownership) timer is a watchdog timer
376 that will reboot the machine after its second expiration. The
377 expiration time can be configured with the "heartbeat" parameter.
379 On some motherboards the driver may fail to reset the chipset's
380 NO_REBOOT flag which prevents the watchdog from rebooting the
381 machine. If this is the case you will get a kernel message like
382 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
384 To compile this driver as a module, choose M here: the
385 module will be called iTCO_wdt.
387 config ITCO_VENDOR_SUPPORT
388 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
391 Add vendor specific support to the intel TCO timer based watchdog
392 devices. At this moment we only have additional support for some
393 SuperMicro Inc. motherboards.
396 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
399 This is a driver for National Semiconductor PC87307/PC97307 hardware
400 watchdog cards as found on the SC1200. This watchdog is mainly used
401 for power management purposes and can be used to power down the device
402 during inactivity periods (includes interrupt activity monitoring).
404 To compile this driver as a module, choose M here: the
405 module will be called sc1200wdt.
407 Most people will say N.
410 tristate "National Semiconductor SCx200 Watchdog"
411 depends on SCx200 && PCI
413 Enable the built-in watchdog timer support on the National
414 Semiconductor SCx200 processors.
416 If compiled as a module, it will be called scx200_wdt.
419 tristate "NS PC87413 watchdog"
422 This is the driver for the hardware watchdog on the PC87413 chipset
423 This watchdog simply watches your kernel to make sure it doesn't
424 freeze, and if it does, it reboots your computer after a certain
427 To compile this driver as a module, choose M here: the
428 module will be called pc87413_wdt.
430 Most people will say N.
433 tristate "SBC-60XX Watchdog Timer"
436 This driver can be used with the watchdog timer found on some
437 single board computers, namely the 6010 PII based computer.
438 It may well work with other cards. It reads port 0x443 to enable
439 and re-set the watchdog timer, and reads port 0x45 to disable
440 the watchdog. If you have a card that behave in similar ways,
441 you can probably make this driver work with your card as well.
443 You can compile this driver directly into the kernel, or use
444 it as a module. The module will be called sbc60xxwdt.
447 tristate "SBC8360 Watchdog Timer"
451 This is the driver for the hardware watchdog on the SBC8360 Single
452 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
454 To compile this driver as a module, choose M here: the
455 module will be called sbc8360.ko.
457 Most people will say N.
460 tristate "SMA CPU5 Watchdog"
464 To compile this driver as a module, choose M here: the
465 module will be called cpu5wdt.
467 config SMSC37B787_WDT
468 tristate "Winbond SMsC37B787 Watchdog Timer"
471 This is the driver for the hardware watchdog component on the
472 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
473 from Vision Systems and maybe others.
475 This watchdog simply watches your kernel to make sure it doesn't
476 freeze, and if it does, it reboots your computer after a certain
479 Usually a userspace daemon will notify the kernel WDT driver that
480 userspace is still alive, at regular intervals.
482 To compile this driver as a module, choose M here: the
483 module will be called smsc37b787_wdt.
485 Most people will say N.
488 tristate "W83627HF Watchdog Timer"
491 This is the driver for the hardware watchdog on the W83627HF chipset
492 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
493 (and likely others). This watchdog simply watches your kernel to
494 make sure it doesn't freeze, and if it does, it reboots your computer
495 after a certain amount of time.
497 To compile this driver as a module, choose M here: the
498 module will be called w83627hf_wdt.
500 Most people will say N.
503 tristate "W83697HF/W83697HG Watchdog Timer"
506 This is the driver for the hardware watchdog on the W83697HF/HG
507 chipset as used in Dedibox/VIA motherboards (and likely others).
508 This watchdog simply watches your kernel to make sure it doesn't
509 freeze, and if it does, it reboots your computer after a certain
512 To compile this driver as a module, choose M here: the
513 module will be called w83697hf_wdt.
515 Most people will say N.
518 tristate "W83877F (EMACS) Watchdog Timer"
521 This is the driver for the hardware watchdog on the W83877F chipset
522 as used in EMACS PC-104 motherboards (and likely others). This
523 watchdog simply watches your kernel to make sure it doesn't freeze,
524 and if it does, it reboots your computer after a certain amount of
527 To compile this driver as a module, choose M here: the
528 module will be called w83877f_wdt.
530 Most people will say N.
533 tristate "W83977F (PCM-5335) Watchdog Timer"
536 This is the driver for the hardware watchdog on the W83977F I/O chip
537 as used in AAEON's PCM-5335 SBC (and likely others). This
538 watchdog simply watches your kernel to make sure it doesn't freeze,
539 and if it does, it reboots your computer after a certain amount of
542 To compile this driver as a module, choose M here: the
543 module will be called w83977f_wdt.
546 tristate "ZF MachZ Watchdog"
549 If you are using a ZF Micro MachZ processor, say Y here, otherwise
550 N. This is the driver for the watchdog timer built-in on that
551 processor using ZF-Logic interface. This watchdog simply watches
552 your kernel to make sure it doesn't freeze, and if it does, it
553 reboots your computer after a certain amount of time.
555 To compile this driver as a module, choose M here: the
556 module will be called machzwd.
558 config SBC_EPX_C3_WATCHDOG
559 tristate "Winsystems SBC EPX-C3 watchdog"
562 This is the driver for the built-in watchdog timer on the EPX-C3
563 Single-board computer made by Winsystems, Inc.
565 *Note*: This hardware watchdog is not probeable and thus there
566 is no way to know if writing to its IO address will corrupt
567 your system or have any real effect. The only way to be sure
568 that this driver does what you want is to make sure you
569 are running it on an EPX-C3 from Winsystems with the watchdog
570 timer at IO address 0x1ee and 0x1ef. It will write to both those
571 IO ports. Basically, the assumption is made that if you compile
572 this driver into your kernel and/or load it as a module, that you
573 know what you are doing and that you are in fact running on an
576 To compile this driver as a module, choose M here: the
577 module will be called sbc_epx_c3.
583 # M68KNOMMU Architecture
588 tristate "Indy/I2 Hardware Watchdog"
591 Hardware driver for the Indy's/I2's watchdog. This is a
592 watchdog timer that will reboot the machine after a 60 second
593 timer expired and no process has written to /dev/watchdog during
597 tristate "MTX-1 Hardware Watchdog"
600 Hardware driver for the MTX-1 boards. This is a watchdog timer that
601 will reboot the machine after a 100 seconds timer expired.
604 tristate "RM9000/GPI hardware watchdog"
605 depends on CPU_RM9000
607 Watchdog implementation using the GPI hardware found on
608 PMC-Sierra RM9xxx CPUs.
610 To compile this driver as a module, choose M here: the
611 module will be called rm9k_wdt.
613 # PARISC Architecture
615 # POWERPC Architecture
618 tristate "MPC5200 Watchdog Timer"
619 depends on PPC_MPC52xx
622 tristate "MPC8xx Watchdog Timer"
626 tristate "MPC83xx Watchdog Timer"
630 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
634 bool "PowerPC Book-E Watchdog Timer"
635 depends on BOOKE || 4xx
637 Please see Documentation/watchdog/watchdog-api.txt for
643 tristate "RTAS watchdog"
646 This driver adds watchdog support for the RTAS watchdog.
648 To compile this driver as a module, choose M here. The module
649 will be called wdrtas.
654 tristate "z/VM Watchdog Timer"
657 IBM s/390 and zSeries machines running under z/VM 5.1 or later
658 provide a virtual watchdog timer to their guest that cause a
659 user define Control Program command to be executed after a
662 To compile this driver as a module, choose M here. The module
663 will be called vmwatchdog.
665 # SUPERH (sh + sh64) Architecture
668 tristate "SuperH Watchdog"
669 depends on SUPERH && (CPU_SH3 || CPU_SH4)
671 This driver adds watchdog support for the integrated watchdog in the
672 SuperH processors. If you have one of these processors and wish
673 to have watchdog support enabled, say Y, otherwise say N.
675 As a side note, saying Y here will automatically boost HZ to 1000
676 so that the timer has a chance to clear the overflow counter. On
677 slower systems (such as the SH-2 and SH-3) this will likely yield
678 some performance issues. As such, the WDT should be avoided here
679 unless it is absolutely necessary.
681 To compile this driver as a module, choose M here: the
682 module will be called shwdt.
685 bool "Allow mmap of SH WDT"
689 If you say Y here, user applications will be able to mmap the
694 # SPARC64 Architecture
696 config WATCHDOG_CP1XXX
697 tristate "CP1XXX Hardware Watchdog support"
698 depends on SPARC64 && PCI
700 This is the driver for the hardware watchdog timers present on
701 Sun Microsystems CompactPCI models CP1400 and CP1500.
703 To compile this driver as a module, choose M here: the
704 module will be called cpwatchdog.
706 If you do not have a CompactPCI model CP1400 or CP1500, or
707 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
708 you should say N to this option.
711 tristate "RIO Hardware Watchdog support"
712 depends on SPARC64 && PCI
714 Say Y here to support the hardware watchdog capability on Sun RIO
715 machines. The watchdog timeout period is normally one minute but
716 can be changed with a boot-time parameter.
720 # XTENSA Architecture
723 # ISA-based Watchdog Cards
726 comment "ISA-based Watchdog Cards"
730 tristate "Berkshire Products ISA-PC Watchdog"
733 This is the driver for the Berkshire Products ISA-PC Watchdog card.
734 This card simply watches your kernel to make sure it doesn't freeze,
735 and if it does, it reboots your computer after a certain amount of
736 time. This driver is like the WDT501 driver but for different
737 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
738 watchdog cards can be ordered from <http://www.berkprod.com/>.
740 To compile this driver as a module, choose M here: the
741 module will be called pcwd.
743 Most people will say N.
746 tristate "Mixcom Watchdog"
749 This is a driver for the Mixcom hardware watchdog cards. This
750 watchdog simply watches your kernel to make sure it doesn't freeze,
751 and if it does, it reboots your computer after a certain amount of
754 To compile this driver as a module, choose M here: the
755 module will be called mixcomwd.
757 Most people will say N.
760 tristate "WDT Watchdog timer"
763 If you have a WDT500P or WDT501P watchdog board, say Y here,
764 otherwise N. It is not possible to probe for this board, which means
765 that you have to inform the kernel about the IO port and IRQ that
766 is needed (you can do this via the io and irq parameters)
768 To compile this driver as a module, choose M here: the
769 module will be called wdt.
772 bool "WDT501 features"
775 Saying Y here and creating a character special file /dev/temperature
776 with major number 10 and minor number 131 ("man mknod") will give
777 you a thermometer inside your computer: reading from
778 /dev/temperature yields one byte, the temperature in degrees
779 Fahrenheit. This works only if you have a WDT501P watchdog board
782 If you want to enable the Fan Tachometer on the WDT501P, then you
783 can do this via the tachometer parameter. Only do this if you have a
784 fan tachometer actually set up.
787 # PCI-based Watchdog Cards
790 comment "PCI-based Watchdog Cards"
794 tristate "Berkshire Products PCI-PC Watchdog"
797 This is the driver for the Berkshire Products PCI-PC Watchdog card.
798 This card simply watches your kernel to make sure it doesn't freeze,
799 and if it does, it reboots your computer after a certain amount of
800 time. The card can also monitor the internal temperature of the PC.
801 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
803 To compile this driver as a module, choose M here: the
804 module will be called pcwd_pci.
806 Most people will say N.
809 tristate "PCI-WDT500/501 Watchdog timer"
812 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
814 To compile this driver as a module, choose M here: the
815 module will be called wdt_pci.
818 bool "PCI-WDT501 features"
821 Saying Y here and creating a character special file /dev/temperature
822 with major number 10 and minor number 131 ("man mknod") will give
823 you a thermometer inside your computer: reading from
824 /dev/temperature yields one byte, the temperature in degrees
825 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
828 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
829 can do this via the tachometer parameter. Only do this if you have a
830 fan tachometer actually set up.
833 # USB-based Watchdog Cards
836 comment "USB-based Watchdog Cards"
840 tristate "Berkshire Products USB-PC Watchdog"
843 This is the driver for the Berkshire Products USB-PC Watchdog card.
844 This card simply watches your kernel to make sure it doesn't freeze,
845 and if it does, it reboots your computer after a certain amount of
846 time. The card can also monitor the internal temperature of the PC.
847 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
849 To compile this driver as a module, choose M here: the
850 module will be called pcwd_usb.
852 Most people will say N.