Merge git://git.infradead.org/mtd-2.6
[deliverable/linux.git] / drivers / watchdog / Kconfig
1 #
2 # Watchdog device configuration
3 #
4
5 menuconfig WATCHDOG
6 bool "Watchdog Timer Support"
7 ---help---
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
19 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
20
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
25 table is full.
26
27 If unsure, say N.
28
29 if WATCHDOG
30
31 config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
33 help
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
38 it has been started.
39
40 #
41 # General Watchdog drivers
42 #
43
44 comment "Watchdog Device Drivers"
45
46 # Architecture Independent
47
48 config SOFT_WATCHDOG
49 tristate "Software watchdog"
50 help
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.
54
55 To compile this driver as a module, choose M here: the
56 module will be called softdog.
57
58 # ALPHA Architecture
59
60 # ARM Architecture
61
62 config AT91RM9200_WATCHDOG
63 tristate "AT91RM9200 watchdog"
64 depends on ARCH_AT91RM9200
65 help
66 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
67 system when the timeout is reached.
68
69 config 21285_WATCHDOG
70 tristate "DC21285 watchdog"
71 depends on FOOTBRIDGE
72 help
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.
76
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.
80
81 "If in doubt, leave it out" - say N.
82
83 config 977_WATCHDOG
84 tristate "NetWinder WB83C977 watchdog"
85 depends on FOOTBRIDGE && ARCH_NETWINDER
86 help
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.
90
91 Not sure? It's safe to say N.
92
93 config IXP2000_WATCHDOG
94 tristate "IXP2000 Watchdog"
95 depends on ARCH_IXP2000
96 help
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.
101
102 Say N if you are unsure.
103
104 config IXP4XX_WATCHDOG
105 tristate "IXP4xx Watchdog"
106 depends on ARCH_IXP4XX
107 help
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.
112
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).
117
118 Say N if you are unsure.
119
120 config KS8695_WATCHDOG
121 tristate "KS8695 watchdog"
122 depends on ARCH_KS8695
123 help
124 Watchdog timer embedded into KS8695 processor. This will reboot your
125 system when the timeout is reached.
126
127 config S3C2410_WATCHDOG
128 tristate "S3C2410 Watchdog"
129 depends on ARCH_S3C2410
130 help
131 Watchdog timer block in the Samsung S3C2410 chips. This will
132 reboot the system when the timer expires with the watchdog
133 enabled.
134
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
138 unavailable.
139
140 The driver can be built as a module by choosing M, and will
141 be called s3c2410_wdt
142
143 config SA1100_WATCHDOG
144 tristate "SA1100/PXA2xx watchdog"
145 depends on ARCH_SA1100 || ARCH_PXA
146 help
147 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
148 reboot your system when timeout is reached.
149
150 NOTE: once enabled, this timer cannot be disabled.
151
152 To compile this driver as a module, choose M here: the
153 module will be called sa1100_wdt.
154
155 config MPCORE_WATCHDOG
156 tristate "MPcore watchdog"
157 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
158 help
159 Watchdog timer embedded into the MPcore system.
160
161 To compile this driver as a module, choose M here: the
162 module will be called mpcore_wdt.
163
164 config EP93XX_WATCHDOG
165 tristate "EP93xx Watchdog"
166 depends on ARCH_EP93XX
167 help
168 Say Y here if to include support for the watchdog timer
169 embedded in the Cirrus Logic EP93xx family of devices.
170
171 To compile this driver as a module, choose M here: the
172 module will be called ep93xx_wdt.
173
174 config OMAP_WATCHDOG
175 tristate "OMAP Watchdog"
176 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
177 help
178 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
179 enable the OMAP1610/OMAP1710 watchdog timer.
180
181 config PNX4008_WATCHDOG
182 tristate "PNX4008 Watchdog"
183 depends on ARCH_PNX4008
184 help
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.
189
190 Say N if you are unsure.
191
192 config IOP_WATCHDOG
193 tristate "IOP Watchdog"
194 depends on PLAT_IOP
195 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
196 help
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
200 be called iop_wdt.
201
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.
207
208 config DAVINCI_WATCHDOG
209 tristate "DaVinci watchdog"
210 depends on ARCH_DAVINCI
211 help
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.
216
217 NOTE: once enabled, this timer cannot be disabled.
218 Say N if you are unsure.
219
220 # ARM26 Architecture
221
222 # AVR32 Architecture
223
224 config AT32AP700X_WDT
225 tristate "AT32AP700x watchdog"
226 depends on CPU_AT32AP700X
227 help
228 Watchdog timer embedded into AT32AP700x devices. This will reboot
229 your system when the timeout is reached.
230
231 # BLACKFIN Architecture
232
233 config BFIN_WDT
234 tristate "Blackfin On-Chip Watchdog Timer"
235 depends on BLACKFIN
236 ---help---
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.
240
241 To compile this driver as a module, choose M here: the
242 module will be called bfin_wdt.
243
244 # CRIS Architecture
245
246 # FRV Architecture
247
248 # H8300 Architecture
249
250 # X86 (i386 + ia64 + x86_64) Architecture
251
252 config ACQUIRE_WDT
253 tristate "Acquire SBC Watchdog Timer"
254 depends on X86
255 ---help---
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.
260
261 To compile this driver as a module, choose M here: the
262 module will be called acquirewdt.
263
264 Most people will say N.
265
266 config ADVANTECH_WDT
267 tristate "Advantech SBC Watchdog Timer"
268 depends on X86
269 help
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/>
274
275 config ALIM1535_WDT
276 tristate "ALi M1535 PMU Watchdog Timer"
277 depends on X86 && PCI
278 ---help---
279 This is the driver for the hardware watchdog on the ALi M1535 PMU.
280
281 To compile this driver as a module, choose M here: the
282 module will be called alim1535_wdt.
283
284 Most people will say N.
285
286 config ALIM7101_WDT
287 tristate "ALi M7101 PMU Computer Watchdog"
288 depends on X86 && PCI
289 help
290 This is the driver for the hardware watchdog on the ALi M7101 PMU
291 as used in the x86 Cobalt servers.
292
293 To compile this driver as a module, choose M here: the
294 module will be called alim7101_wdt.
295
296 Most people will say N.
297
298 config GEODE_WDT
299 tristate "AMD Geode CS5535/CS5536 Watchdog"
300 depends on MGEODE_LX
301 help
302 This driver enables a watchdog capability built into the
303 CS5535/CS5536 companion chips for the AMD Geode GX and LX
304 processors. This watchdog watches your kernel to make sure
305 it doesn't freeze, and if it does, it reboots your computer after
306 a certain amount of time.
307
308 You can compile this driver directly into the kernel, or use
309 it as a module. The module will be called geodewdt.
310
311 config SC520_WDT
312 tristate "AMD Elan SC520 processor Watchdog"
313 depends on X86
314 help
315 This is the driver for the hardware watchdog built in to the
316 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
317 This watchdog simply watches your kernel to make sure it doesn't
318 freeze, and if it does, it reboots your computer after a certain
319 amount of time.
320
321 You can compile this driver directly into the kernel, or use
322 it as a module. The module will be called sc520_wdt.
323
324 config EUROTECH_WDT
325 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
326 depends on X86
327 help
328 Enable support for the watchdog timer on the Eurotech CPU-1220 and
329 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
330 information are at <http://www.eurotech.it/>.
331
332 config IB700_WDT
333 tristate "IB700 SBC Watchdog Timer"
334 depends on X86
335 ---help---
336 This is the driver for the hardware watchdog on the IB700 Single
337 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
338 simply watches your kernel to make sure it doesn't freeze, and if
339 it does, it reboots your computer after a certain amount of time.
340
341 This driver is like the WDT501 driver but for slightly different hardware.
342
343 To compile this driver as a module, choose M here: the
344 module will be called ib700wdt.
345
346 Most people will say N.
347
348 config IBMASR
349 tristate "IBM Automatic Server Restart"
350 depends on X86
351 help
352 This is the driver for the IBM Automatic Server Restart watchdog
353 timer built-in into some eServer xSeries machines.
354
355 To compile this driver as a module, choose M here: the
356 module will be called ibmasr.
357
358 config WAFER_WDT
359 tristate "ICP Single Board Computer Watchdog Timer"
360 depends on X86
361 help
362 This is a driver for the hardware watchdog on the ICP Single
363 Board Computer. This driver is working on (at least) the following
364 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
365
366 To compile this driver as a module, choose M here: the
367 module will be called wafer5823wdt.
368
369 config I6300ESB_WDT
370 tristate "Intel 6300ESB Timer/Watchdog"
371 depends on X86 && PCI
372 ---help---
373 Hardware driver for the watchdog timer built into the Intel
374 6300ESB controller hub.
375
376 To compile this driver as a module, choose M here: the
377 module will be called i6300esb.
378
379 config ITCO_WDT
380 tristate "Intel TCO Timer/Watchdog"
381 depends on (X86 || IA64) && PCI
382 ---help---
383 Hardware driver for the intel TCO timer based watchdog devices.
384 These drivers are included in the Intel 82801 I/O Controller
385 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
386 controller hub.
387
388 The TCO (Total Cost of Ownership) timer is a watchdog timer
389 that will reboot the machine after its second expiration. The
390 expiration time can be configured with the "heartbeat" parameter.
391
392 On some motherboards the driver may fail to reset the chipset's
393 NO_REBOOT flag which prevents the watchdog from rebooting the
394 machine. If this is the case you will get a kernel message like
395 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
396
397 To compile this driver as a module, choose M here: the
398 module will be called iTCO_wdt.
399
400 config ITCO_VENDOR_SUPPORT
401 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
402 depends on ITCO_WDT
403 ---help---
404 Add vendor specific support to the intel TCO timer based watchdog
405 devices. At this moment we only have additional support for some
406 SuperMicro Inc. motherboards.
407
408 config IT8712F_WDT
409 tristate "IT8712F (Smart Guardian) Watchdog Timer"
410 depends on X86
411 ---help---
412 This is the driver for the built-in watchdog timer on the IT8712F
413 Super I/0 chipset used on many motherboards.
414
415 To compile this driver as a module, choose M here: the
416 module will be called it8712f_wdt.
417
418 config HP_WATCHDOG
419 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
420 depends on X86
421 help
422 A software monitoring watchdog and NMI sourcing driver. This driver
423 will detect lockups and provide stack trace. Also, when an NMI
424 occurs this driver will make the necessary BIOS calls to log
425 the cause of the NMI. This is a driver that will only load on a
426 HP ProLiant system with a minimum of iLO2 support.
427 To compile this driver as a module, choose M here: the
428 module will be called hpwdt.
429
430 config SC1200_WDT
431 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
432 depends on X86
433 help
434 This is a driver for National Semiconductor PC87307/PC97307 hardware
435 watchdog cards as found on the SC1200. This watchdog is mainly used
436 for power management purposes and can be used to power down the device
437 during inactivity periods (includes interrupt activity monitoring).
438
439 To compile this driver as a module, choose M here: the
440 module will be called sc1200wdt.
441
442 Most people will say N.
443
444 config SCx200_WDT
445 tristate "National Semiconductor SCx200 Watchdog"
446 depends on SCx200 && PCI
447 help
448 Enable the built-in watchdog timer support on the National
449 Semiconductor SCx200 processors.
450
451 If compiled as a module, it will be called scx200_wdt.
452
453 config PC87413_WDT
454 tristate "NS PC87413 watchdog"
455 depends on X86
456 ---help---
457 This is the driver for the hardware watchdog on the PC87413 chipset
458 This watchdog simply watches your kernel to make sure it doesn't
459 freeze, and if it does, it reboots your computer after a certain
460 amount of time.
461
462 To compile this driver as a module, choose M here: the
463 module will be called pc87413_wdt.
464
465 Most people will say N.
466
467 config 60XX_WDT
468 tristate "SBC-60XX Watchdog Timer"
469 depends on X86
470 help
471 This driver can be used with the watchdog timer found on some
472 single board computers, namely the 6010 PII based computer.
473 It may well work with other cards. It reads port 0x443 to enable
474 and re-set the watchdog timer, and reads port 0x45 to disable
475 the watchdog. If you have a card that behave in similar ways,
476 you can probably make this driver work with your card as well.
477
478 You can compile this driver directly into the kernel, or use
479 it as a module. The module will be called sbc60xxwdt.
480
481 config SBC8360_WDT
482 tristate "SBC8360 Watchdog Timer"
483 depends on X86
484 ---help---
485
486 This is the driver for the hardware watchdog on the SBC8360 Single
487 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
488
489 To compile this driver as a module, choose M here: the
490 module will be called sbc8360.ko.
491
492 Most people will say N.
493
494 config SBC7240_WDT
495 tristate "SBC Nano 7240 Watchdog Timer"
496 depends on X86_32
497 ---help---
498 This is the driver for the hardware watchdog found on the IEI
499 single board computers EPIC Nano 7240 (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
502 time.
503
504 To compile this driver as a module, choose M here: the
505 module will be called sbc7240_wdt.
506
507 config CPU5_WDT
508 tristate "SMA CPU5 Watchdog"
509 depends on X86
510 ---help---
511 TBD.
512 To compile this driver as a module, choose M here: the
513 module will be called cpu5wdt.
514
515 config SMSC37B787_WDT
516 tristate "Winbond SMsC37B787 Watchdog Timer"
517 depends on X86
518 ---help---
519 This is the driver for the hardware watchdog component on the
520 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
521 from Vision Systems and maybe others.
522
523 This watchdog simply watches your kernel to make sure it doesn't
524 freeze, and if it does, it reboots your computer after a certain
525 amount of time.
526
527 Usually a userspace daemon will notify the kernel WDT driver that
528 userspace is still alive, at regular intervals.
529
530 To compile this driver as a module, choose M here: the
531 module will be called smsc37b787_wdt.
532
533 Most people will say N.
534
535 config W83627HF_WDT
536 tristate "W83627HF Watchdog Timer"
537 depends on X86
538 ---help---
539 This is the driver for the hardware watchdog on the W83627HF chipset
540 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
541 (and likely others). This watchdog simply watches your kernel to
542 make sure it doesn't freeze, and if it does, it reboots your computer
543 after a certain amount of time.
544
545 To compile this driver as a module, choose M here: the
546 module will be called w83627hf_wdt.
547
548 Most people will say N.
549
550 config W83697HF_WDT
551 tristate "W83697HF/W83697HG Watchdog Timer"
552 depends on X86
553 ---help---
554 This is the driver for the hardware watchdog on the W83697HF/HG
555 chipset as used in Dedibox/VIA motherboards (and likely others).
556 This watchdog simply watches your kernel to make sure it doesn't
557 freeze, and if it does, it reboots your computer after a certain
558 amount of time.
559
560 To compile this driver as a module, choose M here: the
561 module will be called w83697hf_wdt.
562
563 Most people will say N.
564
565 config W83877F_WDT
566 tristate "W83877F (EMACS) Watchdog Timer"
567 depends on X86
568 ---help---
569 This is the driver for the hardware watchdog on the W83877F chipset
570 as used in EMACS PC-104 motherboards (and likely others). This
571 watchdog simply watches your kernel to make sure it doesn't freeze,
572 and if it does, it reboots your computer after a certain amount of
573 time.
574
575 To compile this driver as a module, choose M here: the
576 module will be called w83877f_wdt.
577
578 Most people will say N.
579
580 config W83977F_WDT
581 tristate "W83977F (PCM-5335) Watchdog Timer"
582 depends on X86
583 ---help---
584 This is the driver for the hardware watchdog on the W83977F I/O chip
585 as used in AAEON's PCM-5335 SBC (and likely others). This
586 watchdog simply watches your kernel to make sure it doesn't freeze,
587 and if it does, it reboots your computer after a certain amount of
588 time.
589
590 To compile this driver as a module, choose M here: the
591 module will be called w83977f_wdt.
592
593 config MACHZ_WDT
594 tristate "ZF MachZ Watchdog"
595 depends on X86
596 ---help---
597 If you are using a ZF Micro MachZ processor, say Y here, otherwise
598 N. This is the driver for the watchdog timer built-in on that
599 processor using ZF-Logic interface. This watchdog simply watches
600 your kernel to make sure it doesn't freeze, and if it does, it
601 reboots your computer after a certain amount of time.
602
603 To compile this driver as a module, choose M here: the
604 module will be called machzwd.
605
606 config SBC_EPX_C3_WATCHDOG
607 tristate "Winsystems SBC EPX-C3 watchdog"
608 depends on X86
609 ---help---
610 This is the driver for the built-in watchdog timer on the EPX-C3
611 Single-board computer made by Winsystems, Inc.
612
613 *Note*: This hardware watchdog is not probeable and thus there
614 is no way to know if writing to its IO address will corrupt
615 your system or have any real effect. The only way to be sure
616 that this driver does what you want is to make sure you
617 are running it on an EPX-C3 from Winsystems with the watchdog
618 timer at IO address 0x1ee and 0x1ef. It will write to both those
619 IO ports. Basically, the assumption is made that if you compile
620 this driver into your kernel and/or load it as a module, that you
621 know what you are doing and that you are in fact running on an
622 EPX-C3 board!
623
624 To compile this driver as a module, choose M here: the
625 module will be called sbc_epx_c3.
626
627 # M32R Architecture
628
629 # M68K Architecture
630
631 # M68KNOMMU Architecture
632
633 # MIPS Architecture
634
635 config INDYDOG
636 tristate "Indy/I2 Hardware Watchdog"
637 depends on SGI_HAS_INDYDOG
638 help
639 Hardware driver for the Indy's/I2's watchdog. This is a
640 watchdog timer that will reboot the machine after a 60 second
641 timer expired and no process has written to /dev/watchdog during
642 that time.
643
644 config WDT_MTX1
645 tristate "MTX-1 Hardware Watchdog"
646 depends on MIPS_MTX1
647 help
648 Hardware driver for the MTX-1 boards. This is a watchdog timer that
649 will reboot the machine after a 100 seconds timer expired.
650
651 config WDT_RM9K_GPI
652 tristate "RM9000/GPI hardware watchdog"
653 depends on CPU_RM9000
654 help
655 Watchdog implementation using the GPI hardware found on
656 PMC-Sierra RM9xxx CPUs.
657
658 To compile this driver as a module, choose M here: the
659 module will be called rm9k_wdt.
660
661 config SIBYTE_WDOG
662 tristate "Sibyte SoC hardware watchdog"
663 depends on CPU_SB1
664 help
665 Watchdog driver for the built in watchdog hardware in Sibyte
666 SoC processors. There are apparently two watchdog timers
667 on such processors; this driver supports only the first one,
668 because currently Linux only supports exporting one watchdog
669 to userspace.
670
671 To compile this driver as a loadable module, choose M here.
672 The module will be called sb_wdog.
673
674 config AR7_WDT
675 tristate "TI AR7 Watchdog Timer"
676 depends on AR7
677 help
678 Hardware driver for the TI AR7 Watchdog Timer.
679
680 config TXX9_WDT
681 tristate "Toshiba TXx9 Watchdog Timer"
682 depends on CPU_TX39XX || CPU_TX49XX
683 help
684 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
685
686 # PARISC Architecture
687
688 # POWERPC Architecture
689
690 config MPC5200_WDT
691 tristate "MPC5200 Watchdog Timer"
692 depends on PPC_MPC52xx
693
694 config 8xx_WDT
695 tristate "MPC8xx Watchdog Timer"
696 depends on 8xx
697
698 config 83xx_WDT
699 tristate "MPC83xx Watchdog Timer"
700 depends on PPC_83xx
701
702 config MV64X60_WDT
703 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
704 depends on MV64X60
705
706 config BOOKE_WDT
707 bool "PowerPC Book-E Watchdog Timer"
708 depends on BOOKE || 4xx
709 ---help---
710 Please see Documentation/watchdog/watchdog-api.txt for
711 more information.
712
713 # PPC64 Architecture
714
715 config WATCHDOG_RTAS
716 tristate "RTAS watchdog"
717 depends on PPC_RTAS
718 help
719 This driver adds watchdog support for the RTAS watchdog.
720
721 To compile this driver as a module, choose M here. The module
722 will be called wdrtas.
723
724 # S390 Architecture
725
726 config ZVM_WATCHDOG
727 tristate "z/VM Watchdog Timer"
728 depends on S390
729 help
730 IBM s/390 and zSeries machines running under z/VM 5.1 or later
731 provide a virtual watchdog timer to their guest that cause a
732 user define Control Program command to be executed after a
733 timeout.
734
735 To compile this driver as a module, choose M here. The module
736 will be called vmwatchdog.
737
738 # SUPERH (sh + sh64) Architecture
739
740 config SH_WDT
741 tristate "SuperH Watchdog"
742 depends on SUPERH && (CPU_SH3 || CPU_SH4)
743 help
744 This driver adds watchdog support for the integrated watchdog in the
745 SuperH processors. If you have one of these processors and wish
746 to have watchdog support enabled, say Y, otherwise say N.
747
748 As a side note, saying Y here will automatically boost HZ to 1000
749 so that the timer has a chance to clear the overflow counter. On
750 slower systems (such as the SH-2 and SH-3) this will likely yield
751 some performance issues. As such, the WDT should be avoided here
752 unless it is absolutely necessary.
753
754 To compile this driver as a module, choose M here: the
755 module will be called shwdt.
756
757 config SH_WDT_MMAP
758 bool "Allow mmap of SH WDT"
759 default n
760 depends on SH_WDT
761 help
762 If you say Y here, user applications will be able to mmap the
763 WDT/CPG registers.
764
765 # SPARC Architecture
766
767 # SPARC64 Architecture
768
769 config WATCHDOG_CP1XXX
770 tristate "CP1XXX Hardware Watchdog support"
771 depends on SPARC64 && PCI
772 ---help---
773 This is the driver for the hardware watchdog timers present on
774 Sun Microsystems CompactPCI models CP1400 and CP1500.
775
776 To compile this driver as a module, choose M here: the
777 module will be called cpwatchdog.
778
779 If you do not have a CompactPCI model CP1400 or CP1500, or
780 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
781 you should say N to this option.
782
783 config WATCHDOG_RIO
784 tristate "RIO Hardware Watchdog support"
785 depends on SPARC64 && PCI
786 help
787 Say Y here to support the hardware watchdog capability on Sun RIO
788 machines. The watchdog timeout period is normally one minute but
789 can be changed with a boot-time parameter.
790
791 # XTENSA Architecture
792
793 #
794 # ISA-based Watchdog Cards
795 #
796
797 comment "ISA-based Watchdog Cards"
798 depends on ISA
799
800 config PCWATCHDOG
801 tristate "Berkshire Products ISA-PC Watchdog"
802 depends on ISA
803 ---help---
804 This is the driver for the Berkshire Products ISA-PC Watchdog card.
805 This card simply watches your kernel to make sure it doesn't freeze,
806 and if it does, it reboots your computer after a certain amount of
807 time. This driver is like the WDT501 driver but for different
808 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
809 watchdog cards can be ordered from <http://www.berkprod.com/>.
810
811 To compile this driver as a module, choose M here: the
812 module will be called pcwd.
813
814 Most people will say N.
815
816 config MIXCOMWD
817 tristate "Mixcom Watchdog"
818 depends on ISA
819 ---help---
820 This is a driver for the Mixcom hardware watchdog cards. This
821 watchdog simply watches your kernel to make sure it doesn't freeze,
822 and if it does, it reboots your computer after a certain amount of
823 time.
824
825 To compile this driver as a module, choose M here: the
826 module will be called mixcomwd.
827
828 Most people will say N.
829
830 config WDT
831 tristate "WDT Watchdog timer"
832 depends on ISA
833 ---help---
834 If you have a WDT500P or WDT501P watchdog board, say Y here,
835 otherwise N. It is not possible to probe for this board, which means
836 that you have to inform the kernel about the IO port and IRQ that
837 is needed (you can do this via the io and irq parameters)
838
839 To compile this driver as a module, choose M here: the
840 module will be called wdt.
841
842 config WDT_501
843 bool "WDT501 features"
844 depends on WDT
845 help
846 Saying Y here and creating a character special file /dev/temperature
847 with major number 10 and minor number 131 ("man mknod") will give
848 you a thermometer inside your computer: reading from
849 /dev/temperature yields one byte, the temperature in degrees
850 Fahrenheit. This works only if you have a WDT501P watchdog board
851 installed.
852
853 If you want to enable the Fan Tachometer on the WDT501P, then you
854 can do this via the tachometer parameter. Only do this if you have a
855 fan tachometer actually set up.
856
857 #
858 # PCI-based Watchdog Cards
859 #
860
861 comment "PCI-based Watchdog Cards"
862 depends on PCI
863
864 config PCIPCWATCHDOG
865 tristate "Berkshire Products PCI-PC Watchdog"
866 depends on PCI
867 ---help---
868 This is the driver for the Berkshire Products PCI-PC Watchdog card.
869 This card simply watches your kernel to make sure it doesn't freeze,
870 and if it does, it reboots your computer after a certain amount of
871 time. The card can also monitor the internal temperature of the PC.
872 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
873
874 To compile this driver as a module, choose M here: the
875 module will be called pcwd_pci.
876
877 Most people will say N.
878
879 config WDTPCI
880 tristate "PCI-WDT500/501 Watchdog timer"
881 depends on PCI
882 ---help---
883 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
884
885 To compile this driver as a module, choose M here: the
886 module will be called wdt_pci.
887
888 config WDT_501_PCI
889 bool "PCI-WDT501 features"
890 depends on WDTPCI
891 help
892 Saying Y here and creating a character special file /dev/temperature
893 with major number 10 and minor number 131 ("man mknod") will give
894 you a thermometer inside your computer: reading from
895 /dev/temperature yields one byte, the temperature in degrees
896 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
897 installed.
898
899 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
900 can do this via the tachometer parameter. Only do this if you have a
901 fan tachometer actually set up.
902
903 #
904 # USB-based Watchdog Cards
905 #
906
907 comment "USB-based Watchdog Cards"
908 depends on USB
909
910 config USBPCWATCHDOG
911 tristate "Berkshire Products USB-PC Watchdog"
912 depends on USB
913 ---help---
914 This is the driver for the Berkshire Products USB-PC Watchdog card.
915 This card simply watches your kernel to make sure it doesn't freeze,
916 and if it does, it reboots your computer after a certain amount of
917 time. The card can also monitor the internal temperature of the PC.
918 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
919
920 To compile this driver as a module, choose M here: the
921 module will be called pcwd_usb.
922
923 Most people will say N.
924
925 endif # WATCHDOG
This page took 0.052053 seconds and 5 git commands to generate.