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 WM831X_WATCHDOG
59 tristate "WM831x watchdog"
62 Support for the watchdog in the WM831x AudioPlus PMICs. When
63 the watchdog triggers the system will be reset.
65 config WM8350_WATCHDOG
66 tristate "WM8350 watchdog"
69 Support for the watchdog in the WM8350 AudioPlus PMIC. When
70 the watchdog triggers the system will be reset.
77 tristate "RK29 watchdog"
80 Watchdog timer embedded into RK29xx chips. This will reboot your
81 system when the timeout is reached.
83 config RK29_FEED_DOG_BY_INTE
84 bool "feed watchdog by interrupt"
85 depends on RK29_WATCHDOG
87 config RK29_WATCHDOG_ATBOOT
88 bool "start watchdog at system boot"
89 depends on RK29_WATCHDOG
91 config RK29_WATCHDOG_DEFAULT_TIME
92 int "set watchdog time out value (unit second)"
93 depends on RK29_WATCHDOG
95 the real time out value is two times more than the setting value
97 config RK29_WATCHDOG_DEBUG
98 bool "enable watchdog debug"
99 depends on RK29_WATCHDOG
102 config AT91RM9200_WATCHDOG
103 tristate "AT91RM9200 watchdog"
104 depends on ARCH_AT91RM9200
106 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
107 system when the timeout is reached.
109 config AT91SAM9X_WATCHDOG
110 tristate "AT91SAM9X / AT91CAP9 watchdog"
111 depends on ARCH_AT91 && !ARCH_AT91RM9200
113 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
114 reboot your system when the timeout is reached.
116 config 21285_WATCHDOG
117 tristate "DC21285 watchdog"
118 depends on FOOTBRIDGE
120 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
121 here if you wish to use this. Alternatively say M to compile the
122 driver as a module, which will be called wdt285.
124 This driver does not work on all machines. In particular, early CATS
125 boards have hardware problems that will cause the machine to simply
126 lock up if the watchdog fires.
128 "If in doubt, leave it out" - say N.
131 tristate "NetWinder WB83C977 watchdog"
132 depends on FOOTBRIDGE && ARCH_NETWINDER
134 Say Y here to include support for the WB977 watchdog included in
135 NetWinder machines. Alternatively say M to compile the driver as
136 a module, which will be called wdt977.
138 Not sure? It's safe to say N.
140 config IXP2000_WATCHDOG
141 tristate "IXP2000 Watchdog"
142 depends on ARCH_IXP2000
144 Say Y here if to include support for the watchdog timer
145 in the Intel IXP2000(2400, 2800, 2850) network processors.
146 This driver can be built as a module by choosing M. The module
147 will be called ixp2000_wdt.
149 Say N if you are unsure.
151 config IXP4XX_WATCHDOG
152 tristate "IXP4xx Watchdog"
153 depends on ARCH_IXP4XX
155 Say Y here if to include support for the watchdog timer
156 in the Intel IXP4xx network processors. This driver can
157 be built as a module by choosing M. The module will
158 be called ixp4xx_wdt.
160 Note: The internal IXP4xx watchdog does a soft CPU reset
161 which doesn't reset any peripherals. There are circumstances
162 where the watchdog will fail to reset the board correctly
163 (e.g., if the boot ROM is in an unreadable state).
165 Say N if you are unsure.
167 config KS8695_WATCHDOG
168 tristate "KS8695 watchdog"
169 depends on ARCH_KS8695
171 Watchdog timer embedded into KS8695 processor. This will reboot your
172 system when the timeout is reached.
174 config S3C2410_WATCHDOG
175 tristate "S3C2410 Watchdog"
176 depends on ARCH_S3C2410
178 Watchdog timer block in the Samsung S3C2410 chips. This will
179 reboot the system when the timer expires with the watchdog
182 The driver is limited by the speed of the system's PCLK
183 signal, so with reasonably fast systems (PCLK around 50-66MHz)
184 then watchdog intervals of over approximately 20seconds are
187 The driver can be built as a module by choosing M, and will
188 be called s3c2410_wdt
190 config SA1100_WATCHDOG
191 tristate "SA1100/PXA2xx watchdog"
192 depends on ARCH_SA1100 || ARCH_PXA
194 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
195 reboot your system when timeout is reached.
197 NOTE: once enabled, this timer cannot be disabled.
199 To compile this driver as a module, choose M here: the
200 module will be called sa1100_wdt.
202 config MPCORE_WATCHDOG
203 tristate "MPcore watchdog"
204 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
206 Watchdog timer embedded into the MPcore system.
208 To compile this driver as a module, choose M here: the
209 module will be called mpcore_wdt.
211 config EP93XX_WATCHDOG
212 tristate "EP93xx Watchdog"
213 depends on ARCH_EP93XX
215 Say Y here if to include support for the watchdog timer
216 embedded in the Cirrus Logic EP93xx family of devices.
218 To compile this driver as a module, choose M here: the
219 module will be called ep93xx_wdt.
222 tristate "OMAP Watchdog"
223 depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX
225 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430 watchdog. Say 'Y'
226 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430 watchdog timer.
228 config PNX4008_WATCHDOG
229 tristate "PNX4008 Watchdog"
230 depends on ARCH_PNX4008
232 Say Y here if to include support for the watchdog timer
233 in the PNX4008 processor.
234 This driver can be built as a module by choosing M. The module
235 will be called pnx4008_wdt.
237 Say N if you are unsure.
240 tristate "IOP Watchdog"
242 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
244 Say Y here if to include support for the watchdog timer
245 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
246 be built as a module by choosing M. The module will
249 Note: The IOP13XX watchdog does an Internal Bus Reset which will
250 affect both cores and the peripherals of the IOP. The ATU-X
251 and/or ATUe configuration registers will remain intact, but if
252 operating as an Root Complex and/or Central Resource, the PCI-X
253 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
255 config DAVINCI_WATCHDOG
256 tristate "DaVinci watchdog"
257 depends on ARCH_DAVINCI
259 Say Y here if to include support for the watchdog timer
260 in the DaVinci DM644x/DM646x processors.
261 To compile this driver as a module, choose M here: the
262 module will be called davinci_wdt.
264 NOTE: once enabled, this timer cannot be disabled.
265 Say N if you are unsure.
267 config ORION_WATCHDOG
268 tristate "Orion watchdog"
269 depends on ARCH_ORION5X || ARCH_KIRKWOOD
271 Say Y here if to include support for the watchdog timer
272 in the Marvell Orion5x and Kirkwood ARM SoCs.
273 To compile this driver as a module, choose M here: the
274 module will be called orion_wdt.
276 config COH901327_WATCHDOG
277 bool "ST-Ericsson COH 901 327 watchdog"
279 default y if MACH_U300
281 Say Y here to include Watchdog timer support for the
282 watchdog embedded into the ST-Ericsson U300 series platforms.
283 This watchdog is used to reset the system and thus cannot be
284 compiled as a module.
286 config TWL4030_WATCHDOG
287 tristate "TWL4030 Watchdog"
288 depends on TWL4030_CORE
290 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
291 watchdog timer support for TWL4030 chips.
293 config STMP3XXX_WATCHDOG
294 tristate "Freescale STMP3XXX watchdog"
295 depends on ARCH_STMP3XXX
297 Say Y here if to include support for the watchdog timer
298 for the Sigmatel STMP37XX/378X SoC.
299 To compile this driver as a module, choose M here: the
300 module will be called stmp3xxx_wdt.
302 config NUC900_WATCHDOG
303 tristate "Nuvoton NUC900 watchdog"
304 depends on ARCH_W90X900
306 Say Y here if to include support for the watchdog timer
307 for the Nuvoton NUC900 series SoCs.
308 To compile this driver as a module, choose M here: the
309 module will be called nuc900_wdt.
312 tristate "Avionic Design Xanthos watchdog"
313 depends on ARCH_PXA_ADX
315 Say Y here if you want support for the watchdog timer on Avionic
316 Design Xanthos boards.
320 config AT32AP700X_WDT
321 tristate "AT32AP700x watchdog"
322 depends on CPU_AT32AP700X
324 Watchdog timer embedded into AT32AP700x devices. This will reboot
325 your system when the timeout is reached.
327 # BLACKFIN Architecture
330 tristate "Blackfin On-Chip Watchdog Timer"
333 If you say yes here you will get support for the Blackfin On-Chip
334 Watchdog Timer. If you have one of these processors and wish to
335 have watchdog support enabled, say Y, otherwise say N.
337 To compile this driver as a module, choose M here: the
338 module will be called bfin_wdt.
346 # X86 (i386 + ia64 + x86_64) Architecture
349 tristate "Acquire SBC Watchdog Timer"
352 This is the driver for the hardware watchdog on Single Board
353 Computers produced by Acquire Inc (and others). This watchdog
354 simply watches your kernel to make sure it doesn't freeze, and if
355 it does, it reboots your computer after a certain amount of time.
357 To compile this driver as a module, choose M here: the
358 module will be called acquirewdt.
360 Most people will say N.
363 tristate "Advantech SBC Watchdog Timer"
366 If you are configuring a Linux kernel for the Advantech single-board
367 computer, say `Y' here to support its built-in watchdog timer
368 feature. More information can be found at
369 <http://www.advantech.com.tw/products/>
372 tristate "ALi M1535 PMU Watchdog Timer"
373 depends on X86 && PCI
375 This is the driver for the hardware watchdog on the ALi M1535 PMU.
377 To compile this driver as a module, choose M here: the
378 module will be called alim1535_wdt.
380 Most people will say N.
383 tristate "ALi M7101 PMU Computer Watchdog"
386 This is the driver for the hardware watchdog on the ALi M7101 PMU
387 as used in the x86 Cobalt servers and also found in some
388 SPARC Netra servers too.
390 To compile this driver as a module, choose M here: the
391 module will be called alim7101_wdt.
393 Most people will say N.
396 tristate "AMD Geode CS5535/CS5536 Watchdog"
399 This driver enables a watchdog capability built into the
400 CS5535/CS5536 companion chips for the AMD Geode GX and LX
401 processors. This watchdog watches your kernel to make sure
402 it doesn't freeze, and if it does, it reboots your computer after
403 a certain amount of time.
405 You can compile this driver directly into the kernel, or use
406 it as a module. The module will be called geodewdt.
409 tristate "AMD Elan SC520 processor Watchdog"
412 This is the driver for the hardware watchdog built in to the
413 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
414 This watchdog simply watches your kernel to make sure it doesn't
415 freeze, and if it does, it reboots your computer after a certain
418 You can compile this driver directly into the kernel, or use
419 it as a module. The module will be called sc520_wdt.
421 config SBC_FITPC2_WATCHDOG
422 tristate "Compulab SBC-FITPC2 watchdog"
425 This is the driver for the built-in watchdog timer on the fit-PC2
426 Single-board computer made by Compulab.
428 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
429 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
431 Entering BIOS setup temporary disables watchdog operation regardless to current state,
432 so system will not be restarted while user in BIOS setup.
434 Once watchdog was enabled the system will be restarted every
435 "Watchdog Timer Value" period, so to prevent it user can restart or
436 disable the watchdog.
438 To compile this driver as a module, choose M here: the
439 module will be called sbc_fitpc2_wdt.
441 Most people will say N.
444 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
447 Enable support for the watchdog timer on the Eurotech CPU-1220 and
448 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
449 information are at <http://www.eurotech.it/>.
452 tristate "IB700 SBC Watchdog Timer"
455 This is the driver for the hardware watchdog on the IB700 Single
456 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
457 simply watches your kernel to make sure it doesn't freeze, and if
458 it does, it reboots your computer after a certain amount of time.
460 This driver is like the WDT501 driver but for slightly different hardware.
462 To compile this driver as a module, choose M here: the
463 module will be called ib700wdt.
465 Most people will say N.
468 tristate "IBM Automatic Server Restart"
471 This is the driver for the IBM Automatic Server Restart watchdog
472 timer built-in into some eServer xSeries machines.
474 To compile this driver as a module, choose M here: the
475 module will be called ibmasr.
478 tristate "ICP Single Board Computer Watchdog Timer"
481 This is a driver for the hardware watchdog on the ICP Single
482 Board Computer. This driver is working on (at least) the following
483 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
485 To compile this driver as a module, choose M here: the
486 module will be called wafer5823wdt.
489 tristate "Intel 6300ESB Timer/Watchdog"
490 depends on X86 && PCI
492 Hardware driver for the watchdog timer built into the Intel
493 6300ESB controller hub.
495 To compile this driver as a module, choose M here: the
496 module will be called i6300esb.
499 tristate "Intel TCO Timer/Watchdog"
500 depends on (X86 || IA64) && PCI
502 Hardware driver for the intel TCO timer based watchdog devices.
503 These drivers are included in the Intel 82801 I/O Controller
504 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
507 The TCO (Total Cost of Ownership) timer is a watchdog timer
508 that will reboot the machine after its second expiration. The
509 expiration time can be configured with the "heartbeat" parameter.
511 On some motherboards the driver may fail to reset the chipset's
512 NO_REBOOT flag which prevents the watchdog from rebooting the
513 machine. If this is the case you will get a kernel message like
514 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
516 To compile this driver as a module, choose M here: the
517 module will be called iTCO_wdt.
519 config ITCO_VENDOR_SUPPORT
520 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
523 Add vendor specific support to the intel TCO timer based watchdog
524 devices. At this moment we only have additional support for some
525 SuperMicro Inc. motherboards.
528 tristate "IT8712F (Smart Guardian) Watchdog Timer"
531 This is the driver for the built-in watchdog timer on the IT8712F
532 Super I/0 chipset used on many motherboards.
534 To compile this driver as a module, choose M here: the
535 module will be called it8712f_wdt.
538 tristate "IT87 Watchdog Timer"
539 depends on X86 && EXPERIMENTAL
541 This is the driver for the hardware watchdog on the ITE IT8716,
542 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
543 simply watches your kernel to make sure it doesn't freeze, and if
544 it does, it reboots your computer after a certain amount of time.
546 To compile this driver as a module, choose M here: the module will
550 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
553 A software monitoring watchdog and NMI sourcing driver. This driver
554 will detect lockups and provide stack trace. Also, when an NMI
555 occurs this driver will make the necessary BIOS calls to log
556 the cause of the NMI. This is a driver that will only load on a
557 HP ProLiant system with a minimum of iLO2 support.
558 To compile this driver as a module, choose M here: the
559 module will be called hpwdt.
562 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
565 This is a driver for National Semiconductor PC87307/PC97307 hardware
566 watchdog cards as found on the SC1200. This watchdog is mainly used
567 for power management purposes and can be used to power down the device
568 during inactivity periods (includes interrupt activity monitoring).
570 To compile this driver as a module, choose M here: the
571 module will be called sc1200wdt.
573 Most people will say N.
576 tristate "National Semiconductor SCx200 Watchdog"
577 depends on SCx200 && PCI
579 Enable the built-in watchdog timer support on the National
580 Semiconductor SCx200 processors.
582 If compiled as a module, it will be called scx200_wdt.
585 tristate "NS PC87413 watchdog"
588 This is the driver for the hardware watchdog on the PC87413 chipset
589 This watchdog simply watches your kernel to make sure it doesn't
590 freeze, and if it does, it reboots your computer after a certain
593 To compile this driver as a module, choose M here: the
594 module will be called pc87413_wdt.
596 Most people will say N.
599 tristate "RDC R-321x SoC watchdog"
600 depends on X86_RDC321X
602 This is the driver for the built in hardware watchdog
603 in the RDC R-321x SoC.
605 To compile this driver as a module, choose M here: the
606 module will be called rdc321x_wdt.
609 tristate "SBC-60XX Watchdog Timer"
612 This driver can be used with the watchdog timer found on some
613 single board computers, namely the 6010 PII based computer.
614 It may well work with other cards. It reads port 0x443 to enable
615 and re-set the watchdog timer, and reads port 0x45 to disable
616 the watchdog. If you have a card that behave in similar ways,
617 you can probably make this driver work with your card as well.
619 You can compile this driver directly into the kernel, or use
620 it as a module. The module will be called sbc60xxwdt.
623 tristate "SBC8360 Watchdog Timer"
627 This is the driver for the hardware watchdog on the SBC8360 Single
628 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
630 To compile this driver as a module, choose M here: the
631 module will be called sbc8360.
633 Most people will say N.
636 tristate "SBC Nano 7240 Watchdog Timer"
639 This is the driver for the hardware watchdog found on the IEI
640 single board computers EPIC Nano 7240 (and likely others). This
641 watchdog simply watches your kernel to make sure it doesn't freeze,
642 and if it does, it reboots your computer after a certain amount of
645 To compile this driver as a module, choose M here: the
646 module will be called sbc7240_wdt.
649 tristate "SMA CPU5 Watchdog"
653 To compile this driver as a module, choose M here: the
654 module will be called cpu5wdt.
656 config SMSC_SCH311X_WDT
657 tristate "SMSC SCH311X Watchdog Timer"
660 This is the driver for the hardware watchdog timer on the
661 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
662 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
665 To compile this driver as a module, choose M here: the
666 module will be called sch311x_wdt.
668 config SMSC37B787_WDT
669 tristate "Winbond SMsC37B787 Watchdog Timer"
672 This is the driver for the hardware watchdog component on the
673 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
674 from Vision Systems and maybe others.
676 This watchdog simply watches your kernel to make sure it doesn't
677 freeze, and if it does, it reboots your computer after a certain
680 Usually a userspace daemon will notify the kernel WDT driver that
681 userspace is still alive, at regular intervals.
683 To compile this driver as a module, choose M here: the
684 module will be called smsc37b787_wdt.
686 Most people will say N.
689 tristate "W83627HF Watchdog Timer"
692 This is the driver for the hardware watchdog on the W83627HF chipset
693 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
694 (and likely others). This watchdog simply watches your kernel to
695 make sure it doesn't freeze, and if it does, it reboots your computer
696 after a certain amount of time.
698 To compile this driver as a module, choose M here: the
699 module will be called w83627hf_wdt.
701 Most people will say N.
704 tristate "W83697HF/W83697HG Watchdog Timer"
707 This is the driver for the hardware watchdog on the W83697HF/HG
708 chipset as used in Dedibox/VIA motherboards (and likely others).
709 This watchdog simply watches your kernel to make sure it doesn't
710 freeze, and if it does, it reboots your computer after a certain
713 To compile this driver as a module, choose M here: the
714 module will be called w83697hf_wdt.
716 Most people will say N.
719 tristate "W83697UG/W83697UF Watchdog Timer"
722 This is the driver for the hardware watchdog on the W83697UG/UF
723 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
724 This watchdog simply watches your kernel to make sure it doesn't
725 freeze, and if it does, it reboots your computer after a certain
728 To compile this driver as a module, choose M here: the
729 module will be called w83697ug_wdt.
731 Most people will say N.
734 tristate "W83877F (EMACS) Watchdog Timer"
737 This is the driver for the hardware watchdog on the W83877F chipset
738 as used in EMACS PC-104 motherboards (and likely others). This
739 watchdog simply watches your kernel to make sure it doesn't freeze,
740 and if it does, it reboots your computer after a certain amount of
743 To compile this driver as a module, choose M here: the
744 module will be called w83877f_wdt.
746 Most people will say N.
749 tristate "W83977F (PCM-5335) Watchdog Timer"
752 This is the driver for the hardware watchdog on the W83977F I/O chip
753 as used in AAEON's PCM-5335 SBC (and likely others). This
754 watchdog simply watches your kernel to make sure it doesn't freeze,
755 and if it does, it reboots your computer after a certain amount of
758 To compile this driver as a module, choose M here: the
759 module will be called w83977f_wdt.
762 tristate "ZF MachZ Watchdog"
765 If you are using a ZF Micro MachZ processor, say Y here, otherwise
766 N. This is the driver for the watchdog timer built-in on that
767 processor using ZF-Logic interface. This watchdog simply watches
768 your kernel to make sure it doesn't freeze, and if it does, it
769 reboots your computer after a certain amount of time.
771 To compile this driver as a module, choose M here: the
772 module will be called machzwd.
774 config SBC_EPX_C3_WATCHDOG
775 tristate "Winsystems SBC EPX-C3 watchdog"
778 This is the driver for the built-in watchdog timer on the EPX-C3
779 Single-board computer made by Winsystems, Inc.
781 *Note*: This hardware watchdog is not probeable and thus there
782 is no way to know if writing to its IO address will corrupt
783 your system or have any real effect. The only way to be sure
784 that this driver does what you want is to make sure you
785 are running it on an EPX-C3 from Winsystems with the watchdog
786 timer at IO address 0x1ee and 0x1ef. It will write to both those
787 IO ports. Basically, the assumption is made that if you compile
788 this driver into your kernel and/or load it as a module, that you
789 know what you are doing and that you are in fact running on an
792 To compile this driver as a module, choose M here: the
793 module will be called sbc_epx_c3.
799 # M68KNOMMU Architecture
804 tristate "Broadcom BCM47xx Watchdog Timer"
807 Hardware driver for the Broadcom BCM47xx Watchog Timer.
810 tristate "IDT RC32434 SoC Watchdog Timer"
811 depends on MIKROTIK_RB532
813 Hardware driver for the IDT RC32434 SoC built-in
816 To compile this driver as a module, choose M here: the
817 module will be called rc32434_wdt.
820 tristate "Indy/I2 Hardware Watchdog"
821 depends on SGI_HAS_INDYDOG
823 Hardware driver for the Indy's/I2's watchdog. This is a
824 watchdog timer that will reboot the machine after a 60 second
825 timer expired and no process has written to /dev/watchdog during
829 tristate "MTX-1 Hardware Watchdog"
832 Hardware driver for the MTX-1 boards. This is a watchdog timer that
833 will reboot the machine after a 100 seconds timer expired.
836 tristate "PNX833x Hardware Watchdog"
837 depends on SOC_PNX8335
839 Hardware driver for the PNX833x's watchdog. This is a
840 watchdog timer that will reboot the machine after a programable
841 timer has expired and no process has written to /dev/watchdog during
845 tristate "RM9000/GPI hardware watchdog"
846 depends on CPU_RM9000
848 Watchdog implementation using the GPI hardware found on
849 PMC-Sierra RM9xxx CPUs.
851 To compile this driver as a module, choose M here: the
852 module will be called rm9k_wdt.
855 tristate "Sibyte SoC hardware watchdog"
858 Watchdog driver for the built in watchdog hardware in Sibyte
859 SoC processors. There are apparently two watchdog timers
860 on such processors; this driver supports only the first one,
861 because currently Linux only supports exporting one watchdog
864 To compile this driver as a loadable module, choose M here.
865 The module will be called sb_wdog.
868 tristate "TI AR7 Watchdog Timer"
871 Hardware driver for the TI AR7 Watchdog Timer.
874 tristate "Toshiba TXx9 Watchdog Timer"
875 depends on CPU_TX39XX || CPU_TX49XX
877 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
879 # PARISC Architecture
881 # POWERPC Architecture
884 tristate "GE Fanuc Watchdog Timer"
885 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
887 Watchdog timer found in a number of GE Fanuc single board computers.
890 tristate "MPC5200 Watchdog Timer"
891 depends on PPC_MPC52xx
894 tristate "MPC8xxx Platform Watchdog Timer"
895 depends on PPC_8xx || PPC_83xx || PPC_86xx
897 This driver is for a SoC level watchdog that exists on some
898 Freescale PowerPC processors. So far this driver supports:
903 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
906 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
910 tristate "PIKA FPGA Watchdog"
914 This enables the watchdog in the PIKA FPGA. Currently used on
918 bool "PowerPC Book-E Watchdog Timer"
919 depends on BOOKE || 4xx
921 Please see Documentation/watchdog/watchdog-api.txt for
927 tristate "RTAS watchdog"
930 This driver adds watchdog support for the RTAS watchdog.
932 To compile this driver as a module, choose M here. The module
933 will be called wdrtas.
938 tristate "z/VM Watchdog Timer"
941 IBM s/390 and zSeries machines running under z/VM 5.1 or later
942 provide a virtual watchdog timer to their guest that cause a
943 user define Control Program command to be executed after a
946 To compile this driver as a module, choose M here. The module
947 will be called vmwatchdog.
949 # SUPERH (sh + sh64) Architecture
952 tristate "SuperH Watchdog"
953 depends on SUPERH && (CPU_SH3 || CPU_SH4)
955 This driver adds watchdog support for the integrated watchdog in the
956 SuperH processors. If you have one of these processors and wish
957 to have watchdog support enabled, say Y, otherwise say N.
959 As a side note, saying Y here will automatically boost HZ to 1000
960 so that the timer has a chance to clear the overflow counter. On
961 slower systems (such as the SH-2 and SH-3) this will likely yield
962 some performance issues. As such, the WDT should be avoided here
963 unless it is absolutely necessary.
965 To compile this driver as a module, choose M here: the
966 module will be called shwdt.
969 bool "Allow mmap of SH WDT"
973 If you say Y here, user applications will be able to mmap the
978 # SPARC64 Architecture
980 config WATCHDOG_CP1XXX
981 tristate "CP1XXX Hardware Watchdog support"
982 depends on SPARC64 && PCI
984 This is the driver for the hardware watchdog timers present on
985 Sun Microsystems CompactPCI models CP1400 and CP1500.
987 To compile this driver as a module, choose M here: the
988 module will be called cpwatchdog.
990 If you do not have a CompactPCI model CP1400 or CP1500, or
991 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
992 you should say N to this option.
995 tristate "RIO Hardware Watchdog support"
996 depends on SPARC64 && PCI
998 Say Y here to support the hardware watchdog capability on Sun RIO
999 machines. The watchdog timeout period is normally one minute but
1000 can be changed with a boot-time parameter.
1002 # XTENSA Architecture
1005 # ISA-based Watchdog Cards
1008 comment "ISA-based Watchdog Cards"
1012 tristate "Berkshire Products ISA-PC Watchdog"
1015 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1016 This card simply watches your kernel to make sure it doesn't freeze,
1017 and if it does, it reboots your computer after a certain amount of
1018 time. This driver is like the WDT501 driver but for different
1019 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1020 watchdog cards can be ordered from <http://www.berkprod.com/>.
1022 To compile this driver as a module, choose M here: the
1023 module will be called pcwd.
1025 Most people will say N.
1028 tristate "Mixcom Watchdog"
1031 This is a driver for the Mixcom hardware watchdog cards. This
1032 watchdog simply watches your kernel to make sure it doesn't freeze,
1033 and if it does, it reboots your computer after a certain amount of
1036 To compile this driver as a module, choose M here: the
1037 module will be called mixcomwd.
1039 Most people will say N.
1042 tristate "WDT Watchdog timer"
1045 If you have a WDT500P or WDT501P watchdog board, say Y here,
1046 otherwise N. It is not possible to probe for this board, which means
1047 that you have to inform the kernel about the IO port and IRQ that
1048 is needed (you can do this via the io and irq parameters)
1050 To compile this driver as a module, choose M here: the
1051 module will be called wdt.
1054 # PCI-based Watchdog Cards
1057 comment "PCI-based Watchdog Cards"
1060 config PCIPCWATCHDOG
1061 tristate "Berkshire Products PCI-PC Watchdog"
1064 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1065 This card simply watches your kernel to make sure it doesn't freeze,
1066 and if it does, it reboots your computer after a certain amount of
1067 time. The card can also monitor the internal temperature of the PC.
1068 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1070 To compile this driver as a module, choose M here: the
1071 module will be called pcwd_pci.
1073 Most people will say N.
1076 tristate "PCI-WDT500/501 Watchdog timer"
1079 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1081 If you have a PCI-WDT501 watchdog board then you can enable the
1082 temperature sensor by setting the type parameter to 501.
1084 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1085 can do this via the tachometer parameter. Only do this if you have a
1086 fan tachometer actually set up.
1088 To compile this driver as a module, choose M here: the
1089 module will be called wdt_pci.
1092 # USB-based Watchdog Cards
1095 comment "USB-based Watchdog Cards"
1098 config USBPCWATCHDOG
1099 tristate "Berkshire Products USB-PC Watchdog"
1102 This is the driver for the Berkshire Products USB-PC Watchdog card.
1103 This card simply watches your kernel to make sure it doesn't freeze,
1104 and if it does, it reboots your computer after a certain amount of
1105 time. The card can also monitor the internal temperature of the PC.
1106 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1108 To compile this driver as a module, choose M here: the
1109 module will be called pcwd_usb.
1111 Most people will say N.