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 ARM_SP805_WATCHDOG
77 tristate "ARM SP805 Watchdog"
80 ARM Primecell SP805 Watchdog timer. This will reboot your system when
81 the timeout is reached.
83 config AT91RM9200_WATCHDOG
84 tristate "AT91RM9200 watchdog"
85 depends on ARCH_AT91RM9200
87 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
88 system when the timeout is reached.
90 config AT91SAM9X_WATCHDOG
91 tristate "AT91SAM9X / AT91CAP9 watchdog"
92 depends on ARCH_AT91 && !ARCH_AT91RM9200
94 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
95 reboot your system when the timeout is reached.
98 tristate "DC21285 watchdog"
101 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
102 here if you wish to use this. Alternatively say M to compile the
103 driver as a module, which will be called wdt285.
105 This driver does not work on all machines. In particular, early CATS
106 boards have hardware problems that will cause the machine to simply
107 lock up if the watchdog fires.
109 "If in doubt, leave it out" - say N.
112 tristate "NetWinder WB83C977 watchdog"
113 depends on FOOTBRIDGE && ARCH_NETWINDER
115 Say Y here to include support for the WB977 watchdog included in
116 NetWinder machines. Alternatively say M to compile the driver as
117 a module, which will be called wdt977.
119 Not sure? It's safe to say N.
121 config IXP2000_WATCHDOG
122 tristate "IXP2000 Watchdog"
123 depends on ARCH_IXP2000
125 Say Y here if to include support for the watchdog timer
126 in the Intel IXP2000(2400, 2800, 2850) network processors.
127 This driver can be built as a module by choosing M. The module
128 will be called ixp2000_wdt.
130 Say N if you are unsure.
132 config IXP4XX_WATCHDOG
133 tristate "IXP4xx Watchdog"
134 depends on ARCH_IXP4XX
136 Say Y here if to include support for the watchdog timer
137 in the Intel IXP4xx network processors. This driver can
138 be built as a module by choosing M. The module will
139 be called ixp4xx_wdt.
141 Note: The internal IXP4xx watchdog does a soft CPU reset
142 which doesn't reset any peripherals. There are circumstances
143 where the watchdog will fail to reset the board correctly
144 (e.g., if the boot ROM is in an unreadable state).
146 Say N if you are unsure.
148 config KS8695_WATCHDOG
149 tristate "KS8695 watchdog"
150 depends on ARCH_KS8695
152 Watchdog timer embedded into KS8695 processor. This will reboot your
153 system when the timeout is reached.
155 config HAVE_S3C2410_WATCHDOG
158 This will include watchdog timer support for Samsung SoCs. If
159 you want to include watchdog support for any machine, kindly
160 select this in the respective mach-XXXX/Kconfig file.
162 config S3C2410_WATCHDOG
163 tristate "S3C2410 Watchdog"
164 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
166 Watchdog timer block in the Samsung SoCs. This will reboot
167 the system when the timer expires with the watchdog enabled.
169 The driver is limited by the speed of the system's PCLK
170 signal, so with reasonably fast systems (PCLK around 50-66MHz)
171 then watchdog intervals of over approximately 20seconds are
174 The driver can be built as a module by choosing M, and will
175 be called s3c2410_wdt
177 config SA1100_WATCHDOG
178 tristate "SA1100/PXA2xx watchdog"
179 depends on ARCH_SA1100 || ARCH_PXA
181 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
182 reboot your system when timeout is reached.
184 NOTE: once enabled, this timer cannot be disabled.
186 To compile this driver as a module, choose M here: the
187 module will be called sa1100_wdt.
189 config MPCORE_WATCHDOG
190 tristate "MPcore watchdog"
191 depends on HAVE_ARM_TWD
193 Watchdog timer embedded into the MPcore system.
195 To compile this driver as a module, choose M here: the
196 module will be called mpcore_wdt.
198 config TEGRA_WATCHDOG
199 tristate "Tegra watchdog"
200 depends on ARCH_TEGRA
202 Say Y here to include support for the watchdog timer
203 embedded in NVIDIA Tegra SoCs.
205 To compile this driver as a module, choose M here: the
206 module will be called tegra_wdt.
208 config TEGRA_WATCHDOG_ENABLE_ON_PROBE
209 tristate "Tegra watchdog"
210 depends on ARCH_TEGRA && TEGRA_WATCHDOG
212 Say Y here to enable the tegra watchdog at driver
213 probe time, rather than when the device is opened.
215 config EP93XX_WATCHDOG
216 tristate "EP93xx Watchdog"
217 depends on ARCH_EP93XX
219 Say Y here if to include support for the watchdog timer
220 embedded in the Cirrus Logic EP93xx family of devices.
222 To compile this driver as a module, choose M here: the
223 module will be called ep93xx_wdt.
226 tristate "OMAP Watchdog"
227 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
229 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
230 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
232 config PNX4008_WATCHDOG
233 tristate "PNX4008 and LPC32XX Watchdog"
234 depends on ARCH_PNX4008 || ARCH_LPC32XX
236 Say Y here if to include support for the watchdog timer
237 in the PNX4008 or LPC32XX processor.
238 This driver can be built as a module by choosing M. The module
239 will be called pnx4008_wdt.
241 Say N if you are unsure.
244 tristate "IOP Watchdog"
246 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
248 Say Y here if to include support for the watchdog timer
249 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
250 be built as a module by choosing M. The module will
253 Note: The IOP13XX watchdog does an Internal Bus Reset which will
254 affect both cores and the peripherals of the IOP. The ATU-X
255 and/or ATUe configuration registers will remain intact, but if
256 operating as an Root Complex and/or Central Resource, the PCI-X
257 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
259 config DAVINCI_WATCHDOG
260 tristate "DaVinci watchdog"
261 depends on ARCH_DAVINCI
263 Say Y here if to include support for the watchdog timer
264 in the DaVinci DM644x/DM646x processors.
265 To compile this driver as a module, choose M here: the
266 module will be called davinci_wdt.
268 NOTE: once enabled, this timer cannot be disabled.
269 Say N if you are unsure.
271 config ORION_WATCHDOG
272 tristate "Orion watchdog"
273 depends on ARCH_ORION5X || ARCH_KIRKWOOD
275 Say Y here if to include support for the watchdog timer
276 in the Marvell Orion5x and Kirkwood ARM SoCs.
277 To compile this driver as a module, choose M here: the
278 module will be called orion_wdt.
280 config COH901327_WATCHDOG
281 bool "ST-Ericsson COH 901 327 watchdog"
283 default y if MACH_U300
285 Say Y here to include Watchdog timer support for the
286 watchdog embedded into the ST-Ericsson U300 series platforms.
287 This watchdog is used to reset the system and thus cannot be
288 compiled as a module.
290 config TWL4030_WATCHDOG
291 tristate "TWL4030 Watchdog"
292 depends on TWL4030_CORE
294 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
295 watchdog timer support for TWL4030 chips.
297 config STMP3XXX_WATCHDOG
298 tristate "Freescale STMP3XXX watchdog"
299 depends on ARCH_STMP3XXX
301 Say Y here if to include support for the watchdog timer
302 for the Sigmatel STMP37XX/378X SoC.
303 To compile this driver as a module, choose M here: the
304 module will be called stmp3xxx_wdt.
306 config NUC900_WATCHDOG
307 tristate "Nuvoton NUC900 watchdog"
308 depends on ARCH_W90X900
310 Say Y here if to include support for the watchdog timer
311 for the Nuvoton NUC900 series SoCs.
312 To compile this driver as a module, choose M here: the
313 module will be called nuc900_wdt.
316 tristate "Avionic Design Xanthos watchdog"
317 depends on ARCH_PXA_ADX
319 Say Y here if you want support for the watchdog timer on Avionic
320 Design Xanthos boards.
322 config TS72XX_WATCHDOG
323 tristate "TS-72XX SBC Watchdog"
324 depends on MACH_TS72XX
326 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
327 watchdog timer implemented in a external CPLD chip. Say Y here
328 if you want to support for the watchdog timer on TS-72XX boards.
330 To compile this driver as a module, choose M here: the
331 module will be called ts72xx_wdt.
333 config MAX63XX_WATCHDOG
334 tristate "Max63xx watchdog"
335 depends on ARM && HAS_IOMEM
337 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
340 tristate "IMX2+ Watchdog"
341 depends on ARCH_MX2 || ARCH_MX25 || ARCH_MX3 || ARCH_MX5
343 This is the driver for the hardware watchdog
344 on the Freescale IMX2 and later processors.
345 If you have one of these processors and wish to have
346 watchdog support enabled, say Y, otherwise say N.
348 To compile this driver as a module, choose M here: the
349 module will be called imx2_wdt.
353 config AT32AP700X_WDT
354 tristate "AT32AP700x watchdog"
355 depends on CPU_AT32AP700X
357 Watchdog timer embedded into AT32AP700x devices. This will reboot
358 your system when the timeout is reached.
360 # BLACKFIN Architecture
363 tristate "Blackfin On-Chip Watchdog Timer"
366 If you say yes here you will get support for the Blackfin On-Chip
367 Watchdog Timer. If you have one of these processors and wish to
368 have watchdog support enabled, say Y, otherwise say N.
370 To compile this driver as a module, choose M here: the
371 module will be called bfin_wdt.
379 # X86 (i386 + ia64 + x86_64) Architecture
382 tristate "Acquire SBC Watchdog Timer"
385 This is the driver for the hardware watchdog on Single Board
386 Computers produced by Acquire Inc (and others). This watchdog
387 simply watches your kernel to make sure it doesn't freeze, and if
388 it does, it reboots your computer after a certain amount of time.
390 To compile this driver as a module, choose M here: the
391 module will be called acquirewdt.
393 Most people will say N.
396 tristate "Advantech SBC Watchdog Timer"
399 If you are configuring a Linux kernel for the Advantech single-board
400 computer, say `Y' here to support its built-in watchdog timer
401 feature. More information can be found at
402 <http://www.advantech.com.tw/products/>
405 tristate "ALi M1535 PMU Watchdog Timer"
406 depends on X86 && PCI
408 This is the driver for the hardware watchdog on the ALi M1535 PMU.
410 To compile this driver as a module, choose M here: the
411 module will be called alim1535_wdt.
413 Most people will say N.
416 tristate "ALi M7101 PMU Computer Watchdog"
419 This is the driver for the hardware watchdog on the ALi M7101 PMU
420 as used in the x86 Cobalt servers and also found in some
421 SPARC Netra servers too.
423 To compile this driver as a module, choose M here: the
424 module will be called alim7101_wdt.
426 Most people will say N.
429 tristate "Fintek F71808E and F71882FG Watchdog"
430 depends on X86 && EXPERIMENTAL
432 This is the driver for the hardware watchdog on the Fintek
433 F71808E and F71882FG Super I/O controllers.
435 You can compile this driver directly into the kernel, or use
436 it as a module. The module will be called f71808e_wdt.
440 tristate "AMD Geode CS5535/CS5536 Watchdog"
441 depends on CS5535_MFGPT
443 This driver enables a watchdog capability built into the
444 CS5535/CS5536 companion chips for the AMD Geode GX and LX
445 processors. This watchdog watches your kernel to make sure
446 it doesn't freeze, and if it does, it reboots your computer after
447 a certain amount of time.
449 You can compile this driver directly into the kernel, or use
450 it as a module. The module will be called geodewdt.
453 tristate "AMD Elan SC520 processor Watchdog"
456 This is the driver for the hardware watchdog built in to the
457 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
458 This watchdog simply watches your kernel to make sure it doesn't
459 freeze, and if it does, it reboots your computer after a certain
462 You can compile this driver directly into the kernel, or use
463 it as a module. The module will be called sc520_wdt.
465 config SBC_FITPC2_WATCHDOG
466 tristate "Compulab SBC-FITPC2 watchdog"
469 This is the driver for the built-in watchdog timer on the fit-PC2,
470 fit-PC2i, CM-iAM single-board computers made by Compulab.
472 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
473 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
475 Entering BIOS setup temporary disables watchdog operation regardless to current state,
476 so system will not be restarted while user in BIOS setup.
478 Once watchdog was enabled the system will be restarted every
479 "Watchdog Timer Value" period, so to prevent it user can restart or
480 disable the watchdog.
482 To compile this driver as a module, choose M here: the
483 module will be called sbc_fitpc2_wdt.
485 Most people will say N.
488 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
491 Enable support for the watchdog timer on the Eurotech CPU-1220 and
492 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
493 information are at <http://www.eurotech.it/>.
496 tristate "IB700 SBC Watchdog Timer"
499 This is the driver for the hardware watchdog on the IB700 Single
500 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
501 simply watches your kernel to make sure it doesn't freeze, and if
502 it does, it reboots your computer after a certain amount of time.
504 This driver is like the WDT501 driver but for slightly different hardware.
506 To compile this driver as a module, choose M here: the
507 module will be called ib700wdt.
509 Most people will say N.
512 tristate "IBM Automatic Server Restart"
515 This is the driver for the IBM Automatic Server Restart watchdog
516 timer built-in into some eServer xSeries machines.
518 To compile this driver as a module, choose M here: the
519 module will be called ibmasr.
522 tristate "ICP Single Board Computer Watchdog Timer"
525 This is a driver for the hardware watchdog on the ICP Single
526 Board Computer. This driver is working on (at least) the following
527 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
529 To compile this driver as a module, choose M here: the
530 module will be called wafer5823wdt.
533 tristate "Intel 6300ESB Timer/Watchdog"
534 depends on X86 && PCI
536 Hardware driver for the watchdog timer built into the Intel
537 6300ESB controller hub.
539 To compile this driver as a module, choose M here: the
540 module will be called i6300esb.
543 tristate "Intel TCO Timer/Watchdog"
544 depends on (X86 || IA64) && PCI
546 Hardware driver for the intel TCO timer based watchdog devices.
547 These drivers are included in the Intel 82801 I/O Controller
548 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
551 The TCO (Total Cost of Ownership) timer is a watchdog timer
552 that will reboot the machine after its second expiration. The
553 expiration time can be configured with the "heartbeat" parameter.
555 On some motherboards the driver may fail to reset the chipset's
556 NO_REBOOT flag which prevents the watchdog from rebooting the
557 machine. If this is the case you will get a kernel message like
558 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
560 To compile this driver as a module, choose M here: the
561 module will be called iTCO_wdt.
563 config ITCO_VENDOR_SUPPORT
564 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
567 Add vendor specific support to the intel TCO timer based watchdog
568 devices. At this moment we only have additional support for some
569 SuperMicro Inc. motherboards.
572 tristate "IT8712F (Smart Guardian) Watchdog Timer"
575 This is the driver for the built-in watchdog timer on the IT8712F
576 Super I/0 chipset used on many motherboards.
578 To compile this driver as a module, choose M here: the
579 module will be called it8712f_wdt.
582 tristate "IT87 Watchdog Timer"
583 depends on X86 && EXPERIMENTAL
585 This is the driver for the hardware watchdog on the ITE IT8716,
586 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
587 simply watches your kernel to make sure it doesn't freeze, and if
588 it does, it reboots your computer after a certain amount of time.
590 To compile this driver as a module, choose M here: the module will
594 tristate "HP Proliant iLO2+ Hardware Watchdog Timer"
597 A software monitoring watchdog and NMI sourcing driver. This driver
598 will detect lockups and provide a stack trace. This is a driver that
599 will only load on a HP ProLiant system with a minimum of iLO2 support.
600 To compile this driver as a module, choose M here: the module will be
603 config HPWDT_NMI_DECODING
604 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
605 depends on HP_WATCHDOG
607 When an NMI occurs this feature will make the necessary BIOS calls to
608 log the cause of the NMI.
611 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
614 This is a driver for National Semiconductor PC87307/PC97307 hardware
615 watchdog cards as found on the SC1200. This watchdog is mainly used
616 for power management purposes and can be used to power down the device
617 during inactivity periods (includes interrupt activity monitoring).
619 To compile this driver as a module, choose M here: the
620 module will be called sc1200wdt.
622 Most people will say N.
625 tristate "National Semiconductor SCx200 Watchdog"
626 depends on SCx200 && PCI
628 Enable the built-in watchdog timer support on the National
629 Semiconductor SCx200 processors.
631 If compiled as a module, it will be called scx200_wdt.
634 tristate "NS PC87413 watchdog"
637 This is the driver for the hardware watchdog on the PC87413 chipset
638 This watchdog simply watches your kernel to make sure it doesn't
639 freeze, and if it does, it reboots your computer after a certain
642 To compile this driver as a module, choose M here: the
643 module will be called pc87413_wdt.
645 Most people will say N.
648 tristate "RDC R-321x SoC watchdog"
649 depends on X86_RDC321X
651 This is the driver for the built in hardware watchdog
652 in the RDC R-321x SoC.
654 To compile this driver as a module, choose M here: the
655 module will be called rdc321x_wdt.
658 tristate "SBC-60XX Watchdog Timer"
661 This driver can be used with the watchdog timer found on some
662 single board computers, namely the 6010 PII based computer.
663 It may well work with other cards. It reads port 0x443 to enable
664 and re-set the watchdog timer, and reads port 0x45 to disable
665 the watchdog. If you have a card that behave in similar ways,
666 you can probably make this driver work with your card as well.
668 You can compile this driver directly into the kernel, or use
669 it as a module. The module will be called sbc60xxwdt.
672 tristate "SBC8360 Watchdog Timer"
676 This is the driver for the hardware watchdog on the SBC8360 Single
677 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
679 To compile this driver as a module, choose M here: the
680 module will be called sbc8360.
682 Most people will say N.
685 tristate "SBC Nano 7240 Watchdog Timer"
688 This is the driver for the hardware watchdog found on the IEI
689 single board computers EPIC Nano 7240 (and likely others). This
690 watchdog simply watches your kernel to make sure it doesn't freeze,
691 and if it does, it reboots your computer after a certain amount of
694 To compile this driver as a module, choose M here: the
695 module will be called sbc7240_wdt.
698 tristate "SMA CPU5 Watchdog"
702 To compile this driver as a module, choose M here: the
703 module will be called cpu5wdt.
705 config SMSC_SCH311X_WDT
706 tristate "SMSC SCH311X Watchdog Timer"
709 This is the driver for the hardware watchdog timer on the
710 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
711 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
714 To compile this driver as a module, choose M here: the
715 module will be called sch311x_wdt.
717 config SMSC37B787_WDT
718 tristate "Winbond SMsC37B787 Watchdog Timer"
721 This is the driver for the hardware watchdog component on the
722 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
723 from Vision Systems and maybe others.
725 This watchdog simply watches your kernel to make sure it doesn't
726 freeze, and if it does, it reboots your computer after a certain
729 Usually a userspace daemon will notify the kernel WDT driver that
730 userspace is still alive, at regular intervals.
732 To compile this driver as a module, choose M here: the
733 module will be called smsc37b787_wdt.
735 Most people will say N.
738 tristate "W83627HF Watchdog Timer"
741 This is the driver for the hardware watchdog on the W83627HF chipset
742 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
743 (and likely others). This watchdog simply watches your kernel to
744 make sure it doesn't freeze, and if it does, it reboots your computer
745 after a certain amount of time.
747 To compile this driver as a module, choose M here: the
748 module will be called w83627hf_wdt.
750 Most people will say N.
753 tristate "W83697HF/W83697HG Watchdog Timer"
756 This is the driver for the hardware watchdog on the W83697HF/HG
757 chipset as used in Dedibox/VIA motherboards (and likely others).
758 This watchdog simply watches your kernel to make sure it doesn't
759 freeze, and if it does, it reboots your computer after a certain
762 To compile this driver as a module, choose M here: the
763 module will be called w83697hf_wdt.
765 Most people will say N.
768 tristate "W83697UG/W83697UF Watchdog Timer"
771 This is the driver for the hardware watchdog on the W83697UG/UF
772 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
773 This watchdog simply watches your kernel to make sure it doesn't
774 freeze, and if it does, it reboots your computer after a certain
777 To compile this driver as a module, choose M here: the
778 module will be called w83697ug_wdt.
780 Most people will say N.
783 tristate "W83877F (EMACS) Watchdog Timer"
786 This is the driver for the hardware watchdog on the W83877F chipset
787 as used in EMACS PC-104 motherboards (and likely others). This
788 watchdog simply watches your kernel to make sure it doesn't freeze,
789 and if it does, it reboots your computer after a certain amount of
792 To compile this driver as a module, choose M here: the
793 module will be called w83877f_wdt.
795 Most people will say N.
798 tristate "W83977F (PCM-5335) Watchdog Timer"
801 This is the driver for the hardware watchdog on the W83977F I/O chip
802 as used in AAEON's PCM-5335 SBC (and likely others). This
803 watchdog simply watches your kernel to make sure it doesn't freeze,
804 and if it does, it reboots your computer after a certain amount of
807 To compile this driver as a module, choose M here: the
808 module will be called w83977f_wdt.
811 tristate "ZF MachZ Watchdog"
814 If you are using a ZF Micro MachZ processor, say Y here, otherwise
815 N. This is the driver for the watchdog timer built-in on that
816 processor using ZF-Logic interface. This watchdog simply watches
817 your kernel to make sure it doesn't freeze, and if it does, it
818 reboots your computer after a certain amount of time.
820 To compile this driver as a module, choose M here: the
821 module will be called machzwd.
823 config SBC_EPX_C3_WATCHDOG
824 tristate "Winsystems SBC EPX-C3 watchdog"
827 This is the driver for the built-in watchdog timer on the EPX-C3
828 Single-board computer made by Winsystems, Inc.
830 *Note*: This hardware watchdog is not probeable and thus there
831 is no way to know if writing to its IO address will corrupt
832 your system or have any real effect. The only way to be sure
833 that this driver does what you want is to make sure you
834 are running it on an EPX-C3 from Winsystems with the watchdog
835 timer at IO address 0x1ee and 0x1ef. It will write to both those
836 IO ports. Basically, the assumption is made that if you compile
837 this driver into your kernel and/or load it as a module, that you
838 know what you are doing and that you are in fact running on an
841 To compile this driver as a module, choose M here: the
842 module will be called sbc_epx_c3.
848 # M68KNOMMU Architecture
853 tristate "Broadcom BCM47xx Watchdog Timer"
856 Hardware driver for the Broadcom BCM47xx Watchog Timer.
859 tristate "IDT RC32434 SoC Watchdog Timer"
860 depends on MIKROTIK_RB532
862 Hardware driver for the IDT RC32434 SoC built-in
865 To compile this driver as a module, choose M here: the
866 module will be called rc32434_wdt.
869 tristate "Indy/I2 Hardware Watchdog"
870 depends on SGI_HAS_INDYDOG
872 Hardware driver for the Indy's/I2's watchdog. This is a
873 watchdog timer that will reboot the machine after a 60 second
874 timer expired and no process has written to /dev/watchdog during
878 tristate "MTX-1 Hardware Watchdog"
881 Hardware driver for the MTX-1 boards. This is a watchdog timer that
882 will reboot the machine after a 100 seconds timer expired.
885 tristate "PNX833x Hardware Watchdog"
886 depends on SOC_PNX8335
888 Hardware driver for the PNX833x's watchdog. This is a
889 watchdog timer that will reboot the machine after a programable
890 timer has expired and no process has written to /dev/watchdog during
894 tristate "Sibyte SoC hardware watchdog"
897 Watchdog driver for the built in watchdog hardware in Sibyte
898 SoC processors. There are apparently two watchdog timers
899 on such processors; this driver supports only the first one,
900 because currently Linux only supports exporting one watchdog
903 To compile this driver as a loadable module, choose M here.
904 The module will be called sb_wdog.
907 tristate "TI AR7 Watchdog Timer"
910 Hardware driver for the TI AR7 Watchdog Timer.
913 tristate "Toshiba TXx9 Watchdog Timer"
914 depends on CPU_TX39XX || CPU_TX49XX
916 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
919 tristate "Cavium OCTEON SOC family Watchdog Timer"
920 depends on CPU_CAVIUM_OCTEON
922 select EXPORT_UASM if OCTEON_WDT = m
924 Hardware driver for OCTEON's on chip watchdog timer.
925 Enables the watchdog for all cores running Linux. It
926 installs a NMI handler and pokes the watchdog based on an
927 interrupt. On first expiration of the watchdog, the
928 interrupt handler pokes it. The second expiration causes an
929 NMI that prints a message. The third expiration causes a
932 When userspace has /dev/watchdog open, no poking is done
933 from the first interrupt, it is then only poked when the
936 # PARISC Architecture
938 # POWERPC Architecture
941 tristate "GE Watchdog Timer"
942 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
944 Watchdog timer found in a number of GE single board computers.
947 bool "MPC52xx Watchdog Timer"
948 depends on PPC_MPC52xx
950 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
953 tristate "MPC8xxx Platform Watchdog Timer"
954 depends on PPC_8xx || PPC_83xx || PPC_86xx
956 This driver is for a SoC level watchdog that exists on some
957 Freescale PowerPC processors. So far this driver supports:
962 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
965 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
969 tristate "PIKA FPGA Watchdog"
973 This enables the watchdog in the PIKA FPGA. Currently used on
977 bool "PowerPC Book-E Watchdog Timer"
978 depends on BOOKE || 4xx
980 Please see Documentation/watchdog/watchdog-api.txt for
986 tristate "RTAS watchdog"
989 This driver adds watchdog support for the RTAS watchdog.
991 To compile this driver as a module, choose M here. The module
992 will be called wdrtas.
997 tristate "z/VM Watchdog Timer"
1000 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1001 provide a virtual watchdog timer to their guest that cause a
1002 user define Control Program command to be executed after a
1005 To compile this driver as a module, choose M here. The module
1006 will be called vmwatchdog.
1008 # SUPERH (sh + sh64) Architecture
1011 tristate "SuperH Watchdog"
1012 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1014 This driver adds watchdog support for the integrated watchdog in the
1015 SuperH processors. If you have one of these processors and wish
1016 to have watchdog support enabled, say Y, otherwise say N.
1018 As a side note, saying Y here will automatically boost HZ to 1000
1019 so that the timer has a chance to clear the overflow counter. On
1020 slower systems (such as the SH-2 and SH-3) this will likely yield
1021 some performance issues. As such, the WDT should be avoided here
1022 unless it is absolutely necessary.
1024 To compile this driver as a module, choose M here: the
1025 module will be called shwdt.
1028 bool "Allow mmap of SH WDT"
1032 If you say Y here, user applications will be able to mmap the
1035 # SPARC Architecture
1037 # SPARC64 Architecture
1039 config WATCHDOG_CP1XXX
1040 tristate "CP1XXX Hardware Watchdog support"
1041 depends on SPARC64 && PCI
1043 This is the driver for the hardware watchdog timers present on
1044 Sun Microsystems CompactPCI models CP1400 and CP1500.
1046 To compile this driver as a module, choose M here: the
1047 module will be called cpwatchdog.
1049 If you do not have a CompactPCI model CP1400 or CP1500, or
1050 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1051 you should say N to this option.
1054 tristate "RIO Hardware Watchdog support"
1055 depends on SPARC64 && PCI
1057 Say Y here to support the hardware watchdog capability on Sun RIO
1058 machines. The watchdog timeout period is normally one minute but
1059 can be changed with a boot-time parameter.
1061 # XTENSA Architecture
1064 # ISA-based Watchdog Cards
1067 comment "ISA-based Watchdog Cards"
1071 tristate "Berkshire Products ISA-PC Watchdog"
1074 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1075 This card simply watches your kernel to make sure it doesn't freeze,
1076 and if it does, it reboots your computer after a certain amount of
1077 time. This driver is like the WDT501 driver but for different
1078 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1079 watchdog cards can be ordered from <http://www.berkprod.com/>.
1081 To compile this driver as a module, choose M here: the
1082 module will be called pcwd.
1084 Most people will say N.
1087 tristate "Mixcom Watchdog"
1090 This is a driver for the Mixcom hardware watchdog cards. This
1091 watchdog simply watches your kernel to make sure it doesn't freeze,
1092 and if it does, it reboots your computer after a certain amount of
1095 To compile this driver as a module, choose M here: the
1096 module will be called mixcomwd.
1098 Most people will say N.
1101 tristate "WDT Watchdog timer"
1104 If you have a WDT500P or WDT501P watchdog board, say Y here,
1105 otherwise N. It is not possible to probe for this board, which means
1106 that you have to inform the kernel about the IO port and IRQ that
1107 is needed (you can do this via the io and irq parameters)
1109 To compile this driver as a module, choose M here: the
1110 module will be called wdt.
1113 # PCI-based Watchdog Cards
1116 comment "PCI-based Watchdog Cards"
1119 config PCIPCWATCHDOG
1120 tristate "Berkshire Products PCI-PC Watchdog"
1123 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1124 This card simply watches your kernel to make sure it doesn't freeze,
1125 and if it does, it reboots your computer after a certain amount of
1126 time. The card can also monitor the internal temperature of the PC.
1127 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1129 To compile this driver as a module, choose M here: the
1130 module will be called pcwd_pci.
1132 Most people will say N.
1135 tristate "PCI-WDT500/501 Watchdog timer"
1138 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1140 If you have a PCI-WDT501 watchdog board then you can enable the
1141 temperature sensor by setting the type parameter to 501.
1143 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1144 can do this via the tachometer parameter. Only do this if you have a
1145 fan tachometer actually set up.
1147 To compile this driver as a module, choose M here: the
1148 module will be called wdt_pci.
1151 # USB-based Watchdog Cards
1154 comment "USB-based Watchdog Cards"
1157 config USBPCWATCHDOG
1158 tristate "Berkshire Products USB-PC Watchdog"
1161 This is the driver for the Berkshire Products USB-PC Watchdog card.
1162 This card simply watches your kernel to make sure it doesn't freeze,
1163 and if it does, it reboots your computer after a certain amount of
1164 time. The card can also monitor the internal temperature of the PC.
1165 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1167 To compile this driver as a module, choose M here: the
1168 module will be called pcwd_usb.
1170 Most people will say N.