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 MAX63XX_WATCHDOG
59 tristate "Max63xx watchdog"
61 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
63 config WM831X_WATCHDOG
64 tristate "WM831x watchdog"
67 Support for the watchdog in the WM831x AudioPlus PMICs. When
68 the watchdog triggers the system will be reset.
70 config WM8350_WATCHDOG
71 tristate "WM8350 watchdog"
74 Support for the watchdog in the WM8350 AudioPlus PMIC. When
75 the watchdog triggers the system will be reset.
81 config AT91RM9200_WATCHDOG
82 tristate "AT91RM9200 watchdog"
83 depends on ARCH_AT91RM9200
85 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
86 system when the timeout is reached.
88 config AT91SAM9X_WATCHDOG
89 tristate "AT91SAM9X / AT91CAP9 watchdog"
90 depends on ARCH_AT91 && !ARCH_AT91RM9200
92 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
93 reboot your system when the timeout is reached.
96 tristate "DC21285 watchdog"
99 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
100 here if you wish to use this. Alternatively say M to compile the
101 driver as a module, which will be called wdt285.
103 This driver does not work on all machines. In particular, early CATS
104 boards have hardware problems that will cause the machine to simply
105 lock up if the watchdog fires.
107 "If in doubt, leave it out" - say N.
110 tristate "NetWinder WB83C977 watchdog"
111 depends on FOOTBRIDGE && ARCH_NETWINDER
113 Say Y here to include support for the WB977 watchdog included in
114 NetWinder machines. Alternatively say M to compile the driver as
115 a module, which will be called wdt977.
117 Not sure? It's safe to say N.
119 config IXP2000_WATCHDOG
120 tristate "IXP2000 Watchdog"
121 depends on ARCH_IXP2000
123 Say Y here if to include support for the watchdog timer
124 in the Intel IXP2000(2400, 2800, 2850) network processors.
125 This driver can be built as a module by choosing M. The module
126 will be called ixp2000_wdt.
128 Say N if you are unsure.
130 config IXP4XX_WATCHDOG
131 tristate "IXP4xx Watchdog"
132 depends on ARCH_IXP4XX
134 Say Y here if to include support for the watchdog timer
135 in the Intel IXP4xx network processors. This driver can
136 be built as a module by choosing M. The module will
137 be called ixp4xx_wdt.
139 Note: The internal IXP4xx watchdog does a soft CPU reset
140 which doesn't reset any peripherals. There are circumstances
141 where the watchdog will fail to reset the board correctly
142 (e.g., if the boot ROM is in an unreadable state).
144 Say N if you are unsure.
146 config KS8695_WATCHDOG
147 tristate "KS8695 watchdog"
148 depends on ARCH_KS8695
150 Watchdog timer embedded into KS8695 processor. This will reboot your
151 system when the timeout is reached.
153 config S3C2410_WATCHDOG
154 tristate "S3C2410 Watchdog"
155 depends on ARCH_S3C2410
157 Watchdog timer block in the Samsung S3C2410 chips. This will
158 reboot the system when the timer expires with the watchdog
161 The driver is limited by the speed of the system's PCLK
162 signal, so with reasonably fast systems (PCLK around 50-66MHz)
163 then watchdog intervals of over approximately 20seconds are
166 The driver can be built as a module by choosing M, and will
167 be called s3c2410_wdt
169 config SA1100_WATCHDOG
170 tristate "SA1100/PXA2xx watchdog"
171 depends on ARCH_SA1100 || ARCH_PXA
173 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
174 reboot your system when timeout is reached.
176 NOTE: once enabled, this timer cannot be disabled.
178 To compile this driver as a module, choose M here: the
179 module will be called sa1100_wdt.
181 config MPCORE_WATCHDOG
182 tristate "MPcore watchdog"
183 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
185 Watchdog timer embedded into the MPcore system.
187 To compile this driver as a module, choose M here: the
188 module will be called mpcore_wdt.
190 config EP93XX_WATCHDOG
191 tristate "EP93xx Watchdog"
192 depends on ARCH_EP93XX
194 Say Y here if to include support for the watchdog timer
195 embedded in the Cirrus Logic EP93xx family of devices.
197 To compile this driver as a module, choose M here: the
198 module will be called ep93xx_wdt.
201 tristate "OMAP Watchdog"
202 depends on ARCH_OMAP16XX || ARCH_OMAP2 || ARCH_OMAP3
204 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430 watchdog. Say 'Y'
205 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430 watchdog timer.
207 config PNX4008_WATCHDOG
208 tristate "PNX4008 Watchdog"
209 depends on ARCH_PNX4008
211 Say Y here if to include support for the watchdog timer
212 in the PNX4008 processor.
213 This driver can be built as a module by choosing M. The module
214 will be called pnx4008_wdt.
216 Say N if you are unsure.
219 tristate "IOP Watchdog"
221 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
223 Say Y here if to include support for the watchdog timer
224 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
225 be built as a module by choosing M. The module will
228 Note: The IOP13XX watchdog does an Internal Bus Reset which will
229 affect both cores and the peripherals of the IOP. The ATU-X
230 and/or ATUe configuration registers will remain intact, but if
231 operating as an Root Complex and/or Central Resource, the PCI-X
232 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
234 config DAVINCI_WATCHDOG
235 tristate "DaVinci watchdog"
236 depends on ARCH_DAVINCI
238 Say Y here if to include support for the watchdog timer
239 in the DaVinci DM644x/DM646x processors.
240 To compile this driver as a module, choose M here: the
241 module will be called davinci_wdt.
243 NOTE: once enabled, this timer cannot be disabled.
244 Say N if you are unsure.
246 config ORION_WATCHDOG
247 tristate "Orion watchdog"
248 depends on ARCH_ORION5X || ARCH_KIRKWOOD
250 Say Y here if to include support for the watchdog timer
251 in the Marvell Orion5x and Kirkwood ARM SoCs.
252 To compile this driver as a module, choose M here: the
253 module will be called orion_wdt.
255 config COH901327_WATCHDOG
256 bool "ST-Ericsson COH 901 327 watchdog"
258 default y if MACH_U300
260 Say Y here to include Watchdog timer support for the
261 watchdog embedded into the ST-Ericsson U300 series platforms.
262 This watchdog is used to reset the system and thus cannot be
263 compiled as a module.
265 config TWL4030_WATCHDOG
266 tristate "TWL4030 Watchdog"
267 depends on TWL4030_CORE
269 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
270 watchdog timer support for TWL4030 chips.
272 config STMP3XXX_WATCHDOG
273 tristate "Freescale STMP3XXX watchdog"
274 depends on ARCH_STMP3XXX
276 Say Y here if to include support for the watchdog timer
277 for the Sigmatel STMP37XX/378X SoC.
278 To compile this driver as a module, choose M here: the
279 module will be called stmp3xxx_wdt.
281 config NUC900_WATCHDOG
282 tristate "Nuvoton NUC900 watchdog"
283 depends on ARCH_W90X900
285 Say Y here if to include support for the watchdog timer
286 for the Nuvoton NUC900 series SoCs.
287 To compile this driver as a module, choose M here: the
288 module will be called nuc900_wdt.
291 tristate "Avionic Design Xanthos watchdog"
292 depends on ARCH_PXA_ADX
294 Say Y here if you want support for the watchdog timer on Avionic
295 Design Xanthos boards.
297 config TS72XX_WATCHDOG
298 tristate "TS-72XX SBC Watchdog"
299 depends on MACH_TS72XX
301 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
302 watchdog timer implemented in a external CPLD chip. Say Y here
303 if you want to support for the watchdog timer on TS-72XX boards.
305 To compile this driver as a module, choose M here: the
306 module will be called ts72xx_wdt.
310 config AT32AP700X_WDT
311 tristate "AT32AP700x watchdog"
312 depends on CPU_AT32AP700X
314 Watchdog timer embedded into AT32AP700x devices. This will reboot
315 your system when the timeout is reached.
317 # BLACKFIN Architecture
320 tristate "Blackfin On-Chip Watchdog Timer"
323 If you say yes here you will get support for the Blackfin On-Chip
324 Watchdog Timer. If you have one of these processors and wish to
325 have watchdog support enabled, say Y, otherwise say N.
327 To compile this driver as a module, choose M here: the
328 module will be called bfin_wdt.
336 # X86 (i386 + ia64 + x86_64) Architecture
339 tristate "Acquire SBC Watchdog Timer"
342 This is the driver for the hardware watchdog on Single Board
343 Computers produced by Acquire Inc (and others). This watchdog
344 simply watches your kernel to make sure it doesn't freeze, and if
345 it does, it reboots your computer after a certain amount of time.
347 To compile this driver as a module, choose M here: the
348 module will be called acquirewdt.
350 Most people will say N.
353 tristate "Advantech SBC Watchdog Timer"
356 If you are configuring a Linux kernel for the Advantech single-board
357 computer, say `Y' here to support its built-in watchdog timer
358 feature. More information can be found at
359 <http://www.advantech.com.tw/products/>
362 tristate "ALi M1535 PMU Watchdog Timer"
363 depends on X86 && PCI
365 This is the driver for the hardware watchdog on the ALi M1535 PMU.
367 To compile this driver as a module, choose M here: the
368 module will be called alim1535_wdt.
370 Most people will say N.
373 tristate "ALi M7101 PMU Computer Watchdog"
376 This is the driver for the hardware watchdog on the ALi M7101 PMU
377 as used in the x86 Cobalt servers and also found in some
378 SPARC Netra servers too.
380 To compile this driver as a module, choose M here: the
381 module will be called alim7101_wdt.
383 Most people will say N.
386 tristate "AMD Geode CS5535/CS5536 Watchdog"
387 depends on CS5535_MFGPT
389 This driver enables a watchdog capability built into the
390 CS5535/CS5536 companion chips for the AMD Geode GX and LX
391 processors. This watchdog watches your kernel to make sure
392 it doesn't freeze, and if it does, it reboots your computer after
393 a certain amount of time.
395 You can compile this driver directly into the kernel, or use
396 it as a module. The module will be called geodewdt.
399 tristate "AMD Elan SC520 processor Watchdog"
402 This is the driver for the hardware watchdog built in to the
403 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
404 This watchdog simply watches your kernel to make sure it doesn't
405 freeze, and if it does, it reboots your computer after a certain
408 You can compile this driver directly into the kernel, or use
409 it as a module. The module will be called sc520_wdt.
411 config SBC_FITPC2_WATCHDOG
412 tristate "Compulab SBC-FITPC2 watchdog"
415 This is the driver for the built-in watchdog timer on the fit-PC2,
416 fit-PC2i, CM-iAM single-board computers made by Compulab.
418 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
419 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
421 Entering BIOS setup temporary disables watchdog operation regardless to current state,
422 so system will not be restarted while user in BIOS setup.
424 Once watchdog was enabled the system will be restarted every
425 "Watchdog Timer Value" period, so to prevent it user can restart or
426 disable the watchdog.
428 To compile this driver as a module, choose M here: the
429 module will be called sbc_fitpc2_wdt.
431 Most people will say N.
434 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
437 Enable support for the watchdog timer on the Eurotech CPU-1220 and
438 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
439 information are at <http://www.eurotech.it/>.
442 tristate "IB700 SBC Watchdog Timer"
445 This is the driver for the hardware watchdog on the IB700 Single
446 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
447 simply watches your kernel to make sure it doesn't freeze, and if
448 it does, it reboots your computer after a certain amount of time.
450 This driver is like the WDT501 driver but for slightly different hardware.
452 To compile this driver as a module, choose M here: the
453 module will be called ib700wdt.
455 Most people will say N.
458 tristate "IBM Automatic Server Restart"
461 This is the driver for the IBM Automatic Server Restart watchdog
462 timer built-in into some eServer xSeries machines.
464 To compile this driver as a module, choose M here: the
465 module will be called ibmasr.
468 tristate "ICP Single Board Computer Watchdog Timer"
471 This is a driver for the hardware watchdog on the ICP Single
472 Board Computer. This driver is working on (at least) the following
473 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
475 To compile this driver as a module, choose M here: the
476 module will be called wafer5823wdt.
479 tristate "Intel 6300ESB Timer/Watchdog"
480 depends on X86 && PCI
482 Hardware driver for the watchdog timer built into the Intel
483 6300ESB controller hub.
485 To compile this driver as a module, choose M here: the
486 module will be called i6300esb.
489 tristate "Intel TCO Timer/Watchdog"
490 depends on (X86 || IA64) && PCI
492 Hardware driver for the intel TCO timer based watchdog devices.
493 These drivers are included in the Intel 82801 I/O Controller
494 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
497 The TCO (Total Cost of Ownership) timer is a watchdog timer
498 that will reboot the machine after its second expiration. The
499 expiration time can be configured with the "heartbeat" parameter.
501 On some motherboards the driver may fail to reset the chipset's
502 NO_REBOOT flag which prevents the watchdog from rebooting the
503 machine. If this is the case you will get a kernel message like
504 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
506 To compile this driver as a module, choose M here: the
507 module will be called iTCO_wdt.
509 config ITCO_VENDOR_SUPPORT
510 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
513 Add vendor specific support to the intel TCO timer based watchdog
514 devices. At this moment we only have additional support for some
515 SuperMicro Inc. motherboards.
518 tristate "IT8712F (Smart Guardian) Watchdog Timer"
521 This is the driver for the built-in watchdog timer on the IT8712F
522 Super I/0 chipset used on many motherboards.
524 To compile this driver as a module, choose M here: the
525 module will be called it8712f_wdt.
528 tristate "IT87 Watchdog Timer"
529 depends on X86 && EXPERIMENTAL
531 This is the driver for the hardware watchdog on the ITE IT8716,
532 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
533 simply watches your kernel to make sure it doesn't freeze, and if
534 it does, it reboots your computer after a certain amount of time.
536 To compile this driver as a module, choose M here: the module will
540 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
543 A software monitoring watchdog and NMI sourcing driver. This driver
544 will detect lockups and provide stack trace. Also, when an NMI
545 occurs this driver will make the necessary BIOS calls to log
546 the cause of the NMI. This is a driver that will only load on a
547 HP ProLiant system with a minimum of iLO2 support.
548 To compile this driver as a module, choose M here: the
549 module will be called hpwdt.
552 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
555 This is a driver for National Semiconductor PC87307/PC97307 hardware
556 watchdog cards as found on the SC1200. This watchdog is mainly used
557 for power management purposes and can be used to power down the device
558 during inactivity periods (includes interrupt activity monitoring).
560 To compile this driver as a module, choose M here: the
561 module will be called sc1200wdt.
563 Most people will say N.
566 tristate "National Semiconductor SCx200 Watchdog"
567 depends on SCx200 && PCI
569 Enable the built-in watchdog timer support on the National
570 Semiconductor SCx200 processors.
572 If compiled as a module, it will be called scx200_wdt.
575 tristate "NS PC87413 watchdog"
578 This is the driver for the hardware watchdog on the PC87413 chipset
579 This watchdog simply watches your kernel to make sure it doesn't
580 freeze, and if it does, it reboots your computer after a certain
583 To compile this driver as a module, choose M here: the
584 module will be called pc87413_wdt.
586 Most people will say N.
589 tristate "RDC R-321x SoC watchdog"
590 depends on X86_RDC321X
592 This is the driver for the built in hardware watchdog
593 in the RDC R-321x SoC.
595 To compile this driver as a module, choose M here: the
596 module will be called rdc321x_wdt.
599 tristate "SBC-60XX Watchdog Timer"
602 This driver can be used with the watchdog timer found on some
603 single board computers, namely the 6010 PII based computer.
604 It may well work with other cards. It reads port 0x443 to enable
605 and re-set the watchdog timer, and reads port 0x45 to disable
606 the watchdog. If you have a card that behave in similar ways,
607 you can probably make this driver work with your card as well.
609 You can compile this driver directly into the kernel, or use
610 it as a module. The module will be called sbc60xxwdt.
613 tristate "SBC8360 Watchdog Timer"
617 This is the driver for the hardware watchdog on the SBC8360 Single
618 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
620 To compile this driver as a module, choose M here: the
621 module will be called sbc8360.
623 Most people will say N.
626 tristate "SBC Nano 7240 Watchdog Timer"
629 This is the driver for the hardware watchdog found on the IEI
630 single board computers EPIC Nano 7240 (and likely others). This
631 watchdog simply watches your kernel to make sure it doesn't freeze,
632 and if it does, it reboots your computer after a certain amount of
635 To compile this driver as a module, choose M here: the
636 module will be called sbc7240_wdt.
639 tristate "SMA CPU5 Watchdog"
643 To compile this driver as a module, choose M here: the
644 module will be called cpu5wdt.
646 config SMSC_SCH311X_WDT
647 tristate "SMSC SCH311X Watchdog Timer"
650 This is the driver for the hardware watchdog timer on the
651 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
652 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
655 To compile this driver as a module, choose M here: the
656 module will be called sch311x_wdt.
658 config SMSC37B787_WDT
659 tristate "Winbond SMsC37B787 Watchdog Timer"
662 This is the driver for the hardware watchdog component on the
663 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
664 from Vision Systems and maybe others.
666 This watchdog simply watches your kernel to make sure it doesn't
667 freeze, and if it does, it reboots your computer after a certain
670 Usually a userspace daemon will notify the kernel WDT driver that
671 userspace is still alive, at regular intervals.
673 To compile this driver as a module, choose M here: the
674 module will be called smsc37b787_wdt.
676 Most people will say N.
679 tristate "W83627HF Watchdog Timer"
682 This is the driver for the hardware watchdog on the W83627HF chipset
683 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
684 (and likely others). This watchdog simply watches your kernel to
685 make sure it doesn't freeze, and if it does, it reboots your computer
686 after a certain amount of time.
688 To compile this driver as a module, choose M here: the
689 module will be called w83627hf_wdt.
691 Most people will say N.
694 tristate "W83697HF/W83697HG Watchdog Timer"
697 This is the driver for the hardware watchdog on the W83697HF/HG
698 chipset as used in Dedibox/VIA motherboards (and likely others).
699 This watchdog simply watches your kernel to make sure it doesn't
700 freeze, and if it does, it reboots your computer after a certain
703 To compile this driver as a module, choose M here: the
704 module will be called w83697hf_wdt.
706 Most people will say N.
709 tristate "W83697UG/W83697UF Watchdog Timer"
712 This is the driver for the hardware watchdog on the W83697UG/UF
713 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
714 This watchdog simply watches your kernel to make sure it doesn't
715 freeze, and if it does, it reboots your computer after a certain
718 To compile this driver as a module, choose M here: the
719 module will be called w83697ug_wdt.
721 Most people will say N.
724 tristate "W83877F (EMACS) Watchdog Timer"
727 This is the driver for the hardware watchdog on the W83877F chipset
728 as used in EMACS PC-104 motherboards (and likely others). This
729 watchdog simply watches your kernel to make sure it doesn't freeze,
730 and if it does, it reboots your computer after a certain amount of
733 To compile this driver as a module, choose M here: the
734 module will be called w83877f_wdt.
736 Most people will say N.
739 tristate "W83977F (PCM-5335) Watchdog Timer"
742 This is the driver for the hardware watchdog on the W83977F I/O chip
743 as used in AAEON's PCM-5335 SBC (and likely others). This
744 watchdog simply watches your kernel to make sure it doesn't freeze,
745 and if it does, it reboots your computer after a certain amount of
748 To compile this driver as a module, choose M here: the
749 module will be called w83977f_wdt.
752 tristate "ZF MachZ Watchdog"
755 If you are using a ZF Micro MachZ processor, say Y here, otherwise
756 N. This is the driver for the watchdog timer built-in on that
757 processor using ZF-Logic interface. This watchdog simply watches
758 your kernel to make sure it doesn't freeze, and if it does, it
759 reboots your computer after a certain amount of time.
761 To compile this driver as a module, choose M here: the
762 module will be called machzwd.
764 config SBC_EPX_C3_WATCHDOG
765 tristate "Winsystems SBC EPX-C3 watchdog"
768 This is the driver for the built-in watchdog timer on the EPX-C3
769 Single-board computer made by Winsystems, Inc.
771 *Note*: This hardware watchdog is not probeable and thus there
772 is no way to know if writing to its IO address will corrupt
773 your system or have any real effect. The only way to be sure
774 that this driver does what you want is to make sure you
775 are running it on an EPX-C3 from Winsystems with the watchdog
776 timer at IO address 0x1ee and 0x1ef. It will write to both those
777 IO ports. Basically, the assumption is made that if you compile
778 this driver into your kernel and/or load it as a module, that you
779 know what you are doing and that you are in fact running on an
782 To compile this driver as a module, choose M here: the
783 module will be called sbc_epx_c3.
789 # M68KNOMMU Architecture
794 tristate "Broadcom BCM47xx Watchdog Timer"
797 Hardware driver for the Broadcom BCM47xx Watchog Timer.
800 tristate "IDT RC32434 SoC Watchdog Timer"
801 depends on MIKROTIK_RB532
803 Hardware driver for the IDT RC32434 SoC built-in
806 To compile this driver as a module, choose M here: the
807 module will be called rc32434_wdt.
810 tristate "Indy/I2 Hardware Watchdog"
811 depends on SGI_HAS_INDYDOG
813 Hardware driver for the Indy's/I2's watchdog. This is a
814 watchdog timer that will reboot the machine after a 60 second
815 timer expired and no process has written to /dev/watchdog during
819 tristate "MTX-1 Hardware Watchdog"
822 Hardware driver for the MTX-1 boards. This is a watchdog timer that
823 will reboot the machine after a 100 seconds timer expired.
826 tristate "PNX833x Hardware Watchdog"
827 depends on SOC_PNX8335
829 Hardware driver for the PNX833x's watchdog. This is a
830 watchdog timer that will reboot the machine after a programable
831 timer has expired and no process has written to /dev/watchdog during
835 tristate "Sibyte SoC hardware watchdog"
838 Watchdog driver for the built in watchdog hardware in Sibyte
839 SoC processors. There are apparently two watchdog timers
840 on such processors; this driver supports only the first one,
841 because currently Linux only supports exporting one watchdog
844 To compile this driver as a loadable module, choose M here.
845 The module will be called sb_wdog.
848 tristate "TI AR7 Watchdog Timer"
851 Hardware driver for the TI AR7 Watchdog Timer.
854 tristate "Toshiba TXx9 Watchdog Timer"
855 depends on CPU_TX39XX || CPU_TX49XX
857 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
859 # PARISC Architecture
861 # POWERPC Architecture
864 tristate "GE Watchdog Timer"
865 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
867 Watchdog timer found in a number of GE single board computers.
870 bool "MPC52xx Watchdog Timer"
871 depends on PPC_MPC52xx
873 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
876 tristate "MPC8xxx Platform Watchdog Timer"
877 depends on PPC_8xx || PPC_83xx || PPC_86xx
879 This driver is for a SoC level watchdog that exists on some
880 Freescale PowerPC processors. So far this driver supports:
885 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
888 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
892 tristate "PIKA FPGA Watchdog"
896 This enables the watchdog in the PIKA FPGA. Currently used on
900 bool "PowerPC Book-E Watchdog Timer"
901 depends on BOOKE || 4xx
903 Please see Documentation/watchdog/watchdog-api.txt for
909 tristate "RTAS watchdog"
912 This driver adds watchdog support for the RTAS watchdog.
914 To compile this driver as a module, choose M here. The module
915 will be called wdrtas.
920 tristate "z/VM Watchdog Timer"
923 IBM s/390 and zSeries machines running under z/VM 5.1 or later
924 provide a virtual watchdog timer to their guest that cause a
925 user define Control Program command to be executed after a
928 To compile this driver as a module, choose M here. The module
929 will be called vmwatchdog.
931 # SUPERH (sh + sh64) Architecture
934 tristate "SuperH Watchdog"
935 depends on SUPERH && (CPU_SH3 || CPU_SH4)
937 This driver adds watchdog support for the integrated watchdog in the
938 SuperH processors. If you have one of these processors and wish
939 to have watchdog support enabled, say Y, otherwise say N.
941 As a side note, saying Y here will automatically boost HZ to 1000
942 so that the timer has a chance to clear the overflow counter. On
943 slower systems (such as the SH-2 and SH-3) this will likely yield
944 some performance issues. As such, the WDT should be avoided here
945 unless it is absolutely necessary.
947 To compile this driver as a module, choose M here: the
948 module will be called shwdt.
951 bool "Allow mmap of SH WDT"
955 If you say Y here, user applications will be able to mmap the
960 # SPARC64 Architecture
962 config WATCHDOG_CP1XXX
963 tristate "CP1XXX Hardware Watchdog support"
964 depends on SPARC64 && PCI
966 This is the driver for the hardware watchdog timers present on
967 Sun Microsystems CompactPCI models CP1400 and CP1500.
969 To compile this driver as a module, choose M here: the
970 module will be called cpwatchdog.
972 If you do not have a CompactPCI model CP1400 or CP1500, or
973 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
974 you should say N to this option.
977 tristate "RIO Hardware Watchdog support"
978 depends on SPARC64 && PCI
980 Say Y here to support the hardware watchdog capability on Sun RIO
981 machines. The watchdog timeout period is normally one minute but
982 can be changed with a boot-time parameter.
984 # XTENSA Architecture
987 # ISA-based Watchdog Cards
990 comment "ISA-based Watchdog Cards"
994 tristate "Berkshire Products ISA-PC Watchdog"
997 This is the driver for the Berkshire Products ISA-PC Watchdog card.
998 This card simply watches your kernel to make sure it doesn't freeze,
999 and if it does, it reboots your computer after a certain amount of
1000 time. This driver is like the WDT501 driver but for different
1001 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1002 watchdog cards can be ordered from <http://www.berkprod.com/>.
1004 To compile this driver as a module, choose M here: the
1005 module will be called pcwd.
1007 Most people will say N.
1010 tristate "Mixcom Watchdog"
1013 This is a driver for the Mixcom hardware watchdog cards. This
1014 watchdog simply watches your kernel to make sure it doesn't freeze,
1015 and if it does, it reboots your computer after a certain amount of
1018 To compile this driver as a module, choose M here: the
1019 module will be called mixcomwd.
1021 Most people will say N.
1024 tristate "WDT Watchdog timer"
1027 If you have a WDT500P or WDT501P watchdog board, say Y here,
1028 otherwise N. It is not possible to probe for this board, which means
1029 that you have to inform the kernel about the IO port and IRQ that
1030 is needed (you can do this via the io and irq parameters)
1032 To compile this driver as a module, choose M here: the
1033 module will be called wdt.
1036 # PCI-based Watchdog Cards
1039 comment "PCI-based Watchdog Cards"
1042 config PCIPCWATCHDOG
1043 tristate "Berkshire Products PCI-PC Watchdog"
1046 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1047 This card simply watches your kernel to make sure it doesn't freeze,
1048 and if it does, it reboots your computer after a certain amount of
1049 time. The card can also monitor the internal temperature of the PC.
1050 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1052 To compile this driver as a module, choose M here: the
1053 module will be called pcwd_pci.
1055 Most people will say N.
1058 tristate "PCI-WDT500/501 Watchdog timer"
1061 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1063 If you have a PCI-WDT501 watchdog board then you can enable the
1064 temperature sensor by setting the type parameter to 501.
1066 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1067 can do this via the tachometer parameter. Only do this if you have a
1068 fan tachometer actually set up.
1070 To compile this driver as a module, choose M here: the
1071 module will be called wdt_pci.
1074 # USB-based Watchdog Cards
1077 comment "USB-based Watchdog Cards"
1080 config USBPCWATCHDOG
1081 tristate "Berkshire Products USB-PC Watchdog"
1084 This is the driver for the Berkshire Products USB-PC Watchdog card.
1085 This card simply watches your kernel to make sure it doesn't freeze,
1086 and if it does, it reboots your computer after a certain amount of
1087 time. The card can also monitor the internal temperature of the PC.
1088 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1090 To compile this driver as a module, choose M here: the
1091 module will be called pcwd_usb.
1093 Most people will say N.