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
32 bool "WatchDog Timer Driver Core"
34 Say Y here if you want to use the new watchdog timer driver core.
35 This driver provides a framework for all watchdog timer drivers
36 and gives them the /dev/watchdog interface (and later also the
39 To compile this driver as a module, choose M here: the module will
42 config WATCHDOG_NOWAYOUT
43 bool "Disable watchdog shutdown on close"
45 The default watchdog behaviour (which you get if you say N here) is
46 to stop the timer if the process managing it closes the file
47 /dev/watchdog. It's always remotely possible that this process might
48 get killed. If you say Y here, the watchdog cannot be stopped once
52 # General Watchdog drivers
55 comment "Watchdog Device Drivers"
57 # Architecture Independent
60 tristate "Software watchdog"
62 A software monitoring watchdog. This will fail to reboot your system
63 from some situations that the hardware watchdog will recover
64 from. Equally it's a lot cheaper to install.
66 To compile this driver as a module, choose M here: the
67 module will be called softdog.
69 config WM831X_WATCHDOG
70 tristate "WM831x watchdog"
73 Support for the watchdog in the WM831x AudioPlus PMICs. When
74 the watchdog triggers the system will be reset.
76 config WM8350_WATCHDOG
77 tristate "WM8350 watchdog"
80 Support for the watchdog in the WM8350 AudioPlus PMIC. When
81 the watchdog triggers the system will be reset.
87 config ARM_SP805_WATCHDOG
88 tristate "ARM SP805 Watchdog"
91 ARM Primecell SP805 Watchdog timer. This will reboot your system when
92 the timeout is reached.
94 config AT91RM9200_WATCHDOG
95 tristate "AT91RM9200 watchdog"
96 depends on ARCH_AT91RM9200
98 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
99 system when the timeout is reached.
101 config AT91SAM9X_WATCHDOG
102 tristate "AT91SAM9X / AT91CAP9 watchdog"
103 depends on ARCH_AT91 && !ARCH_AT91RM9200
105 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
106 reboot your system when the timeout is reached.
108 config 21285_WATCHDOG
109 tristate "DC21285 watchdog"
110 depends on FOOTBRIDGE
112 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
113 here if you wish to use this. Alternatively say M to compile the
114 driver as a module, which will be called wdt285.
116 This driver does not work on all machines. In particular, early CATS
117 boards have hardware problems that will cause the machine to simply
118 lock up if the watchdog fires.
120 "If in doubt, leave it out" - say N.
123 tristate "NetWinder WB83C977 watchdog"
124 depends on FOOTBRIDGE && ARCH_NETWINDER
126 Say Y here to include support for the WB977 watchdog included in
127 NetWinder machines. Alternatively say M to compile the driver as
128 a module, which will be called wdt977.
130 Not sure? It's safe to say N.
132 config IXP2000_WATCHDOG
133 tristate "IXP2000 Watchdog"
134 depends on ARCH_IXP2000
136 Say Y here if to include support for the watchdog timer
137 in the Intel IXP2000(2400, 2800, 2850) network processors.
138 This driver can be built as a module by choosing M. The module
139 will be called ixp2000_wdt.
141 Say N if you are unsure.
143 config IXP4XX_WATCHDOG
144 tristate "IXP4xx Watchdog"
145 depends on ARCH_IXP4XX
147 Say Y here if to include support for the watchdog timer
148 in the Intel IXP4xx network processors. This driver can
149 be built as a module by choosing M. The module will
150 be called ixp4xx_wdt.
152 Note: The internal IXP4xx watchdog does a soft CPU reset
153 which doesn't reset any peripherals. There are circumstances
154 where the watchdog will fail to reset the board correctly
155 (e.g., if the boot ROM is in an unreadable state).
157 Say N if you are unsure.
159 config KS8695_WATCHDOG
160 tristate "KS8695 watchdog"
161 depends on ARCH_KS8695
163 Watchdog timer embedded into KS8695 processor. This will reboot your
164 system when the timeout is reached.
166 config HAVE_S3C2410_WATCHDOG
169 This will include watchdog timer support for Samsung SoCs. If
170 you want to include watchdog support for any machine, kindly
171 select this in the respective mach-XXXX/Kconfig file.
173 config S3C2410_WATCHDOG
174 tristate "S3C2410 Watchdog"
175 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
177 Watchdog timer block in the Samsung SoCs. This will reboot
178 the system when the timer expires with the watchdog enabled.
180 The driver is limited by the speed of the system's PCLK
181 signal, so with reasonably fast systems (PCLK around 50-66MHz)
182 then watchdog intervals of over approximately 20seconds are
185 The driver can be built as a module by choosing M, and will
186 be called s3c2410_wdt
188 config SA1100_WATCHDOG
189 tristate "SA1100/PXA2xx watchdog"
190 depends on ARCH_SA1100 || ARCH_PXA
192 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
193 reboot your system when timeout is reached.
195 NOTE: once enabled, this timer cannot be disabled.
197 To compile this driver as a module, choose M here: the
198 module will be called sa1100_wdt.
201 tristate "Synopsys DesignWare watchdog"
202 depends on ARM && HAVE_CLK
204 Say Y here if to include support for the Synopsys DesignWare
205 watchdog timer found in many ARM chips.
206 To compile this driver as a module, choose M here: the
207 module will be called dw_wdt.
209 config MPCORE_WATCHDOG
210 tristate "MPcore watchdog"
211 depends on HAVE_ARM_TWD
213 Watchdog timer embedded into the MPcore system.
215 To compile this driver as a module, choose M here: the
216 module will be called mpcore_wdt.
218 config EP93XX_WATCHDOG
219 tristate "EP93xx Watchdog"
220 depends on ARCH_EP93XX
222 Say Y here if to include support for the watchdog timer
223 embedded in the Cirrus Logic EP93xx family of devices.
225 To compile this driver as a module, choose M here: the
226 module will be called ep93xx_wdt.
229 tristate "OMAP Watchdog"
230 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
232 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
233 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
235 config PNX4008_WATCHDOG
236 tristate "PNX4008 and LPC32XX Watchdog"
237 depends on ARCH_PNX4008 || ARCH_LPC32XX
239 Say Y here if to include support for the watchdog timer
240 in the PNX4008 or LPC32XX processor.
241 This driver can be built as a module by choosing M. The module
242 will be called pnx4008_wdt.
244 Say N if you are unsure.
247 tristate "IOP Watchdog"
249 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
251 Say Y here if to include support for the watchdog timer
252 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
253 be built as a module by choosing M. The module will
256 Note: The IOP13XX watchdog does an Internal Bus Reset which will
257 affect both cores and the peripherals of the IOP. The ATU-X
258 and/or ATUe configuration registers will remain intact, but if
259 operating as an Root Complex and/or Central Resource, the PCI-X
260 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
262 config DAVINCI_WATCHDOG
263 tristate "DaVinci watchdog"
264 depends on ARCH_DAVINCI
266 Say Y here if to include support for the watchdog timer
267 in the DaVinci DM644x/DM646x processors.
268 To compile this driver as a module, choose M here: the
269 module will be called davinci_wdt.
271 NOTE: once enabled, this timer cannot be disabled.
272 Say N if you are unsure.
274 config ORION_WATCHDOG
275 tristate "Orion watchdog"
276 depends on ARCH_ORION5X || ARCH_KIRKWOOD
278 Say Y here if to include support for the watchdog timer
279 in the Marvell Orion5x and Kirkwood ARM SoCs.
280 To compile this driver as a module, choose M here: the
281 module will be called orion_wdt.
283 config COH901327_WATCHDOG
284 bool "ST-Ericsson COH 901 327 watchdog"
286 default y if MACH_U300
288 Say Y here to include Watchdog timer support for the
289 watchdog embedded into the ST-Ericsson U300 series platforms.
290 This watchdog is used to reset the system and thus cannot be
291 compiled as a module.
293 config TWL4030_WATCHDOG
294 tristate "TWL4030 Watchdog"
295 depends on TWL4030_CORE
297 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
298 watchdog timer support for TWL4030 chips.
300 config STMP3XXX_WATCHDOG
301 tristate "Freescale STMP3XXX watchdog"
302 depends on ARCH_STMP3XXX
304 Say Y here if to include support for the watchdog timer
305 for the Sigmatel STMP37XX/378X SoC.
306 To compile this driver as a module, choose M here: the
307 module will be called stmp3xxx_wdt.
309 config NUC900_WATCHDOG
310 tristate "Nuvoton NUC900 watchdog"
311 depends on ARCH_W90X900
313 Say Y here if to include support for the watchdog timer
314 for the Nuvoton NUC900 series SoCs.
315 To compile this driver as a module, choose M here: the
316 module will be called nuc900_wdt.
319 tristate "Avionic Design Xanthos watchdog"
320 depends on ARCH_PXA_ADX
322 Say Y here if you want support for the watchdog timer on Avionic
323 Design Xanthos boards.
325 config TS72XX_WATCHDOG
326 tristate "TS-72XX SBC Watchdog"
327 depends on MACH_TS72XX
329 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
330 watchdog timer implemented in a external CPLD chip. Say Y here
331 if you want to support for the watchdog timer on TS-72XX boards.
333 To compile this driver as a module, choose M here: the
334 module will be called ts72xx_wdt.
336 config MAX63XX_WATCHDOG
337 tristate "Max63xx watchdog"
338 depends on ARM && HAS_IOMEM
340 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
343 tristate "IMX2+ Watchdog"
344 depends on IMX_HAVE_PLATFORM_IMX2_WDT
346 This is the driver for the hardware watchdog
347 on the Freescale IMX2 and later processors.
348 If you have one of these processors and wish to have
349 watchdog support enabled, say Y, otherwise say N.
351 To compile this driver as a module, choose M here: the
352 module will be called imx2_wdt.
356 config AT32AP700X_WDT
357 tristate "AT32AP700x watchdog"
358 depends on CPU_AT32AP700X
360 Watchdog timer embedded into AT32AP700x devices. This will reboot
361 your system when the timeout is reached.
363 # BLACKFIN Architecture
366 tristate "Blackfin On-Chip Watchdog Timer"
369 If you say yes here you will get support for the Blackfin On-Chip
370 Watchdog Timer. If you have one of these processors and wish to
371 have watchdog support enabled, say Y, otherwise say N.
373 To compile this driver as a module, choose M here: the
374 module will be called bfin_wdt.
382 # X86 (i386 + ia64 + x86_64) Architecture
385 tristate "Acquire SBC Watchdog Timer"
388 This is the driver for the hardware watchdog on Single Board
389 Computers produced by Acquire Inc (and others). This watchdog
390 simply watches your kernel to make sure it doesn't freeze, and if
391 it does, it reboots your computer after a certain amount of time.
393 To compile this driver as a module, choose M here: the
394 module will be called acquirewdt.
396 Most people will say N.
399 tristate "Advantech SBC Watchdog Timer"
402 If you are configuring a Linux kernel for the Advantech single-board
403 computer, say `Y' here to support its built-in watchdog timer
404 feature. More information can be found at
405 <http://www.advantech.com.tw/products/>
408 tristate "ALi M1535 PMU Watchdog Timer"
409 depends on X86 && PCI
411 This is the driver for the hardware watchdog on the ALi M1535 PMU.
413 To compile this driver as a module, choose M here: the
414 module will be called alim1535_wdt.
416 Most people will say N.
419 tristate "ALi M7101 PMU Computer Watchdog"
422 This is the driver for the hardware watchdog on the ALi M7101 PMU
423 as used in the x86 Cobalt servers and also found in some
424 SPARC Netra servers too.
426 To compile this driver as a module, choose M here: the
427 module will be called alim7101_wdt.
429 Most people will say N.
432 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
433 depends on X86 && EXPERIMENTAL
435 This is the driver for the hardware watchdog on the Fintek
436 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
438 You can compile this driver directly into the kernel, or use
439 it as a module. The module will be called f71808e_wdt.
442 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
443 depends on X86 && PCI
445 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
446 (Total Cost of Ownership) timer is a watchdog timer that will reboot
447 the machine after its expiration. The expiration time can be
448 configured with the "heartbeat" parameter.
450 To compile this driver as a module, choose M here: the
451 module will be called sp5100_tco.
454 tristate "AMD Geode CS5535/CS5536 Watchdog"
455 depends on CS5535_MFGPT
457 This driver enables a watchdog capability built into the
458 CS5535/CS5536 companion chips for the AMD Geode GX and LX
459 processors. This watchdog watches your kernel to make sure
460 it doesn't freeze, and if it does, it reboots your computer after
461 a certain amount of time.
463 You can compile this driver directly into the kernel, or use
464 it as a module. The module will be called geodewdt.
467 tristate "AMD Elan SC520 processor Watchdog"
470 This is the driver for the hardware watchdog built in to the
471 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
472 This watchdog simply watches your kernel to make sure it doesn't
473 freeze, and if it does, it reboots your computer after a certain
476 You can compile this driver directly into the kernel, or use
477 it as a module. The module will be called sc520_wdt.
479 config SBC_FITPC2_WATCHDOG
480 tristate "Compulab SBC-FITPC2 watchdog"
483 This is the driver for the built-in watchdog timer on the fit-PC2,
484 fit-PC2i, CM-iAM single-board computers made by Compulab.
486 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
487 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
489 Entering BIOS setup temporary disables watchdog operation regardless to current state,
490 so system will not be restarted while user in BIOS setup.
492 Once watchdog was enabled the system will be restarted every
493 "Watchdog Timer Value" period, so to prevent it user can restart or
494 disable the watchdog.
496 To compile this driver as a module, choose M here: the
497 module will be called sbc_fitpc2_wdt.
499 Most people will say N.
502 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
505 Enable support for the watchdog timer on the Eurotech CPU-1220 and
506 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
507 information are at <http://www.eurotech.it/>.
510 tristate "IB700 SBC Watchdog Timer"
513 This is the driver for the hardware watchdog on the IB700 Single
514 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
515 simply watches your kernel to make sure it doesn't freeze, and if
516 it does, it reboots your computer after a certain amount of time.
518 This driver is like the WDT501 driver but for slightly different hardware.
520 To compile this driver as a module, choose M here: the
521 module will be called ib700wdt.
523 Most people will say N.
526 tristate "IBM Automatic Server Restart"
529 This is the driver for the IBM Automatic Server Restart watchdog
530 timer built-in into some eServer xSeries machines.
532 To compile this driver as a module, choose M here: the
533 module will be called ibmasr.
536 tristate "ICP Single Board Computer Watchdog Timer"
539 This is a driver for the hardware watchdog on the ICP Single
540 Board Computer. This driver is working on (at least) the following
541 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
543 To compile this driver as a module, choose M here: the
544 module will be called wafer5823wdt.
547 tristate "Intel 6300ESB Timer/Watchdog"
548 depends on X86 && PCI
550 Hardware driver for the watchdog timer built into the Intel
551 6300ESB controller hub.
553 To compile this driver as a module, choose M here: the
554 module will be called i6300esb.
556 config INTEL_SCU_WATCHDOG
557 bool "Intel SCU Watchdog for Mobile Platforms"
560 Hardware driver for the watchdog time built into the Intel SCU
561 for Intel Mobile Platforms.
563 To compile this driver as a module, choose M here.
566 tristate "Intel TCO Timer/Watchdog"
567 depends on (X86 || IA64) && PCI
569 Hardware driver for the intel TCO timer based watchdog devices.
570 These drivers are included in the Intel 82801 I/O Controller
571 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
574 The TCO (Total Cost of Ownership) timer is a watchdog timer
575 that will reboot the machine after its second expiration. The
576 expiration time can be configured with the "heartbeat" parameter.
578 On some motherboards the driver may fail to reset the chipset's
579 NO_REBOOT flag which prevents the watchdog from rebooting the
580 machine. If this is the case you will get a kernel message like
581 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
583 To compile this driver as a module, choose M here: the
584 module will be called iTCO_wdt.
586 config ITCO_VENDOR_SUPPORT
587 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
590 Add vendor specific support to the intel TCO timer based watchdog
591 devices. At this moment we only have additional support for some
592 SuperMicro Inc. motherboards.
595 tristate "IT8712F (Smart Guardian) Watchdog Timer"
598 This is the driver for the built-in watchdog timer on the IT8712F
599 Super I/0 chipset used on many motherboards.
601 If the driver does not work, then make sure that the game port in
604 To compile this driver as a module, choose M here: the
605 module will be called it8712f_wdt.
608 tristate "IT87 Watchdog Timer"
609 depends on X86 && EXPERIMENTAL
611 This is the driver for the hardware watchdog on the ITE IT8702,
612 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
613 This watchdog simply watches your kernel to make sure it doesn't
614 freeze, and if it does, it reboots your computer after a certain
617 To compile this driver as a module, choose M here: the module will
621 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
622 depends on X86 && PCI
624 A software monitoring watchdog and NMI sourcing driver. This driver
625 will detect lockups and provide a stack trace. This is a driver that
626 will only load on an HP ProLiant system with a minimum of iLO2 support.
627 To compile this driver as a module, choose M here: the module will be
630 config HPWDT_NMI_DECODING
631 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
632 depends on HP_WATCHDOG
635 When an NMI occurs this feature will make the necessary BIOS calls to
636 log the cause of the NMI.
639 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
642 This is a driver for National Semiconductor PC87307/PC97307 hardware
643 watchdog cards as found on the SC1200. This watchdog is mainly used
644 for power management purposes and can be used to power down the device
645 during inactivity periods (includes interrupt activity monitoring).
647 To compile this driver as a module, choose M here: the
648 module will be called sc1200wdt.
650 Most people will say N.
653 tristate "National Semiconductor SCx200 Watchdog"
654 depends on SCx200 && PCI
656 Enable the built-in watchdog timer support on the National
657 Semiconductor SCx200 processors.
659 If compiled as a module, it will be called scx200_wdt.
662 tristate "NS PC87413 watchdog"
665 This is the driver for the hardware watchdog on the PC87413 chipset
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 To compile this driver as a module, choose M here: the
671 module will be called pc87413_wdt.
673 Most people will say N.
676 tristate "nVidia TCO Timer/Watchdog"
677 depends on X86 && PCI
679 Hardware driver for the TCO timer built into the nVidia Hub family
680 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
681 watchdog timer that will reboot the machine after its second
682 expiration. The expiration time can be configured with the
683 "heartbeat" parameter.
685 On some motherboards the driver may fail to reset the chipset's
686 NO_REBOOT flag which prevents the watchdog from rebooting the
687 machine. If this is the case you will get a kernel message like
688 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
690 To compile this driver as a module, choose M here: the
691 module will be called nv_tco.
694 tristate "RDC R-321x SoC watchdog"
695 depends on X86_RDC321X
697 This is the driver for the built in hardware watchdog
698 in the RDC R-321x SoC.
700 To compile this driver as a module, choose M here: the
701 module will be called rdc321x_wdt.
704 tristate "SBC-60XX Watchdog Timer"
707 This driver can be used with the watchdog timer found on some
708 single board computers, namely the 6010 PII based computer.
709 It may well work with other cards. It reads port 0x443 to enable
710 and re-set the watchdog timer, and reads port 0x45 to disable
711 the watchdog. If you have a card that behave in similar ways,
712 you can probably make this driver work with your card as well.
714 You can compile this driver directly into the kernel, or use
715 it as a module. The module will be called sbc60xxwdt.
718 tristate "SBC8360 Watchdog Timer"
722 This is the driver for the hardware watchdog on the SBC8360 Single
723 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
725 To compile this driver as a module, choose M here: the
726 module will be called sbc8360.
728 Most people will say N.
731 tristate "SBC Nano 7240 Watchdog Timer"
734 This is the driver for the hardware watchdog found on the IEI
735 single board computers EPIC Nano 7240 (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 sbc7240_wdt.
744 tristate "SMA CPU5 Watchdog"
748 To compile this driver as a module, choose M here: the
749 module will be called cpu5wdt.
751 config SMSC_SCH311X_WDT
752 tristate "SMSC SCH311X Watchdog Timer"
755 This is the driver for the hardware watchdog timer on the
756 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
757 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
760 To compile this driver as a module, choose M here: the
761 module will be called sch311x_wdt.
763 config SMSC37B787_WDT
764 tristate "Winbond SMsC37B787 Watchdog Timer"
767 This is the driver for the hardware watchdog component on the
768 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
769 from Vision Systems and maybe others.
771 This watchdog simply watches your kernel to make sure it doesn't
772 freeze, and if it does, it reboots your computer after a certain
775 Usually a userspace daemon will notify the kernel WDT driver that
776 userspace is still alive, at regular intervals.
778 To compile this driver as a module, choose M here: the
779 module will be called smsc37b787_wdt.
781 Most people will say N.
784 tristate "W83627HF/W83627DHG Watchdog Timer"
787 This is the driver for the hardware watchdog on the W83627HF chipset
788 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
789 (and likely others). The driver also supports the W83627DHG chip.
790 This watchdog simply watches your kernel to make sure it doesn't
791 freeze, and if it does, it reboots your computer after a certain
794 To compile this driver as a module, choose M here: the
795 module will be called w83627hf_wdt.
797 Most people will say N.
800 tristate "W83697HF/W83697HG Watchdog Timer"
803 This is the driver for the hardware watchdog on the W83697HF/HG
804 chipset as used in Dedibox/VIA motherboards (and likely others).
805 This watchdog simply watches your kernel to make sure it doesn't
806 freeze, and if it does, it reboots your computer after a certain
809 To compile this driver as a module, choose M here: the
810 module will be called w83697hf_wdt.
812 Most people will say N.
815 tristate "W83697UG/W83697UF Watchdog Timer"
818 This is the driver for the hardware watchdog on the W83697UG/UF
819 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
820 This watchdog simply watches your kernel to make sure it doesn't
821 freeze, and if it does, it reboots your computer after a certain
824 To compile this driver as a module, choose M here: the
825 module will be called w83697ug_wdt.
827 Most people will say N.
830 tristate "W83877F (EMACS) Watchdog Timer"
833 This is the driver for the hardware watchdog on the W83877F chipset
834 as used in EMACS PC-104 motherboards (and likely others). This
835 watchdog simply watches your kernel to make sure it doesn't freeze,
836 and if it does, it reboots your computer after a certain amount of
839 To compile this driver as a module, choose M here: the
840 module will be called w83877f_wdt.
842 Most people will say N.
845 tristate "W83977F (PCM-5335) Watchdog Timer"
848 This is the driver for the hardware watchdog on the W83977F I/O chip
849 as used in AAEON's PCM-5335 SBC (and likely others). This
850 watchdog simply watches your kernel to make sure it doesn't freeze,
851 and if it does, it reboots your computer after a certain amount of
854 To compile this driver as a module, choose M here: the
855 module will be called w83977f_wdt.
858 tristate "ZF MachZ Watchdog"
861 If you are using a ZF Micro MachZ processor, say Y here, otherwise
862 N. This is the driver for the watchdog timer built-in on that
863 processor using ZF-Logic interface. This watchdog simply watches
864 your kernel to make sure it doesn't freeze, and if it does, it
865 reboots your computer after a certain amount of time.
867 To compile this driver as a module, choose M here: the
868 module will be called machzwd.
870 config SBC_EPX_C3_WATCHDOG
871 tristate "Winsystems SBC EPX-C3 watchdog"
874 This is the driver for the built-in watchdog timer on the EPX-C3
875 Single-board computer made by Winsystems, Inc.
877 *Note*: This hardware watchdog is not probeable and thus there
878 is no way to know if writing to its IO address will corrupt
879 your system or have any real effect. The only way to be sure
880 that this driver does what you want is to make sure you
881 are running it on an EPX-C3 from Winsystems with the watchdog
882 timer at IO address 0x1ee and 0x1ef. It will write to both those
883 IO ports. Basically, the assumption is made that if you compile
884 this driver into your kernel and/or load it as a module, that you
885 know what you are doing and that you are in fact running on an
888 To compile this driver as a module, choose M here: the
889 module will be called sbc_epx_c3.
895 config M54xx_WATCHDOG
896 tristate "MCF54xx watchdog support"
899 To compile this driver as a module, choose M here: the
900 module will be called m54xx_wdt.
902 # MicroBlaze Architecture
904 config XILINX_WATCHDOG
905 tristate "Xilinx Watchdog timer"
906 depends on MICROBLAZE
908 Watchdog driver for the xps_timebase_wdt ip core.
910 IMPORTANT: The xps_timebase_wdt parent must have the property
911 "clock-frequency" at device tree.
913 To compile this driver as a module, choose M here: the
914 module will be called of_xilinx_wdt.
919 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
922 Hardware driver for the built-in watchdog timer on the Atheros
923 AR71XX/AR724X/AR913X SoCs.
926 tristate "Broadcom BCM47xx Watchdog Timer"
929 Hardware driver for the Broadcom BCM47xx Watchog Timer.
932 tristate "IDT RC32434 SoC Watchdog Timer"
933 depends on MIKROTIK_RB532
935 Hardware driver for the IDT RC32434 SoC built-in
938 To compile this driver as a module, choose M here: the
939 module will be called rc32434_wdt.
942 tristate "Indy/I2 Hardware Watchdog"
943 depends on SGI_HAS_INDYDOG
945 Hardware driver for the Indy's/I2's watchdog. This is a
946 watchdog timer that will reboot the machine after a 60 second
947 timer expired and no process has written to /dev/watchdog during
951 tristate "Ingenic jz4740 SoC hardware watchdog"
952 depends on MACH_JZ4740
954 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
957 tristate "MTX-1 Hardware Watchdog"
960 Hardware driver for the MTX-1 boards. This is a watchdog timer that
961 will reboot the machine after a 100 seconds timer expired.
964 tristate "PNX833x Hardware Watchdog"
965 depends on SOC_PNX8335
967 Hardware driver for the PNX833x's watchdog. This is a
968 watchdog timer that will reboot the machine after a programmable
969 timer has expired and no process has written to /dev/watchdog during
973 tristate "Sibyte SoC hardware watchdog"
976 Watchdog driver for the built in watchdog hardware in Sibyte
977 SoC processors. There are apparently two watchdog timers
978 on such processors; this driver supports only the first one,
979 because currently Linux only supports exporting one watchdog
982 To compile this driver as a loadable module, choose M here.
983 The module will be called sb_wdog.
986 tristate "TI AR7 Watchdog Timer"
989 Hardware driver for the TI AR7 Watchdog Timer.
992 tristate "Toshiba TXx9 Watchdog Timer"
993 depends on CPU_TX39XX || CPU_TX49XX
995 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
998 tristate "Cavium OCTEON SOC family Watchdog Timer"
999 depends on CPU_CAVIUM_OCTEON
1001 select EXPORT_UASM if OCTEON_WDT = m
1003 Hardware driver for OCTEON's on chip watchdog timer.
1004 Enables the watchdog for all cores running Linux. It
1005 installs a NMI handler and pokes the watchdog based on an
1006 interrupt. On first expiration of the watchdog, the
1007 interrupt handler pokes it. The second expiration causes an
1008 NMI that prints a message. The third expiration causes a
1011 When userspace has /dev/watchdog open, no poking is done
1012 from the first interrupt, it is then only poked when the
1016 tristate "Broadcom BCM63xx hardware watchdog"
1019 Watchdog driver for the built in watchdog hardware in Broadcom
1022 To compile this driver as a loadable module, choose M here.
1023 The module will be called bcm63xx_wdt.
1026 tristate "Lantiq SoC watchdog"
1029 Hardware driver for the Lantiq SoC Watchdog Timer.
1031 # PARISC Architecture
1033 # POWERPC Architecture
1036 tristate "GE Watchdog Timer"
1037 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
1039 Watchdog timer found in a number of GE single board computers.
1042 bool "MPC52xx Watchdog Timer"
1043 depends on PPC_MPC52xx
1045 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1048 tristate "MPC8xxx Platform Watchdog Timer"
1049 depends on PPC_8xx || PPC_83xx || PPC_86xx
1051 This driver is for a SoC level watchdog that exists on some
1052 Freescale PowerPC processors. So far this driver supports:
1057 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1060 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1064 tristate "PIKA FPGA Watchdog"
1068 This enables the watchdog in the PIKA FPGA. Currently used on
1072 tristate "PowerPC Book-E Watchdog Timer"
1073 depends on BOOKE || 4xx
1075 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1076 MPC85xx SOCs and the IBM PowerPC 440.
1078 Please see Documentation/watchdog/watchdog-api.txt for
1081 config BOOKE_WDT_DEFAULT_TIMEOUT
1082 int "PowerPC Book-E Watchdog Timer Default Timeout"
1083 depends on BOOKE_WDT
1084 default 38 if FSL_BOOKE
1085 range 0 63 if FSL_BOOKE
1086 default 3 if !FSL_BOOKE
1087 range 0 3 if !FSL_BOOKE
1089 Select the default watchdog timer period to be used by the PowerPC
1090 Book-E watchdog driver. A watchdog "event" occurs when the bit
1091 position represented by this number transitions from zero to one.
1093 For Freescale Book-E processors, this is a number between 0 and 63.
1094 For other Book-E processors, this is a number between 0 and 3.
1096 The value can be overidden by the wdt_period command-line parameter.
1098 # PPC64 Architecture
1100 config WATCHDOG_RTAS
1101 tristate "RTAS watchdog"
1104 This driver adds watchdog support for the RTAS watchdog.
1106 To compile this driver as a module, choose M here. The module
1107 will be called wdrtas.
1112 tristate "z/VM Watchdog Timer"
1115 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1116 provide a virtual watchdog timer to their guest that cause a
1117 user define Control Program command to be executed after a
1120 To compile this driver as a module, choose M here. The module
1121 will be called vmwatchdog.
1123 # SUPERH (sh + sh64) Architecture
1126 tristate "SuperH Watchdog"
1127 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1129 This driver adds watchdog support for the integrated watchdog in the
1130 SuperH processors. If you have one of these processors and wish
1131 to have watchdog support enabled, say Y, otherwise say N.
1133 As a side note, saying Y here will automatically boost HZ to 1000
1134 so that the timer has a chance to clear the overflow counter. On
1135 slower systems (such as the SH-2 and SH-3) this will likely yield
1136 some performance issues. As such, the WDT should be avoided here
1137 unless it is absolutely necessary.
1139 To compile this driver as a module, choose M here: the
1140 module will be called shwdt.
1142 # SPARC Architecture
1144 # SPARC64 Architecture
1146 config WATCHDOG_CP1XXX
1147 tristate "CP1XXX Hardware Watchdog support"
1148 depends on SPARC64 && PCI
1150 This is the driver for the hardware watchdog timers present on
1151 Sun Microsystems CompactPCI models CP1400 and CP1500.
1153 To compile this driver as a module, choose M here: the
1154 module will be called cpwatchdog.
1156 If you do not have a CompactPCI model CP1400 or CP1500, or
1157 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1158 you should say N to this option.
1161 tristate "RIO Hardware Watchdog support"
1162 depends on SPARC64 && PCI
1164 Say Y here to support the hardware watchdog capability on Sun RIO
1165 machines. The watchdog timeout period is normally one minute but
1166 can be changed with a boot-time parameter.
1168 # XTENSA Architecture
1173 tristate "Xen Watchdog support"
1176 Say Y here to support the hypervisor watchdog capability provided
1177 by Xen 4.0 and newer. The watchdog timeout period is normally one
1178 minute but can be changed with a boot-time parameter.
1181 # ISA-based Watchdog Cards
1184 comment "ISA-based Watchdog Cards"
1188 tristate "Berkshire Products ISA-PC Watchdog"
1191 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1192 This card simply watches your kernel to make sure it doesn't freeze,
1193 and if it does, it reboots your computer after a certain amount of
1194 time. This driver is like the WDT501 driver but for different
1195 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1196 watchdog cards can be ordered from <http://www.berkprod.com/>.
1198 To compile this driver as a module, choose M here: the
1199 module will be called pcwd.
1201 Most people will say N.
1204 tristate "Mixcom Watchdog"
1207 This is a driver for the Mixcom hardware watchdog cards. This
1208 watchdog simply watches your kernel to make sure it doesn't freeze,
1209 and if it does, it reboots your computer after a certain amount of
1212 To compile this driver as a module, choose M here: the
1213 module will be called mixcomwd.
1215 Most people will say N.
1218 tristate "WDT Watchdog timer"
1221 If you have a WDT500P or WDT501P watchdog board, say Y here,
1222 otherwise N. It is not possible to probe for this board, which means
1223 that you have to inform the kernel about the IO port and IRQ that
1224 is needed (you can do this via the io and irq parameters)
1226 To compile this driver as a module, choose M here: the
1227 module will be called wdt.
1230 # PCI-based Watchdog Cards
1233 comment "PCI-based Watchdog Cards"
1236 config PCIPCWATCHDOG
1237 tristate "Berkshire Products PCI-PC Watchdog"
1240 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1241 This card simply watches your kernel to make sure it doesn't freeze,
1242 and if it does, it reboots your computer after a certain amount of
1243 time. The card can also monitor the internal temperature of the PC.
1244 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1246 To compile this driver as a module, choose M here: the
1247 module will be called pcwd_pci.
1249 Most people will say N.
1252 tristate "PCI-WDT500/501 Watchdog timer"
1255 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1257 If you have a PCI-WDT501 watchdog board then you can enable the
1258 temperature sensor by setting the type parameter to 501.
1260 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1261 can do this via the tachometer parameter. Only do this if you have a
1262 fan tachometer actually set up.
1264 To compile this driver as a module, choose M here: the
1265 module will be called wdt_pci.
1268 # USB-based Watchdog Cards
1271 comment "USB-based Watchdog Cards"
1274 config USBPCWATCHDOG
1275 tristate "Berkshire Products USB-PC Watchdog"
1278 This is the driver for the Berkshire Products USB-PC Watchdog card.
1279 This card simply watches your kernel to make sure it doesn't freeze,
1280 and if it does, it reboots your computer after a certain amount of
1281 time. The card can also monitor the internal temperature of the PC.
1282 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1284 To compile this driver as a module, choose M here: the
1285 module will be called pcwd_usb.
1287 Most people will say N.