blob: 06a31da2381c4a119a99eb18840d20e927289d02 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Watchdog device configuration
3#
4
5menu "Watchdog Cards"
6
7config WATCHDOG
8 bool "Watchdog Timer Support"
9 ---help---
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>
21 in the kernel source.
22
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
27 table is full.
28
29 If unsure, say N.
30
31config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
33 depends on WATCHDOG
34 help
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
39 it has been started.
40
41#
42# General Watchdog drivers
43#
44
45comment "Watchdog Device Drivers"
46 depends on WATCHDOG
47
48# Architecture Independant
49
50config SOFT_WATCHDOG
51 tristate "Software watchdog"
52 depends on WATCHDOG
53 help
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.
57
58 To compile this driver as a module, choose M here: the
59 module will be called softdog.
60
61# ARM Architecture
62
63config 21285_WATCHDOG
64 tristate "DC21285 watchdog"
65 depends on WATCHDOG && FOOTBRIDGE
66 help
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.
70
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.
74
75 "If in doubt, leave it out" - say N.
76
77config 977_WATCHDOG
78 tristate "NetWinder WB83C977 watchdog"
79 depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER
80 help
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.
84
85 Not sure? It's safe to say N.
86
87config IXP4XX_WATCHDOG
88 tristate "IXP4xx Watchdog"
89 depends on WATCHDOG && ARCH_IXP4XX
90 help
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
94 be called ixp4xx_wdt.
95
96 Note: The internal IXP4xx watchdog does a soft CPU reset
97 which doesn't reset any peripherals. There are circumstances
98 where the watchdog will fail to reset the board correctly
99 (e.g., if the boot ROM is in an unreadable state).
100
101 Say N if you are unsure.
102
103config IXP2000_WATCHDOG
104 tristate "IXP2000 Watchdog"
105 depends on WATCHDOG && ARCH_IXP2000
106 help
107 Say Y here if to include support for the watchdog timer
108 in the Intel IXP2000(2400, 2800, 2850) network processors.
109 This driver can be built as a module by choosing M. The module
110 will be called ixp2000_wdt.
111
112 Say N if you are unsure.
113
114config S3C2410_WATCHDOG
115 tristate "S3C2410 Watchdog"
116 depends on WATCHDOG && ARCH_S3C2410
117 help
118 Watchdog timer block in the Samsung S3C2410 chips. This will
119 reboot the system when the timer expires with the watchdog
120 enabled.
121
122 The driver is limited by the speed of the system's PCLK
123 signal, so with reasonbaly fast systems (PCLK around 50-66MHz)
124 then watchdog intervals of over approximately 20seconds are
125 unavailable.
126
127 The driver can be built as a module by choosing M, and will
128 be called s3c2410_wdt
129
130config SA1100_WATCHDOG
131 tristate "SA1100/PXA2xx watchdog"
132 depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA )
133 help
134 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
135 reboot your system when timeout is reached.
136
137 NOTE: once enabled, this timer cannot be disabled.
138
139 To compile this driver as a module, choose M here: the
140 module will be called sa1100_wdt.
141
142# X86 (i386 + ia64 + x86_64) Architecture
143
144config ACQUIRE_WDT
145 tristate "Acquire SBC Watchdog Timer"
146 depends on WATCHDOG && X86
147 ---help---
148 This is the driver for the hardware watchdog on Single Board
149 Computers produced by Acquire Inc (and others). This watchdog
150 simply watches your kernel to make sure it doesn't freeze, and if
151 it does, it reboots your computer after a certain amount of time.
152
153 To compile this driver as a module, choose M here: the
154 module will be called acquirewdt.
155
156 Most people will say N.
157
158config ADVANTECH_WDT
159 tristate "Advantech SBC Watchdog Timer"
160 depends on WATCHDOG && X86
161 help
162 If you are configuring a Linux kernel for the Advantech single-board
163 computer, say `Y' here to support its built-in watchdog timer
164 feature. More information can be found at
165 <http://www.advantech.com.tw/products/>
166
167config ALIM1535_WDT
168 tristate "ALi M1535 PMU Watchdog Timer"
169 depends on WATCHDOG && X86 && PCI
170 ---help---
171 This is the driver for the hardware watchdog on the ALi M1535 PMU.
172
173 To compile this driver as a module, choose M here: the
174 module will be called alim1535_wdt.
175
176 Most people will say N.
177
178config ALIM7101_WDT
179 tristate "ALi M7101 PMU Computer Watchdog"
180 depends on WATCHDOG && X86 && PCI
181 help
182 This is the driver for the hardware watchdog on the ALi M7101 PMU
183 as used in the x86 Cobalt servers.
184
185 To compile this driver as a module, choose M here: the
186 module will be called alim7101_wdt.
187
188 Most people will say N.
189
190config SC520_WDT
191 tristate "AMD Elan SC520 processor Watchdog"
192 depends on WATCHDOG && X86
193 help
194 This is the driver for the hardware watchdog built in to the
195 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
196 This watchdog simply watches your kernel to make sure it doesn't
197 freeze, and if it does, it reboots your computer after a certain
198 amount of time.
199
200 You can compile this driver directly into the kernel, or use
201 it as a module. The module will be called sc520_wdt.
202
203config EUROTECH_WDT
204 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
205 depends on WATCHDOG && X86
206 help
207 Enable support for the watchdog timer on the Eurotech CPU-1220 and
208 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
209 information are at <http://www.eurotech.it/>.
210
211config IB700_WDT
212 tristate "IB700 SBC Watchdog Timer"
213 depends on WATCHDOG && X86
214 ---help---
215 This is the driver for the hardware watchdog on the IB700 Single
216 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
217 simply watches your kernel to make sure it doesn't freeze, and if
218 it does, it reboots your computer after a certain amount of time.
219
220 This driver is like the WDT501 driver but for slightly different hardware.
221
222 To compile this driver as a module, choose M here: the
223 module will be called ib700wdt.
224
225 Most people will say N.
226
227config WAFER_WDT
228 tristate "ICP Wafer 5823 Single Board Computer Watchdog"
229 depends on WATCHDOG && X86
230 help
231 This is a driver for the hardware watchdog on the ICP Wafer 5823
232 Single Board Computer (and probably other similar models).
233
234 To compile this driver as a module, choose M here: the
235 module will be called wafer5823wdt.
236
237config I8XX_TCO
238 tristate "Intel i8xx TCO Timer/Watchdog"
239 depends on WATCHDOG && (X86 || IA64) && PCI
240 ---help---
241 Hardware driver for the TCO timer built into the Intel 82801
242 I/O Controller Hub family. The TCO (Total Cost of Ownership)
243 timer is a watchdog timer that will reboot the machine after
244 its second expiration. The expiration time can be configured
245 with the "heartbeat" parameter.
246
247 On some motherboards the driver may fail to reset the chipset's
248 NO_REBOOT flag which prevents the watchdog from rebooting the
249 machine. If this is the case you will get a kernel message like
250 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
251
252 To compile this driver as a module, choose M here: the
253 module will be called i8xx_tco.
254
255config SC1200_WDT
256 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
257 depends on WATCHDOG && X86
258 help
259 This is a driver for National Semiconductor PC87307/PC97307 hardware
260 watchdog cards as found on the SC1200. This watchdog is mainly used
261 for power management purposes and can be used to power down the device
262 during inactivity periods (includes interrupt activity monitoring).
263
264 To compile this driver as a module, choose M here: the
265 module will be called sc1200wdt.
266
267 Most people will say N.
268
269config SCx200_WDT
270 tristate "National Semiconductor SCx200 Watchdog"
271 depends on WATCHDOG && SCx200 && PCI
272 help
273 Enable the built-in watchdog timer support on the National
274 Semiconductor SCx200 processors.
275
276 If compiled as a module, it will be called scx200_wdt.
277
278config 60XX_WDT
279 tristate "SBC-60XX Watchdog Timer"
280 depends on WATCHDOG && X86
281 help
282 This driver can be used with the watchdog timer found on some
283 single board computers, namely the 6010 PII based computer.
284 It may well work with other cards. It reads port 0x443 to enable
285 and re-set the watchdog timer, and reads port 0x45 to disable
286 the watchdog. If you have a card that behave in similar ways,
287 you can probably make this driver work with your card as well.
288
289 You can compile this driver directly into the kernel, or use
290 it as a module. The module will be called sbc60xxwdt.
291
292config CPU5_WDT
293 tristate "SMA CPU5 Watchdog"
294 depends on WATCHDOG && X86
295 ---help---
296 TBD.
297 To compile this driver as a module, choose M here: the
298 module will be called cpu5wdt.
299
300config W83627HF_WDT
301 tristate "W83627HF Watchdog Timer"
302 depends on WATCHDOG && X86
303 ---help---
304 This is the driver for the hardware watchdog on the W83627HF chipset
305 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
306 (and likely others). This watchdog simply watches your kernel to
307 make sure it doesn't freeze, and if it does, it reboots your computer
308 after a certain amount of time.
309
310 To compile this driver as a module, choose M here: the
311 module will be called w83627hf_wdt.
312
313 Most people will say N.
314
315config W83877F_WDT
316 tristate "W83877F (EMACS) Watchdog Timer"
317 depends on WATCHDOG && X86
318 ---help---
319 This is the driver for the hardware watchdog on the W83877F chipset
320 as used in EMACS PC-104 motherboards (and likely others). This
321 watchdog simply watches your kernel to make sure it doesn't freeze,
322 and if it does, it reboots your computer after a certain amount of
323 time.
324
325 To compile this driver as a module, choose M here: the
326 module will be called w83877f_wdt.
327
328 Most people will say N.
329
330config MACHZ_WDT
331 tristate "ZF MachZ Watchdog"
332 depends on WATCHDOG && X86
333 ---help---
334 If you are using a ZF Micro MachZ processor, say Y here, otherwise
335 N. This is the driver for the watchdog timer builtin on that
336 processor using ZF-Logic interface. This watchdog simply watches
337 your kernel to make sure it doesn't freeze, and if it does, it
338 reboots your computer after a certain amount of time.
339
340 To compile this driver as a module, choose M here: the
341 module will be called machzwd.
342
343# PowerPC Architecture
344
345config 8xx_WDT
346 tristate "MPC8xx Watchdog Timer"
347 depends on WATCHDOG && 8xx
348
349# MIPS Architecture
350
351config INDYDOG
352 tristate "Indy/I2 Hardware Watchdog"
353 depends on WATCHDOG && SGI_IP22
354 help
355 Hardwaredriver for the Indy's/I2's watchdog. This is a
356 watchdog timer that will reboot the machine after a 60 second
357 timer expired and no process has written to /dev/watchdog during
358 that time.
359
360# S390 Architecture
361
362config ZVM_WATCHDOG
363 tristate "z/VM Watchdog Timer"
364 depends on WATCHDOG && ARCH_S390
365 help
366 IBM s/390 and zSeries machines running under z/VM 5.1 or later
367 provide a virtual watchdog timer to their guest that cause a
368 user define Control Program command to be executed after a
369 timeout.
370
371 To compile this driver as a module, choose M here. The module
372 will be called vmwatchdog.
373
374# SUPERH Architecture
375
376config SH_WDT
377 tristate "SuperH Watchdog"
378 depends on WATCHDOG && SUPERH
379 help
380 This driver adds watchdog support for the integrated watchdog in the
381 SuperH processors. If you have one of these processors and wish
382 to have watchdog support enabled, say Y, otherwise say N.
383
384 As a side note, saying Y here will automatically boost HZ to 1000
385 so that the timer has a chance to clear the overflow counter. On
386 slower systems (such as the SH-2 and SH-3) this will likely yield
387 some performance issues. As such, the WDT should be avoided here
388 unless it is absolutely necessary.
389
390 To compile this driver as a module, choose M here: the
391 module will be called shwdt.
392
393# SPARC64 Architecture
394
395config WATCHDOG_CP1XXX
396 tristate "CP1XXX Hardware Watchdog support"
397 depends on WATCHDOG && SPARC64 && PCI
398 ---help---
399 This is the driver for the hardware watchdog timers present on
400 Sun Microsystems CompactPCI models CP1400 and CP1500.
401
402 To compile this driver as a module, choose M here: the
403 module will be called cpwatchdog.
404
405 If you do not have a CompactPCI model CP1400 or CP1500, or
406 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
407 you should say N to this option.
408
409config WATCHDOG_RIO
410 tristate "RIO Hardware Watchdog support"
411 depends on WATCHDOG && SPARC64 && PCI
412 help
413 Say Y here to support the hardware watchdog capability on Sun RIO
414 machines. The watchdog timeout period is normally one minute but
415 can be changed with a boot-time parameter.
416
417#
418# ISA-based Watchdog Cards
419#
420
421comment "ISA-based Watchdog Cards"
422 depends on WATCHDOG && ISA
423
424config PCWATCHDOG
425 tristate "Berkshire Products ISA-PC Watchdog"
426 depends on WATCHDOG && ISA
427 ---help---
428 This is the driver for the Berkshire Products ISA-PC Watchdog card.
429 This card simply watches your kernel to make sure it doesn't freeze,
430 and if it does, it reboots your computer after a certain amount of
431 time. This driver is like the WDT501 driver but for different
432 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
433 watchdog cards can be ordered from <http://www.berkprod.com/>.
434
435 To compile this driver as a module, choose M here: the
436 module will be called pcwd.
437
438 Most people will say N.
439
440config MIXCOMWD
441 tristate "Mixcom Watchdog"
442 depends on WATCHDOG && ISA
443 ---help---
444 This is a driver for the Mixcom hardware watchdog cards. This
445 watchdog simply watches your kernel to make sure it doesn't freeze,
446 and if it does, it reboots your computer after a certain amount of
447 time.
448
449 To compile this driver as a module, choose M here: the
450 module will be called mixcomwd.
451
452 Most people will say N.
453
454config WDT
455 tristate "WDT Watchdog timer"
456 depends on WATCHDOG && ISA
457 ---help---
458 If you have a WDT500P or WDT501P watchdog board, say Y here,
459 otherwise N. It is not possible to probe for this board, which means
460 that you have to inform the kernel about the IO port and IRQ that
461 is needed (you can do this via the io and irq parameters)
462
463 To compile this driver as a module, choose M here: the
464 module will be called wdt.
465
466config WDT_501
467 bool "WDT501 features"
468 depends on WDT
469 help
470 Saying Y here and creating a character special file /dev/temperature
471 with major number 10 and minor number 131 ("man mknod") will give
472 you a thermometer inside your computer: reading from
473 /dev/temperature yields one byte, the temperature in degrees
474 Fahrenheit. This works only if you have a WDT501P watchdog board
475 installed.
476
477 If you want to enable the Fan Tachometer on the WDT501P, then you
478 can do this via the tachometer parameter. Only do this if you have a
479 fan tachometer actually set up.
480
481#
482# PCI-based Watchdog Cards
483#
484
485comment "PCI-based Watchdog Cards"
486 depends on WATCHDOG && PCI
487
488config PCIPCWATCHDOG
489 tristate "Berkshire Products PCI-PC Watchdog"
490 depends on WATCHDOG && PCI
491 ---help---
492 This is the driver for the Berkshire Products PCI-PC Watchdog card.
493 This card simply watches your kernel to make sure it doesn't freeze,
494 and if it does, it reboots your computer after a certain amount of
495 time. The card can also monitor the internal temperature of the PC.
496 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
497
498 To compile this driver as a module, choose M here: the
499 module will be called pcwd_pci.
500
501 Most people will say N.
502
503config WDTPCI
504 tristate "PCI-WDT500/501 Watchdog timer"
505 depends on WATCHDOG && PCI
506 ---help---
507 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
508
509 To compile this driver as a module, choose M here: the
510 module will be called wdt_pci.
511
512config WDT_501_PCI
513 bool "PCI-WDT501 features"
514 depends on WDTPCI
515 help
516 Saying Y here and creating a character special file /dev/temperature
517 with major number 10 and minor number 131 ("man mknod") will give
518 you a thermometer inside your computer: reading from
519 /dev/temperature yields one byte, the temperature in degrees
520 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
521 installed.
522
523 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
524 can do this via the tachometer parameter. Only do this if you have a
525 fan tachometer actually set up.
526
527#
528# USB-based Watchdog Cards
529#
530
531comment "USB-based Watchdog Cards"
532 depends on WATCHDOG && USB
533
534config USBPCWATCHDOG
535 tristate "Berkshire Products USB-PC Watchdog"
536 depends on WATCHDOG && USB
537 ---help---
538 This is the driver for the Berkshire Products USB-PC Watchdog card.
539 This card simply watches your kernel to make sure it doesn't freeze,
540 and if it does, it reboots your computer after a certain amount of
541 time. The card can also monitor the internal temperature of the PC.
542 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
543
544 To compile this driver as a module, choose M here: the
545 module will be called pcwd_usb.
546
547 Most people will say N.
548
549endmenu