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 config WATCHDOG_NOWAYOUT
40 bool "Disable watchdog shutdown on close"
42 The default watchdog behaviour (which you get if you say N here) is
43 to stop the timer if the process managing it closes the file
44 /dev/watchdog. It's always remotely possible that this process might
45 get killed. If you say Y here, the watchdog cannot be stopped once
49 # General Watchdog drivers
52 comment "Watchdog Device Drivers"
54 # Architecture Independent
57 tristate "Software watchdog"
60 A software monitoring watchdog. This will fail to reboot your system
61 from some situations that the hardware watchdog will recover
62 from. Equally it's a lot cheaper to install.
64 To compile this driver as a module, choose M here: the
65 module will be called softdog.
67 config WM831X_WATCHDOG
68 tristate "WM831x watchdog"
72 Support for the watchdog in the WM831x AudioPlus PMICs. When
73 the watchdog triggers the system will be reset.
75 config WM8350_WATCHDOG
76 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
178 Watchdog timer block in the Samsung SoCs. This will reboot
179 the system when the timer expires with the watchdog enabled.
181 The driver is limited by the speed of the system's PCLK
182 signal, so with reasonably fast systems (PCLK around 50-66MHz)
183 then watchdog intervals of over approximately 20seconds are
186 The driver can be built as a module by choosing M, and will
187 be called s3c2410_wdt
189 config SA1100_WATCHDOG
190 tristate "SA1100/PXA2xx watchdog"
191 depends on ARCH_SA1100 || ARCH_PXA
193 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
194 reboot your system when timeout is reached.
196 NOTE: once enabled, this timer cannot be disabled.
198 To compile this driver as a module, choose M here: the
199 module will be called sa1100_wdt.
202 tristate "Synopsys DesignWare watchdog"
203 depends on ARM && HAVE_CLK
205 Say Y here if to include support for the Synopsys DesignWare
206 watchdog timer found in many ARM chips.
207 To compile this driver as a module, choose M here: the
208 module will be called dw_wdt.
210 config MPCORE_WATCHDOG
211 tristate "MPcore watchdog"
212 depends on HAVE_ARM_TWD
214 Watchdog timer embedded into the MPcore system.
216 To compile this driver as a module, choose M here: the
217 module will be called mpcore_wdt.
219 config EP93XX_WATCHDOG
220 tristate "EP93xx Watchdog"
221 depends on ARCH_EP93XX
224 Say Y here if to include support for the watchdog timer
225 embedded in the Cirrus Logic EP93xx family of devices.
227 To compile this driver as a module, choose M here: the
228 module will be called ep93xx_wdt.
231 tristate "OMAP Watchdog"
232 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
234 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
235 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
237 config PNX4008_WATCHDOG
238 tristate "PNX4008 and LPC32XX Watchdog"
239 depends on ARCH_PNX4008 || ARCH_LPC32XX
242 Say Y here if to include support for the watchdog timer
243 in the PNX4008 or LPC32XX processor.
244 This driver can be built as a module by choosing M. The module
245 will be called pnx4008_wdt.
247 Say N if you are unsure.
250 tristate "IOP Watchdog"
252 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
254 Say Y here if to include support for the watchdog timer
255 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
256 be built as a module by choosing M. The module will
259 Note: The IOP13XX watchdog does an Internal Bus Reset which will
260 affect both cores and the peripherals of the IOP. The ATU-X
261 and/or ATUe configuration registers will remain intact, but if
262 operating as an Root Complex and/or Central Resource, the PCI-X
263 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
265 config DAVINCI_WATCHDOG
266 tristate "DaVinci watchdog"
267 depends on ARCH_DAVINCI
269 Say Y here if to include support for the watchdog timer
270 in the DaVinci DM644x/DM646x processors.
271 To compile this driver as a module, choose M here: the
272 module will be called davinci_wdt.
274 NOTE: once enabled, this timer cannot be disabled.
275 Say N if you are unsure.
277 config ORION_WATCHDOG
278 tristate "Orion watchdog"
279 depends on ARCH_ORION5X || ARCH_KIRKWOOD
281 Say Y here if to include support for the watchdog timer
282 in the Marvell Orion5x and Kirkwood ARM SoCs.
283 To compile this driver as a module, choose M here: the
284 module will be called orion_wdt.
286 config COH901327_WATCHDOG
287 bool "ST-Ericsson COH 901 327 watchdog"
289 default y if MACH_U300
291 Say Y here to include Watchdog timer support for the
292 watchdog embedded into the ST-Ericsson U300 series platforms.
293 This watchdog is used to reset the system and thus cannot be
294 compiled as a module.
296 config TWL4030_WATCHDOG
297 tristate "TWL4030 Watchdog"
298 depends on TWL4030_CORE
300 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
301 watchdog timer support for TWL4030 chips.
303 config STMP3XXX_WATCHDOG
304 tristate "Freescale STMP3XXX watchdog"
305 depends on ARCH_STMP3XXX
307 Say Y here if to include support for the watchdog timer
308 for the Sigmatel STMP37XX/378X SoC.
309 To compile this driver as a module, choose M here: the
310 module will be called stmp3xxx_wdt.
312 config NUC900_WATCHDOG
313 tristate "Nuvoton NUC900 watchdog"
314 depends on ARCH_W90X900
316 Say Y here if to include support for the watchdog timer
317 for the Nuvoton NUC900 series SoCs.
318 To compile this driver as a module, choose M here: the
319 module will be called nuc900_wdt.
321 config TS72XX_WATCHDOG
322 tristate "TS-72XX SBC Watchdog"
323 depends on MACH_TS72XX
325 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
326 watchdog timer implemented in a external CPLD chip. Say Y here
327 if you want to support for the watchdog timer on TS-72XX boards.
329 To compile this driver as a module, choose M here: the
330 module will be called ts72xx_wdt.
332 config MAX63XX_WATCHDOG
333 tristate "Max63xx watchdog"
334 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 IMX_HAVE_PLATFORM_IMX2_WDT
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, F71862FG, F71869, F71882FG and F71889FG Watchdog"
430 depends on X86 && EXPERIMENTAL
432 This is the driver for the hardware watchdog on the Fintek
433 F71808E, F71862FG, F71869, F71882FG and F71889FG 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.
439 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
440 depends on X86 && PCI
442 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
443 (Total Cost of Ownership) timer is a watchdog timer that will reboot
444 the machine after its expiration. The expiration time can be
445 configured with the "heartbeat" parameter.
447 To compile this driver as a module, choose M here: the
448 module will be called sp5100_tco.
451 tristate "AMD Geode CS5535/CS5536 Watchdog"
452 depends on CS5535_MFGPT
454 This driver enables a watchdog capability built into the
455 CS5535/CS5536 companion chips for the AMD Geode GX and LX
456 processors. This watchdog watches your kernel to make sure
457 it doesn't freeze, and if it does, it reboots your computer after
458 a certain amount of time.
460 You can compile this driver directly into the kernel, or use
461 it as a module. The module will be called geodewdt.
464 tristate "AMD Elan SC520 processor Watchdog"
467 This is the driver for the hardware watchdog built in to the
468 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
469 This watchdog simply watches your kernel to make sure it doesn't
470 freeze, and if it does, it reboots your computer after a certain
473 You can compile this driver directly into the kernel, or use
474 it as a module. The module will be called sc520_wdt.
476 config SBC_FITPC2_WATCHDOG
477 tristate "Compulab SBC-FITPC2 watchdog"
480 This is the driver for the built-in watchdog timer on the fit-PC2,
481 fit-PC2i, CM-iAM single-board computers made by Compulab.
483 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
484 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
486 Entering BIOS setup temporary disables watchdog operation regardless to current state,
487 so system will not be restarted while user in BIOS setup.
489 Once watchdog was enabled the system will be restarted every
490 "Watchdog Timer Value" period, so to prevent it user can restart or
491 disable the watchdog.
493 To compile this driver as a module, choose M here: the
494 module will be called sbc_fitpc2_wdt.
496 Most people will say N.
499 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
502 Enable support for the watchdog timer on the Eurotech CPU-1220 and
503 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
504 information are at <http://www.eurotech.it/>.
507 tristate "IB700 SBC Watchdog Timer"
510 This is the driver for the hardware watchdog on the IB700 Single
511 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
512 simply watches your kernel to make sure it doesn't freeze, and if
513 it does, it reboots your computer after a certain amount of time.
515 This driver is like the WDT501 driver but for slightly different hardware.
517 To compile this driver as a module, choose M here: the
518 module will be called ib700wdt.
520 Most people will say N.
523 tristate "IBM Automatic Server Restart"
526 This is the driver for the IBM Automatic Server Restart watchdog
527 timer built-in into some eServer xSeries machines.
529 To compile this driver as a module, choose M here: the
530 module will be called ibmasr.
533 tristate "ICP Single Board Computer Watchdog Timer"
536 This is a driver for the hardware watchdog on the ICP Single
537 Board Computer. This driver is working on (at least) the following
538 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
540 To compile this driver as a module, choose M here: the
541 module will be called wafer5823wdt.
544 tristate "Intel 6300ESB Timer/Watchdog"
545 depends on X86 && PCI
547 Hardware driver for the watchdog timer built into the Intel
548 6300ESB controller hub.
550 To compile this driver as a module, choose M here: the
551 module will be called i6300esb.
553 config INTEL_SCU_WATCHDOG
554 bool "Intel SCU Watchdog for Mobile Platforms"
557 Hardware driver for the watchdog time built into the Intel SCU
558 for Intel Mobile Platforms.
560 To compile this driver as a module, choose M here.
563 tristate "Intel TCO Timer/Watchdog"
564 depends on (X86 || IA64) && PCI
566 Hardware driver for the intel TCO timer based watchdog devices.
567 These drivers are included in the Intel 82801 I/O Controller
568 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
571 The TCO (Total Cost of Ownership) timer is a watchdog timer
572 that will reboot the machine after its second expiration. The
573 expiration time can be configured with the "heartbeat" parameter.
575 On some motherboards the driver may fail to reset the chipset's
576 NO_REBOOT flag which prevents the watchdog from rebooting the
577 machine. If this is the case you will get a kernel message like
578 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
580 To compile this driver as a module, choose M here: the
581 module will be called iTCO_wdt.
583 config ITCO_VENDOR_SUPPORT
584 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
587 Add vendor specific support to the intel TCO timer based watchdog
588 devices. At this moment we only have additional support for some
589 SuperMicro Inc. motherboards.
592 tristate "IT8712F (Smart Guardian) Watchdog Timer"
595 This is the driver for the built-in watchdog timer on the IT8712F
596 Super I/0 chipset used on many motherboards.
598 If the driver does not work, then make sure that the game port in
601 To compile this driver as a module, choose M here: the
602 module will be called it8712f_wdt.
605 tristate "IT87 Watchdog Timer"
606 depends on X86 && EXPERIMENTAL
608 This is the driver for the hardware watchdog on the ITE IT8702,
609 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
610 This watchdog simply watches your kernel to make sure it doesn't
611 freeze, and if it does, it reboots your computer after a certain
614 To compile this driver as a module, choose M here: the module will
618 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
619 depends on X86 && PCI
621 A software monitoring watchdog and NMI sourcing driver. This driver
622 will detect lockups and provide a stack trace. This is a driver that
623 will only load on an HP ProLiant system with a minimum of iLO2 support.
624 To compile this driver as a module, choose M here: the module will be
627 config HPWDT_NMI_DECODING
628 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
629 depends on HP_WATCHDOG
632 When an NMI occurs this feature will make the necessary BIOS calls to
633 log the cause of the NMI.
636 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
639 This is a driver for National Semiconductor PC87307/PC97307 hardware
640 watchdog cards as found on the SC1200. This watchdog is mainly used
641 for power management purposes and can be used to power down the device
642 during inactivity periods (includes interrupt activity monitoring).
644 To compile this driver as a module, choose M here: the
645 module will be called sc1200wdt.
647 Most people will say N.
650 tristate "National Semiconductor SCx200 Watchdog"
651 depends on SCx200 && PCI
653 Enable the built-in watchdog timer support on the National
654 Semiconductor SCx200 processors.
656 If compiled as a module, it will be called scx200_wdt.
659 tristate "NS PC87413 watchdog"
662 This is the driver for the hardware watchdog on the PC87413 chipset
663 This watchdog simply watches your kernel to make sure it doesn't
664 freeze, and if it does, it reboots your computer after a certain
667 To compile this driver as a module, choose M here: the
668 module will be called pc87413_wdt.
670 Most people will say N.
673 tristate "nVidia TCO Timer/Watchdog"
674 depends on X86 && PCI
676 Hardware driver for the TCO timer built into the nVidia Hub family
677 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
678 watchdog timer that will reboot the machine after its second
679 expiration. The expiration time can be configured with the
680 "heartbeat" parameter.
682 On some motherboards the driver may fail to reset the chipset's
683 NO_REBOOT flag which prevents the watchdog from rebooting the
684 machine. If this is the case you will get a kernel message like
685 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
687 To compile this driver as a module, choose M here: the
688 module will be called nv_tco.
691 tristate "RDC R-321x SoC watchdog"
692 depends on X86_RDC321X
694 This is the driver for the built in hardware watchdog
695 in the RDC R-321x SoC.
697 To compile this driver as a module, choose M here: the
698 module will be called rdc321x_wdt.
701 tristate "SBC-60XX Watchdog Timer"
704 This driver can be used with the watchdog timer found on some
705 single board computers, namely the 6010 PII based computer.
706 It may well work with other cards. It reads port 0x443 to enable
707 and re-set the watchdog timer, and reads port 0x45 to disable
708 the watchdog. If you have a card that behave in similar ways,
709 you can probably make this driver work with your card as well.
711 You can compile this driver directly into the kernel, or use
712 it as a module. The module will be called sbc60xxwdt.
715 tristate "SBC8360 Watchdog Timer"
719 This is the driver for the hardware watchdog on the SBC8360 Single
720 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
722 To compile this driver as a module, choose M here: the
723 module will be called sbc8360.
725 Most people will say N.
728 tristate "SBC Nano 7240 Watchdog Timer"
729 depends on X86_32 && !UML
731 This is the driver for the hardware watchdog found on the IEI
732 single board computers EPIC Nano 7240 (and likely others). This
733 watchdog simply watches your kernel to make sure it doesn't freeze,
734 and if it does, it reboots your computer after a certain amount of
737 To compile this driver as a module, choose M here: the
738 module will be called sbc7240_wdt.
741 tristate "SMA CPU5 Watchdog"
745 To compile this driver as a module, choose M here: the
746 module will be called cpu5wdt.
748 config SMSC_SCH311X_WDT
749 tristate "SMSC SCH311X Watchdog Timer"
752 This is the driver for the hardware watchdog timer on the
753 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
754 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
757 To compile this driver as a module, choose M here: the
758 module will be called sch311x_wdt.
760 config SMSC37B787_WDT
761 tristate "Winbond SMsC37B787 Watchdog Timer"
764 This is the driver for the hardware watchdog component on the
765 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
766 from Vision Systems and maybe others.
768 This watchdog simply watches your kernel to make sure it doesn't
769 freeze, and if it does, it reboots your computer after a certain
772 Usually a userspace daemon will notify the kernel WDT driver that
773 userspace is still alive, at regular intervals.
775 To compile this driver as a module, choose M here: the
776 module will be called smsc37b787_wdt.
778 Most people will say N.
781 tristate "VIA Watchdog Timer"
785 This is the driver for the hardware watchdog timer on VIA
786 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
788 To compile this driver as a module, choose M here; the module
789 will be called via_wdt.
791 Most people will say N.
794 tristate "W83627HF/W83627DHG Watchdog Timer"
797 This is the driver for the hardware watchdog on the W83627HF chipset
798 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
799 (and likely others). The driver also supports the W83627DHG chip.
800 This watchdog simply watches your kernel to make sure it doesn't
801 freeze, and if it does, it reboots your computer after a certain
804 To compile this driver as a module, choose M here: the
805 module will be called w83627hf_wdt.
807 Most people will say N.
810 tristate "W83697HF/W83697HG Watchdog Timer"
813 This is the driver for the hardware watchdog on the W83697HF/HG
814 chipset as used in Dedibox/VIA motherboards (and likely others).
815 This watchdog simply watches your kernel to make sure it doesn't
816 freeze, and if it does, it reboots your computer after a certain
819 To compile this driver as a module, choose M here: the
820 module will be called w83697hf_wdt.
822 Most people will say N.
825 tristate "W83697UG/W83697UF Watchdog Timer"
828 This is the driver for the hardware watchdog on the W83697UG/UF
829 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
830 This watchdog simply watches your kernel to make sure it doesn't
831 freeze, and if it does, it reboots your computer after a certain
834 To compile this driver as a module, choose M here: the
835 module will be called w83697ug_wdt.
837 Most people will say N.
840 tristate "W83877F (EMACS) Watchdog Timer"
843 This is the driver for the hardware watchdog on the W83877F chipset
844 as used in EMACS PC-104 motherboards (and likely others). This
845 watchdog simply watches your kernel to make sure it doesn't freeze,
846 and if it does, it reboots your computer after a certain amount of
849 To compile this driver as a module, choose M here: the
850 module will be called w83877f_wdt.
852 Most people will say N.
855 tristate "W83977F (PCM-5335) Watchdog Timer"
858 This is the driver for the hardware watchdog on the W83977F I/O chip
859 as used in AAEON's PCM-5335 SBC (and likely others). This
860 watchdog simply watches your kernel to make sure it doesn't freeze,
861 and if it does, it reboots your computer after a certain amount of
864 To compile this driver as a module, choose M here: the
865 module will be called w83977f_wdt.
868 tristate "ZF MachZ Watchdog"
871 If you are using a ZF Micro MachZ processor, say Y here, otherwise
872 N. This is the driver for the watchdog timer built-in on that
873 processor using ZF-Logic interface. This watchdog simply watches
874 your kernel to make sure it doesn't freeze, and if it does, it
875 reboots your computer after a certain amount of time.
877 To compile this driver as a module, choose M here: the
878 module will be called machzwd.
880 config SBC_EPX_C3_WATCHDOG
881 tristate "Winsystems SBC EPX-C3 watchdog"
884 This is the driver for the built-in watchdog timer on the EPX-C3
885 Single-board computer made by Winsystems, Inc.
887 *Note*: This hardware watchdog is not probeable and thus there
888 is no way to know if writing to its IO address will corrupt
889 your system or have any real effect. The only way to be sure
890 that this driver does what you want is to make sure you
891 are running it on an EPX-C3 from Winsystems with the watchdog
892 timer at IO address 0x1ee and 0x1ef. It will write to both those
893 IO ports. Basically, the assumption is made that if you compile
894 this driver into your kernel and/or load it as a module, that you
895 know what you are doing and that you are in fact running on an
898 To compile this driver as a module, choose M here: the
899 module will be called sbc_epx_c3.
905 config M54xx_WATCHDOG
906 tristate "MCF54xx watchdog support"
909 To compile this driver as a module, choose M here: the
910 module will be called m54xx_wdt.
912 # MicroBlaze Architecture
914 config XILINX_WATCHDOG
915 tristate "Xilinx Watchdog timer"
916 depends on MICROBLAZE
918 Watchdog driver for the xps_timebase_wdt ip core.
920 IMPORTANT: The xps_timebase_wdt parent must have the property
921 "clock-frequency" at device tree.
923 To compile this driver as a module, choose M here: the
924 module will be called of_xilinx_wdt.
929 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
932 Hardware driver for the built-in watchdog timer on the Atheros
933 AR71XX/AR724X/AR913X SoCs.
936 tristate "Broadcom BCM47xx Watchdog Timer"
939 Hardware driver for the Broadcom BCM47xx Watchog Timer.
942 tristate "IDT RC32434 SoC Watchdog Timer"
943 depends on MIKROTIK_RB532
945 Hardware driver for the IDT RC32434 SoC built-in
948 To compile this driver as a module, choose M here: the
949 module will be called rc32434_wdt.
952 tristate "Indy/I2 Hardware Watchdog"
953 depends on SGI_HAS_INDYDOG
955 Hardware driver for the Indy's/I2's watchdog. This is a
956 watchdog timer that will reboot the machine after a 60 second
957 timer expired and no process has written to /dev/watchdog during
961 tristate "Ingenic jz4740 SoC hardware watchdog"
962 depends on MACH_JZ4740
965 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
968 tristate "MTX-1 Hardware Watchdog"
971 Hardware driver for the MTX-1 boards. This is a watchdog timer that
972 will reboot the machine after a 100 seconds timer expired.
975 tristate "PNX833x Hardware Watchdog"
976 depends on SOC_PNX8335
978 Hardware driver for the PNX833x's watchdog. This is a
979 watchdog timer that will reboot the machine after a programmable
980 timer has expired and no process has written to /dev/watchdog during
984 tristate "Sibyte SoC hardware watchdog"
987 Watchdog driver for the built in watchdog hardware in Sibyte
988 SoC processors. There are apparently two watchdog timers
989 on such processors; this driver supports only the first one,
990 because currently Linux only supports exporting one watchdog
993 To compile this driver as a loadable module, choose M here.
994 The module will be called sb_wdog.
997 tristate "TI AR7 Watchdog Timer"
1000 Hardware driver for the TI AR7 Watchdog Timer.
1003 tristate "Toshiba TXx9 Watchdog Timer"
1004 depends on CPU_TX39XX || CPU_TX49XX
1006 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1009 tristate "Cavium OCTEON SOC family Watchdog Timer"
1010 depends on CPU_CAVIUM_OCTEON
1012 select EXPORT_UASM if OCTEON_WDT = m
1014 Hardware driver for OCTEON's on chip watchdog timer.
1015 Enables the watchdog for all cores running Linux. It
1016 installs a NMI handler and pokes the watchdog based on an
1017 interrupt. On first expiration of the watchdog, the
1018 interrupt handler pokes it. The second expiration causes an
1019 NMI that prints a message. The third expiration causes a
1022 When userspace has /dev/watchdog open, no poking is done
1023 from the first interrupt, it is then only poked when the
1027 tristate "Broadcom BCM63xx hardware watchdog"
1030 Watchdog driver for the built in watchdog hardware in Broadcom
1033 To compile this driver as a loadable module, choose M here.
1034 The module will be called bcm63xx_wdt.
1037 tristate "Lantiq SoC watchdog"
1040 Hardware driver for the Lantiq SoC Watchdog Timer.
1042 # PARISC Architecture
1044 # POWERPC Architecture
1047 tristate "GE Watchdog Timer"
1050 Watchdog timer found in a number of GE single board computers.
1053 bool "MPC52xx Watchdog Timer"
1054 depends on PPC_MPC52xx
1056 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1059 tristate "MPC8xxx Platform Watchdog Timer"
1060 depends on PPC_8xx || PPC_83xx || PPC_86xx
1062 This driver is for a SoC level watchdog that exists on some
1063 Freescale PowerPC processors. So far this driver supports:
1068 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1071 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1075 tristate "PIKA FPGA Watchdog"
1079 This enables the watchdog in the PIKA FPGA. Currently used on
1083 tristate "PowerPC Book-E Watchdog Timer"
1084 depends on BOOKE || 4xx
1086 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1087 MPC85xx SOCs and the IBM PowerPC 440.
1089 Please see Documentation/watchdog/watchdog-api.txt for
1092 config BOOKE_WDT_DEFAULT_TIMEOUT
1093 int "PowerPC Book-E Watchdog Timer Default Timeout"
1094 depends on BOOKE_WDT
1095 default 38 if FSL_BOOKE
1096 range 0 63 if FSL_BOOKE
1097 default 3 if !FSL_BOOKE
1098 range 0 3 if !FSL_BOOKE
1100 Select the default watchdog timer period to be used by the PowerPC
1101 Book-E watchdog driver. A watchdog "event" occurs when the bit
1102 position represented by this number transitions from zero to one.
1104 For Freescale Book-E processors, this is a number between 0 and 63.
1105 For other Book-E processors, this is a number between 0 and 3.
1107 The value can be overridden by the wdt_period command-line parameter.
1109 # PPC64 Architecture
1111 config WATCHDOG_RTAS
1112 tristate "RTAS watchdog"
1115 This driver adds watchdog support for the RTAS watchdog.
1117 To compile this driver as a module, choose M here. The module
1118 will be called wdrtas.
1123 tristate "z/VM Watchdog Timer"
1126 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1127 provide a virtual watchdog timer to their guest that cause a
1128 user define Control Program command to be executed after a
1131 To compile this driver as a module, choose M here. The module
1132 will be called vmwatchdog.
1134 # SUPERH (sh + sh64) Architecture
1137 tristate "SuperH Watchdog"
1138 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1140 This driver adds watchdog support for the integrated watchdog in the
1141 SuperH processors. If you have one of these processors and wish
1142 to have watchdog support enabled, say Y, otherwise say N.
1144 As a side note, saying Y here will automatically boost HZ to 1000
1145 so that the timer has a chance to clear the overflow counter. On
1146 slower systems (such as the SH-2 and SH-3) this will likely yield
1147 some performance issues. As such, the WDT should be avoided here
1148 unless it is absolutely necessary.
1150 To compile this driver as a module, choose M here: the
1151 module will be called shwdt.
1153 # SPARC Architecture
1155 # SPARC64 Architecture
1157 config WATCHDOG_CP1XXX
1158 tristate "CP1XXX Hardware Watchdog support"
1159 depends on SPARC64 && PCI
1161 This is the driver for the hardware watchdog timers present on
1162 Sun Microsystems CompactPCI models CP1400 and CP1500.
1164 To compile this driver as a module, choose M here: the
1165 module will be called cpwatchdog.
1167 If you do not have a CompactPCI model CP1400 or CP1500, or
1168 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1169 you should say N to this option.
1172 tristate "RIO Hardware Watchdog support"
1173 depends on SPARC64 && PCI
1175 Say Y here to support the hardware watchdog capability on Sun RIO
1176 machines. The watchdog timeout period is normally one minute but
1177 can be changed with a boot-time parameter.
1179 # XTENSA Architecture
1184 tristate "Xen Watchdog support"
1187 Say Y here to support the hypervisor watchdog capability provided
1188 by Xen 4.0 and newer. The watchdog timeout period is normally one
1189 minute but can be changed with a boot-time parameter.
1192 tristate "UML watchdog"
1196 # ISA-based Watchdog Cards
1199 comment "ISA-based Watchdog Cards"
1203 tristate "Berkshire Products ISA-PC Watchdog"
1206 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1207 This card simply watches your kernel to make sure it doesn't freeze,
1208 and if it does, it reboots your computer after a certain amount of
1209 time. This driver is like the WDT501 driver but for different
1210 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1211 watchdog cards can be ordered from <http://www.berkprod.com/>.
1213 To compile this driver as a module, choose M here: the
1214 module will be called pcwd.
1216 Most people will say N.
1219 tristate "Mixcom Watchdog"
1222 This is a driver for the Mixcom hardware watchdog cards. This
1223 watchdog simply watches your kernel to make sure it doesn't freeze,
1224 and if it does, it reboots your computer after a certain amount of
1227 To compile this driver as a module, choose M here: the
1228 module will be called mixcomwd.
1230 Most people will say N.
1233 tristate "WDT Watchdog timer"
1236 If you have a WDT500P or WDT501P watchdog board, say Y here,
1237 otherwise N. It is not possible to probe for this board, which means
1238 that you have to inform the kernel about the IO port and IRQ that
1239 is needed (you can do this via the io and irq parameters)
1241 To compile this driver as a module, choose M here: the
1242 module will be called wdt.
1245 # PCI-based Watchdog Cards
1248 comment "PCI-based Watchdog Cards"
1251 config PCIPCWATCHDOG
1252 tristate "Berkshire Products PCI-PC Watchdog"
1255 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1256 This card simply watches your kernel to make sure it doesn't freeze,
1257 and if it does, it reboots your computer after a certain amount of
1258 time. The card can also monitor the internal temperature of the PC.
1259 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1261 To compile this driver as a module, choose M here: the
1262 module will be called pcwd_pci.
1264 Most people will say N.
1267 tristate "PCI-WDT500/501 Watchdog timer"
1270 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1272 If you have a PCI-WDT501 watchdog board then you can enable the
1273 temperature sensor by setting the type parameter to 501.
1275 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1276 can do this via the tachometer parameter. Only do this if you have a
1277 fan tachometer actually set up.
1279 To compile this driver as a module, choose M here: the
1280 module will be called wdt_pci.
1283 # USB-based Watchdog Cards
1286 comment "USB-based Watchdog Cards"
1289 config USBPCWATCHDOG
1290 tristate "Berkshire Products USB-PC Watchdog"
1293 This is the driver for the Berkshire Products USB-PC Watchdog card.
1294 This card simply watches your kernel to make sure it doesn't freeze,
1295 and if it does, it reboots your computer after a certain amount of
1296 time. The card can also monitor the internal temperature of the PC.
1297 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1299 To compile this driver as a module, choose M here: the
1300 module will be called pcwd_usb.
1302 Most people will say N.