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.
76 config AT91RM9200_WATCHDOG
77 tristate "AT91RM9200 watchdog"
78 depends on ARCH_AT91RM9200
80 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
81 system when the timeout is reached.
83 config AT91SAM9X_WATCHDOG
84 tristate "AT91SAM9X / AT91CAP9 watchdog"
85 depends on ARCH_AT91 && !ARCH_AT91RM9200
87 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
88 reboot your system when the timeout is reached.
91 tristate "DC21285 watchdog"
94 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
95 here if you wish to use this. Alternatively say M to compile the
96 driver as a module, which will be called wdt285.
98 This driver does not work on all machines. In particular, early CATS
99 boards have hardware problems that will cause the machine to simply
100 lock up if the watchdog fires.
102 "If in doubt, leave it out" - say N.
105 tristate "NetWinder WB83C977 watchdog"
106 depends on FOOTBRIDGE && ARCH_NETWINDER
108 Say Y here to include support for the WB977 watchdog included in
109 NetWinder machines. Alternatively say M to compile the driver as
110 a module, which will be called wdt977.
112 Not sure? It's safe to say N.
114 config IXP2000_WATCHDOG
115 tristate "IXP2000 Watchdog"
116 depends on ARCH_IXP2000
118 Say Y here if to include support for the watchdog timer
119 in the Intel IXP2000(2400, 2800, 2850) network processors.
120 This driver can be built as a module by choosing M. The module
121 will be called ixp2000_wdt.
123 Say N if you are unsure.
125 config IXP4XX_WATCHDOG
126 tristate "IXP4xx Watchdog"
127 depends on ARCH_IXP4XX
129 Say Y here if to include support for the watchdog timer
130 in the Intel IXP4xx network processors. This driver can
131 be built as a module by choosing M. The module will
132 be called ixp4xx_wdt.
134 Note: The internal IXP4xx watchdog does a soft CPU reset
135 which doesn't reset any peripherals. There are circumstances
136 where the watchdog will fail to reset the board correctly
137 (e.g., if the boot ROM is in an unreadable state).
139 Say N if you are unsure.
141 config KS8695_WATCHDOG
142 tristate "KS8695 watchdog"
143 depends on ARCH_KS8695
145 Watchdog timer embedded into KS8695 processor. This will reboot your
146 system when the timeout is reached.
148 config HAVE_S3C2410_WATCHDOG
151 This will include watchdog timer support for Samsung SoCs. If
152 you want to include watchdog support for any machine, kindly
153 select this in the respective mach-XXXX/Kconfig file.
155 config S3C2410_WATCHDOG
156 tristate "S3C2410 Watchdog"
157 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
159 Watchdog timer block in the Samsung SoCs. This will reboot
160 the system when the timer expires with the watchdog enabled.
162 The driver is limited by the speed of the system's PCLK
163 signal, so with reasonably fast systems (PCLK around 50-66MHz)
164 then watchdog intervals of over approximately 20seconds are
167 The driver can be built as a module by choosing M, and will
168 be called s3c2410_wdt
170 config SA1100_WATCHDOG
171 tristate "SA1100/PXA2xx watchdog"
172 depends on ARCH_SA1100 || ARCH_PXA
174 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
175 reboot your system when timeout is reached.
177 NOTE: once enabled, this timer cannot be disabled.
179 To compile this driver as a module, choose M here: the
180 module will be called sa1100_wdt.
182 config MPCORE_WATCHDOG
183 tristate "MPcore watchdog"
184 depends on HAVE_ARM_TWD
186 Watchdog timer embedded into the MPcore system.
188 To compile this driver as a module, choose M here: the
189 module will be called mpcore_wdt.
191 config EP93XX_WATCHDOG
192 tristate "EP93xx Watchdog"
193 depends on ARCH_EP93XX
195 Say Y here if to include support for the watchdog timer
196 embedded in the Cirrus Logic EP93xx family of devices.
198 To compile this driver as a module, choose M here: the
199 module will be called ep93xx_wdt.
202 tristate "OMAP Watchdog"
203 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
205 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
206 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
208 config PNX4008_WATCHDOG
209 tristate "PNX4008 Watchdog"
210 depends on ARCH_PNX4008
212 Say Y here if to include support for the watchdog timer
213 in the PNX4008 processor.
214 This driver can be built as a module by choosing M. The module
215 will be called pnx4008_wdt.
217 Say N if you are unsure.
220 tristate "IOP Watchdog"
222 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
224 Say Y here if to include support for the watchdog timer
225 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
226 be built as a module by choosing M. The module will
229 Note: The IOP13XX watchdog does an Internal Bus Reset which will
230 affect both cores and the peripherals of the IOP. The ATU-X
231 and/or ATUe configuration registers will remain intact, but if
232 operating as an Root Complex and/or Central Resource, the PCI-X
233 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
235 config DAVINCI_WATCHDOG
236 tristate "DaVinci watchdog"
237 depends on ARCH_DAVINCI
239 Say Y here if to include support for the watchdog timer
240 in the DaVinci DM644x/DM646x processors.
241 To compile this driver as a module, choose M here: the
242 module will be called davinci_wdt.
244 NOTE: once enabled, this timer cannot be disabled.
245 Say N if you are unsure.
247 config ORION_WATCHDOG
248 tristate "Orion watchdog"
249 depends on ARCH_ORION5X || ARCH_KIRKWOOD
251 Say Y here if to include support for the watchdog timer
252 in the Marvell Orion5x and Kirkwood ARM SoCs.
253 To compile this driver as a module, choose M here: the
254 module will be called orion_wdt.
256 config COH901327_WATCHDOG
257 bool "ST-Ericsson COH 901 327 watchdog"
259 default y if MACH_U300
261 Say Y here to include Watchdog timer support for the
262 watchdog embedded into the ST-Ericsson U300 series platforms.
263 This watchdog is used to reset the system and thus cannot be
264 compiled as a module.
266 config TWL4030_WATCHDOG
267 tristate "TWL4030 Watchdog"
268 depends on TWL4030_CORE
270 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
271 watchdog timer support for TWL4030 chips.
273 config STMP3XXX_WATCHDOG
274 tristate "Freescale STMP3XXX watchdog"
275 depends on ARCH_STMP3XXX
277 Say Y here if to include support for the watchdog timer
278 for the Sigmatel STMP37XX/378X SoC.
279 To compile this driver as a module, choose M here: the
280 module will be called stmp3xxx_wdt.
282 config NUC900_WATCHDOG
283 tristate "Nuvoton NUC900 watchdog"
284 depends on ARCH_W90X900
286 Say Y here if to include support for the watchdog timer
287 for the Nuvoton NUC900 series SoCs.
288 To compile this driver as a module, choose M here: the
289 module will be called nuc900_wdt.
292 tristate "Avionic Design Xanthos watchdog"
293 depends on ARCH_PXA_ADX
295 Say Y here if you want support for the watchdog timer on Avionic
296 Design Xanthos boards.
298 config TS72XX_WATCHDOG
299 tristate "TS-72XX SBC Watchdog"
300 depends on MACH_TS72XX
302 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
303 watchdog timer implemented in a external CPLD chip. Say Y here
304 if you want to support for the watchdog timer on TS-72XX boards.
306 To compile this driver as a module, choose M here: the
307 module will be called ts72xx_wdt.
309 config MAX63XX_WATCHDOG
310 tristate "Max63xx watchdog"
311 depends on ARM && HAS_IOMEM
313 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
317 config AT32AP700X_WDT
318 tristate "AT32AP700x watchdog"
319 depends on CPU_AT32AP700X
321 Watchdog timer embedded into AT32AP700x devices. This will reboot
322 your system when the timeout is reached.
324 # BLACKFIN Architecture
327 tristate "Blackfin On-Chip Watchdog Timer"
330 If you say yes here you will get support for the Blackfin On-Chip
331 Watchdog Timer. If you have one of these processors and wish to
332 have watchdog support enabled, say Y, otherwise say N.
334 To compile this driver as a module, choose M here: the
335 module will be called bfin_wdt.
343 # X86 (i386 + ia64 + x86_64) Architecture
346 tristate "Acquire SBC Watchdog Timer"
349 This is the driver for the hardware watchdog on Single Board
350 Computers produced by Acquire Inc (and others). This watchdog
351 simply watches your kernel to make sure it doesn't freeze, and if
352 it does, it reboots your computer after a certain amount of time.
354 To compile this driver as a module, choose M here: the
355 module will be called acquirewdt.
357 Most people will say N.
360 tristate "Advantech SBC Watchdog Timer"
363 If you are configuring a Linux kernel for the Advantech single-board
364 computer, say `Y' here to support its built-in watchdog timer
365 feature. More information can be found at
366 <http://www.advantech.com.tw/products/>
369 tristate "ALi M1535 PMU Watchdog Timer"
370 depends on X86 && PCI
372 This is the driver for the hardware watchdog on the ALi M1535 PMU.
374 To compile this driver as a module, choose M here: the
375 module will be called alim1535_wdt.
377 Most people will say N.
380 tristate "ALi M7101 PMU Computer Watchdog"
383 This is the driver for the hardware watchdog on the ALi M7101 PMU
384 as used in the x86 Cobalt servers and also found in some
385 SPARC Netra servers too.
387 To compile this driver as a module, choose M here: the
388 module will be called alim7101_wdt.
390 Most people will say N.
393 tristate "AMD Geode CS5535/CS5536 Watchdog"
394 depends on CS5535_MFGPT
396 This driver enables a watchdog capability built into the
397 CS5535/CS5536 companion chips for the AMD Geode GX and LX
398 processors. This watchdog watches your kernel to make sure
399 it doesn't freeze, and if it does, it reboots your computer after
400 a certain amount of time.
402 You can compile this driver directly into the kernel, or use
403 it as a module. The module will be called geodewdt.
406 tristate "AMD Elan SC520 processor Watchdog"
409 This is the driver for the hardware watchdog built in to the
410 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
411 This watchdog simply watches your kernel to make sure it doesn't
412 freeze, and if it does, it reboots your computer after a certain
415 You can compile this driver directly into the kernel, or use
416 it as a module. The module will be called sc520_wdt.
418 config SBC_FITPC2_WATCHDOG
419 tristate "Compulab SBC-FITPC2 watchdog"
422 This is the driver for the built-in watchdog timer on the fit-PC2,
423 fit-PC2i, CM-iAM single-board computers made by Compulab.
425 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
426 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
428 Entering BIOS setup temporary disables watchdog operation regardless to current state,
429 so system will not be restarted while user in BIOS setup.
431 Once watchdog was enabled the system will be restarted every
432 "Watchdog Timer Value" period, so to prevent it user can restart or
433 disable the watchdog.
435 To compile this driver as a module, choose M here: the
436 module will be called sbc_fitpc2_wdt.
438 Most people will say N.
441 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
444 Enable support for the watchdog timer on the Eurotech CPU-1220 and
445 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
446 information are at <http://www.eurotech.it/>.
449 tristate "IB700 SBC Watchdog Timer"
452 This is the driver for the hardware watchdog on the IB700 Single
453 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
454 simply watches your kernel to make sure it doesn't freeze, and if
455 it does, it reboots your computer after a certain amount of time.
457 This driver is like the WDT501 driver but for slightly different hardware.
459 To compile this driver as a module, choose M here: the
460 module will be called ib700wdt.
462 Most people will say N.
465 tristate "IBM Automatic Server Restart"
468 This is the driver for the IBM Automatic Server Restart watchdog
469 timer built-in into some eServer xSeries machines.
471 To compile this driver as a module, choose M here: the
472 module will be called ibmasr.
475 tristate "ICP Single Board Computer Watchdog Timer"
478 This is a driver for the hardware watchdog on the ICP Single
479 Board Computer. This driver is working on (at least) the following
480 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
482 To compile this driver as a module, choose M here: the
483 module will be called wafer5823wdt.
486 tristate "Intel 6300ESB Timer/Watchdog"
487 depends on X86 && PCI
489 Hardware driver for the watchdog timer built into the Intel
490 6300ESB controller hub.
492 To compile this driver as a module, choose M here: the
493 module will be called i6300esb.
496 tristate "Intel TCO Timer/Watchdog"
497 depends on (X86 || IA64) && PCI
499 Hardware driver for the intel TCO timer based watchdog devices.
500 These drivers are included in the Intel 82801 I/O Controller
501 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
504 The TCO (Total Cost of Ownership) timer is a watchdog timer
505 that will reboot the machine after its second expiration. The
506 expiration time can be configured with the "heartbeat" parameter.
508 On some motherboards the driver may fail to reset the chipset's
509 NO_REBOOT flag which prevents the watchdog from rebooting the
510 machine. If this is the case you will get a kernel message like
511 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
513 To compile this driver as a module, choose M here: the
514 module will be called iTCO_wdt.
516 config ITCO_VENDOR_SUPPORT
517 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
520 Add vendor specific support to the intel TCO timer based watchdog
521 devices. At this moment we only have additional support for some
522 SuperMicro Inc. motherboards.
525 tristate "IT8712F (Smart Guardian) Watchdog Timer"
528 This is the driver for the built-in watchdog timer on the IT8712F
529 Super I/0 chipset used on many motherboards.
531 To compile this driver as a module, choose M here: the
532 module will be called it8712f_wdt.
535 tristate "IT87 Watchdog Timer"
536 depends on X86 && EXPERIMENTAL
538 This is the driver for the hardware watchdog on the ITE IT8716,
539 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
540 simply watches your kernel to make sure it doesn't freeze, and if
541 it does, it reboots your computer after a certain amount of time.
543 To compile this driver as a module, choose M here: the module will
547 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
550 A software monitoring watchdog and NMI sourcing driver. This driver
551 will detect lockups and provide stack trace. Also, when an NMI
552 occurs this driver will make the necessary BIOS calls to log
553 the cause of the NMI. This is a driver that will only load on a
554 HP ProLiant system with a minimum of iLO2 support.
555 To compile this driver as a module, choose M here: the
556 module will be called hpwdt.
559 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
562 This is a driver for National Semiconductor PC87307/PC97307 hardware
563 watchdog cards as found on the SC1200. This watchdog is mainly used
564 for power management purposes and can be used to power down the device
565 during inactivity periods (includes interrupt activity monitoring).
567 To compile this driver as a module, choose M here: the
568 module will be called sc1200wdt.
570 Most people will say N.
573 tristate "National Semiconductor SCx200 Watchdog"
574 depends on SCx200 && PCI
576 Enable the built-in watchdog timer support on the National
577 Semiconductor SCx200 processors.
579 If compiled as a module, it will be called scx200_wdt.
582 tristate "NS PC87413 watchdog"
585 This is the driver for the hardware watchdog on the PC87413 chipset
586 This watchdog simply watches your kernel to make sure it doesn't
587 freeze, and if it does, it reboots your computer after a certain
590 To compile this driver as a module, choose M here: the
591 module will be called pc87413_wdt.
593 Most people will say N.
596 tristate "RDC R-321x SoC watchdog"
597 depends on X86_RDC321X
599 This is the driver for the built in hardware watchdog
600 in the RDC R-321x SoC.
602 To compile this driver as a module, choose M here: the
603 module will be called rdc321x_wdt.
606 tristate "SBC-60XX Watchdog Timer"
609 This driver can be used with the watchdog timer found on some
610 single board computers, namely the 6010 PII based computer.
611 It may well work with other cards. It reads port 0x443 to enable
612 and re-set the watchdog timer, and reads port 0x45 to disable
613 the watchdog. If you have a card that behave in similar ways,
614 you can probably make this driver work with your card as well.
616 You can compile this driver directly into the kernel, or use
617 it as a module. The module will be called sbc60xxwdt.
620 tristate "SBC8360 Watchdog Timer"
624 This is the driver for the hardware watchdog on the SBC8360 Single
625 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
627 To compile this driver as a module, choose M here: the
628 module will be called sbc8360.
630 Most people will say N.
633 tristate "SBC Nano 7240 Watchdog Timer"
636 This is the driver for the hardware watchdog found on the IEI
637 single board computers EPIC Nano 7240 (and likely others). This
638 watchdog simply watches your kernel to make sure it doesn't freeze,
639 and if it does, it reboots your computer after a certain amount of
642 To compile this driver as a module, choose M here: the
643 module will be called sbc7240_wdt.
646 tristate "SMA CPU5 Watchdog"
650 To compile this driver as a module, choose M here: the
651 module will be called cpu5wdt.
653 config SMSC_SCH311X_WDT
654 tristate "SMSC SCH311X Watchdog Timer"
657 This is the driver for the hardware watchdog timer on the
658 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
659 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
662 To compile this driver as a module, choose M here: the
663 module will be called sch311x_wdt.
665 config SMSC37B787_WDT
666 tristate "Winbond SMsC37B787 Watchdog Timer"
669 This is the driver for the hardware watchdog component on the
670 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
671 from Vision Systems and maybe others.
673 This watchdog simply watches your kernel to make sure it doesn't
674 freeze, and if it does, it reboots your computer after a certain
677 Usually a userspace daemon will notify the kernel WDT driver that
678 userspace is still alive, at regular intervals.
680 To compile this driver as a module, choose M here: the
681 module will be called smsc37b787_wdt.
683 Most people will say N.
686 tristate "W83627HF Watchdog Timer"
689 This is the driver for the hardware watchdog on the W83627HF chipset
690 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
691 (and likely others). This watchdog simply watches your kernel to
692 make sure it doesn't freeze, and if it does, it reboots your computer
693 after a certain amount of time.
695 To compile this driver as a module, choose M here: the
696 module will be called w83627hf_wdt.
698 Most people will say N.
701 tristate "W83697HF/W83697HG Watchdog Timer"
704 This is the driver for the hardware watchdog on the W83697HF/HG
705 chipset as used in Dedibox/VIA motherboards (and likely others).
706 This watchdog simply watches your kernel to make sure it doesn't
707 freeze, and if it does, it reboots your computer after a certain
710 To compile this driver as a module, choose M here: the
711 module will be called w83697hf_wdt.
713 Most people will say N.
716 tristate "W83697UG/W83697UF Watchdog Timer"
719 This is the driver for the hardware watchdog on the W83697UG/UF
720 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
721 This watchdog simply watches your kernel to make sure it doesn't
722 freeze, and if it does, it reboots your computer after a certain
725 To compile this driver as a module, choose M here: the
726 module will be called w83697ug_wdt.
728 Most people will say N.
731 tristate "W83877F (EMACS) Watchdog Timer"
734 This is the driver for the hardware watchdog on the W83877F chipset
735 as used in EMACS PC-104 motherboards (and likely others). This
736 watchdog simply watches your kernel to make sure it doesn't freeze,
737 and if it does, it reboots your computer after a certain amount of
740 To compile this driver as a module, choose M here: the
741 module will be called w83877f_wdt.
743 Most people will say N.
746 tristate "W83977F (PCM-5335) Watchdog Timer"
749 This is the driver for the hardware watchdog on the W83977F I/O chip
750 as used in AAEON's PCM-5335 SBC (and likely others). This
751 watchdog simply watches your kernel to make sure it doesn't freeze,
752 and if it does, it reboots your computer after a certain amount of
755 To compile this driver as a module, choose M here: the
756 module will be called w83977f_wdt.
759 tristate "ZF MachZ Watchdog"
762 If you are using a ZF Micro MachZ processor, say Y here, otherwise
763 N. This is the driver for the watchdog timer built-in on that
764 processor using ZF-Logic interface. This watchdog simply watches
765 your kernel to make sure it doesn't freeze, and if it does, it
766 reboots your computer after a certain amount of time.
768 To compile this driver as a module, choose M here: the
769 module will be called machzwd.
771 config SBC_EPX_C3_WATCHDOG
772 tristate "Winsystems SBC EPX-C3 watchdog"
775 This is the driver for the built-in watchdog timer on the EPX-C3
776 Single-board computer made by Winsystems, Inc.
778 *Note*: This hardware watchdog is not probeable and thus there
779 is no way to know if writing to its IO address will corrupt
780 your system or have any real effect. The only way to be sure
781 that this driver does what you want is to make sure you
782 are running it on an EPX-C3 from Winsystems with the watchdog
783 timer at IO address 0x1ee and 0x1ef. It will write to both those
784 IO ports. Basically, the assumption is made that if you compile
785 this driver into your kernel and/or load it as a module, that you
786 know what you are doing and that you are in fact running on an
789 To compile this driver as a module, choose M here: the
790 module will be called sbc_epx_c3.
796 # M68KNOMMU Architecture
801 tristate "Broadcom BCM47xx Watchdog Timer"
804 Hardware driver for the Broadcom BCM47xx Watchog Timer.
807 tristate "IDT RC32434 SoC Watchdog Timer"
808 depends on MIKROTIK_RB532
810 Hardware driver for the IDT RC32434 SoC built-in
813 To compile this driver as a module, choose M here: the
814 module will be called rc32434_wdt.
817 tristate "Indy/I2 Hardware Watchdog"
818 depends on SGI_HAS_INDYDOG
820 Hardware driver for the Indy's/I2's watchdog. This is a
821 watchdog timer that will reboot the machine after a 60 second
822 timer expired and no process has written to /dev/watchdog during
826 tristate "MTX-1 Hardware Watchdog"
829 Hardware driver for the MTX-1 boards. This is a watchdog timer that
830 will reboot the machine after a 100 seconds timer expired.
833 tristate "PNX833x Hardware Watchdog"
834 depends on SOC_PNX8335
836 Hardware driver for the PNX833x's watchdog. This is a
837 watchdog timer that will reboot the machine after a programable
838 timer has expired and no process has written to /dev/watchdog during
842 tristate "Sibyte SoC hardware watchdog"
845 Watchdog driver for the built in watchdog hardware in Sibyte
846 SoC processors. There are apparently two watchdog timers
847 on such processors; this driver supports only the first one,
848 because currently Linux only supports exporting one watchdog
851 To compile this driver as a loadable module, choose M here.
852 The module will be called sb_wdog.
855 tristate "TI AR7 Watchdog Timer"
858 Hardware driver for the TI AR7 Watchdog Timer.
861 tristate "Toshiba TXx9 Watchdog Timer"
862 depends on CPU_TX39XX || CPU_TX49XX
864 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
866 # PARISC Architecture
868 # POWERPC Architecture
871 tristate "GE Watchdog Timer"
872 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
874 Watchdog timer found in a number of GE single board computers.
877 bool "MPC52xx Watchdog Timer"
878 depends on PPC_MPC52xx
880 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
883 tristate "MPC8xxx Platform Watchdog Timer"
884 depends on PPC_8xx || PPC_83xx || PPC_86xx
886 This driver is for a SoC level watchdog that exists on some
887 Freescale PowerPC processors. So far this driver supports:
892 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
895 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
899 tristate "PIKA FPGA Watchdog"
903 This enables the watchdog in the PIKA FPGA. Currently used on
907 bool "PowerPC Book-E Watchdog Timer"
908 depends on BOOKE || 4xx
910 Please see Documentation/watchdog/watchdog-api.txt for
916 tristate "RTAS watchdog"
919 This driver adds watchdog support for the RTAS watchdog.
921 To compile this driver as a module, choose M here. The module
922 will be called wdrtas.
927 tristate "z/VM Watchdog Timer"
930 IBM s/390 and zSeries machines running under z/VM 5.1 or later
931 provide a virtual watchdog timer to their guest that cause a
932 user define Control Program command to be executed after a
935 To compile this driver as a module, choose M here. The module
936 will be called vmwatchdog.
938 # SUPERH (sh + sh64) Architecture
941 tristate "SuperH Watchdog"
942 depends on SUPERH && (CPU_SH3 || CPU_SH4)
944 This driver adds watchdog support for the integrated watchdog in the
945 SuperH processors. If you have one of these processors and wish
946 to have watchdog support enabled, say Y, otherwise say N.
948 As a side note, saying Y here will automatically boost HZ to 1000
949 so that the timer has a chance to clear the overflow counter. On
950 slower systems (such as the SH-2 and SH-3) this will likely yield
951 some performance issues. As such, the WDT should be avoided here
952 unless it is absolutely necessary.
954 To compile this driver as a module, choose M here: the
955 module will be called shwdt.
958 bool "Allow mmap of SH WDT"
962 If you say Y here, user applications will be able to mmap the
967 # SPARC64 Architecture
969 config WATCHDOG_CP1XXX
970 tristate "CP1XXX Hardware Watchdog support"
971 depends on SPARC64 && PCI
973 This is the driver for the hardware watchdog timers present on
974 Sun Microsystems CompactPCI models CP1400 and CP1500.
976 To compile this driver as a module, choose M here: the
977 module will be called cpwatchdog.
979 If you do not have a CompactPCI model CP1400 or CP1500, or
980 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
981 you should say N to this option.
984 tristate "RIO Hardware Watchdog support"
985 depends on SPARC64 && PCI
987 Say Y here to support the hardware watchdog capability on Sun RIO
988 machines. The watchdog timeout period is normally one minute but
989 can be changed with a boot-time parameter.
991 # XTENSA Architecture
994 # ISA-based Watchdog Cards
997 comment "ISA-based Watchdog Cards"
1001 tristate "Berkshire Products ISA-PC Watchdog"
1004 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1005 This card simply watches your kernel to make sure it doesn't freeze,
1006 and if it does, it reboots your computer after a certain amount of
1007 time. This driver is like the WDT501 driver but for different
1008 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1009 watchdog cards can be ordered from <http://www.berkprod.com/>.
1011 To compile this driver as a module, choose M here: the
1012 module will be called pcwd.
1014 Most people will say N.
1017 tristate "Mixcom Watchdog"
1020 This is a driver for the Mixcom hardware watchdog cards. This
1021 watchdog simply watches your kernel to make sure it doesn't freeze,
1022 and if it does, it reboots your computer after a certain amount of
1025 To compile this driver as a module, choose M here: the
1026 module will be called mixcomwd.
1028 Most people will say N.
1031 tristate "WDT Watchdog timer"
1034 If you have a WDT500P or WDT501P watchdog board, say Y here,
1035 otherwise N. It is not possible to probe for this board, which means
1036 that you have to inform the kernel about the IO port and IRQ that
1037 is needed (you can do this via the io and irq parameters)
1039 To compile this driver as a module, choose M here: the
1040 module will be called wdt.
1043 # PCI-based Watchdog Cards
1046 comment "PCI-based Watchdog Cards"
1049 config PCIPCWATCHDOG
1050 tristate "Berkshire Products PCI-PC Watchdog"
1053 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1054 This card simply watches your kernel to make sure it doesn't freeze,
1055 and if it does, it reboots your computer after a certain amount of
1056 time. The card can also monitor the internal temperature of the PC.
1057 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1059 To compile this driver as a module, choose M here: the
1060 module will be called pcwd_pci.
1062 Most people will say N.
1065 tristate "PCI-WDT500/501 Watchdog timer"
1068 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1070 If you have a PCI-WDT501 watchdog board then you can enable the
1071 temperature sensor by setting the type parameter to 501.
1073 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1074 can do this via the tachometer parameter. Only do this if you have a
1075 fan tachometer actually set up.
1077 To compile this driver as a module, choose M here: the
1078 module will be called wdt_pci.
1081 # USB-based Watchdog Cards
1084 comment "USB-based Watchdog Cards"
1087 config USBPCWATCHDOG
1088 tristate "Berkshire Products USB-PC Watchdog"
1091 This is the driver for the Berkshire Products USB-PC Watchdog card.
1092 This card simply watches your kernel to make sure it doesn't freeze,
1093 and if it does, it reboots your computer after a certain amount of
1094 time. The card can also monitor the internal temperature of the PC.
1095 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1097 To compile this driver as a module, choose M here: the
1098 module will be called pcwd_usb.
1100 Most people will say N.