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 MPCORE_WATCHDOG
225 tristate "MPcore watchdog"
226 depends on HAVE_ARM_TWD
228 Watchdog timer embedded into the MPcore system.
230 To compile this driver as a module, choose M here: the
231 module will be called mpcore_wdt.
233 config EP93XX_WATCHDOG
234 tristate "EP93xx Watchdog"
235 depends on ARCH_EP93XX
238 Say Y here if to include support for the watchdog timer
239 embedded in the Cirrus Logic EP93xx family of devices.
241 To compile this driver as a module, choose M here: the
242 module will be called ep93xx_wdt.
245 tristate "OMAP Watchdog"
246 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
249 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
250 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
252 config PNX4008_WATCHDOG
253 tristate "LPC32XX Watchdog"
254 depends on ARCH_LPC32XX
257 Say Y here if to include support for the watchdog timer
258 in the LPC32XX processor.
259 This driver can be built as a module by choosing M. The module
260 will be called pnx4008_wdt.
262 Say N if you are unsure.
265 tristate "IOP Watchdog"
267 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
269 Say Y here if to include support for the watchdog timer
270 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
271 be built as a module by choosing M. The module will
274 Note: The IOP13XX watchdog does an Internal Bus Reset which will
275 affect both cores and the peripherals of the IOP. The ATU-X
276 and/or ATUe configuration registers will remain intact, but if
277 operating as an Root Complex and/or Central Resource, the PCI-X
278 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
280 config DAVINCI_WATCHDOG
281 tristate "DaVinci watchdog"
282 depends on ARCH_DAVINCI
284 Say Y here if to include support for the watchdog timer
285 in the DaVinci DM644x/DM646x processors.
286 To compile this driver as a module, choose M here: the
287 module will be called davinci_wdt.
289 NOTE: once enabled, this timer cannot be disabled.
290 Say N if you are unsure.
292 config ORION_WATCHDOG
293 tristate "Orion watchdog"
294 depends on ARCH_ORION5X || ARCH_KIRKWOOD
297 Say Y here if to include support for the watchdog timer
298 in the Marvell Orion5x and Kirkwood ARM SoCs.
299 To compile this driver as a module, choose M here: the
300 module will be called orion_wdt.
302 config COH901327_WATCHDOG
303 bool "ST-Ericsson COH 901 327 watchdog"
305 default y if MACH_U300
308 Say Y here to include Watchdog timer support for the
309 watchdog embedded into the ST-Ericsson U300 series platforms.
310 This watchdog is used to reset the system and thus cannot be
311 compiled as a module.
313 config TWL4030_WATCHDOG
314 tristate "TWL4030 Watchdog"
315 depends on TWL4030_CORE
318 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
319 watchdog timer support for TWL4030 chips.
321 config STMP3XXX_RTC_WATCHDOG
322 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
323 depends on RTC_DRV_STMP
326 Say Y here to include support for the watchdog timer inside
327 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
328 To compile this driver as a module, choose M here: the
329 module will be called stmp3xxx_rtc_wdt.
331 config NUC900_WATCHDOG
332 tristate "Nuvoton NUC900 watchdog"
333 depends on ARCH_W90X900
335 Say Y here if to include support for the watchdog timer
336 for the Nuvoton NUC900 series SoCs.
337 To compile this driver as a module, choose M here: the
338 module will be called nuc900_wdt.
340 config TS72XX_WATCHDOG
341 tristate "TS-72XX SBC Watchdog"
342 depends on MACH_TS72XX
344 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
345 watchdog timer implemented in a external CPLD chip. Say Y here
346 if you want to support for the watchdog timer on TS-72XX boards.
348 To compile this driver as a module, choose M here: the
349 module will be called ts72xx_wdt.
351 config MAX63XX_WATCHDOG
352 tristate "Max63xx watchdog"
353 depends on ARM && HAS_IOMEM
356 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
359 tristate "IMX2+ Watchdog"
362 This is the driver for the hardware watchdog
363 on the Freescale IMX2 and later processors.
364 If you have one of these processors and wish to have
365 watchdog support enabled, say Y, otherwise say N.
367 To compile this driver as a module, choose M here: the
368 module will be called imx2_wdt.
370 config UX500_WATCHDOG
371 tristate "ST-Ericsson Ux500 watchdog"
372 depends on MFD_DB8500_PRCMU
376 Say Y here to include Watchdog timer support for the watchdog
377 existing in the prcmu of ST-Ericsson Ux500 series platforms.
379 To compile this driver as a module, choose M here: the
380 module will be called ux500_wdt.
383 tristate "Retu watchdog"
387 Retu watchdog driver for Nokia Internet Tablets (770, N800,
388 N810). At least on N800 the watchdog cannot be disabled, so
389 this driver is essential and you should enable it.
391 To compile this driver as a module, choose M here: the
392 module will be called retu_wdt.
396 config AT32AP700X_WDT
397 tristate "AT32AP700x watchdog"
398 depends on CPU_AT32AP700X
400 Watchdog timer embedded into AT32AP700x devices. This will reboot
401 your system when the timeout is reached.
403 # BLACKFIN Architecture
406 tristate "Blackfin On-Chip Watchdog Timer"
409 If you say yes here you will get support for the Blackfin On-Chip
410 Watchdog Timer. If you have one of these processors and wish to
411 have watchdog support enabled, say Y, otherwise say N.
413 To compile this driver as a module, choose M here: the
414 module will be called bfin_wdt.
422 # X86 (i386 + ia64 + x86_64) Architecture
425 tristate "Acquire SBC Watchdog Timer"
428 This is the driver for the hardware watchdog on Single Board
429 Computers produced by Acquire Inc (and others). This watchdog
430 simply watches your kernel to make sure it doesn't freeze, and if
431 it does, it reboots your computer after a certain amount of time.
433 To compile this driver as a module, choose M here: the
434 module will be called acquirewdt.
436 Most people will say N.
439 tristate "Advantech SBC Watchdog Timer"
442 If you are configuring a Linux kernel for the Advantech single-board
443 computer, say `Y' here to support its built-in watchdog timer
444 feature. More information can be found at
445 <http://www.advantech.com.tw/products/>
448 tristate "ALi M1535 PMU Watchdog Timer"
449 depends on X86 && PCI
451 This is the driver for the hardware watchdog on the ALi M1535 PMU.
453 To compile this driver as a module, choose M here: the
454 module will be called alim1535_wdt.
456 Most people will say N.
459 tristate "ALi M7101 PMU Computer Watchdog"
462 This is the driver for the hardware watchdog on the ALi M7101 PMU
463 as used in the x86 Cobalt servers and also found in some
464 SPARC Netra servers too.
466 To compile this driver as a module, choose M here: the
467 module will be called alim7101_wdt.
469 Most people will say N.
472 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
475 This is the driver for the hardware watchdog on the Fintek
476 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
478 You can compile this driver directly into the kernel, or use
479 it as a module. The module will be called f71808e_wdt.
482 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
483 depends on X86 && PCI
485 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
486 (Total Cost of Ownership) timer is a watchdog timer that will reboot
487 the machine after its expiration. The expiration time can be
488 configured with the "heartbeat" parameter.
490 To compile this driver as a module, choose M here: the
491 module will be called sp5100_tco.
494 tristate "AMD Geode CS5535/CS5536 Watchdog"
495 depends on CS5535_MFGPT
497 This driver enables a watchdog capability built into the
498 CS5535/CS5536 companion chips for the AMD Geode GX and LX
499 processors. This watchdog watches your kernel to make sure
500 it doesn't freeze, and if it does, it reboots your computer after
501 a certain amount of time.
503 You can compile this driver directly into the kernel, or use
504 it as a module. The module will be called geodewdt.
507 tristate "AMD Elan SC520 processor Watchdog"
510 This is the driver for the hardware watchdog built in to the
511 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
512 This watchdog simply watches your kernel to make sure it doesn't
513 freeze, and if it does, it reboots your computer after a certain
516 You can compile this driver directly into the kernel, or use
517 it as a module. The module will be called sc520_wdt.
519 config SBC_FITPC2_WATCHDOG
520 tristate "Compulab SBC-FITPC2 watchdog"
523 This is the driver for the built-in watchdog timer on the fit-PC2,
524 fit-PC2i, CM-iAM single-board computers made by Compulab.
526 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
527 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
529 Entering BIOS setup temporary disables watchdog operation regardless to current state,
530 so system will not be restarted while user in BIOS setup.
532 Once watchdog was enabled the system will be restarted every
533 "Watchdog Timer Value" period, so to prevent it user can restart or
534 disable the watchdog.
536 To compile this driver as a module, choose M here: the
537 module will be called sbc_fitpc2_wdt.
539 Most people will say N.
542 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
545 Enable support for the watchdog timer on the Eurotech CPU-1220 and
546 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
547 information are at <http://www.eurotech.it/>.
550 tristate "IB700 SBC Watchdog Timer"
553 This is the driver for the hardware watchdog on the IB700 Single
554 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
555 simply watches your kernel to make sure it doesn't freeze, and if
556 it does, it reboots your computer after a certain amount of time.
558 This driver is like the WDT501 driver but for slightly different hardware.
560 To compile this driver as a module, choose M here: the
561 module will be called ib700wdt.
563 Most people will say N.
566 tristate "IBM Automatic Server Restart"
569 This is the driver for the IBM Automatic Server Restart watchdog
570 timer built-in into some eServer xSeries machines.
572 To compile this driver as a module, choose M here: the
573 module will be called ibmasr.
576 tristate "ICP Single Board Computer Watchdog Timer"
579 This is a driver for the hardware watchdog on the ICP Single
580 Board Computer. This driver is working on (at least) the following
581 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
583 To compile this driver as a module, choose M here: the
584 module will be called wafer5823wdt.
587 tristate "Intel 6300ESB Timer/Watchdog"
590 Hardware driver for the watchdog timer built into the Intel
591 6300ESB controller hub.
593 To compile this driver as a module, choose M here: the
594 module will be called i6300esb.
597 tristate "Intel Atom E6xx Watchdog"
598 depends on X86 && PCI
603 Hardware driver for the watchdog timer built into the Intel
604 Atom E6XX (TunnelCreek) processor.
606 To compile this driver as a module, choose M here: the
607 module will be called ie6xx_wdt.
609 config INTEL_SCU_WATCHDOG
610 bool "Intel SCU Watchdog for Mobile Platforms"
611 depends on X86_INTEL_MID
613 Hardware driver for the watchdog time built into the Intel SCU
614 for Intel Mobile Platforms.
616 To compile this driver as a module, choose M here.
619 tristate "Intel TCO Timer/Watchdog"
620 depends on (X86 || IA64) && PCI
624 Hardware driver for the intel TCO timer based watchdog devices.
625 These drivers are included in the Intel 82801 I/O Controller
626 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
629 The TCO (Total Cost of Ownership) timer is a watchdog timer
630 that will reboot the machine after its second expiration. The
631 expiration time can be configured with the "heartbeat" parameter.
633 On some motherboards the driver may fail to reset the chipset's
634 NO_REBOOT flag which prevents the watchdog from rebooting the
635 machine. If this is the case you will get a kernel message like
636 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
638 To compile this driver as a module, choose M here: the
639 module will be called iTCO_wdt.
641 config ITCO_VENDOR_SUPPORT
642 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
645 Add vendor specific support to the intel TCO timer based watchdog
646 devices. At this moment we only have additional support for some
647 SuperMicro Inc. motherboards.
650 tristate "IT8712F (Smart Guardian) Watchdog Timer"
653 This is the driver for the built-in watchdog timer on the IT8712F
654 Super I/0 chipset used on many motherboards.
656 If the driver does not work, then make sure that the game port in
659 To compile this driver as a module, choose M here: the
660 module will be called it8712f_wdt.
663 tristate "IT87 Watchdog Timer"
666 This is the driver for the hardware watchdog on the ITE IT8702,
667 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
670 If the driver does not work, then make sure that the game port in
673 This watchdog simply watches your kernel to make sure it doesn't
674 freeze, and if it does, it reboots your computer after a certain
677 To compile this driver as a module, choose M here: the module will
681 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
682 depends on X86 && PCI
684 A software monitoring watchdog and NMI sourcing driver. This driver
685 will detect lockups and provide a stack trace. This is a driver that
686 will only load on an HP ProLiant system with a minimum of iLO2 support.
687 To compile this driver as a module, choose M here: the module will be
690 config HPWDT_NMI_DECODING
691 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
692 depends on HP_WATCHDOG
695 When an NMI occurs this feature will make the necessary BIOS calls to
696 log the cause of the NMI.
699 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
702 This is a driver for National Semiconductor PC87307/PC97307 hardware
703 watchdog cards as found on the SC1200. This watchdog is mainly used
704 for power management purposes and can be used to power down the device
705 during inactivity periods (includes interrupt activity monitoring).
707 To compile this driver as a module, choose M here: the
708 module will be called sc1200wdt.
710 Most people will say N.
713 tristate "National Semiconductor SCx200 Watchdog"
714 depends on SCx200 && PCI
716 Enable the built-in watchdog timer support on the National
717 Semiconductor SCx200 processors.
719 If compiled as a module, it will be called scx200_wdt.
722 tristate "NS PC87413 watchdog"
725 This is the driver for the hardware watchdog on the PC87413 chipset
726 This watchdog simply watches your kernel to make sure it doesn't
727 freeze, and if it does, it reboots your computer after a certain
730 To compile this driver as a module, choose M here: the
731 module will be called pc87413_wdt.
733 Most people will say N.
736 tristate "nVidia TCO Timer/Watchdog"
737 depends on X86 && PCI
739 Hardware driver for the TCO timer built into the nVidia Hub family
740 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
741 watchdog timer that will reboot the machine after its second
742 expiration. The expiration time can be configured with the
743 "heartbeat" parameter.
745 On some motherboards the driver may fail to reset the chipset's
746 NO_REBOOT flag which prevents the watchdog from rebooting the
747 machine. If this is the case you will get a kernel message like
748 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
750 To compile this driver as a module, choose M here: the
751 module will be called nv_tco.
754 tristate "RDC R-321x SoC watchdog"
755 depends on X86_RDC321X
757 This is the driver for the built in hardware watchdog
758 in the RDC R-321x SoC.
760 To compile this driver as a module, choose M here: the
761 module will be called rdc321x_wdt.
764 tristate "SBC-60XX Watchdog Timer"
767 This driver can be used with the watchdog timer found on some
768 single board computers, namely the 6010 PII based computer.
769 It may well work with other cards. It reads port 0x443 to enable
770 and re-set the watchdog timer, and reads port 0x45 to disable
771 the watchdog. If you have a card that behave in similar ways,
772 you can probably make this driver work with your card as well.
774 You can compile this driver directly into the kernel, or use
775 it as a module. The module will be called sbc60xxwdt.
778 tristate "SBC8360 Watchdog Timer"
782 This is the driver for the hardware watchdog on the SBC8360 Single
783 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
785 To compile this driver as a module, choose M here: the
786 module will be called sbc8360.
788 Most people will say N.
791 tristate "SBC Nano 7240 Watchdog Timer"
792 depends on X86_32 && !UML
794 This is the driver for the hardware watchdog found on the IEI
795 single board computers EPIC Nano 7240 (and likely others). This
796 watchdog simply watches your kernel to make sure it doesn't freeze,
797 and if it does, it reboots your computer after a certain amount of
800 To compile this driver as a module, choose M here: the
801 module will be called sbc7240_wdt.
804 tristate "SMA CPU5 Watchdog"
808 To compile this driver as a module, choose M here: the
809 module will be called cpu5wdt.
811 config SMSC_SCH311X_WDT
812 tristate "SMSC SCH311X Watchdog Timer"
815 This is the driver for the hardware watchdog timer on the
816 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
817 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
820 To compile this driver as a module, choose M here: the
821 module will be called sch311x_wdt.
823 config SMSC37B787_WDT
824 tristate "Winbond SMsC37B787 Watchdog Timer"
827 This is the driver for the hardware watchdog component on the
828 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
829 from Vision Systems and maybe others.
831 This watchdog simply watches your kernel to make sure it doesn't
832 freeze, and if it does, it reboots your computer after a certain
835 Usually a userspace daemon will notify the kernel WDT driver that
836 userspace is still alive, at regular intervals.
838 To compile this driver as a module, choose M here: the
839 module will be called smsc37b787_wdt.
841 Most people will say N.
844 tristate "VIA Watchdog Timer"
845 depends on X86 && PCI
848 This is the driver for the hardware watchdog timer on VIA
849 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
851 To compile this driver as a module, choose M here; the module
852 will be called via_wdt.
854 Most people will say N.
857 tristate "W83627HF/W83627DHG Watchdog Timer"
860 This is the driver for the hardware watchdog on the W83627HF chipset
861 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
862 (and likely others). The driver also supports the W83627DHG chip.
863 This watchdog simply watches your kernel to make sure it doesn't
864 freeze, and if it does, it reboots your computer after a certain
867 To compile this driver as a module, choose M here: the
868 module will be called w83627hf_wdt.
870 Most people will say N.
873 tristate "W83697HF/W83697HG Watchdog Timer"
876 This is the driver for the hardware watchdog on the W83697HF/HG
877 chipset as used in Dedibox/VIA motherboards (and likely others).
878 This watchdog simply watches your kernel to make sure it doesn't
879 freeze, and if it does, it reboots your computer after a certain
882 To compile this driver as a module, choose M here: the
883 module will be called w83697hf_wdt.
885 Most people will say N.
888 tristate "W83697UG/W83697UF Watchdog Timer"
891 This is the driver for the hardware watchdog on the W83697UG/UF
892 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
893 This watchdog simply watches your kernel to make sure it doesn't
894 freeze, and if it does, it reboots your computer after a certain
897 To compile this driver as a module, choose M here: the
898 module will be called w83697ug_wdt.
900 Most people will say N.
903 tristate "W83877F (EMACS) Watchdog Timer"
906 This is the driver for the hardware watchdog on the W83877F chipset
907 as used in EMACS PC-104 motherboards (and likely others). This
908 watchdog simply watches your kernel to make sure it doesn't freeze,
909 and if it does, it reboots your computer after a certain amount of
912 To compile this driver as a module, choose M here: the
913 module will be called w83877f_wdt.
915 Most people will say N.
918 tristate "W83977F (PCM-5335) Watchdog Timer"
921 This is the driver for the hardware watchdog on the W83977F I/O chip
922 as used in AAEON's PCM-5335 SBC (and likely others). This
923 watchdog simply watches your kernel to make sure it doesn't freeze,
924 and if it does, it reboots your computer after a certain amount of
927 To compile this driver as a module, choose M here: the
928 module will be called w83977f_wdt.
931 tristate "ZF MachZ Watchdog"
934 If you are using a ZF Micro MachZ processor, say Y here, otherwise
935 N. This is the driver for the watchdog timer built-in on that
936 processor using ZF-Logic interface. This watchdog simply watches
937 your kernel to make sure it doesn't freeze, and if it does, it
938 reboots your computer after a certain amount of time.
940 To compile this driver as a module, choose M here: the
941 module will be called machzwd.
943 config SBC_EPX_C3_WATCHDOG
944 tristate "Winsystems SBC EPX-C3 watchdog"
947 This is the driver for the built-in watchdog timer on the EPX-C3
948 Single-board computer made by Winsystems, Inc.
950 *Note*: This hardware watchdog is not probeable and thus there
951 is no way to know if writing to its IO address will corrupt
952 your system or have any real effect. The only way to be sure
953 that this driver does what you want is to make sure you
954 are running it on an EPX-C3 from Winsystems with the watchdog
955 timer at IO address 0x1ee and 0x1ef. It will write to both those
956 IO ports. Basically, the assumption is made that if you compile
957 this driver into your kernel and/or load it as a module, that you
958 know what you are doing and that you are in fact running on an
961 To compile this driver as a module, choose M here: the
962 module will be called sbc_epx_c3.
968 config M54xx_WATCHDOG
969 tristate "MCF54xx watchdog support"
972 To compile this driver as a module, choose M here: the
973 module will be called m54xx_wdt.
975 # MicroBlaze Architecture
977 config XILINX_WATCHDOG
978 tristate "Xilinx Watchdog timer"
979 depends on MICROBLAZE
981 Watchdog driver for the xps_timebase_wdt ip core.
983 IMPORTANT: The xps_timebase_wdt parent must have the property
984 "clock-frequency" at device tree.
986 To compile this driver as a module, choose M here: the
987 module will be called of_xilinx_wdt.
992 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
995 Hardware driver for the built-in watchdog timer on the Atheros
996 AR71XX/AR724X/AR913X SoCs.
999 tristate "Broadcom BCM47xx Watchdog Timer"
1001 select WATCHDOG_CORE
1003 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1006 tristate "IDT RC32434 SoC Watchdog Timer"
1007 depends on MIKROTIK_RB532
1009 Hardware driver for the IDT RC32434 SoC built-in
1012 To compile this driver as a module, choose M here: the
1013 module will be called rc32434_wdt.
1016 tristate "Indy/I2 Hardware Watchdog"
1017 depends on SGI_HAS_INDYDOG
1019 Hardware driver for the Indy's/I2's watchdog. This is a
1020 watchdog timer that will reboot the machine after a 60 second
1021 timer expired and no process has written to /dev/watchdog during
1025 tristate "Ingenic jz4740 SoC hardware watchdog"
1026 depends on MACH_JZ4740
1027 select WATCHDOG_CORE
1029 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1032 tristate "MTX-1 Hardware Watchdog"
1033 depends on MIPS_MTX1
1035 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1036 will reboot the machine after a 100 seconds timer expired.
1039 tristate "PNX833x Hardware Watchdog"
1040 depends on SOC_PNX8335
1042 Hardware driver for the PNX833x's watchdog. This is a
1043 watchdog timer that will reboot the machine after a programmable
1044 timer has expired and no process has written to /dev/watchdog during
1048 tristate "Sibyte SoC hardware watchdog"
1051 Watchdog driver for the built in watchdog hardware in Sibyte
1052 SoC processors. There are apparently two watchdog timers
1053 on such processors; this driver supports only the first one,
1054 because currently Linux only supports exporting one watchdog
1057 To compile this driver as a loadable module, choose M here.
1058 The module will be called sb_wdog.
1061 tristate "TI AR7 Watchdog Timer"
1064 Hardware driver for the TI AR7 Watchdog Timer.
1067 tristate "Toshiba TXx9 Watchdog Timer"
1068 depends on CPU_TX39XX || CPU_TX49XX
1069 select WATCHDOG_CORE
1071 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1074 tristate "Cavium OCTEON SOC family Watchdog Timer"
1075 depends on CPU_CAVIUM_OCTEON
1077 select EXPORT_UASM if OCTEON_WDT = m
1079 Hardware driver for OCTEON's on chip watchdog timer.
1080 Enables the watchdog for all cores running Linux. It
1081 installs a NMI handler and pokes the watchdog based on an
1082 interrupt. On first expiration of the watchdog, the
1083 interrupt handler pokes it. The second expiration causes an
1084 NMI that prints a message. The third expiration causes a
1087 When userspace has /dev/watchdog open, no poking is done
1088 from the first interrupt, it is then only poked when the
1092 tristate "Broadcom BCM63xx hardware watchdog"
1095 Watchdog driver for the built in watchdog hardware in Broadcom
1098 To compile this driver as a loadable module, choose M here.
1099 The module will be called bcm63xx_wdt.
1102 tristate "Lantiq SoC watchdog"
1105 Hardware driver for the Lantiq SoC Watchdog Timer.
1107 # PARISC Architecture
1109 # POWERPC Architecture
1112 tristate "GE Watchdog Timer"
1115 Watchdog timer found in a number of GE single board computers.
1118 bool "MPC52xx Watchdog Timer"
1119 depends on PPC_MPC52xx
1121 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1124 tristate "MPC8xxx Platform Watchdog Timer"
1125 depends on PPC_8xx || PPC_83xx || PPC_86xx
1127 This driver is for a SoC level watchdog that exists on some
1128 Freescale PowerPC processors. So far this driver supports:
1133 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1136 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1140 tristate "PIKA FPGA Watchdog"
1144 This enables the watchdog in the PIKA FPGA. Currently used on
1148 tristate "PowerPC Book-E Watchdog Timer"
1149 depends on BOOKE || 4xx
1150 select WATCHDOG_CORE
1152 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1153 MPC85xx SOCs and the IBM PowerPC 440.
1155 Please see Documentation/watchdog/watchdog-api.txt for
1158 config BOOKE_WDT_DEFAULT_TIMEOUT
1159 int "PowerPC Book-E Watchdog Timer Default Timeout"
1160 depends on BOOKE_WDT
1161 default 38 if PPC_FSL_BOOK3E
1162 range 0 63 if PPC_FSL_BOOK3E
1163 default 3 if !PPC_FSL_BOOK3E
1164 range 0 3 if !PPC_FSL_BOOK3E
1166 Select the default watchdog timer period to be used by the PowerPC
1167 Book-E watchdog driver. A watchdog "event" occurs when the bit
1168 position represented by this number transitions from zero to one.
1170 For Freescale Book-E processors, this is a number between 0 and 63.
1171 For other Book-E processors, this is a number between 0 and 3.
1173 The value can be overridden by the wdt_period command-line parameter.
1175 # PPC64 Architecture
1177 config WATCHDOG_RTAS
1178 tristate "RTAS watchdog"
1181 This driver adds watchdog support for the RTAS watchdog.
1183 To compile this driver as a module, choose M here. The module
1184 will be called wdrtas.
1189 tristate "z/VM Watchdog Timer"
1192 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1193 provide a virtual watchdog timer to their guest that cause a
1194 user define Control Program command to be executed after a
1197 To compile this driver as a module, choose M here. The module
1198 will be called vmwatchdog.
1200 # SUPERH (sh + sh64) Architecture
1203 tristate "SuperH Watchdog"
1204 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1205 select WATCHDOG_CORE
1207 This driver adds watchdog support for the integrated watchdog in the
1208 SuperH processors. If you have one of these processors and wish
1209 to have watchdog support enabled, say Y, otherwise say N.
1211 As a side note, saying Y here will automatically boost HZ to 1000
1212 so that the timer has a chance to clear the overflow counter. On
1213 slower systems (such as the SH-2 and SH-3) this will likely yield
1214 some performance issues. As such, the WDT should be avoided here
1215 unless it is absolutely necessary.
1217 To compile this driver as a module, choose M here: the
1218 module will be called shwdt.
1220 # SPARC Architecture
1222 # SPARC64 Architecture
1224 config WATCHDOG_CP1XXX
1225 tristate "CP1XXX Hardware Watchdog support"
1226 depends on SPARC64 && PCI
1228 This is the driver for the hardware watchdog timers present on
1229 Sun Microsystems CompactPCI models CP1400 and CP1500.
1231 To compile this driver as a module, choose M here: the
1232 module will be called cpwatchdog.
1234 If you do not have a CompactPCI model CP1400 or CP1500, or
1235 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1236 you should say N to this option.
1239 tristate "RIO Hardware Watchdog support"
1240 depends on SPARC64 && PCI
1242 Say Y here to support the hardware watchdog capability on Sun RIO
1243 machines. The watchdog timeout period is normally one minute but
1244 can be changed with a boot-time parameter.
1246 # XTENSA Architecture
1251 tristate "Xen Watchdog support"
1254 Say Y here to support the hypervisor watchdog capability provided
1255 by Xen 4.0 and newer. The watchdog timeout period is normally one
1256 minute but can be changed with a boot-time parameter.
1259 tristate "UML watchdog"
1263 # ISA-based Watchdog Cards
1266 comment "ISA-based Watchdog Cards"
1270 tristate "Berkshire Products ISA-PC Watchdog"
1273 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1274 This card simply watches your kernel to make sure it doesn't freeze,
1275 and if it does, it reboots your computer after a certain amount of
1276 time. This driver is like the WDT501 driver but for different
1277 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1278 watchdog cards can be ordered from <http://www.berkprod.com/>.
1280 To compile this driver as a module, choose M here: the
1281 module will be called pcwd.
1283 Most people will say N.
1286 tristate "Mixcom Watchdog"
1289 This is a driver for the Mixcom hardware watchdog cards. This
1290 watchdog simply watches your kernel to make sure it doesn't freeze,
1291 and if it does, it reboots your computer after a certain amount of
1294 To compile this driver as a module, choose M here: the
1295 module will be called mixcomwd.
1297 Most people will say N.
1300 tristate "WDT Watchdog timer"
1303 If you have a WDT500P or WDT501P watchdog board, say Y here,
1304 otherwise N. It is not possible to probe for this board, which means
1305 that you have to inform the kernel about the IO port and IRQ that
1306 is needed (you can do this via the io and irq parameters)
1308 To compile this driver as a module, choose M here: the
1309 module will be called wdt.
1312 # PCI-based Watchdog Cards
1315 comment "PCI-based Watchdog Cards"
1318 config PCIPCWATCHDOG
1319 tristate "Berkshire Products PCI-PC Watchdog"
1322 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1323 This card simply watches your kernel to make sure it doesn't freeze,
1324 and if it does, it reboots your computer after a certain amount of
1325 time. The card can also monitor the internal temperature of the PC.
1326 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1328 To compile this driver as a module, choose M here: the
1329 module will be called pcwd_pci.
1331 Most people will say N.
1334 tristate "PCI-WDT500/501 Watchdog timer"
1337 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1339 If you have a PCI-WDT501 watchdog board then you can enable the
1340 temperature sensor by setting the type parameter to 501.
1342 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1343 can do this via the tachometer parameter. Only do this if you have a
1344 fan tachometer actually set up.
1346 To compile this driver as a module, choose M here: the
1347 module will be called wdt_pci.
1350 # USB-based Watchdog Cards
1353 comment "USB-based Watchdog Cards"
1356 config USBPCWATCHDOG
1357 tristate "Berkshire Products USB-PC Watchdog"
1360 This is the driver for the Berkshire Products USB-PC Watchdog card.
1361 This card simply watches your kernel to make sure it doesn't freeze,
1362 and if it does, it reboots your computer after a certain amount of
1363 time. The card can also monitor the internal temperature of the PC.
1364 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1366 To compile this driver as a module, choose M here: the
1367 module will be called pcwd_usb.
1369 Most people will say N.