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
19 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
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.
69 config AT91SAM9X_WATCHDOG
70 tristate "AT91SAM9X watchdog"
71 depends on WATCHDOG && (ARCH_AT91SAM9260 || ARCH_AT91SAM9261)
73 Watchdog timer embedded into AT91SAM9X chips. This will reboot your
74 system when the timeout is reached.
77 tristate "DC21285 watchdog"
80 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
81 here if you wish to use this. Alternatively say M to compile the
82 driver as a module, which will be called wdt285.
84 This driver does not work on all machines. In particular, early CATS
85 boards have hardware problems that will cause the machine to simply
86 lock up if the watchdog fires.
88 "If in doubt, leave it out" - say N.
91 tristate "NetWinder WB83C977 watchdog"
92 depends on FOOTBRIDGE && ARCH_NETWINDER
94 Say Y here to include support for the WB977 watchdog included in
95 NetWinder machines. Alternatively say M to compile the driver as
96 a module, which will be called wdt977.
98 Not sure? It's safe to say N.
100 config IXP2000_WATCHDOG
101 tristate "IXP2000 Watchdog"
102 depends on ARCH_IXP2000
104 Say Y here if to include support for the watchdog timer
105 in the Intel IXP2000(2400, 2800, 2850) network processors.
106 This driver can be built as a module by choosing M. The module
107 will be called ixp2000_wdt.
109 Say N if you are unsure.
111 config IXP4XX_WATCHDOG
112 tristate "IXP4xx Watchdog"
113 depends on ARCH_IXP4XX
115 Say Y here if to include support for the watchdog timer
116 in the Intel IXP4xx network processors. This driver can
117 be built as a module by choosing M. The module will
118 be called ixp4xx_wdt.
120 Note: The internal IXP4xx watchdog does a soft CPU reset
121 which doesn't reset any peripherals. There are circumstances
122 where the watchdog will fail to reset the board correctly
123 (e.g., if the boot ROM is in an unreadable state).
125 Say N if you are unsure.
127 config KS8695_WATCHDOG
128 tristate "KS8695 watchdog"
129 depends on ARCH_KS8695
131 Watchdog timer embedded into KS8695 processor. This will reboot your
132 system when the timeout is reached.
134 config S3C2410_WATCHDOG
135 tristate "S3C2410 Watchdog"
136 depends on ARCH_S3C2410
138 Watchdog timer block in the Samsung S3C2410 chips. This will
139 reboot the system when the timer expires with the watchdog
142 The driver is limited by the speed of the system's PCLK
143 signal, so with reasonably fast systems (PCLK around 50-66MHz)
144 then watchdog intervals of over approximately 20seconds are
147 The driver can be built as a module by choosing M, and will
148 be called s3c2410_wdt
150 config SA1100_WATCHDOG
151 tristate "SA1100/PXA2xx watchdog"
152 depends on ARCH_SA1100 || ARCH_PXA
154 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
155 reboot your system when timeout is reached.
157 NOTE: once enabled, this timer cannot be disabled.
159 To compile this driver as a module, choose M here: the
160 module will be called sa1100_wdt.
162 config MPCORE_WATCHDOG
163 tristate "MPcore watchdog"
164 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
166 Watchdog timer embedded into the MPcore system.
168 To compile this driver as a module, choose M here: the
169 module will be called mpcore_wdt.
171 config EP93XX_WATCHDOG
172 tristate "EP93xx Watchdog"
173 depends on ARCH_EP93XX
175 Say Y here if to include support for the watchdog timer
176 embedded in the Cirrus Logic EP93xx family of devices.
178 To compile this driver as a module, choose M here: the
179 module will be called ep93xx_wdt.
182 tristate "OMAP Watchdog"
183 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
185 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
186 enable the OMAP1610/OMAP1710 watchdog timer.
188 config PNX4008_WATCHDOG
189 tristate "PNX4008 Watchdog"
190 depends on ARCH_PNX4008
192 Say Y here if to include support for the watchdog timer
193 in the PNX4008 processor.
194 This driver can be built as a module by choosing M. The module
195 will be called pnx4008_wdt.
197 Say N if you are unsure.
200 tristate "IOP Watchdog"
202 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
204 Say Y here if to include support for the watchdog timer
205 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
206 be built as a module by choosing M. The module will
209 Note: The IOP13XX watchdog does an Internal Bus Reset which will
210 affect both cores and the peripherals of the IOP. The ATU-X
211 and/or ATUe configuration registers will remain intact, but if
212 operating as an Root Complex and/or Central Resource, the PCI-X
213 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
215 config DAVINCI_WATCHDOG
216 tristate "DaVinci watchdog"
217 depends on ARCH_DAVINCI
219 Say Y here if to include support for the watchdog timer
220 in the DaVinci DM644x/DM646x processors.
221 To compile this driver as a module, choose M here: the
222 module will be called davinci_wdt.
224 NOTE: once enabled, this timer cannot be disabled.
225 Say N if you are unsure.
227 config ORION5X_WATCHDOG
228 tristate "Orion5x watchdog"
229 depends on ARCH_ORION5X
231 Say Y here if to include support for the watchdog timer
232 in the Orion5x ARM SoCs.
233 To compile this driver as a module, choose M here: the
234 module will be called orion5x_wdt.
240 config AT32AP700X_WDT
241 tristate "AT32AP700x watchdog"
242 depends on CPU_AT32AP700X
244 Watchdog timer embedded into AT32AP700x devices. This will reboot
245 your system when the timeout is reached.
247 # BLACKFIN Architecture
250 tristate "Blackfin On-Chip Watchdog Timer"
253 If you say yes here you will get support for the Blackfin On-Chip
254 Watchdog Timer. If you have one of these processors and wish to
255 have watchdog support enabled, say Y, otherwise say N.
257 To compile this driver as a module, choose M here: the
258 module will be called bfin_wdt.
266 # X86 (i386 + ia64 + x86_64) Architecture
269 tristate "Acquire SBC Watchdog Timer"
272 This is the driver for the hardware watchdog on Single Board
273 Computers produced by Acquire Inc (and others). This watchdog
274 simply watches your kernel to make sure it doesn't freeze, and if
275 it does, it reboots your computer after a certain amount of time.
277 To compile this driver as a module, choose M here: the
278 module will be called acquirewdt.
280 Most people will say N.
283 tristate "Advantech SBC Watchdog Timer"
286 If you are configuring a Linux kernel for the Advantech single-board
287 computer, say `Y' here to support its built-in watchdog timer
288 feature. More information can be found at
289 <http://www.advantech.com.tw/products/>
292 tristate "ALi M1535 PMU Watchdog Timer"
293 depends on X86 && PCI
295 This is the driver for the hardware watchdog on the ALi M1535 PMU.
297 To compile this driver as a module, choose M here: the
298 module will be called alim1535_wdt.
300 Most people will say N.
303 tristate "ALi M7101 PMU Computer Watchdog"
306 This is the driver for the hardware watchdog on the ALi M7101 PMU
307 as used in the x86 Cobalt servers and also found in some
308 SPARC Netra servers too.
310 To compile this driver as a module, choose M here: the
311 module will be called alim7101_wdt.
313 Most people will say N.
316 tristate "AMD Geode CS5535/CS5536 Watchdog"
319 This driver enables a watchdog capability built into the
320 CS5535/CS5536 companion chips for the AMD Geode GX and LX
321 processors. This watchdog watches your kernel to make sure
322 it doesn't freeze, and if it does, it reboots your computer after
323 a certain amount of time.
325 You can compile this driver directly into the kernel, or use
326 it as a module. The module will be called geodewdt.
329 tristate "AMD Elan SC520 processor Watchdog"
332 This is the driver for the hardware watchdog built in to the
333 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
334 This watchdog simply watches your kernel to make sure it doesn't
335 freeze, and if it does, it reboots your computer after a certain
338 You can compile this driver directly into the kernel, or use
339 it as a module. The module will be called sc520_wdt.
342 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
345 Enable support for the watchdog timer on the Eurotech CPU-1220 and
346 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
347 information are at <http://www.eurotech.it/>.
350 tristate "IB700 SBC Watchdog Timer"
353 This is the driver for the hardware watchdog on the IB700 Single
354 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
355 simply watches your kernel to make sure it doesn't freeze, and if
356 it does, it reboots your computer after a certain amount of time.
358 This driver is like the WDT501 driver but for slightly different hardware.
360 To compile this driver as a module, choose M here: the
361 module will be called ib700wdt.
363 Most people will say N.
366 tristate "IBM Automatic Server Restart"
369 This is the driver for the IBM Automatic Server Restart watchdog
370 timer built-in into some eServer xSeries machines.
372 To compile this driver as a module, choose M here: the
373 module will be called ibmasr.
376 tristate "ICP Single Board Computer Watchdog Timer"
379 This is a driver for the hardware watchdog on the ICP Single
380 Board Computer. This driver is working on (at least) the following
381 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
383 To compile this driver as a module, choose M here: the
384 module will be called wafer5823wdt.
387 tristate "Intel 6300ESB Timer/Watchdog"
388 depends on X86 && PCI
390 Hardware driver for the watchdog timer built into the Intel
391 6300ESB controller hub.
393 To compile this driver as a module, choose M here: the
394 module will be called i6300esb.
397 tristate "Intel TCO Timer/Watchdog"
398 depends on (X86 || IA64) && PCI
400 Hardware driver for the intel TCO timer based watchdog devices.
401 These drivers are included in the Intel 82801 I/O Controller
402 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
405 The TCO (Total Cost of Ownership) timer is a watchdog timer
406 that will reboot the machine after its second expiration. The
407 expiration time can be configured with the "heartbeat" parameter.
409 On some motherboards the driver may fail to reset the chipset's
410 NO_REBOOT flag which prevents the watchdog from rebooting the
411 machine. If this is the case you will get a kernel message like
412 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
414 To compile this driver as a module, choose M here: the
415 module will be called iTCO_wdt.
417 config ITCO_VENDOR_SUPPORT
418 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
421 Add vendor specific support to the intel TCO timer based watchdog
422 devices. At this moment we only have additional support for some
423 SuperMicro Inc. motherboards.
426 tristate "IT8712F (Smart Guardian) Watchdog Timer"
429 This is the driver for the built-in watchdog timer on the IT8712F
430 Super I/0 chipset used on many motherboards.
432 To compile this driver as a module, choose M here: the
433 module will be called it8712f_wdt.
436 tristate "IT87 Watchdog Timer"
437 depends on X86 && EXPERIMENTAL
439 This is the driver for the hardware watchdog on the ITE IT8716,
440 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
441 simply watches your kernel to make sure it doesn't freeze, and if
442 it does, it reboots your computer after a certain amount of time.
444 To compile this driver as a module, choose M here: the module will
448 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
451 A software monitoring watchdog and NMI sourcing driver. This driver
452 will detect lockups and provide stack trace. Also, when an NMI
453 occurs this driver will make the necessary BIOS calls to log
454 the cause of the NMI. This is a driver that will only load on a
455 HP ProLiant system with a minimum of iLO2 support.
456 To compile this driver as a module, choose M here: the
457 module will be called hpwdt.
460 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
463 This is a driver for National Semiconductor PC87307/PC97307 hardware
464 watchdog cards as found on the SC1200. This watchdog is mainly used
465 for power management purposes and can be used to power down the device
466 during inactivity periods (includes interrupt activity monitoring).
468 To compile this driver as a module, choose M here: the
469 module will be called sc1200wdt.
471 Most people will say N.
474 tristate "National Semiconductor SCx200 Watchdog"
475 depends on SCx200 && PCI
477 Enable the built-in watchdog timer support on the National
478 Semiconductor SCx200 processors.
480 If compiled as a module, it will be called scx200_wdt.
483 tristate "NS PC87413 watchdog"
486 This is the driver for the hardware watchdog on the PC87413 chipset
487 This watchdog simply watches your kernel to make sure it doesn't
488 freeze, and if it does, it reboots your computer after a certain
491 To compile this driver as a module, choose M here: the
492 module will be called pc87413_wdt.
494 Most people will say N.
497 tristate "RDC R-321x SoC watchdog"
498 depends on X86_RDC321X
500 This is the driver for the built in hardware watchdog
501 in the RDC R-321x SoC.
503 To compile this driver as a module, choose M here: the
504 module will be called rdc321x_wdt.
507 tristate "SBC-60XX Watchdog Timer"
510 This driver can be used with the watchdog timer found on some
511 single board computers, namely the 6010 PII based computer.
512 It may well work with other cards. It reads port 0x443 to enable
513 and re-set the watchdog timer, and reads port 0x45 to disable
514 the watchdog. If you have a card that behave in similar ways,
515 you can probably make this driver work with your card as well.
517 You can compile this driver directly into the kernel, or use
518 it as a module. The module will be called sbc60xxwdt.
521 tristate "SBC8360 Watchdog Timer"
525 This is the driver for the hardware watchdog on the SBC8360 Single
526 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
528 To compile this driver as a module, choose M here: the
529 module will be called sbc8360.ko.
531 Most people will say N.
534 tristate "SBC Nano 7240 Watchdog Timer"
537 This is the driver for the hardware watchdog found on the IEI
538 single board computers EPIC Nano 7240 (and likely others). This
539 watchdog 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
543 To compile this driver as a module, choose M here: the
544 module will be called sbc7240_wdt.
547 tristate "SMA CPU5 Watchdog"
551 To compile this driver as a module, choose M here: the
552 module will be called cpu5wdt.
554 config SMSC37B787_WDT
555 tristate "Winbond SMsC37B787 Watchdog Timer"
558 This is the driver for the hardware watchdog component on the
559 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
560 from Vision Systems and maybe others.
562 This watchdog simply watches your kernel to make sure it doesn't
563 freeze, and if it does, it reboots your computer after a certain
566 Usually a userspace daemon will notify the kernel WDT driver that
567 userspace is still alive, at regular intervals.
569 To compile this driver as a module, choose M here: the
570 module will be called smsc37b787_wdt.
572 Most people will say N.
575 tristate "W83627HF Watchdog Timer"
578 This is the driver for the hardware watchdog on the W83627HF chipset
579 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
580 (and likely others). This watchdog simply watches your kernel to
581 make sure it doesn't freeze, and if it does, it reboots your computer
582 after a certain amount of time.
584 To compile this driver as a module, choose M here: the
585 module will be called w83627hf_wdt.
587 Most people will say N.
590 tristate "W83697HF/W83697HG Watchdog Timer"
593 This is the driver for the hardware watchdog on the W83697HF/HG
594 chipset as used in Dedibox/VIA motherboards (and likely others).
595 This watchdog simply watches your kernel to make sure it doesn't
596 freeze, and if it does, it reboots your computer after a certain
599 To compile this driver as a module, choose M here: the
600 module will be called w83697hf_wdt.
602 Most people will say N.
605 tristate "W83697UG/W83697UF Watchdog Timer"
608 This is the driver for the hardware watchdog on the W83697UG/UF
609 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
610 This watchdog simply watches your kernel to make sure it doesn't
611 freeze, and if it does, it reboots your computer after a certain
614 To compile this driver as a module, choose M here: the
615 module will be called w83697ug_wdt.
617 Most people will say N.
620 tristate "W83877F (EMACS) Watchdog Timer"
623 This is the driver for the hardware watchdog on the W83877F chipset
624 as used in EMACS PC-104 motherboards (and likely others). This
625 watchdog simply watches your kernel to make sure it doesn't freeze,
626 and if it does, it reboots your computer after a certain amount of
629 To compile this driver as a module, choose M here: the
630 module will be called w83877f_wdt.
632 Most people will say N.
635 tristate "W83977F (PCM-5335) Watchdog Timer"
638 This is the driver for the hardware watchdog on the W83977F I/O chip
639 as used in AAEON's PCM-5335 SBC (and likely others). This
640 watchdog simply watches your kernel to make sure it doesn't freeze,
641 and if it does, it reboots your computer after a certain amount of
644 To compile this driver as a module, choose M here: the
645 module will be called w83977f_wdt.
648 tristate "ZF MachZ Watchdog"
651 If you are using a ZF Micro MachZ processor, say Y here, otherwise
652 N. This is the driver for the watchdog timer built-in on that
653 processor using ZF-Logic interface. This watchdog simply watches
654 your kernel to make sure it doesn't freeze, and if it does, it
655 reboots your computer after a certain amount of time.
657 To compile this driver as a module, choose M here: the
658 module will be called machzwd.
660 config SBC_EPX_C3_WATCHDOG
661 tristate "Winsystems SBC EPX-C3 watchdog"
664 This is the driver for the built-in watchdog timer on the EPX-C3
665 Single-board computer made by Winsystems, Inc.
667 *Note*: This hardware watchdog is not probeable and thus there
668 is no way to know if writing to its IO address will corrupt
669 your system or have any real effect. The only way to be sure
670 that this driver does what you want is to make sure you
671 are running it on an EPX-C3 from Winsystems with the watchdog
672 timer at IO address 0x1ee and 0x1ef. It will write to both those
673 IO ports. Basically, the assumption is made that if you compile
674 this driver into your kernel and/or load it as a module, that you
675 know what you are doing and that you are in fact running on an
678 To compile this driver as a module, choose M here: the
679 module will be called sbc_epx_c3.
685 # M68KNOMMU Architecture
690 tristate "IDT RC32434 SoC Watchdog Timer"
691 depends on MIKROTIK_RB532
693 Hardware driver for the IDT RC32434 SoC built-in
696 To compile this driver as a module, choose M here: the
697 module will be called rc32434_wdt.
700 tristate "Indy/I2 Hardware Watchdog"
701 depends on SGI_HAS_INDYDOG
703 Hardware driver for the Indy's/I2's watchdog. This is a
704 watchdog timer that will reboot the machine after a 60 second
705 timer expired and no process has written to /dev/watchdog during
709 tristate "MTX-1 Hardware Watchdog"
712 Hardware driver for the MTX-1 boards. This is a watchdog timer that
713 will reboot the machine after a 100 seconds timer expired.
716 tristate "RM9000/GPI hardware watchdog"
717 depends on CPU_RM9000
719 Watchdog implementation using the GPI hardware found on
720 PMC-Sierra RM9xxx CPUs.
722 To compile this driver as a module, choose M here: the
723 module will be called rm9k_wdt.
726 tristate "Sibyte SoC hardware watchdog"
729 Watchdog driver for the built in watchdog hardware in Sibyte
730 SoC processors. There are apparently two watchdog timers
731 on such processors; this driver supports only the first one,
732 because currently Linux only supports exporting one watchdog
735 To compile this driver as a loadable module, choose M here.
736 The module will be called sb_wdog.
739 tristate "TI AR7 Watchdog Timer"
742 Hardware driver for the TI AR7 Watchdog Timer.
745 tristate "Toshiba TXx9 Watchdog Timer"
746 depends on CPU_TX39XX || CPU_TX49XX
748 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
750 # PARISC Architecture
752 # POWERPC Architecture
755 tristate "MPC5200 Watchdog Timer"
756 depends on PPC_MPC52xx
759 tristate "MPC8xxx Platform Watchdog Timer"
760 depends on PPC_8xx || PPC_83xx || PPC_86xx
762 This driver is for a SoC level watchdog that exists on some
763 Freescale PowerPC processors. So far this driver supports:
768 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
771 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
775 bool "PowerPC Book-E Watchdog Timer"
776 depends on BOOKE || 4xx
778 Please see Documentation/watchdog/watchdog-api.txt for
784 tristate "RTAS watchdog"
787 This driver adds watchdog support for the RTAS watchdog.
789 To compile this driver as a module, choose M here. The module
790 will be called wdrtas.
795 tristate "z/VM Watchdog Timer"
798 IBM s/390 and zSeries machines running under z/VM 5.1 or later
799 provide a virtual watchdog timer to their guest that cause a
800 user define Control Program command to be executed after a
803 To compile this driver as a module, choose M here. The module
804 will be called vmwatchdog.
806 # SUPERH (sh + sh64) Architecture
809 tristate "SuperH Watchdog"
810 depends on SUPERH && (CPU_SH3 || CPU_SH4)
812 This driver adds watchdog support for the integrated watchdog in the
813 SuperH processors. If you have one of these processors and wish
814 to have watchdog support enabled, say Y, otherwise say N.
816 As a side note, saying Y here will automatically boost HZ to 1000
817 so that the timer has a chance to clear the overflow counter. On
818 slower systems (such as the SH-2 and SH-3) this will likely yield
819 some performance issues. As such, the WDT should be avoided here
820 unless it is absolutely necessary.
822 To compile this driver as a module, choose M here: the
823 module will be called shwdt.
826 bool "Allow mmap of SH WDT"
830 If you say Y here, user applications will be able to mmap the
835 # SPARC64 Architecture
837 config WATCHDOG_CP1XXX
838 tristate "CP1XXX Hardware Watchdog support"
839 depends on SPARC64 && PCI
841 This is the driver for the hardware watchdog timers present on
842 Sun Microsystems CompactPCI models CP1400 and CP1500.
844 To compile this driver as a module, choose M here: the
845 module will be called cpwatchdog.
847 If you do not have a CompactPCI model CP1400 or CP1500, or
848 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
849 you should say N to this option.
852 tristate "RIO Hardware Watchdog support"
853 depends on SPARC64 && PCI
855 Say Y here to support the hardware watchdog capability on Sun RIO
856 machines. The watchdog timeout period is normally one minute but
857 can be changed with a boot-time parameter.
859 # XTENSA Architecture
862 # ISA-based Watchdog Cards
865 comment "ISA-based Watchdog Cards"
869 tristate "Berkshire Products ISA-PC Watchdog"
872 This is the driver for the Berkshire Products ISA-PC Watchdog card.
873 This card simply watches your kernel to make sure it doesn't freeze,
874 and if it does, it reboots your computer after a certain amount of
875 time. This driver is like the WDT501 driver but for different
876 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
877 watchdog cards can be ordered from <http://www.berkprod.com/>.
879 To compile this driver as a module, choose M here: the
880 module will be called pcwd.
882 Most people will say N.
885 tristate "Mixcom Watchdog"
888 This is a driver for the Mixcom hardware watchdog cards. This
889 watchdog simply watches your kernel to make sure it doesn't freeze,
890 and if it does, it reboots your computer after a certain amount of
893 To compile this driver as a module, choose M here: the
894 module will be called mixcomwd.
896 Most people will say N.
899 tristate "WDT Watchdog timer"
902 If you have a WDT500P or WDT501P watchdog board, say Y here,
903 otherwise N. It is not possible to probe for this board, which means
904 that you have to inform the kernel about the IO port and IRQ that
905 is needed (you can do this via the io and irq parameters)
907 To compile this driver as a module, choose M here: the
908 module will be called wdt.
911 bool "WDT501 features"
914 Saying Y here and creating a character special file /dev/temperature
915 with major number 10 and minor number 131 ("man mknod") will give
916 you a thermometer inside your computer: reading from
917 /dev/temperature yields one byte, the temperature in degrees
918 Fahrenheit. This works only if you have a WDT501P watchdog board
921 If you want to enable the Fan Tachometer on the WDT501P, then you
922 can do this via the tachometer parameter. Only do this if you have a
923 fan tachometer actually set up.
926 # PCI-based Watchdog Cards
929 comment "PCI-based Watchdog Cards"
933 tristate "Berkshire Products PCI-PC Watchdog"
936 This is the driver for the Berkshire Products PCI-PC Watchdog card.
937 This card simply watches your kernel to make sure it doesn't freeze,
938 and if it does, it reboots your computer after a certain amount of
939 time. The card can also monitor the internal temperature of the PC.
940 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
942 To compile this driver as a module, choose M here: the
943 module will be called pcwd_pci.
945 Most people will say N.
948 tristate "PCI-WDT500/501 Watchdog timer"
951 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
953 To compile this driver as a module, choose M here: the
954 module will be called wdt_pci.
957 bool "PCI-WDT501 features"
960 Saying Y here and creating a character special file /dev/temperature
961 with major number 10 and minor number 131 ("man mknod") will give
962 you a thermometer inside your computer: reading from
963 /dev/temperature yields one byte, the temperature in degrees
964 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
967 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
968 can do this via the tachometer parameter. Only do this if you have a
969 fan tachometer actually set up.
972 # USB-based Watchdog Cards
975 comment "USB-based Watchdog Cards"
979 tristate "Berkshire Products USB-PC Watchdog"
982 This is the driver for the Berkshire Products USB-PC Watchdog card.
983 This card simply watches your kernel to make sure it doesn't freeze,
984 and if it does, it reboots your computer after a certain amount of
985 time. The card can also monitor the internal temperature of the PC.
986 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
988 To compile this driver as a module, choose M here: the
989 module will be called pcwd_usb.
991 Most people will say N.