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 DA9055_WATCHDOG
80 tristate "Dialog Semiconductor DA9055 Watchdog"
84 If you say yes here you get support for watchdog on the Dialog
85 Semiconductor DA9055 PMIC.
87 This driver can also be built as a module. If so, the module
88 will be called da9055_wdt.
90 config WM831X_WATCHDOG
91 tristate "WM831x watchdog"
95 Support for the watchdog in the WM831x AudioPlus PMICs. When
96 the watchdog triggers the system will be reset.
98 config WM8350_WATCHDOG
99 tristate "WM8350 watchdog"
100 depends on MFD_WM8350
103 Support for the watchdog in the WM8350 AudioPlus PMIC. When
104 the watchdog triggers the system will be reset.
110 config ARM_SP805_WATCHDOG
111 tristate "ARM SP805 Watchdog"
112 depends on ARM && ARM_AMBA
115 ARM Primecell SP805 Watchdog timer. This will reboot your system when
116 the timeout is reached.
118 config AT91RM9200_WATCHDOG
119 tristate "AT91RM9200 watchdog"
120 depends on ARCH_AT91RM9200
122 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
123 system when the timeout is reached.
125 config AT91SAM9X_WATCHDOG
126 tristate "AT91SAM9X / AT91CAP9 watchdog"
127 depends on ARCH_AT91 && !ARCH_AT91RM9200
130 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
131 reboot your system when the timeout is reached.
133 config 21285_WATCHDOG
134 tristate "DC21285 watchdog"
135 depends on FOOTBRIDGE
137 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
138 here if you wish to use this. Alternatively say M to compile the
139 driver as a module, which will be called wdt285.
141 This driver does not work on all machines. In particular, early CATS
142 boards have hardware problems that will cause the machine to simply
143 lock up if the watchdog fires.
145 "If in doubt, leave it out" - say N.
148 tristate "NetWinder WB83C977 watchdog"
149 depends on FOOTBRIDGE && ARCH_NETWINDER
151 Say Y here to include support for the WB977 watchdog included in
152 NetWinder machines. Alternatively say M to compile the driver as
153 a module, which will be called wdt977.
155 Not sure? It's safe to say N.
157 config IXP4XX_WATCHDOG
158 tristate "IXP4xx Watchdog"
159 depends on ARCH_IXP4XX
161 Say Y here if to include support for the watchdog timer
162 in the Intel IXP4xx network processors. This driver can
163 be built as a module by choosing M. The module will
164 be called ixp4xx_wdt.
166 Note: The internal IXP4xx watchdog does a soft CPU reset
167 which doesn't reset any peripherals. There are circumstances
168 where the watchdog will fail to reset the board correctly
169 (e.g., if the boot ROM is in an unreadable state).
171 Say N if you are unsure.
173 config KS8695_WATCHDOG
174 tristate "KS8695 watchdog"
175 depends on ARCH_KS8695
177 Watchdog timer embedded into KS8695 processor. This will reboot your
178 system when the timeout is reached.
180 config HAVE_S3C2410_WATCHDOG
183 This will include watchdog timer support for Samsung SoCs. If
184 you want to include watchdog support for any machine, kindly
185 select this in the respective mach-XXXX/Kconfig file.
187 config S3C2410_WATCHDOG
188 tristate "S3C2410 Watchdog"
189 depends on HAVE_S3C2410_WATCHDOG
192 Watchdog timer block in the Samsung SoCs. This will reboot
193 the system when the timer expires with the watchdog enabled.
195 The driver is limited by the speed of the system's PCLK
196 signal, so with reasonably fast systems (PCLK around 50-66MHz)
197 then watchdog intervals of over approximately 20seconds are
200 The driver can be built as a module by choosing M, and will
201 be called s3c2410_wdt
203 config SA1100_WATCHDOG
204 tristate "SA1100/PXA2xx watchdog"
205 depends on ARCH_SA1100 || ARCH_PXA
207 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
208 reboot your system when timeout is reached.
210 NOTE: once enabled, this timer cannot be disabled.
212 To compile this driver as a module, choose M here: the
213 module will be called sa1100_wdt.
216 tristate "Synopsys DesignWare watchdog"
217 depends on ARM && HAVE_CLK
219 Say Y here if to include support for the Synopsys DesignWare
220 watchdog timer found in many ARM chips.
221 To compile this driver as a module, choose M here: the
222 module will be called dw_wdt.
224 config EP93XX_WATCHDOG
225 tristate "EP93xx Watchdog"
226 depends on ARCH_EP93XX
229 Say Y here if to include support for the watchdog timer
230 embedded in the Cirrus Logic EP93xx family of devices.
232 To compile this driver as a module, choose M here: the
233 module will be called ep93xx_wdt.
236 tristate "OMAP Watchdog"
237 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
240 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
241 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
243 config PNX4008_WATCHDOG
244 tristate "LPC32XX Watchdog"
245 depends on ARCH_LPC32XX
248 Say Y here if to include support for the watchdog timer
249 in the LPC32XX processor.
250 This driver can be built as a module by choosing M. The module
251 will be called pnx4008_wdt.
253 Say N if you are unsure.
256 tristate "IOP Watchdog"
258 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
260 Say Y here if to include support for the watchdog timer
261 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
262 be built as a module by choosing M. The module will
265 Note: The IOP13XX watchdog does an Internal Bus Reset which will
266 affect both cores and the peripherals of the IOP. The ATU-X
267 and/or ATUe configuration registers will remain intact, but if
268 operating as an Root Complex and/or Central Resource, the PCI-X
269 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
271 config DAVINCI_WATCHDOG
272 tristate "DaVinci watchdog"
273 depends on ARCH_DAVINCI
275 Say Y here if to include support for the watchdog timer
276 in the DaVinci DM644x/DM646x processors.
277 To compile this driver as a module, choose M here: the
278 module will be called davinci_wdt.
280 NOTE: once enabled, this timer cannot be disabled.
281 Say N if you are unsure.
283 config ORION_WATCHDOG
284 tristate "Orion watchdog"
285 depends on ARCH_ORION5X || ARCH_KIRKWOOD || ARCH_DOVE
288 Say Y here if to include support for the watchdog timer
289 in the Marvell Orion5x and Kirkwood ARM SoCs.
290 To compile this driver as a module, choose M here: the
291 module will be called orion_wdt.
293 config COH901327_WATCHDOG
294 bool "ST-Ericsson COH 901 327 watchdog"
296 default y if MACH_U300
299 Say Y here to include Watchdog timer support for the
300 watchdog embedded into the ST-Ericsson U300 series platforms.
301 This watchdog is used to reset the system and thus cannot be
302 compiled as a module.
304 config TWL4030_WATCHDOG
305 tristate "TWL4030 Watchdog"
306 depends on TWL4030_CORE
309 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
310 watchdog timer support for TWL4030 chips.
312 config STMP3XXX_RTC_WATCHDOG
313 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
314 depends on RTC_DRV_STMP
317 Say Y here to include support for the watchdog timer inside
318 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
319 To compile this driver as a module, choose M here: the
320 module will be called stmp3xxx_rtc_wdt.
322 config NUC900_WATCHDOG
323 tristate "Nuvoton NUC900 watchdog"
324 depends on ARCH_W90X900
326 Say Y here if to include support for the watchdog timer
327 for the Nuvoton NUC900 series SoCs.
328 To compile this driver as a module, choose M here: the
329 module will be called nuc900_wdt.
331 config TS72XX_WATCHDOG
332 tristate "TS-72XX SBC Watchdog"
333 depends on MACH_TS72XX
335 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
336 watchdog timer implemented in a external CPLD chip. Say Y here
337 if you want to support for the watchdog timer on TS-72XX boards.
339 To compile this driver as a module, choose M here: the
340 module will be called ts72xx_wdt.
342 config MAX63XX_WATCHDOG
343 tristate "Max63xx watchdog"
344 depends on ARM && HAS_IOMEM
347 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
350 tristate "IMX2+ Watchdog"
353 This is the driver for the hardware watchdog
354 on the Freescale IMX2 and later processors.
355 If you have one of these processors and wish to have
356 watchdog support enabled, say Y, otherwise say N.
358 To compile this driver as a module, choose M here: the
359 module will be called imx2_wdt.
361 config UX500_WATCHDOG
362 tristate "ST-Ericsson Ux500 watchdog"
363 depends on MFD_DB8500_PRCMU
367 Say Y here to include Watchdog timer support for the watchdog
368 existing in the prcmu of ST-Ericsson Ux500 series platforms.
370 To compile this driver as a module, choose M here: the
371 module will be called ux500_wdt.
374 tristate "Retu watchdog"
378 Retu watchdog driver for Nokia Internet Tablets (770, N800,
379 N810). At least on N800 the watchdog cannot be disabled, so
380 this driver is essential and you should enable it.
382 To compile this driver as a module, choose M here: the
383 module will be called retu_wdt.
387 config AT32AP700X_WDT
388 tristate "AT32AP700x watchdog"
389 depends on CPU_AT32AP700X
391 Watchdog timer embedded into AT32AP700x devices. This will reboot
392 your system when the timeout is reached.
394 # BLACKFIN Architecture
397 tristate "Blackfin On-Chip Watchdog Timer"
400 If you say yes here you will get support for the Blackfin On-Chip
401 Watchdog Timer. If you have one of these processors and wish to
402 have watchdog support enabled, say Y, otherwise say N.
404 To compile this driver as a module, choose M here: the
405 module will be called bfin_wdt.
413 # X86 (i386 + ia64 + x86_64) Architecture
416 tristate "Acquire SBC Watchdog Timer"
419 This is the driver for the hardware watchdog on Single Board
420 Computers produced by Acquire Inc (and others). This watchdog
421 simply watches your kernel to make sure it doesn't freeze, and if
422 it does, it reboots your computer after a certain amount of time.
424 To compile this driver as a module, choose M here: the
425 module will be called acquirewdt.
427 Most people will say N.
430 tristate "Advantech SBC Watchdog Timer"
433 If you are configuring a Linux kernel for the Advantech single-board
434 computer, say `Y' here to support its built-in watchdog timer
435 feature. More information can be found at
436 <http://www.advantech.com.tw/products/>
439 tristate "ALi M1535 PMU Watchdog Timer"
440 depends on X86 && PCI
442 This is the driver for the hardware watchdog on the ALi M1535 PMU.
444 To compile this driver as a module, choose M here: the
445 module will be called alim1535_wdt.
447 Most people will say N.
450 tristate "ALi M7101 PMU Computer Watchdog"
453 This is the driver for the hardware watchdog on the ALi M7101 PMU
454 as used in the x86 Cobalt servers and also found in some
455 SPARC Netra servers too.
457 To compile this driver as a module, choose M here: the
458 module will be called alim7101_wdt.
460 Most people will say N.
463 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
466 This is the driver for the hardware watchdog on the Fintek
467 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
469 You can compile this driver directly into the kernel, or use
470 it as a module. The module will be called f71808e_wdt.
473 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
474 depends on X86 && PCI
476 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
477 (Total Cost of Ownership) timer is a watchdog timer that will reboot
478 the machine after its expiration. The expiration time can be
479 configured with the "heartbeat" parameter.
481 To compile this driver as a module, choose M here: the
482 module will be called sp5100_tco.
485 tristate "AMD Geode CS5535/CS5536 Watchdog"
486 depends on CS5535_MFGPT
488 This driver enables a watchdog capability built into the
489 CS5535/CS5536 companion chips for the AMD Geode GX and LX
490 processors. This watchdog watches your kernel to make sure
491 it doesn't freeze, and if it does, it reboots your computer after
492 a certain amount of time.
494 You can compile this driver directly into the kernel, or use
495 it as a module. The module will be called geodewdt.
498 tristate "AMD Elan SC520 processor Watchdog"
501 This is the driver for the hardware watchdog built in to the
502 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
503 This watchdog simply watches your kernel to make sure it doesn't
504 freeze, and if it does, it reboots your computer after a certain
507 You can compile this driver directly into the kernel, or use
508 it as a module. The module will be called sc520_wdt.
510 config SBC_FITPC2_WATCHDOG
511 tristate "Compulab SBC-FITPC2 watchdog"
514 This is the driver for the built-in watchdog timer on the fit-PC2,
515 fit-PC2i, CM-iAM single-board computers made by Compulab.
517 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
518 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
520 Entering BIOS setup temporary disables watchdog operation regardless to current state,
521 so system will not be restarted while user in BIOS setup.
523 Once watchdog was enabled the system will be restarted every
524 "Watchdog Timer Value" period, so to prevent it user can restart or
525 disable the watchdog.
527 To compile this driver as a module, choose M here: the
528 module will be called sbc_fitpc2_wdt.
530 Most people will say N.
533 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
536 Enable support for the watchdog timer on the Eurotech CPU-1220 and
537 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
538 information are at <http://www.eurotech.it/>.
541 tristate "IB700 SBC Watchdog Timer"
544 This is the driver for the hardware watchdog on the IB700 Single
545 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
546 simply watches your kernel to make sure it doesn't freeze, and if
547 it does, it reboots your computer after a certain amount of time.
549 This driver is like the WDT501 driver but for slightly different hardware.
551 To compile this driver as a module, choose M here: the
552 module will be called ib700wdt.
554 Most people will say N.
557 tristate "IBM Automatic Server Restart"
560 This is the driver for the IBM Automatic Server Restart watchdog
561 timer built-in into some eServer xSeries machines.
563 To compile this driver as a module, choose M here: the
564 module will be called ibmasr.
567 tristate "ICP Single Board Computer Watchdog Timer"
570 This is a driver for the hardware watchdog on the ICP Single
571 Board Computer. This driver is working on (at least) the following
572 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
574 To compile this driver as a module, choose M here: the
575 module will be called wafer5823wdt.
578 tristate "Intel 6300ESB Timer/Watchdog"
581 Hardware driver for the watchdog timer built into the Intel
582 6300ESB controller hub.
584 To compile this driver as a module, choose M here: the
585 module will be called i6300esb.
588 tristate "Intel Atom E6xx Watchdog"
589 depends on X86 && PCI
594 Hardware driver for the watchdog timer built into the Intel
595 Atom E6XX (TunnelCreek) processor.
597 To compile this driver as a module, choose M here: the
598 module will be called ie6xx_wdt.
600 config INTEL_SCU_WATCHDOG
601 bool "Intel SCU Watchdog for Mobile Platforms"
602 depends on X86_INTEL_MID
604 Hardware driver for the watchdog time built into the Intel SCU
605 for Intel Mobile Platforms.
607 To compile this driver as a module, choose M here.
610 tristate "Intel TCO Timer/Watchdog"
611 depends on (X86 || IA64) && PCI
615 Hardware driver for the intel TCO timer based watchdog devices.
616 These drivers are included in the Intel 82801 I/O Controller
617 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
620 The TCO (Total Cost of Ownership) timer is a watchdog timer
621 that will reboot the machine after its second expiration. The
622 expiration time can be configured with the "heartbeat" parameter.
624 On some motherboards the driver may fail to reset the chipset's
625 NO_REBOOT flag which prevents the watchdog from rebooting the
626 machine. If this is the case you will get a kernel message like
627 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
629 To compile this driver as a module, choose M here: the
630 module will be called iTCO_wdt.
632 config ITCO_VENDOR_SUPPORT
633 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
636 Add vendor specific support to the intel TCO timer based watchdog
637 devices. At this moment we only have additional support for some
638 SuperMicro Inc. motherboards.
641 tristate "IT8712F (Smart Guardian) Watchdog Timer"
644 This is the driver for the built-in watchdog timer on the IT8712F
645 Super I/0 chipset used on many motherboards.
647 If the driver does not work, then make sure that the game port in
650 To compile this driver as a module, choose M here: the
651 module will be called it8712f_wdt.
654 tristate "IT87 Watchdog Timer"
657 This is the driver for the hardware watchdog on the ITE IT8702,
658 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
661 If the driver does not work, then make sure that the game port in
664 This watchdog simply watches your kernel to make sure it doesn't
665 freeze, and if it does, it reboots your computer after a certain
668 To compile this driver as a module, choose M here: the module will
672 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
673 depends on X86 && PCI
675 A software monitoring watchdog and NMI sourcing driver. This driver
676 will detect lockups and provide a stack trace. This is a driver that
677 will only load on an HP ProLiant system with a minimum of iLO2 support.
678 To compile this driver as a module, choose M here: the module will be
682 tristate "Kontron COM Watchdog Timer"
683 depends on MFD_KEMPLD
686 Support for the PLD watchdog on some Kontron ETX and COMexpress
689 This driver can also be built as a module. If so, the module will be
692 config HPWDT_NMI_DECODING
693 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
694 depends on HP_WATCHDOG
697 When an NMI occurs this feature will make the necessary BIOS calls to
698 log the cause of the NMI.
701 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
704 This is a driver for National Semiconductor PC87307/PC97307 hardware
705 watchdog cards as found on the SC1200. This watchdog is mainly used
706 for power management purposes and can be used to power down the device
707 during inactivity periods (includes interrupt activity monitoring).
709 To compile this driver as a module, choose M here: the
710 module will be called sc1200wdt.
712 Most people will say N.
715 tristate "National Semiconductor SCx200 Watchdog"
716 depends on SCx200 && PCI
718 Enable the built-in watchdog timer support on the National
719 Semiconductor SCx200 processors.
721 If compiled as a module, it will be called scx200_wdt.
724 tristate "NS PC87413 watchdog"
727 This is the driver for the hardware watchdog on the PC87413 chipset
728 This watchdog simply watches your kernel to make sure it doesn't
729 freeze, and if it does, it reboots your computer after a certain
732 To compile this driver as a module, choose M here: the
733 module will be called pc87413_wdt.
735 Most people will say N.
738 tristate "nVidia TCO Timer/Watchdog"
739 depends on X86 && PCI
741 Hardware driver for the TCO timer built into the nVidia Hub family
742 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
743 watchdog timer that will reboot the machine after its second
744 expiration. The expiration time can be configured with the
745 "heartbeat" parameter.
747 On some motherboards the driver may fail to reset the chipset's
748 NO_REBOOT flag which prevents the watchdog from rebooting the
749 machine. If this is the case you will get a kernel message like
750 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
752 To compile this driver as a module, choose M here: the
753 module will be called nv_tco.
756 tristate "RDC R-321x SoC watchdog"
757 depends on X86_RDC321X
759 This is the driver for the built in hardware watchdog
760 in the RDC R-321x SoC.
762 To compile this driver as a module, choose M here: the
763 module will be called rdc321x_wdt.
766 tristate "SBC-60XX Watchdog Timer"
769 This driver can be used with the watchdog timer found on some
770 single board computers, namely the 6010 PII based computer.
771 It may well work with other cards. It reads port 0x443 to enable
772 and re-set the watchdog timer, and reads port 0x45 to disable
773 the watchdog. If you have a card that behave in similar ways,
774 you can probably make this driver work with your card as well.
776 You can compile this driver directly into the kernel, or use
777 it as a module. The module will be called sbc60xxwdt.
780 tristate "SBC8360 Watchdog Timer"
784 This is the driver for the hardware watchdog on the SBC8360 Single
785 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
787 To compile this driver as a module, choose M here: the
788 module will be called sbc8360.
790 Most people will say N.
793 tristate "SBC Nano 7240 Watchdog Timer"
794 depends on X86_32 && !UML
796 This is the driver for the hardware watchdog found on the IEI
797 single board computers EPIC Nano 7240 (and likely others). This
798 watchdog simply watches your kernel to make sure it doesn't freeze,
799 and if it does, it reboots your computer after a certain amount of
802 To compile this driver as a module, choose M here: the
803 module will be called sbc7240_wdt.
806 tristate "SMA CPU5 Watchdog"
810 To compile this driver as a module, choose M here: the
811 module will be called cpu5wdt.
813 config SMSC_SCH311X_WDT
814 tristate "SMSC SCH311X Watchdog Timer"
817 This is the driver for the hardware watchdog timer on the
818 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
819 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
822 To compile this driver as a module, choose M here: the
823 module will be called sch311x_wdt.
825 config SMSC37B787_WDT
826 tristate "Winbond SMsC37B787 Watchdog Timer"
829 This is the driver for the hardware watchdog component on the
830 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
831 from Vision Systems and maybe others.
833 This watchdog simply watches your kernel to make sure it doesn't
834 freeze, and if it does, it reboots your computer after a certain
837 Usually a userspace daemon will notify the kernel WDT driver that
838 userspace is still alive, at regular intervals.
840 To compile this driver as a module, choose M here: the
841 module will be called smsc37b787_wdt.
843 Most people will say N.
846 tristate "VIA Watchdog Timer"
847 depends on X86 && PCI
850 This is the driver for the hardware watchdog timer on VIA
851 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
853 To compile this driver as a module, choose M here; the module
854 will be called via_wdt.
856 Most people will say N.
859 tristate "W83627HF/W83627DHG Watchdog Timer"
862 This is the driver for the hardware watchdog on the W83627HF chipset
863 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
864 (and likely others). The driver also supports the W83627DHG chip.
865 This watchdog simply watches your kernel to make sure it doesn't
866 freeze, and if it does, it reboots your computer after a certain
869 To compile this driver as a module, choose M here: the
870 module will be called w83627hf_wdt.
872 Most people will say N.
875 tristate "W83697HF/W83697HG Watchdog Timer"
878 This is the driver for the hardware watchdog on the W83697HF/HG
879 chipset as used in Dedibox/VIA motherboards (and likely others).
880 This watchdog simply watches your kernel to make sure it doesn't
881 freeze, and if it does, it reboots your computer after a certain
884 To compile this driver as a module, choose M here: the
885 module will be called w83697hf_wdt.
887 Most people will say N.
890 tristate "W83697UG/W83697UF Watchdog Timer"
893 This is the driver for the hardware watchdog on the W83697UG/UF
894 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
895 This watchdog simply watches your kernel to make sure it doesn't
896 freeze, and if it does, it reboots your computer after a certain
899 To compile this driver as a module, choose M here: the
900 module will be called w83697ug_wdt.
902 Most people will say N.
905 tristate "W83877F (EMACS) Watchdog Timer"
908 This is the driver for the hardware watchdog on the W83877F chipset
909 as used in EMACS PC-104 motherboards (and likely others). This
910 watchdog simply watches your kernel to make sure it doesn't freeze,
911 and if it does, it reboots your computer after a certain amount of
914 To compile this driver as a module, choose M here: the
915 module will be called w83877f_wdt.
917 Most people will say N.
920 tristate "W83977F (PCM-5335) Watchdog Timer"
923 This is the driver for the hardware watchdog on the W83977F I/O chip
924 as used in AAEON's PCM-5335 SBC (and likely others). This
925 watchdog simply watches your kernel to make sure it doesn't freeze,
926 and if it does, it reboots your computer after a certain amount of
929 To compile this driver as a module, choose M here: the
930 module will be called w83977f_wdt.
933 tristate "ZF MachZ Watchdog"
936 If you are using a ZF Micro MachZ processor, say Y here, otherwise
937 N. This is the driver for the watchdog timer built-in on that
938 processor using ZF-Logic interface. This watchdog simply watches
939 your kernel to make sure it doesn't freeze, and if it does, it
940 reboots your computer after a certain amount of time.
942 To compile this driver as a module, choose M here: the
943 module will be called machzwd.
945 config SBC_EPX_C3_WATCHDOG
946 tristate "Winsystems SBC EPX-C3 watchdog"
949 This is the driver for the built-in watchdog timer on the EPX-C3
950 Single-board computer made by Winsystems, Inc.
952 *Note*: This hardware watchdog is not probeable and thus there
953 is no way to know if writing to its IO address will corrupt
954 your system or have any real effect. The only way to be sure
955 that this driver does what you want is to make sure you
956 are running it on an EPX-C3 from Winsystems with the watchdog
957 timer at IO address 0x1ee and 0x1ef. It will write to both those
958 IO ports. Basically, the assumption is made that if you compile
959 this driver into your kernel and/or load it as a module, that you
960 know what you are doing and that you are in fact running on an
963 To compile this driver as a module, choose M here: the
964 module will be called sbc_epx_c3.
970 config M54xx_WATCHDOG
971 tristate "MCF54xx watchdog support"
974 To compile this driver as a module, choose M here: the
975 module will be called m54xx_wdt.
977 # MicroBlaze Architecture
979 config XILINX_WATCHDOG
980 tristate "Xilinx Watchdog timer"
981 depends on MICROBLAZE
983 Watchdog driver for the xps_timebase_wdt ip core.
985 IMPORTANT: The xps_timebase_wdt parent must have the property
986 "clock-frequency" at device tree.
988 To compile this driver as a module, choose M here: the
989 module will be called of_xilinx_wdt.
994 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
997 Hardware driver for the built-in watchdog timer on the Atheros
998 AR71XX/AR724X/AR913X SoCs.
1001 tristate "Broadcom BCM47xx Watchdog Timer"
1003 select WATCHDOG_CORE
1005 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1008 tristate "IDT RC32434 SoC Watchdog Timer"
1009 depends on MIKROTIK_RB532
1011 Hardware driver for the IDT RC32434 SoC built-in
1014 To compile this driver as a module, choose M here: the
1015 module will be called rc32434_wdt.
1018 tristate "Indy/I2 Hardware Watchdog"
1019 depends on SGI_HAS_INDYDOG
1021 Hardware driver for the Indy's/I2's watchdog. This is a
1022 watchdog timer that will reboot the machine after a 60 second
1023 timer expired and no process has written to /dev/watchdog during
1027 tristate "Ingenic jz4740 SoC hardware watchdog"
1028 depends on MACH_JZ4740
1029 select WATCHDOG_CORE
1031 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1034 tristate "MTX-1 Hardware Watchdog"
1035 depends on MIPS_MTX1
1037 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1038 will reboot the machine after a 100 seconds timer expired.
1041 tristate "PNX833x Hardware Watchdog"
1042 depends on SOC_PNX8335
1044 Hardware driver for the PNX833x's watchdog. This is a
1045 watchdog timer that will reboot the machine after a programmable
1046 timer has expired and no process has written to /dev/watchdog during
1050 tristate "Sibyte SoC hardware watchdog"
1053 Watchdog driver for the built in watchdog hardware in Sibyte
1054 SoC processors. There are apparently two watchdog timers
1055 on such processors; this driver supports only the first one,
1056 because currently Linux only supports exporting one watchdog
1059 To compile this driver as a loadable module, choose M here.
1060 The module will be called sb_wdog.
1063 tristate "TI AR7 Watchdog Timer"
1066 Hardware driver for the TI AR7 Watchdog Timer.
1069 tristate "Toshiba TXx9 Watchdog Timer"
1070 depends on CPU_TX39XX || CPU_TX49XX
1071 select WATCHDOG_CORE
1073 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1076 tristate "Cavium OCTEON SOC family Watchdog Timer"
1077 depends on CAVIUM_OCTEON_SOC
1079 select EXPORT_UASM if OCTEON_WDT = m
1081 Hardware driver for OCTEON's on chip watchdog timer.
1082 Enables the watchdog for all cores running Linux. It
1083 installs a NMI handler and pokes the watchdog based on an
1084 interrupt. On first expiration of the watchdog, the
1085 interrupt handler pokes it. The second expiration causes an
1086 NMI that prints a message. The third expiration causes a
1089 When userspace has /dev/watchdog open, no poking is done
1090 from the first interrupt, it is then only poked when the
1094 tristate "Broadcom BCM63xx hardware watchdog"
1097 Watchdog driver for the built in watchdog hardware in Broadcom
1100 To compile this driver as a loadable module, choose M here.
1101 The module will be called bcm63xx_wdt.
1104 tristate "Broadcom BCM2835 hardware watchdog"
1105 depends on ARCH_BCM2835
1106 select WATCHDOG_CORE
1108 Watchdog driver for the built in watchdog hardware in Broadcom
1111 To compile this driver as a loadable module, choose M here.
1112 The module will be called bcm2835_wdt.
1115 tristate "Lantiq SoC watchdog"
1118 Hardware driver for the Lantiq SoC Watchdog Timer.
1120 # PARISC Architecture
1122 # POWERPC Architecture
1125 tristate "GE Watchdog Timer"
1128 Watchdog timer found in a number of GE single board computers.
1131 bool "MPC52xx Watchdog Timer"
1132 depends on PPC_MPC52xx
1134 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1137 tristate "MPC8xxx Platform Watchdog Timer"
1138 depends on PPC_8xx || PPC_83xx || PPC_86xx
1140 This driver is for a SoC level watchdog that exists on some
1141 Freescale PowerPC processors. So far this driver supports:
1146 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1149 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1153 tristate "PIKA FPGA Watchdog"
1157 This enables the watchdog in the PIKA FPGA. Currently used on
1161 tristate "PowerPC Book-E Watchdog Timer"
1162 depends on BOOKE || 4xx
1163 select WATCHDOG_CORE
1165 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1166 MPC85xx SOCs and the IBM PowerPC 440.
1168 Please see Documentation/watchdog/watchdog-api.txt for
1171 config BOOKE_WDT_DEFAULT_TIMEOUT
1172 int "PowerPC Book-E Watchdog Timer Default Timeout"
1173 depends on BOOKE_WDT
1174 default 38 if PPC_FSL_BOOK3E
1175 range 0 63 if PPC_FSL_BOOK3E
1176 default 3 if !PPC_FSL_BOOK3E
1177 range 0 3 if !PPC_FSL_BOOK3E
1179 Select the default watchdog timer period to be used by the PowerPC
1180 Book-E watchdog driver. A watchdog "event" occurs when the bit
1181 position represented by this number transitions from zero to one.
1183 For Freescale Book-E processors, this is a number between 0 and 63.
1184 For other Book-E processors, this is a number between 0 and 3.
1186 The value can be overridden by the wdt_period command-line parameter.
1189 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1190 select WATCHDOG_CORE
1193 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1195 The driver can also be built as a module. If so, the module will be
1198 If unsure select N here.
1200 # PPC64 Architecture
1202 config WATCHDOG_RTAS
1203 tristate "RTAS watchdog"
1206 This driver adds watchdog support for the RTAS watchdog.
1208 To compile this driver as a module, choose M here. The module
1209 will be called wdrtas.
1214 tristate "z/VM Watchdog Timer"
1217 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1218 provide a virtual watchdog timer to their guest that cause a
1219 user define Control Program command to be executed after a
1222 To compile this driver as a module, choose M here. The module
1223 will be called vmwatchdog.
1225 # SUPERH (sh + sh64) Architecture
1228 tristate "SuperH Watchdog"
1229 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1230 select WATCHDOG_CORE
1232 This driver adds watchdog support for the integrated watchdog in the
1233 SuperH processors. If you have one of these processors and wish
1234 to have watchdog support enabled, say Y, otherwise say N.
1236 As a side note, saying Y here will automatically boost HZ to 1000
1237 so that the timer has a chance to clear the overflow counter. On
1238 slower systems (such as the SH-2 and SH-3) this will likely yield
1239 some performance issues. As such, the WDT should be avoided here
1240 unless it is absolutely necessary.
1242 To compile this driver as a module, choose M here: the
1243 module will be called shwdt.
1245 # SPARC Architecture
1247 # SPARC64 Architecture
1249 config WATCHDOG_CP1XXX
1250 tristate "CP1XXX Hardware Watchdog support"
1251 depends on SPARC64 && PCI
1253 This is the driver for the hardware watchdog timers present on
1254 Sun Microsystems CompactPCI models CP1400 and CP1500.
1256 To compile this driver as a module, choose M here: the
1257 module will be called cpwatchdog.
1259 If you do not have a CompactPCI model CP1400 or CP1500, or
1260 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1261 you should say N to this option.
1264 tristate "RIO Hardware Watchdog support"
1265 depends on SPARC64 && PCI
1267 Say Y here to support the hardware watchdog capability on Sun RIO
1268 machines. The watchdog timeout period is normally one minute but
1269 can be changed with a boot-time parameter.
1271 # XTENSA Architecture
1276 tristate "Xen Watchdog support"
1279 Say Y here to support the hypervisor watchdog capability provided
1280 by Xen 4.0 and newer. The watchdog timeout period is normally one
1281 minute but can be changed with a boot-time parameter.
1284 tristate "UML watchdog"
1288 # ISA-based Watchdog Cards
1291 comment "ISA-based Watchdog Cards"
1295 tristate "Berkshire Products ISA-PC Watchdog"
1298 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1299 This card simply watches your kernel to make sure it doesn't freeze,
1300 and if it does, it reboots your computer after a certain amount of
1301 time. This driver is like the WDT501 driver but for different
1302 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1303 watchdog cards can be ordered from <http://www.berkprod.com/>.
1305 To compile this driver as a module, choose M here: the
1306 module will be called pcwd.
1308 Most people will say N.
1311 tristate "Mixcom Watchdog"
1314 This is a driver for the Mixcom hardware watchdog cards. This
1315 watchdog simply watches your kernel to make sure it doesn't freeze,
1316 and if it does, it reboots your computer after a certain amount of
1319 To compile this driver as a module, choose M here: the
1320 module will be called mixcomwd.
1322 Most people will say N.
1325 tristate "WDT Watchdog timer"
1328 If you have a WDT500P or WDT501P watchdog board, say Y here,
1329 otherwise N. It is not possible to probe for this board, which means
1330 that you have to inform the kernel about the IO port and IRQ that
1331 is needed (you can do this via the io and irq parameters)
1333 To compile this driver as a module, choose M here: the
1334 module will be called wdt.
1337 # PCI-based Watchdog Cards
1340 comment "PCI-based Watchdog Cards"
1343 config PCIPCWATCHDOG
1344 tristate "Berkshire Products PCI-PC Watchdog"
1347 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1348 This card simply watches your kernel to make sure it doesn't freeze,
1349 and if it does, it reboots your computer after a certain amount of
1350 time. The card can also monitor the internal temperature of the PC.
1351 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1353 To compile this driver as a module, choose M here: the
1354 module will be called pcwd_pci.
1356 Most people will say N.
1359 tristate "PCI-WDT500/501 Watchdog timer"
1362 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1364 If you have a PCI-WDT501 watchdog board then you can enable the
1365 temperature sensor by setting the type parameter to 501.
1367 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1368 can do this via the tachometer parameter. Only do this if you have a
1369 fan tachometer actually set up.
1371 To compile this driver as a module, choose M here: the
1372 module will be called wdt_pci.
1375 # USB-based Watchdog Cards
1378 comment "USB-based Watchdog Cards"
1381 config USBPCWATCHDOG
1382 tristate "Berkshire Products USB-PC Watchdog"
1385 This is the driver for the Berkshire Products USB-PC Watchdog card.
1386 This card simply watches your kernel to make sure it doesn't freeze,
1387 and if it does, it reboots your computer after a certain amount of
1388 time. The card can also monitor the internal temperature of the PC.
1389 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1391 To compile this driver as a module, choose M here: the
1392 module will be called pcwd_usb.
1394 Most people will say N.