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.
58 config WM8350_WATCHDOG
59 tristate "WM8350 watchdog"
62 Support for the watchdog in the WM8350 AudioPlus PMIC. When
63 the watchdog triggers the system will be reset.
69 config AT91RM9200_WATCHDOG
70 tristate "AT91RM9200 watchdog"
71 depends on ARCH_AT91RM9200
73 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
74 system when the timeout is reached.
76 config AT91SAM9X_WATCHDOG
77 tristate "AT91SAM9X / AT91CAP9 watchdog"
78 depends on ARCH_AT91 && !ARCH_AT91RM9200
80 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
81 reboot your system when the timeout is reached.
84 tristate "DC21285 watchdog"
87 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
88 here if you wish to use this. Alternatively say M to compile the
89 driver as a module, which will be called wdt285.
91 This driver does not work on all machines. In particular, early CATS
92 boards have hardware problems that will cause the machine to simply
93 lock up if the watchdog fires.
95 "If in doubt, leave it out" - say N.
98 tristate "NetWinder WB83C977 watchdog"
99 depends on FOOTBRIDGE && ARCH_NETWINDER
101 Say Y here to include support for the WB977 watchdog included in
102 NetWinder machines. Alternatively say M to compile the driver as
103 a module, which will be called wdt977.
105 Not sure? It's safe to say N.
107 config IXP2000_WATCHDOG
108 tristate "IXP2000 Watchdog"
109 depends on ARCH_IXP2000
111 Say Y here if to include support for the watchdog timer
112 in the Intel IXP2000(2400, 2800, 2850) network processors.
113 This driver can be built as a module by choosing M. The module
114 will be called ixp2000_wdt.
116 Say N if you are unsure.
118 config IXP4XX_WATCHDOG
119 tristate "IXP4xx Watchdog"
120 depends on ARCH_IXP4XX
122 Say Y here if to include support for the watchdog timer
123 in the Intel IXP4xx network processors. This driver can
124 be built as a module by choosing M. The module will
125 be called ixp4xx_wdt.
127 Note: The internal IXP4xx watchdog does a soft CPU reset
128 which doesn't reset any peripherals. There are circumstances
129 where the watchdog will fail to reset the board correctly
130 (e.g., if the boot ROM is in an unreadable state).
132 Say N if you are unsure.
134 config KS8695_WATCHDOG
135 tristate "KS8695 watchdog"
136 depends on ARCH_KS8695
138 Watchdog timer embedded into KS8695 processor. This will reboot your
139 system when the timeout is reached.
141 config S3C2410_WATCHDOG
142 tristate "S3C2410 Watchdog"
143 depends on ARCH_S3C2410
145 Watchdog timer block in the Samsung S3C2410 chips. This will
146 reboot the system when the timer expires with the watchdog
149 The driver is limited by the speed of the system's PCLK
150 signal, so with reasonably fast systems (PCLK around 50-66MHz)
151 then watchdog intervals of over approximately 20seconds are
154 The driver can be built as a module by choosing M, and will
155 be called s3c2410_wdt
157 config SA1100_WATCHDOG
158 tristate "SA1100/PXA2xx watchdog"
159 depends on ARCH_SA1100 || ARCH_PXA
161 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
162 reboot your system when timeout is reached.
164 NOTE: once enabled, this timer cannot be disabled.
166 To compile this driver as a module, choose M here: the
167 module will be called sa1100_wdt.
169 config MPCORE_WATCHDOG
170 tristate "MPcore watchdog"
171 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
173 Watchdog timer embedded into the MPcore system.
175 To compile this driver as a module, choose M here: the
176 module will be called mpcore_wdt.
178 config EP93XX_WATCHDOG
179 tristate "EP93xx Watchdog"
180 depends on ARCH_EP93XX
182 Say Y here if to include support for the watchdog timer
183 embedded in the Cirrus Logic EP93xx family of devices.
185 To compile this driver as a module, choose M here: the
186 module will be called ep93xx_wdt.
189 tristate "OMAP Watchdog"
190 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
192 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
193 enable the OMAP1610/OMAP1710 watchdog timer.
195 config PNX4008_WATCHDOG
196 tristate "PNX4008 Watchdog"
197 depends on ARCH_PNX4008
199 Say Y here if to include support for the watchdog timer
200 in the PNX4008 processor.
201 This driver can be built as a module by choosing M. The module
202 will be called pnx4008_wdt.
204 Say N if you are unsure.
207 tristate "IOP Watchdog"
209 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
211 Say Y here if to include support for the watchdog timer
212 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
213 be built as a module by choosing M. The module will
216 Note: The IOP13XX watchdog does an Internal Bus Reset which will
217 affect both cores and the peripherals of the IOP. The ATU-X
218 and/or ATUe configuration registers will remain intact, but if
219 operating as an Root Complex and/or Central Resource, the PCI-X
220 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
222 config DAVINCI_WATCHDOG
223 tristate "DaVinci watchdog"
224 depends on ARCH_DAVINCI
226 Say Y here if to include support for the watchdog timer
227 in the DaVinci DM644x/DM646x processors.
228 To compile this driver as a module, choose M here: the
229 module will be called davinci_wdt.
231 NOTE: once enabled, this timer cannot be disabled.
232 Say N if you are unsure.
234 config ORION5X_WATCHDOG
235 tristate "Orion5x watchdog"
236 depends on ARCH_ORION5X
238 Say Y here if to include support for the watchdog timer
239 in the Orion5x ARM SoCs.
240 To compile this driver as a module, choose M here: the
241 module will be called orion5x_wdt.
247 config AT32AP700X_WDT
248 tristate "AT32AP700x watchdog"
249 depends on CPU_AT32AP700X
251 Watchdog timer embedded into AT32AP700x devices. This will reboot
252 your system when the timeout is reached.
254 # BLACKFIN Architecture
257 tristate "Blackfin On-Chip Watchdog Timer"
260 If you say yes here you will get support for the Blackfin On-Chip
261 Watchdog Timer. If you have one of these processors and wish to
262 have watchdog support enabled, say Y, otherwise say N.
264 To compile this driver as a module, choose M here: the
265 module will be called bfin_wdt.
273 # X86 (i386 + ia64 + x86_64) Architecture
276 tristate "Acquire SBC Watchdog Timer"
279 This is the driver for the hardware watchdog on Single Board
280 Computers produced by Acquire Inc (and others). This watchdog
281 simply watches your kernel to make sure it doesn't freeze, and if
282 it does, it reboots your computer after a certain amount of time.
284 To compile this driver as a module, choose M here: the
285 module will be called acquirewdt.
287 Most people will say N.
290 tristate "Advantech SBC Watchdog Timer"
293 If you are configuring a Linux kernel for the Advantech single-board
294 computer, say `Y' here to support its built-in watchdog timer
295 feature. More information can be found at
296 <http://www.advantech.com.tw/products/>
299 tristate "ALi M1535 PMU Watchdog Timer"
300 depends on X86 && PCI
302 This is the driver for the hardware watchdog on the ALi M1535 PMU.
304 To compile this driver as a module, choose M here: the
305 module will be called alim1535_wdt.
307 Most people will say N.
310 tristate "ALi M7101 PMU Computer Watchdog"
313 This is the driver for the hardware watchdog on the ALi M7101 PMU
314 as used in the x86 Cobalt servers and also found in some
315 SPARC Netra servers too.
317 To compile this driver as a module, choose M here: the
318 module will be called alim7101_wdt.
320 Most people will say N.
323 tristate "AMD Geode CS5535/CS5536 Watchdog"
326 This driver enables a watchdog capability built into the
327 CS5535/CS5536 companion chips for the AMD Geode GX and LX
328 processors. This watchdog watches your kernel to make sure
329 it doesn't freeze, and if it does, it reboots your computer after
330 a certain amount of time.
332 You can compile this driver directly into the kernel, or use
333 it as a module. The module will be called geodewdt.
336 tristate "AMD Elan SC520 processor Watchdog"
339 This is the driver for the hardware watchdog built in to the
340 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
341 This watchdog simply watches your kernel to make sure it doesn't
342 freeze, and if it does, it reboots your computer after a certain
345 You can compile this driver directly into the kernel, or use
346 it as a module. The module will be called sc520_wdt.
349 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
352 Enable support for the watchdog timer on the Eurotech CPU-1220 and
353 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
354 information are at <http://www.eurotech.it/>.
357 tristate "IB700 SBC Watchdog Timer"
360 This is the driver for the hardware watchdog on the IB700 Single
361 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
362 simply watches your kernel to make sure it doesn't freeze, and if
363 it does, it reboots your computer after a certain amount of time.
365 This driver is like the WDT501 driver but for slightly different hardware.
367 To compile this driver as a module, choose M here: the
368 module will be called ib700wdt.
370 Most people will say N.
373 tristate "IBM Automatic Server Restart"
376 This is the driver for the IBM Automatic Server Restart watchdog
377 timer built-in into some eServer xSeries machines.
379 To compile this driver as a module, choose M here: the
380 module will be called ibmasr.
383 tristate "ICP Single Board Computer Watchdog Timer"
386 This is a driver for the hardware watchdog on the ICP Single
387 Board Computer. This driver is working on (at least) the following
388 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
390 To compile this driver as a module, choose M here: the
391 module will be called wafer5823wdt.
394 tristate "Intel 6300ESB Timer/Watchdog"
395 depends on X86 && PCI
397 Hardware driver for the watchdog timer built into the Intel
398 6300ESB controller hub.
400 To compile this driver as a module, choose M here: the
401 module will be called i6300esb.
404 tristate "Intel TCO Timer/Watchdog"
405 depends on (X86 || IA64) && PCI
407 Hardware driver for the intel TCO timer based watchdog devices.
408 These drivers are included in the Intel 82801 I/O Controller
409 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
412 The TCO (Total Cost of Ownership) timer is a watchdog timer
413 that will reboot the machine after its second expiration. The
414 expiration time can be configured with the "heartbeat" parameter.
416 On some motherboards the driver may fail to reset the chipset's
417 NO_REBOOT flag which prevents the watchdog from rebooting the
418 machine. If this is the case you will get a kernel message like
419 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
421 To compile this driver as a module, choose M here: the
422 module will be called iTCO_wdt.
424 config ITCO_VENDOR_SUPPORT
425 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
428 Add vendor specific support to the intel TCO timer based watchdog
429 devices. At this moment we only have additional support for some
430 SuperMicro Inc. motherboards.
433 tristate "IT8712F (Smart Guardian) Watchdog Timer"
436 This is the driver for the built-in watchdog timer on the IT8712F
437 Super I/0 chipset used on many motherboards.
439 To compile this driver as a module, choose M here: the
440 module will be called it8712f_wdt.
443 tristate "IT87 Watchdog Timer"
444 depends on X86 && EXPERIMENTAL
446 This is the driver for the hardware watchdog on the ITE IT8716,
447 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
448 simply watches your kernel to make sure it doesn't freeze, and if
449 it does, it reboots your computer after a certain amount of time.
451 To compile this driver as a module, choose M here: the module will
455 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
458 A software monitoring watchdog and NMI sourcing driver. This driver
459 will detect lockups and provide stack trace. Also, when an NMI
460 occurs this driver will make the necessary BIOS calls to log
461 the cause of the NMI. This is a driver that will only load on a
462 HP ProLiant system with a minimum of iLO2 support.
463 To compile this driver as a module, choose M here: the
464 module will be called hpwdt.
467 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
470 This is a driver for National Semiconductor PC87307/PC97307 hardware
471 watchdog cards as found on the SC1200. This watchdog is mainly used
472 for power management purposes and can be used to power down the device
473 during inactivity periods (includes interrupt activity monitoring).
475 To compile this driver as a module, choose M here: the
476 module will be called sc1200wdt.
478 Most people will say N.
481 tristate "National Semiconductor SCx200 Watchdog"
482 depends on SCx200 && PCI
484 Enable the built-in watchdog timer support on the National
485 Semiconductor SCx200 processors.
487 If compiled as a module, it will be called scx200_wdt.
490 tristate "NS PC87413 watchdog"
493 This is the driver for the hardware watchdog on the PC87413 chipset
494 This watchdog simply watches your kernel to make sure it doesn't
495 freeze, and if it does, it reboots your computer after a certain
498 To compile this driver as a module, choose M here: the
499 module will be called pc87413_wdt.
501 Most people will say N.
504 tristate "RDC R-321x SoC watchdog"
505 depends on X86_RDC321X
507 This is the driver for the built in hardware watchdog
508 in the RDC R-321x SoC.
510 To compile this driver as a module, choose M here: the
511 module will be called rdc321x_wdt.
514 tristate "SBC-60XX Watchdog Timer"
517 This driver can be used with the watchdog timer found on some
518 single board computers, namely the 6010 PII based computer.
519 It may well work with other cards. It reads port 0x443 to enable
520 and re-set the watchdog timer, and reads port 0x45 to disable
521 the watchdog. If you have a card that behave in similar ways,
522 you can probably make this driver work with your card as well.
524 You can compile this driver directly into the kernel, or use
525 it as a module. The module will be called sbc60xxwdt.
528 tristate "SBC8360 Watchdog Timer"
532 This is the driver for the hardware watchdog on the SBC8360 Single
533 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
535 To compile this driver as a module, choose M here: the
536 module will be called sbc8360.ko.
538 Most people will say N.
541 tristate "SBC Nano 7240 Watchdog Timer"
544 This is the driver for the hardware watchdog found on the IEI
545 single board computers EPIC Nano 7240 (and likely others). This
546 watchdog simply watches your kernel to make sure it doesn't freeze,
547 and if it does, it reboots your computer after a certain amount of
550 To compile this driver as a module, choose M here: the
551 module will be called sbc7240_wdt.
554 tristate "SMA CPU5 Watchdog"
558 To compile this driver as a module, choose M here: the
559 module will be called cpu5wdt.
561 config SMSC_SCH311X_WDT
562 tristate "SMSC SCH311X Watchdog Timer"
565 This is the driver for the hardware watchdog timer on the
566 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
567 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
570 To compile this driver as a module, choose M here: the
571 module will be called sch311x_wdt.
573 config SMSC37B787_WDT
574 tristate "Winbond SMsC37B787 Watchdog Timer"
577 This is the driver for the hardware watchdog component on the
578 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
579 from Vision Systems and maybe others.
581 This watchdog simply watches your kernel to make sure it doesn't
582 freeze, and if it does, it reboots your computer after a certain
585 Usually a userspace daemon will notify the kernel WDT driver that
586 userspace is still alive, at regular intervals.
588 To compile this driver as a module, choose M here: the
589 module will be called smsc37b787_wdt.
591 Most people will say N.
594 tristate "W83627HF Watchdog Timer"
597 This is the driver for the hardware watchdog on the W83627HF chipset
598 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
599 (and likely others). This watchdog simply watches your kernel to
600 make sure it doesn't freeze, and if it does, it reboots your computer
601 after a certain amount of time.
603 To compile this driver as a module, choose M here: the
604 module will be called w83627hf_wdt.
606 Most people will say N.
609 tristate "W83697HF/W83697HG Watchdog Timer"
612 This is the driver for the hardware watchdog on the W83697HF/HG
613 chipset as used in Dedibox/VIA motherboards (and likely others).
614 This watchdog simply watches your kernel to make sure it doesn't
615 freeze, and if it does, it reboots your computer after a certain
618 To compile this driver as a module, choose M here: the
619 module will be called w83697hf_wdt.
621 Most people will say N.
624 tristate "W83697UG/W83697UF Watchdog Timer"
627 This is the driver for the hardware watchdog on the W83697UG/UF
628 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
629 This watchdog simply watches your kernel to make sure it doesn't
630 freeze, and if it does, it reboots your computer after a certain
633 To compile this driver as a module, choose M here: the
634 module will be called w83697ug_wdt.
636 Most people will say N.
639 tristate "W83877F (EMACS) Watchdog Timer"
642 This is the driver for the hardware watchdog on the W83877F chipset
643 as used in EMACS PC-104 motherboards (and likely others). This
644 watchdog simply watches your kernel to make sure it doesn't freeze,
645 and if it does, it reboots your computer after a certain amount of
648 To compile this driver as a module, choose M here: the
649 module will be called w83877f_wdt.
651 Most people will say N.
654 tristate "W83977F (PCM-5335) Watchdog Timer"
657 This is the driver for the hardware watchdog on the W83977F I/O chip
658 as used in AAEON's PCM-5335 SBC (and likely others). This
659 watchdog simply watches your kernel to make sure it doesn't freeze,
660 and if it does, it reboots your computer after a certain amount of
663 To compile this driver as a module, choose M here: the
664 module will be called w83977f_wdt.
667 tristate "ZF MachZ Watchdog"
670 If you are using a ZF Micro MachZ processor, say Y here, otherwise
671 N. This is the driver for the watchdog timer built-in on that
672 processor using ZF-Logic interface. This watchdog simply watches
673 your kernel to make sure it doesn't freeze, and if it does, it
674 reboots your computer after a certain amount of time.
676 To compile this driver as a module, choose M here: the
677 module will be called machzwd.
679 config SBC_EPX_C3_WATCHDOG
680 tristate "Winsystems SBC EPX-C3 watchdog"
683 This is the driver for the built-in watchdog timer on the EPX-C3
684 Single-board computer made by Winsystems, Inc.
686 *Note*: This hardware watchdog is not probeable and thus there
687 is no way to know if writing to its IO address will corrupt
688 your system or have any real effect. The only way to be sure
689 that this driver does what you want is to make sure you
690 are running it on an EPX-C3 from Winsystems with the watchdog
691 timer at IO address 0x1ee and 0x1ef. It will write to both those
692 IO ports. Basically, the assumption is made that if you compile
693 this driver into your kernel and/or load it as a module, that you
694 know what you are doing and that you are in fact running on an
697 To compile this driver as a module, choose M here: the
698 module will be called sbc_epx_c3.
704 # M68KNOMMU Architecture
709 tristate "IDT RC32434 SoC Watchdog Timer"
710 depends on MIKROTIK_RB532
712 Hardware driver for the IDT RC32434 SoC built-in
715 To compile this driver as a module, choose M here: the
716 module will be called rc32434_wdt.
719 tristate "Indy/I2 Hardware Watchdog"
720 depends on SGI_HAS_INDYDOG
722 Hardware driver for the Indy's/I2's watchdog. This is a
723 watchdog timer that will reboot the machine after a 60 second
724 timer expired and no process has written to /dev/watchdog during
728 tristate "MTX-1 Hardware Watchdog"
731 Hardware driver for the MTX-1 boards. This is a watchdog timer that
732 will reboot the machine after a 100 seconds timer expired.
735 tristate "RM9000/GPI hardware watchdog"
736 depends on CPU_RM9000
738 Watchdog implementation using the GPI hardware found on
739 PMC-Sierra RM9xxx CPUs.
741 To compile this driver as a module, choose M here: the
742 module will be called rm9k_wdt.
745 tristate "Sibyte SoC hardware watchdog"
748 Watchdog driver for the built in watchdog hardware in Sibyte
749 SoC processors. There are apparently two watchdog timers
750 on such processors; this driver supports only the first one,
751 because currently Linux only supports exporting one watchdog
754 To compile this driver as a loadable module, choose M here.
755 The module will be called sb_wdog.
758 tristate "TI AR7 Watchdog Timer"
761 Hardware driver for the TI AR7 Watchdog Timer.
764 tristate "Toshiba TXx9 Watchdog Timer"
765 depends on CPU_TX39XX || CPU_TX49XX
767 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
769 # PARISC Architecture
771 # POWERPC Architecture
774 tristate "MPC5200 Watchdog Timer"
775 depends on PPC_MPC52xx
778 tristate "MPC8xxx Platform Watchdog Timer"
779 depends on PPC_8xx || PPC_83xx || PPC_86xx
781 This driver is for a SoC level watchdog that exists on some
782 Freescale PowerPC processors. So far this driver supports:
787 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
790 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
794 bool "PowerPC Book-E Watchdog Timer"
795 depends on BOOKE || 4xx
797 Please see Documentation/watchdog/watchdog-api.txt for
803 tristate "RTAS watchdog"
806 This driver adds watchdog support for the RTAS watchdog.
808 To compile this driver as a module, choose M here. The module
809 will be called wdrtas.
814 tristate "z/VM Watchdog Timer"
817 IBM s/390 and zSeries machines running under z/VM 5.1 or later
818 provide a virtual watchdog timer to their guest that cause a
819 user define Control Program command to be executed after a
822 To compile this driver as a module, choose M here. The module
823 will be called vmwatchdog.
825 # SUPERH (sh + sh64) Architecture
828 tristate "SuperH Watchdog"
829 depends on SUPERH && (CPU_SH3 || CPU_SH4)
831 This driver adds watchdog support for the integrated watchdog in the
832 SuperH processors. If you have one of these processors and wish
833 to have watchdog support enabled, say Y, otherwise say N.
835 As a side note, saying Y here will automatically boost HZ to 1000
836 so that the timer has a chance to clear the overflow counter. On
837 slower systems (such as the SH-2 and SH-3) this will likely yield
838 some performance issues. As such, the WDT should be avoided here
839 unless it is absolutely necessary.
841 To compile this driver as a module, choose M here: the
842 module will be called shwdt.
845 bool "Allow mmap of SH WDT"
849 If you say Y here, user applications will be able to mmap the
854 # SPARC64 Architecture
856 config WATCHDOG_CP1XXX
857 tristate "CP1XXX Hardware Watchdog support"
858 depends on SPARC64 && PCI
860 This is the driver for the hardware watchdog timers present on
861 Sun Microsystems CompactPCI models CP1400 and CP1500.
863 To compile this driver as a module, choose M here: the
864 module will be called cpwatchdog.
866 If you do not have a CompactPCI model CP1400 or CP1500, or
867 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
868 you should say N to this option.
871 tristate "RIO Hardware Watchdog support"
872 depends on SPARC64 && PCI
874 Say Y here to support the hardware watchdog capability on Sun RIO
875 machines. The watchdog timeout period is normally one minute but
876 can be changed with a boot-time parameter.
878 # XTENSA Architecture
881 # ISA-based Watchdog Cards
884 comment "ISA-based Watchdog Cards"
888 tristate "Berkshire Products ISA-PC Watchdog"
891 This is the driver for the Berkshire Products ISA-PC Watchdog card.
892 This card simply watches your kernel to make sure it doesn't freeze,
893 and if it does, it reboots your computer after a certain amount of
894 time. This driver is like the WDT501 driver but for different
895 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
896 watchdog cards can be ordered from <http://www.berkprod.com/>.
898 To compile this driver as a module, choose M here: the
899 module will be called pcwd.
901 Most people will say N.
904 tristate "Mixcom Watchdog"
907 This is a driver for the Mixcom hardware watchdog cards. This
908 watchdog simply watches your kernel to make sure it doesn't freeze,
909 and if it does, it reboots your computer after a certain amount of
912 To compile this driver as a module, choose M here: the
913 module will be called mixcomwd.
915 Most people will say N.
918 tristate "WDT Watchdog timer"
921 If you have a WDT500P or WDT501P watchdog board, say Y here,
922 otherwise N. It is not possible to probe for this board, which means
923 that you have to inform the kernel about the IO port and IRQ that
924 is needed (you can do this via the io and irq parameters)
926 To compile this driver as a module, choose M here: the
927 module will be called wdt.
930 bool "WDT501 features"
933 Saying Y here and creating a character special file /dev/temperature
934 with major number 10 and minor number 131 ("man mknod") will give
935 you a thermometer inside your computer: reading from
936 /dev/temperature yields one byte, the temperature in degrees
937 Fahrenheit. This works only if you have a WDT501P watchdog board
940 If you want to enable the Fan Tachometer on the WDT501P, then you
941 can do this via the tachometer parameter. Only do this if you have a
942 fan tachometer actually set up.
945 # PCI-based Watchdog Cards
948 comment "PCI-based Watchdog Cards"
952 tristate "Berkshire Products PCI-PC Watchdog"
955 This is the driver for the Berkshire Products PCI-PC Watchdog card.
956 This card simply watches your kernel to make sure it doesn't freeze,
957 and if it does, it reboots your computer after a certain amount of
958 time. The card can also monitor the internal temperature of the PC.
959 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
961 To compile this driver as a module, choose M here: the
962 module will be called pcwd_pci.
964 Most people will say N.
967 tristate "PCI-WDT500/501 Watchdog timer"
970 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
972 To compile this driver as a module, choose M here: the
973 module will be called wdt_pci.
976 bool "PCI-WDT501 features"
979 Saying Y here and creating a character special file /dev/temperature
980 with major number 10 and minor number 131 ("man mknod") will give
981 you a thermometer inside your computer: reading from
982 /dev/temperature yields one byte, the temperature in degrees
983 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
986 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
987 can do this via the tachometer parameter. Only do this if you have a
988 fan tachometer actually set up.
991 # USB-based Watchdog Cards
994 comment "USB-based Watchdog Cards"
998 tristate "Berkshire Products USB-PC Watchdog"
1001 This is the driver for the Berkshire Products USB-PC Watchdog card.
1002 This card simply watches your kernel to make sure it doesn't freeze,
1003 and if it does, it reboots your computer after a certain amount of
1004 time. The card can also monitor the internal temperature of the PC.
1005 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1007 To compile this driver as a module, choose M here: the
1008 module will be called pcwd_usb.
1010 Most people will say N.