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 DA9052_WATCHDOG
68 tristate "Dialog DA9052 Watchdog"
69 depends on PMIC_DA9052
72 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
75 Say Y here to include support for the DA9052 watchdog.
76 Alternatively say M to compile the driver as a module,
77 which will be called da9052_wdt.
79 config WM831X_WATCHDOG
80 tristate "WM831x watchdog"
84 Support for the watchdog in the WM831x AudioPlus PMICs. When
85 the watchdog triggers the system will be reset.
87 config WM8350_WATCHDOG
88 tristate "WM8350 watchdog"
92 Support for the watchdog in the WM8350 AudioPlus PMIC. When
93 the watchdog triggers the system will be reset.
99 config ARM_SP805_WATCHDOG
100 tristate "ARM SP805 Watchdog"
104 ARM Primecell SP805 Watchdog timer. This will reboot your system when
105 the timeout is reached.
107 config AT91RM9200_WATCHDOG
108 tristate "AT91RM9200 watchdog"
109 depends on ARCH_AT91RM9200
111 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
112 system when the timeout is reached.
114 config AT91SAM9X_WATCHDOG
115 tristate "AT91SAM9X / AT91CAP9 watchdog"
116 depends on ARCH_AT91 && !ARCH_AT91RM9200
118 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
119 reboot your system when the timeout is reached.
121 config 21285_WATCHDOG
122 tristate "DC21285 watchdog"
123 depends on FOOTBRIDGE
125 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
126 here if you wish to use this. Alternatively say M to compile the
127 driver as a module, which will be called wdt285.
129 This driver does not work on all machines. In particular, early CATS
130 boards have hardware problems that will cause the machine to simply
131 lock up if the watchdog fires.
133 "If in doubt, leave it out" - say N.
136 tristate "NetWinder WB83C977 watchdog"
137 depends on FOOTBRIDGE && ARCH_NETWINDER
139 Say Y here to include support for the WB977 watchdog included in
140 NetWinder machines. Alternatively say M to compile the driver as
141 a module, which will be called wdt977.
143 Not sure? It's safe to say N.
145 config IXP4XX_WATCHDOG
146 tristate "IXP4xx Watchdog"
147 depends on ARCH_IXP4XX
149 Say Y here if to include support for the watchdog timer
150 in the Intel IXP4xx network processors. This driver can
151 be built as a module by choosing M. The module will
152 be called ixp4xx_wdt.
154 Note: The internal IXP4xx watchdog does a soft CPU reset
155 which doesn't reset any peripherals. There are circumstances
156 where the watchdog will fail to reset the board correctly
157 (e.g., if the boot ROM is in an unreadable state).
159 Say N if you are unsure.
161 config KS8695_WATCHDOG
162 tristate "KS8695 watchdog"
163 depends on ARCH_KS8695
165 Watchdog timer embedded into KS8695 processor. This will reboot your
166 system when the timeout is reached.
168 config HAVE_S3C2410_WATCHDOG
171 This will include watchdog timer support for Samsung SoCs. If
172 you want to include watchdog support for any machine, kindly
173 select this in the respective mach-XXXX/Kconfig file.
175 config S3C2410_WATCHDOG
176 tristate "S3C2410 Watchdog"
177 depends on HAVE_S3C2410_WATCHDOG
180 Watchdog timer block in the Samsung SoCs. This will reboot
181 the system when the timer expires with the watchdog enabled.
183 The driver is limited by the speed of the system's PCLK
184 signal, so with reasonably fast systems (PCLK around 50-66MHz)
185 then watchdog intervals of over approximately 20seconds are
188 The driver can be built as a module by choosing M, and will
189 be called s3c2410_wdt
191 config SA1100_WATCHDOG
192 tristate "SA1100/PXA2xx watchdog"
193 depends on ARCH_SA1100 || ARCH_PXA
195 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
196 reboot your system when timeout is reached.
198 NOTE: once enabled, this timer cannot be disabled.
200 To compile this driver as a module, choose M here: the
201 module will be called sa1100_wdt.
204 tristate "Synopsys DesignWare watchdog"
205 depends on ARM && HAVE_CLK
207 Say Y here if to include support for the Synopsys DesignWare
208 watchdog timer found in many ARM chips.
209 To compile this driver as a module, choose M here: the
210 module will be called dw_wdt.
212 config MPCORE_WATCHDOG
213 tristate "MPcore watchdog"
214 depends on HAVE_ARM_TWD
216 Watchdog timer embedded into the MPcore system.
218 To compile this driver as a module, choose M here: the
219 module will be called mpcore_wdt.
221 config EP93XX_WATCHDOG
222 tristate "EP93xx Watchdog"
223 depends on ARCH_EP93XX
226 Say Y here if to include support for the watchdog timer
227 embedded in the Cirrus Logic EP93xx family of devices.
229 To compile this driver as a module, choose M here: the
230 module will be called ep93xx_wdt.
233 tristate "OMAP Watchdog"
234 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
236 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
237 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
239 config PNX4008_WATCHDOG
240 tristate "PNX4008 and LPC32XX Watchdog"
241 depends on ARCH_PNX4008 || ARCH_LPC32XX
244 Say Y here if to include support for the watchdog timer
245 in the PNX4008 or LPC32XX processor.
246 This driver can be built as a module by choosing M. The module
247 will be called pnx4008_wdt.
249 Say N if you are unsure.
252 tristate "IOP Watchdog"
254 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
256 Say Y here if to include support for the watchdog timer
257 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
258 be built as a module by choosing M. The module will
261 Note: The IOP13XX watchdog does an Internal Bus Reset which will
262 affect both cores and the peripherals of the IOP. The ATU-X
263 and/or ATUe configuration registers will remain intact, but if
264 operating as an Root Complex and/or Central Resource, the PCI-X
265 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
267 config DAVINCI_WATCHDOG
268 tristate "DaVinci watchdog"
269 depends on ARCH_DAVINCI
271 Say Y here if to include support for the watchdog timer
272 in the DaVinci DM644x/DM646x processors.
273 To compile this driver as a module, choose M here: the
274 module will be called davinci_wdt.
276 NOTE: once enabled, this timer cannot be disabled.
277 Say N if you are unsure.
279 config ORION_WATCHDOG
280 tristate "Orion watchdog"
281 depends on ARCH_ORION5X || ARCH_KIRKWOOD
284 Say Y here if to include support for the watchdog timer
285 in the Marvell Orion5x and Kirkwood ARM SoCs.
286 To compile this driver as a module, choose M here: the
287 module will be called orion_wdt.
289 config COH901327_WATCHDOG
290 bool "ST-Ericsson COH 901 327 watchdog"
292 default y if MACH_U300
295 Say Y here to include Watchdog timer support for the
296 watchdog embedded into the ST-Ericsson U300 series platforms.
297 This watchdog is used to reset the system and thus cannot be
298 compiled as a module.
300 config TWL4030_WATCHDOG
301 tristate "TWL4030 Watchdog"
302 depends on TWL4030_CORE
304 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
305 watchdog timer support for TWL4030 chips.
307 config STMP3XXX_WATCHDOG
308 tristate "Freescale STMP3XXX watchdog"
309 depends on ARCH_STMP3XXX
311 Say Y here if to include support for the watchdog timer
312 for the Sigmatel STMP37XX/378X SoC.
313 To compile this driver as a module, choose M here: the
314 module will be called stmp3xxx_wdt.
316 config NUC900_WATCHDOG
317 tristate "Nuvoton NUC900 watchdog"
318 depends on ARCH_W90X900
320 Say Y here if to include support for the watchdog timer
321 for the Nuvoton NUC900 series SoCs.
322 To compile this driver as a module, choose M here: the
323 module will be called nuc900_wdt.
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
341 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
344 tristate "IMX2+ Watchdog"
345 depends on IMX_HAVE_PLATFORM_IMX2_WDT
347 This is the driver for the hardware watchdog
348 on the Freescale IMX2 and later processors.
349 If you have one of these processors and wish to have
350 watchdog support enabled, say Y, otherwise say N.
352 To compile this driver as a module, choose M here: the
353 module will be called imx2_wdt.
357 config AT32AP700X_WDT
358 tristate "AT32AP700x watchdog"
359 depends on CPU_AT32AP700X
361 Watchdog timer embedded into AT32AP700x devices. This will reboot
362 your system when the timeout is reached.
364 # BLACKFIN Architecture
367 tristate "Blackfin On-Chip Watchdog Timer"
370 If you say yes here you will get support for the Blackfin On-Chip
371 Watchdog Timer. If you have one of these processors and wish to
372 have watchdog support enabled, say Y, otherwise say N.
374 To compile this driver as a module, choose M here: the
375 module will be called bfin_wdt.
383 # X86 (i386 + ia64 + x86_64) Architecture
386 tristate "Acquire SBC Watchdog Timer"
389 This is the driver for the hardware watchdog on Single Board
390 Computers produced by Acquire Inc (and others). This watchdog
391 simply watches your kernel to make sure it doesn't freeze, and if
392 it does, it reboots your computer after a certain amount of time.
394 To compile this driver as a module, choose M here: the
395 module will be called acquirewdt.
397 Most people will say N.
400 tristate "Advantech SBC Watchdog Timer"
403 If you are configuring a Linux kernel for the Advantech single-board
404 computer, say `Y' here to support its built-in watchdog timer
405 feature. More information can be found at
406 <http://www.advantech.com.tw/products/>
409 tristate "ALi M1535 PMU Watchdog Timer"
410 depends on X86 && PCI
412 This is the driver for the hardware watchdog on the ALi M1535 PMU.
414 To compile this driver as a module, choose M here: the
415 module will be called alim1535_wdt.
417 Most people will say N.
420 tristate "ALi M7101 PMU Computer Watchdog"
423 This is the driver for the hardware watchdog on the ALi M7101 PMU
424 as used in the x86 Cobalt servers and also found in some
425 SPARC Netra servers too.
427 To compile this driver as a module, choose M here: the
428 module will be called alim7101_wdt.
430 Most people will say N.
433 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
434 depends on X86 && EXPERIMENTAL
436 This is the driver for the hardware watchdog on the Fintek
437 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
439 You can compile this driver directly into the kernel, or use
440 it as a module. The module will be called f71808e_wdt.
443 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
444 depends on X86 && PCI
446 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
447 (Total Cost of Ownership) timer is a watchdog timer that will reboot
448 the machine after its expiration. The expiration time can be
449 configured with the "heartbeat" parameter.
451 To compile this driver as a module, choose M here: the
452 module will be called sp5100_tco.
455 tristate "AMD Geode CS5535/CS5536 Watchdog"
456 depends on CS5535_MFGPT
458 This driver enables a watchdog capability built into the
459 CS5535/CS5536 companion chips for the AMD Geode GX and LX
460 processors. This watchdog watches your kernel to make sure
461 it doesn't freeze, and if it does, it reboots your computer after
462 a certain amount of time.
464 You can compile this driver directly into the kernel, or use
465 it as a module. The module will be called geodewdt.
468 tristate "AMD Elan SC520 processor Watchdog"
471 This is the driver for the hardware watchdog built in to the
472 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
473 This watchdog simply watches your kernel to make sure it doesn't
474 freeze, and if it does, it reboots your computer after a certain
477 You can compile this driver directly into the kernel, or use
478 it as a module. The module will be called sc520_wdt.
480 config SBC_FITPC2_WATCHDOG
481 tristate "Compulab SBC-FITPC2 watchdog"
484 This is the driver for the built-in watchdog timer on the fit-PC2,
485 fit-PC2i, CM-iAM single-board computers made by Compulab.
487 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
488 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
490 Entering BIOS setup temporary disables watchdog operation regardless to current state,
491 so system will not be restarted while user in BIOS setup.
493 Once watchdog was enabled the system will be restarted every
494 "Watchdog Timer Value" period, so to prevent it user can restart or
495 disable the watchdog.
497 To compile this driver as a module, choose M here: the
498 module will be called sbc_fitpc2_wdt.
500 Most people will say N.
503 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
506 Enable support for the watchdog timer on the Eurotech CPU-1220 and
507 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
508 information are at <http://www.eurotech.it/>.
511 tristate "IB700 SBC Watchdog Timer"
514 This is the driver for the hardware watchdog on the IB700 Single
515 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
516 simply watches your kernel to make sure it doesn't freeze, and if
517 it does, it reboots your computer after a certain amount of time.
519 This driver is like the WDT501 driver but for slightly different hardware.
521 To compile this driver as a module, choose M here: the
522 module will be called ib700wdt.
524 Most people will say N.
527 tristate "IBM Automatic Server Restart"
530 This is the driver for the IBM Automatic Server Restart watchdog
531 timer built-in into some eServer xSeries machines.
533 To compile this driver as a module, choose M here: the
534 module will be called ibmasr.
537 tristate "ICP Single Board Computer Watchdog Timer"
540 This is a driver for the hardware watchdog on the ICP Single
541 Board Computer. This driver is working on (at least) the following
542 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
544 To compile this driver as a module, choose M here: the
545 module will be called wafer5823wdt.
548 tristate "Intel 6300ESB Timer/Watchdog"
551 Hardware driver for the watchdog timer built into the Intel
552 6300ESB controller hub.
554 To compile this driver as a module, choose M here: the
555 module will be called i6300esb.
558 tristate "Intel Atom E6xx Watchdog"
559 depends on X86 && PCI
564 Hardware driver for the watchdog timer built into the Intel
565 Atom E6XX (TunnelCreek) processor.
567 To compile this driver as a module, choose M here: the
568 module will be called ie6xx_wdt.
570 config INTEL_SCU_WATCHDOG
571 bool "Intel SCU Watchdog for Mobile Platforms"
574 Hardware driver for the watchdog time built into the Intel SCU
575 for Intel Mobile Platforms.
577 To compile this driver as a module, choose M here.
580 tristate "Intel TCO Timer/Watchdog"
581 depends on (X86 || IA64) && PCI
585 Hardware driver for the intel TCO timer based watchdog devices.
586 These drivers are included in the Intel 82801 I/O Controller
587 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
590 The TCO (Total Cost of Ownership) timer is a watchdog timer
591 that will reboot the machine after its second expiration. The
592 expiration time can be configured with the "heartbeat" parameter.
594 On some motherboards the driver may fail to reset the chipset's
595 NO_REBOOT flag which prevents the watchdog from rebooting the
596 machine. If this is the case you will get a kernel message like
597 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
599 To compile this driver as a module, choose M here: the
600 module will be called iTCO_wdt.
602 config ITCO_VENDOR_SUPPORT
603 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
606 Add vendor specific support to the intel TCO timer based watchdog
607 devices. At this moment we only have additional support for some
608 SuperMicro Inc. motherboards.
611 tristate "IT8712F (Smart Guardian) Watchdog Timer"
614 This is the driver for the built-in watchdog timer on the IT8712F
615 Super I/0 chipset used on many motherboards.
617 If the driver does not work, then make sure that the game port in
620 To compile this driver as a module, choose M here: the
621 module will be called it8712f_wdt.
624 tristate "IT87 Watchdog Timer"
625 depends on X86 && EXPERIMENTAL
627 This is the driver for the hardware watchdog on the ITE IT8702,
628 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
631 If the driver does not work, then make sure that the game port in
634 This watchdog simply watches your kernel to make sure it doesn't
635 freeze, and if it does, it reboots your computer after a certain
638 To compile this driver as a module, choose M here: the module will
642 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
643 depends on X86 && PCI
645 A software monitoring watchdog and NMI sourcing driver. This driver
646 will detect lockups and provide a stack trace. This is a driver that
647 will only load on an HP ProLiant system with a minimum of iLO2 support.
648 To compile this driver as a module, choose M here: the module will be
651 config HPWDT_NMI_DECODING
652 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
653 depends on HP_WATCHDOG
656 When an NMI occurs this feature will make the necessary BIOS calls to
657 log the cause of the NMI.
660 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
663 This is a driver for National Semiconductor PC87307/PC97307 hardware
664 watchdog cards as found on the SC1200. This watchdog is mainly used
665 for power management purposes and can be used to power down the device
666 during inactivity periods (includes interrupt activity monitoring).
668 To compile this driver as a module, choose M here: the
669 module will be called sc1200wdt.
671 Most people will say N.
674 tristate "National Semiconductor SCx200 Watchdog"
675 depends on SCx200 && PCI
677 Enable the built-in watchdog timer support on the National
678 Semiconductor SCx200 processors.
680 If compiled as a module, it will be called scx200_wdt.
683 tristate "NS PC87413 watchdog"
686 This is the driver for the hardware watchdog on the PC87413 chipset
687 This watchdog simply watches your kernel to make sure it doesn't
688 freeze, and if it does, it reboots your computer after a certain
691 To compile this driver as a module, choose M here: the
692 module will be called pc87413_wdt.
694 Most people will say N.
697 tristate "nVidia TCO Timer/Watchdog"
698 depends on X86 && PCI
700 Hardware driver for the TCO timer built into the nVidia Hub family
701 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
702 watchdog timer that will reboot the machine after its second
703 expiration. The expiration time can be configured with the
704 "heartbeat" parameter.
706 On some motherboards the driver may fail to reset the chipset's
707 NO_REBOOT flag which prevents the watchdog from rebooting the
708 machine. If this is the case you will get a kernel message like
709 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
711 To compile this driver as a module, choose M here: the
712 module will be called nv_tco.
715 tristate "RDC R-321x SoC watchdog"
716 depends on X86_RDC321X
718 This is the driver for the built in hardware watchdog
719 in the RDC R-321x SoC.
721 To compile this driver as a module, choose M here: the
722 module will be called rdc321x_wdt.
725 tristate "SBC-60XX Watchdog Timer"
728 This driver can be used with the watchdog timer found on some
729 single board computers, namely the 6010 PII based computer.
730 It may well work with other cards. It reads port 0x443 to enable
731 and re-set the watchdog timer, and reads port 0x45 to disable
732 the watchdog. If you have a card that behave in similar ways,
733 you can probably make this driver work with your card as well.
735 You can compile this driver directly into the kernel, or use
736 it as a module. The module will be called sbc60xxwdt.
739 tristate "SBC8360 Watchdog Timer"
743 This is the driver for the hardware watchdog on the SBC8360 Single
744 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
746 To compile this driver as a module, choose M here: the
747 module will be called sbc8360.
749 Most people will say N.
752 tristate "SBC Nano 7240 Watchdog Timer"
753 depends on X86_32 && !UML
755 This is the driver for the hardware watchdog found on the IEI
756 single board computers EPIC Nano 7240 (and likely others). This
757 watchdog simply watches your kernel to make sure it doesn't freeze,
758 and if it does, it reboots your computer after a certain amount of
761 To compile this driver as a module, choose M here: the
762 module will be called sbc7240_wdt.
765 tristate "SMA CPU5 Watchdog"
769 To compile this driver as a module, choose M here: the
770 module will be called cpu5wdt.
772 config SMSC_SCH311X_WDT
773 tristate "SMSC SCH311X Watchdog Timer"
776 This is the driver for the hardware watchdog timer on the
777 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
778 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
781 To compile this driver as a module, choose M here: the
782 module will be called sch311x_wdt.
784 config SMSC37B787_WDT
785 tristate "Winbond SMsC37B787 Watchdog Timer"
788 This is the driver for the hardware watchdog component on the
789 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
790 from Vision Systems and maybe others.
792 This watchdog simply watches your kernel to make sure it doesn't
793 freeze, and if it does, it reboots your computer after a certain
796 Usually a userspace daemon will notify the kernel WDT driver that
797 userspace is still alive, at regular intervals.
799 To compile this driver as a module, choose M here: the
800 module will be called smsc37b787_wdt.
802 Most people will say N.
805 tristate "VIA Watchdog Timer"
806 depends on X86 && PCI
809 This is the driver for the hardware watchdog timer on VIA
810 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
812 To compile this driver as a module, choose M here; the module
813 will be called via_wdt.
815 Most people will say N.
818 tristate "W83627HF/W83627DHG Watchdog Timer"
821 This is the driver for the hardware watchdog on the W83627HF chipset
822 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
823 (and likely others). The driver also supports the W83627DHG chip.
824 This watchdog simply watches your kernel to make sure it doesn't
825 freeze, and if it does, it reboots your computer after a certain
828 To compile this driver as a module, choose M here: the
829 module will be called w83627hf_wdt.
831 Most people will say N.
834 tristate "W83697HF/W83697HG Watchdog Timer"
837 This is the driver for the hardware watchdog on the W83697HF/HG
838 chipset as used in Dedibox/VIA motherboards (and likely others).
839 This watchdog simply watches your kernel to make sure it doesn't
840 freeze, and if it does, it reboots your computer after a certain
843 To compile this driver as a module, choose M here: the
844 module will be called w83697hf_wdt.
846 Most people will say N.
849 tristate "W83697UG/W83697UF Watchdog Timer"
852 This is the driver for the hardware watchdog on the W83697UG/UF
853 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
854 This watchdog simply watches your kernel to make sure it doesn't
855 freeze, and if it does, it reboots your computer after a certain
858 To compile this driver as a module, choose M here: the
859 module will be called w83697ug_wdt.
861 Most people will say N.
864 tristate "W83877F (EMACS) Watchdog Timer"
867 This is the driver for the hardware watchdog on the W83877F chipset
868 as used in EMACS PC-104 motherboards (and likely others). This
869 watchdog simply watches your kernel to make sure it doesn't freeze,
870 and if it does, it reboots your computer after a certain amount of
873 To compile this driver as a module, choose M here: the
874 module will be called w83877f_wdt.
876 Most people will say N.
879 tristate "W83977F (PCM-5335) Watchdog Timer"
882 This is the driver for the hardware watchdog on the W83977F I/O chip
883 as used in AAEON's PCM-5335 SBC (and likely others). This
884 watchdog simply watches your kernel to make sure it doesn't freeze,
885 and if it does, it reboots your computer after a certain amount of
888 To compile this driver as a module, choose M here: the
889 module will be called w83977f_wdt.
892 tristate "ZF MachZ Watchdog"
895 If you are using a ZF Micro MachZ processor, say Y here, otherwise
896 N. This is the driver for the watchdog timer built-in on that
897 processor using ZF-Logic interface. This watchdog simply watches
898 your kernel to make sure it doesn't freeze, and if it does, it
899 reboots your computer after a certain amount of time.
901 To compile this driver as a module, choose M here: the
902 module will be called machzwd.
904 config SBC_EPX_C3_WATCHDOG
905 tristate "Winsystems SBC EPX-C3 watchdog"
908 This is the driver for the built-in watchdog timer on the EPX-C3
909 Single-board computer made by Winsystems, Inc.
911 *Note*: This hardware watchdog is not probeable and thus there
912 is no way to know if writing to its IO address will corrupt
913 your system or have any real effect. The only way to be sure
914 that this driver does what you want is to make sure you
915 are running it on an EPX-C3 from Winsystems with the watchdog
916 timer at IO address 0x1ee and 0x1ef. It will write to both those
917 IO ports. Basically, the assumption is made that if you compile
918 this driver into your kernel and/or load it as a module, that you
919 know what you are doing and that you are in fact running on an
922 To compile this driver as a module, choose M here: the
923 module will be called sbc_epx_c3.
929 config M54xx_WATCHDOG
930 tristate "MCF54xx watchdog support"
933 To compile this driver as a module, choose M here: the
934 module will be called m54xx_wdt.
936 # MicroBlaze Architecture
938 config XILINX_WATCHDOG
939 tristate "Xilinx Watchdog timer"
940 depends on MICROBLAZE
942 Watchdog driver for the xps_timebase_wdt ip core.
944 IMPORTANT: The xps_timebase_wdt parent must have the property
945 "clock-frequency" at device tree.
947 To compile this driver as a module, choose M here: the
948 module will be called of_xilinx_wdt.
953 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
956 Hardware driver for the built-in watchdog timer on the Atheros
957 AR71XX/AR724X/AR913X SoCs.
960 tristate "Broadcom BCM47xx Watchdog Timer"
963 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
966 tristate "IDT RC32434 SoC Watchdog Timer"
967 depends on MIKROTIK_RB532
969 Hardware driver for the IDT RC32434 SoC built-in
972 To compile this driver as a module, choose M here: the
973 module will be called rc32434_wdt.
976 tristate "Indy/I2 Hardware Watchdog"
977 depends on SGI_HAS_INDYDOG
979 Hardware driver for the Indy's/I2's watchdog. This is a
980 watchdog timer that will reboot the machine after a 60 second
981 timer expired and no process has written to /dev/watchdog during
985 tristate "Ingenic jz4740 SoC hardware watchdog"
986 depends on MACH_JZ4740
989 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
992 tristate "MTX-1 Hardware Watchdog"
995 Hardware driver for the MTX-1 boards. This is a watchdog timer that
996 will reboot the machine after a 100 seconds timer expired.
999 tristate "PNX833x Hardware Watchdog"
1000 depends on SOC_PNX8335
1002 Hardware driver for the PNX833x's watchdog. This is a
1003 watchdog timer that will reboot the machine after a programmable
1004 timer has expired and no process has written to /dev/watchdog during
1008 tristate "Sibyte SoC hardware watchdog"
1011 Watchdog driver for the built in watchdog hardware in Sibyte
1012 SoC processors. There are apparently two watchdog timers
1013 on such processors; this driver supports only the first one,
1014 because currently Linux only supports exporting one watchdog
1017 To compile this driver as a loadable module, choose M here.
1018 The module will be called sb_wdog.
1021 tristate "TI AR7 Watchdog Timer"
1024 Hardware driver for the TI AR7 Watchdog Timer.
1027 tristate "Toshiba TXx9 Watchdog Timer"
1028 depends on CPU_TX39XX || CPU_TX49XX
1029 select WATCHDOG_CORE
1031 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1034 tristate "Cavium OCTEON SOC family Watchdog Timer"
1035 depends on CPU_CAVIUM_OCTEON
1037 select EXPORT_UASM if OCTEON_WDT = m
1039 Hardware driver for OCTEON's on chip watchdog timer.
1040 Enables the watchdog for all cores running Linux. It
1041 installs a NMI handler and pokes the watchdog based on an
1042 interrupt. On first expiration of the watchdog, the
1043 interrupt handler pokes it. The second expiration causes an
1044 NMI that prints a message. The third expiration causes a
1047 When userspace has /dev/watchdog open, no poking is done
1048 from the first interrupt, it is then only poked when the
1052 tristate "Broadcom BCM63xx hardware watchdog"
1055 Watchdog driver for the built in watchdog hardware in Broadcom
1058 To compile this driver as a loadable module, choose M here.
1059 The module will be called bcm63xx_wdt.
1062 tristate "Lantiq SoC watchdog"
1065 Hardware driver for the Lantiq SoC Watchdog Timer.
1067 # PARISC Architecture
1069 # POWERPC Architecture
1072 tristate "GE Watchdog Timer"
1075 Watchdog timer found in a number of GE single board computers.
1078 bool "MPC52xx Watchdog Timer"
1079 depends on PPC_MPC52xx
1081 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1084 tristate "MPC8xxx Platform Watchdog Timer"
1085 depends on PPC_8xx || PPC_83xx || PPC_86xx
1087 This driver is for a SoC level watchdog that exists on some
1088 Freescale PowerPC processors. So far this driver supports:
1093 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1096 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1100 tristate "PIKA FPGA Watchdog"
1104 This enables the watchdog in the PIKA FPGA. Currently used on
1108 tristate "PowerPC Book-E Watchdog Timer"
1109 depends on BOOKE || 4xx
1111 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1112 MPC85xx SOCs and the IBM PowerPC 440.
1114 Please see Documentation/watchdog/watchdog-api.txt for
1117 config BOOKE_WDT_DEFAULT_TIMEOUT
1118 int "PowerPC Book-E Watchdog Timer Default Timeout"
1119 depends on BOOKE_WDT
1120 default 38 if PPC_FSL_BOOK3E
1121 range 0 63 if PPC_FSL_BOOK3E
1122 default 3 if !PPC_FSL_BOOK3E
1123 range 0 3 if !PPC_FSL_BOOK3E
1125 Select the default watchdog timer period to be used by the PowerPC
1126 Book-E watchdog driver. A watchdog "event" occurs when the bit
1127 position represented by this number transitions from zero to one.
1129 For Freescale Book-E processors, this is a number between 0 and 63.
1130 For other Book-E processors, this is a number between 0 and 3.
1132 The value can be overridden by the wdt_period command-line parameter.
1134 # PPC64 Architecture
1136 config WATCHDOG_RTAS
1137 tristate "RTAS watchdog"
1140 This driver adds watchdog support for the RTAS watchdog.
1142 To compile this driver as a module, choose M here. The module
1143 will be called wdrtas.
1148 tristate "z/VM Watchdog Timer"
1151 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1152 provide a virtual watchdog timer to their guest that cause a
1153 user define Control Program command to be executed after a
1156 To compile this driver as a module, choose M here. The module
1157 will be called vmwatchdog.
1159 # SUPERH (sh + sh64) Architecture
1162 tristate "SuperH Watchdog"
1163 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1164 select WATCHDOG_CORE
1166 This driver adds watchdog support for the integrated watchdog in the
1167 SuperH processors. If you have one of these processors and wish
1168 to have watchdog support enabled, say Y, otherwise say N.
1170 As a side note, saying Y here will automatically boost HZ to 1000
1171 so that the timer has a chance to clear the overflow counter. On
1172 slower systems (such as the SH-2 and SH-3) this will likely yield
1173 some performance issues. As such, the WDT should be avoided here
1174 unless it is absolutely necessary.
1176 To compile this driver as a module, choose M here: the
1177 module will be called shwdt.
1179 # SPARC Architecture
1181 # SPARC64 Architecture
1183 config WATCHDOG_CP1XXX
1184 tristate "CP1XXX Hardware Watchdog support"
1185 depends on SPARC64 && PCI
1187 This is the driver for the hardware watchdog timers present on
1188 Sun Microsystems CompactPCI models CP1400 and CP1500.
1190 To compile this driver as a module, choose M here: the
1191 module will be called cpwatchdog.
1193 If you do not have a CompactPCI model CP1400 or CP1500, or
1194 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1195 you should say N to this option.
1198 tristate "RIO Hardware Watchdog support"
1199 depends on SPARC64 && PCI
1201 Say Y here to support the hardware watchdog capability on Sun RIO
1202 machines. The watchdog timeout period is normally one minute but
1203 can be changed with a boot-time parameter.
1205 # XTENSA Architecture
1210 tristate "Xen Watchdog support"
1213 Say Y here to support the hypervisor watchdog capability provided
1214 by Xen 4.0 and newer. The watchdog timeout period is normally one
1215 minute but can be changed with a boot-time parameter.
1218 tristate "UML watchdog"
1222 # ISA-based Watchdog Cards
1225 comment "ISA-based Watchdog Cards"
1229 tristate "Berkshire Products ISA-PC Watchdog"
1232 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1233 This card simply watches your kernel to make sure it doesn't freeze,
1234 and if it does, it reboots your computer after a certain amount of
1235 time. This driver is like the WDT501 driver but for different
1236 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1237 watchdog cards can be ordered from <http://www.berkprod.com/>.
1239 To compile this driver as a module, choose M here: the
1240 module will be called pcwd.
1242 Most people will say N.
1245 tristate "Mixcom Watchdog"
1248 This is a driver for the Mixcom hardware watchdog cards. This
1249 watchdog simply watches your kernel to make sure it doesn't freeze,
1250 and if it does, it reboots your computer after a certain amount of
1253 To compile this driver as a module, choose M here: the
1254 module will be called mixcomwd.
1256 Most people will say N.
1259 tristate "WDT Watchdog timer"
1262 If you have a WDT500P or WDT501P watchdog board, say Y here,
1263 otherwise N. It is not possible to probe for this board, which means
1264 that you have to inform the kernel about the IO port and IRQ that
1265 is needed (you can do this via the io and irq parameters)
1267 To compile this driver as a module, choose M here: the
1268 module will be called wdt.
1271 # PCI-based Watchdog Cards
1274 comment "PCI-based Watchdog Cards"
1277 config PCIPCWATCHDOG
1278 tristate "Berkshire Products PCI-PC Watchdog"
1281 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1282 This card simply watches your kernel to make sure it doesn't freeze,
1283 and if it does, it reboots your computer after a certain amount of
1284 time. The card can also monitor the internal temperature of the PC.
1285 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1287 To compile this driver as a module, choose M here: the
1288 module will be called pcwd_pci.
1290 Most people will say N.
1293 tristate "PCI-WDT500/501 Watchdog timer"
1296 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1298 If you have a PCI-WDT501 watchdog board then you can enable the
1299 temperature sensor by setting the type parameter to 501.
1301 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1302 can do this via the tachometer parameter. Only do this if you have a
1303 fan tachometer actually set up.
1305 To compile this driver as a module, choose M here: the
1306 module will be called wdt_pci.
1309 # USB-based Watchdog Cards
1312 comment "USB-based Watchdog Cards"
1315 config USBPCWATCHDOG
1316 tristate "Berkshire Products USB-PC Watchdog"
1319 This is the driver for the Berkshire Products USB-PC Watchdog card.
1320 This card simply watches your kernel to make sure it doesn't freeze,
1321 and if it does, it reboots your computer after a certain amount of
1322 time. The card can also monitor the internal temperature of the PC.
1323 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1325 To compile this driver as a module, choose M here: the
1326 module will be called pcwd_usb.
1328 Most people will say N.