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 Independant
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 "DC21285 watchdog"
65 depends on WATCHDOG && FOOTBRIDGE
67 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
68 here if you wish to use this. Alternatively say M to compile the
69 driver as a module, which will be called wdt285.
71 This driver does not work on all machines. In particular, early CATS
72 boards have hardware problems that will cause the machine to simply
73 lock up if the watchdog fires.
75 "If in doubt, leave it out" - say N.
78 tristate "NetWinder WB83C977 watchdog"
79 depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER
81 Say Y here to include support for the WB977 watchdog included in
82 NetWinder machines. Alternatively say M to compile the driver as
83 a module, which will be called wdt977.
85 Not sure? It's safe to say N.
87 config IXP4XX_WATCHDOG
88 tristate "IXP4xx Watchdog"
89 depends on WATCHDOG && ARCH_IXP4XX
91 Say Y here if to include support for the watchdog timer
92 in the Intel IXP4xx network processors. This driver can
93 be built as a module by choosing M. The module will
96 Say N if you are unsure.
98 config IXP2000_WATCHDOG
99 tristate "IXP2000 Watchdog"
100 depends on WATCHDOG && ARCH_IXP2000
102 Say Y here if to include support for the watchdog timer
103 in the Intel IXP2000(2400, 2800, 2850) network processors.
104 This driver can be built as a module by choosing M. The module
105 will be called ixp2000_wdt.
107 Say N if you are unsure.
109 config SA1100_WATCHDOG
110 tristate "SA1100/PXA2xx watchdog"
111 depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA )
113 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
114 reboot your system when timeout is reached.
116 NOTE: once enabled, this timer cannot be disabled.
118 To compile this driver as a module, choose M here: the
119 module will be called sa1100_wdt.
121 # X86 (i386 + ia64 + x86_64) Architecture
124 tristate "Acquire SBC Watchdog Timer"
125 depends on WATCHDOG && X86
127 This is the driver for the hardware watchdog on Single Board
128 Computers produced by Acquire Inc (and others). This watchdog
129 simply watches your kernel to make sure it doesn't freeze, and if
130 it does, it reboots your computer after a certain amount of time.
132 To compile this driver as a module, choose M here: the
133 module will be called acquirewdt.
135 Most people will say N.
138 tristate "Advantech SBC Watchdog Timer"
139 depends on WATCHDOG && X86
141 If you are configuring a Linux kernel for the Advantech single-board
142 computer, say `Y' here to support its built-in watchdog timer
143 feature. More information can be found at
144 <http://www.advantech.com.tw/products/>
147 tristate "ALi M1535 PMU Watchdog Timer"
148 depends on WATCHDOG && X86 && PCI
150 This is the driver for the hardware watchdog on the ALi M1535 PMU.
152 To compile this driver as a module, choose M here: the
153 module will be called alim1535_wdt.
155 Most people will say N.
158 tristate "ALi M7101 PMU Computer Watchdog"
159 depends on WATCHDOG && X86 && PCI
161 This is the driver for the hardware watchdog on the ALi M7101 PMU
162 as used in the x86 Cobalt servers.
164 To compile this driver as a module, choose M here: the
165 module will be called alim7101_wdt.
167 Most people will say N.
170 tristate "AMD Elan SC520 processor Watchdog"
171 depends on WATCHDOG && X86
173 This is the driver for the hardware watchdog built in to the
174 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
175 This watchdog simply watches your kernel to make sure it doesn't
176 freeze, and if it does, it reboots your computer after a certain
179 You can compile this driver directly into the kernel, or use
180 it as a module. The module will be called sc520_wdt.
183 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
184 depends on WATCHDOG && X86
186 Enable support for the watchdog timer on the Eurotech CPU-1220 and
187 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
188 information are at <http://www.eurotech.it/>.
191 tristate "IB700 SBC Watchdog Timer"
192 depends on WATCHDOG && X86
194 This is the driver for the hardware watchdog on the IB700 Single
195 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
196 simply watches your kernel to make sure it doesn't freeze, and if
197 it does, it reboots your computer after a certain amount of time.
199 This driver is like the WDT501 driver but for slightly different hardware.
201 To compile this driver as a module, choose M here: the
202 module will be called ib700wdt.
204 Most people will say N.
207 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
208 depends on WATCHDOG && X86
210 This is a driver for the hardware watchdog on the ICP Wafer 5823
211 Single Board Computer (and probably other similar models).
213 To compile this driver as a module, choose M here: the
214 module will be called wafer5823wdt.
217 tristate "Intel i8xx TCO Timer/Watchdog"
218 depends on WATCHDOG && (X86 || IA64) && PCI
220 Hardware driver for the TCO timer built into the Intel 82801
221 I/O Controller Hub family. The TCO (Total Cost of Ownership)
222 timer is a watchdog timer that will reboot the machine after
223 its second expiration. The expiration time can be configured
224 with the "heartbeat" parameter.
226 On some motherboards the driver may fail to reset the chipset's
227 NO_REBOOT flag which prevents the watchdog from rebooting the
228 machine. If this is the case you will get a kernel message like
229 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
231 To compile this driver as a module, choose M here: the
232 module will be called i8xx_tco.
235 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
236 depends on WATCHDOG && X86
238 This is a driver for National Semiconductor PC87307/PC97307 hardware
239 watchdog cards as found on the SC1200. This watchdog is mainly used
240 for power management purposes and can be used to power down the device
241 during inactivity periods (includes interrupt activity monitoring).
243 To compile this driver as a module, choose M here: the
244 module will be called sc1200wdt.
246 Most people will say N.
249 tristate "National Semiconductor SCx200 Watchdog"
250 depends on WATCHDOG && X86 && PCI
252 Enable the built-in watchdog timer support on the National
253 Semiconductor SCx200 processors.
255 If compiled as a module, it will be called scx200_watchdog.
258 tristate "SBC-60XX Watchdog Timer"
259 depends on WATCHDOG && X86
261 This driver can be used with the watchdog timer found on some
262 single board computers, namely the 6010 PII based computer.
263 It may well work with other cards. It reads port 0x443 to enable
264 and re-set the watchdog timer, and reads port 0x45 to disable
265 the watchdog. If you have a card that behave in similar ways,
266 you can probably make this driver work with your card as well.
268 You can compile this driver directly into the kernel, or use
269 it as a module. The module will be called sbc60xxwdt.
272 tristate "SMA CPU5 Watchdog"
273 depends on WATCHDOG && X86
276 To compile this driver as a module, choose M here: the
277 module will be called cpu5wdt.
280 tristate "W83627HF Watchdog Timer"
281 depends on WATCHDOG && X86
283 This is the driver for the hardware watchdog on the W83627HF chipset
284 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
285 (and likely others). This watchdog simply watches your kernel to
286 make sure it doesn't freeze, and if it does, it reboots your computer
287 after a certain amount of time.
289 To compile this driver as a module, choose M here: the
290 module will be called w83627hf_wdt.
292 Most people will say N.
295 tristate "W83877F (EMACS) Watchdog Timer"
296 depends on WATCHDOG && X86
298 This is the driver for the hardware watchdog on the W83877F chipset
299 as used in EMACS PC-104 motherboards (and likely others). This
300 watchdog simply watches your kernel to make sure it doesn't freeze,
301 and if it does, it reboots your computer after a certain amount of
304 To compile this driver as a module, choose M here: the
305 module will be called w83877f_wdt.
307 Most people will say N.
310 tristate "ZF MachZ Watchdog"
311 depends on WATCHDOG && X86
313 If you are using a ZF Micro MachZ processor, say Y here, otherwise
314 N. This is the driver for the watchdog timer builtin on that
315 processor using ZF-Logic interface. This watchdog simply watches
316 your kernel to make sure it doesn't freeze, and if it does, it
317 reboots your computer after a certain amount of time.
319 To compile this driver as a module, choose M here: the
320 module will be called machzwd.
325 tristate "Indy/I2 Hardware Watchdog"
326 depends on WATCHDOG && SGI_IP22
328 Hardwaredriver for the Indy's/I2's watchdog. This is a
329 watchdog timer that will reboot the machine after a 60 second
330 timer expired and no process has written to /dev/watchdog during
333 # SUPERH Architecture
336 tristate "SuperH Watchdog"
337 depends on WATCHDOG && SUPERH
339 This driver adds watchdog support for the integrated watchdog in the
340 SuperH processors. If you have one of these processors and wish
341 to have watchdog support enabled, say Y, otherwise say N.
343 As a side note, saying Y here will automatically boost HZ to 1000
344 so that the timer has a chance to clear the overflow counter. On
345 slower systems (such as the SH-2 and SH-3) this will likely yield
346 some performance issues. As such, the WDT should be avoided here
347 unless it is absolutely necessary.
349 To compile this driver as a module, choose M here: the
350 module will be called shwdt.
352 # SPARC64 Architecture
354 config WATCHDOG_CP1XXX
355 tristate "CP1XXX Hardware Watchdog support"
356 depends on WATCHDOG && SPARC64 && PCI
358 This is the driver for the hardware watchdog timers present on
359 Sun Microsystems CompactPCI models CP1400 and CP1500.
361 To compile this driver as a module, choose M here: the
362 module will be called cpwatchdog.
364 If you do not have a CompactPCI model CP1400 or CP1500, or
365 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
366 you should say N to this option.
369 tristate "RIO Hardware Watchdog support"
370 depends on WATCHDOG && SPARC64 && PCI
372 Say Y here to support the hardware watchdog capability on Sun RIO
373 machines. The watchdog timeout period is normally one minute but
374 can be changed with a boot-time parameter.
377 # ISA-based Watchdog Cards
380 comment "ISA-based Watchdog Cards"
381 depends on WATCHDOG && ISA
384 tristate "Berkshire Products ISA-PC Watchdog"
385 depends on WATCHDOG && ISA
387 This is the driver for the Berkshire Products ISA-PC Watchdog card.
388 This card simply watches your kernel to make sure it doesn't freeze,
389 and if it does, it reboots your computer after a certain amount of
390 time. This driver is like the WDT501 driver but for different
391 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
392 watchdog cards can be ordered from <http://www.berkprod.com/>.
394 To compile this driver as a module, choose M here: the
395 module will be called pcwd.
397 Most people will say N.
400 tristate "Mixcom Watchdog"
401 depends on WATCHDOG && ISA
403 This is a driver for the Mixcom hardware watchdog cards. This
404 watchdog simply watches your kernel to make sure it doesn't freeze,
405 and if it does, it reboots your computer after a certain amount of
408 To compile this driver as a module, choose M here: the
409 module will be called mixcomwd.
411 Most people will say N.
414 tristate "WDT Watchdog timer"
415 depends on WATCHDOG && ISA
417 If you have a WDT500P or WDT501P watchdog board, say Y here,
418 otherwise N. It is not possible to probe for this board, which means
419 that you have to inform the kernel about the IO port and IRQ that
420 is needed (you can do this via the io and irq parameters)
422 To compile this driver as a module, choose M here: the
423 module will be called wdt.
426 bool "WDT501 features"
429 Saying Y here and creating a character special file /dev/temperature
430 with major number 10 and minor number 131 ("man mknod") will give
431 you a thermometer inside your computer: reading from
432 /dev/temperature yields one byte, the temperature in degrees
433 Fahrenheit. This works only if you have a WDT501P watchdog board
436 If you want to enable the Fan Tachometer on the WDT501P, then you
437 can do this via the tachometer parameter. Only do this if you have a
438 fan tachometer actually set up.
441 # PCI-based Watchdog Cards
444 comment "PCI-based Watchdog Cards"
445 depends on WATCHDOG && PCI
448 tristate "Berkshire Products PCI-PC Watchdog"
449 depends on WATCHDOG && PCI
451 This is the driver for the Berkshire Products PCI-PC Watchdog card.
452 This card simply watches your kernel to make sure it doesn't freeze,
453 and if it does, it reboots your computer after a certain amount of
454 time. The card can also monitor the internal temperature of the PC.
455 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
457 To compile this driver as a module, choose M here: the
458 module will be called pcwd_pci.
460 Most people will say N.
463 tristate "PCI-WDT500/501 Watchdog timer"
464 depends on WATCHDOG && PCI
466 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
468 To compile this driver as a module, choose M here: the
469 module will be called wdt_pci.
472 bool "PCI-WDT501 features"
475 Saying Y here and creating a character special file /dev/temperature
476 with major number 10 and minor number 131 ("man mknod") will give
477 you a thermometer inside your computer: reading from
478 /dev/temperature yields one byte, the temperature in degrees
479 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
482 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
483 can do this via the tachometer parameter. Only do this if you have a
484 fan tachometer actually set up.
487 # USB-based Watchdog Cards
490 comment "USB-based Watchdog Cards"
491 depends on WATCHDOG && USB
494 tristate "Berkshire Products USB-PC Watchdog"
495 depends on WATCHDOG && USB
497 This is the driver for the Berkshire Products USB-PC Watchdog card.
498 This card simply watches your kernel to make sure it doesn't freeze,
499 and if it does, it reboots your computer after a certain amount of
500 time. The card can also monitor the internal temperature of the PC.
501 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
503 To compile this driver as a module, choose M here: the
504 module will be called pcwd_usb.
506 Most people will say N.