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.
111 tristate "RK29 watchdog"
113 Watchdog timer embedded into RK29xx chips. This will reboot your
114 system when the timeout is reached.
116 config RK29_FEED_DOG_BY_INTE
117 bool "feed watchdog by interrupt"
118 depends on RK29_WATCHDOG
120 config RK29_WATCHDOG_ATBOOT
121 bool "start watchdog at system boot"
122 depends on RK29_WATCHDOG
124 config RK29_WATCHDOG_DEFAULT_TIME
125 int "set watchdog time out value (unit second)"
126 depends on RK29_WATCHDOG
128 the real time out value is two times more than the setting value
130 config RK29_WATCHDOG_DEBUG
131 bool "enable watchdog debug"
132 depends on RK29_WATCHDOG
134 config ARM_SP805_WATCHDOG
135 tristate "ARM SP805 Watchdog"
136 depends on ARM && ARM_AMBA
139 ARM Primecell SP805 Watchdog timer. This will reboot your system when
140 the timeout is reached.
142 config AT91RM9200_WATCHDOG
143 tristate "AT91RM9200 watchdog"
144 depends on ARCH_AT91RM9200
146 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
147 system when the timeout is reached.
149 config AT91SAM9X_WATCHDOG
150 tristate "AT91SAM9X / AT91CAP9 watchdog"
151 depends on ARCH_AT91 && !ARCH_AT91RM9200
154 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
155 reboot your system when the timeout is reached.
157 config 21285_WATCHDOG
158 tristate "DC21285 watchdog"
159 depends on FOOTBRIDGE
161 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
162 here if you wish to use this. Alternatively say M to compile the
163 driver as a module, which will be called wdt285.
165 This driver does not work on all machines. In particular, early CATS
166 boards have hardware problems that will cause the machine to simply
167 lock up if the watchdog fires.
169 "If in doubt, leave it out" - say N.
172 tristate "NetWinder WB83C977 watchdog"
173 depends on FOOTBRIDGE && ARCH_NETWINDER
175 Say Y here to include support for the WB977 watchdog included in
176 NetWinder machines. Alternatively say M to compile the driver as
177 a module, which will be called wdt977.
179 Not sure? It's safe to say N.
181 config IXP4XX_WATCHDOG
182 tristate "IXP4xx Watchdog"
183 depends on ARCH_IXP4XX
185 Say Y here if to include support for the watchdog timer
186 in the Intel IXP4xx network processors. This driver can
187 be built as a module by choosing M. The module will
188 be called ixp4xx_wdt.
190 Note: The internal IXP4xx watchdog does a soft CPU reset
191 which doesn't reset any peripherals. There are circumstances
192 where the watchdog will fail to reset the board correctly
193 (e.g., if the boot ROM is in an unreadable state).
195 Say N if you are unsure.
197 config KS8695_WATCHDOG
198 tristate "KS8695 watchdog"
199 depends on ARCH_KS8695
201 Watchdog timer embedded into KS8695 processor. This will reboot your
202 system when the timeout is reached.
204 config HAVE_S3C2410_WATCHDOG
207 This will include watchdog timer support for Samsung SoCs. If
208 you want to include watchdog support for any machine, kindly
209 select this in the respective mach-XXXX/Kconfig file.
211 config S3C2410_WATCHDOG
212 tristate "S3C2410 Watchdog"
213 depends on HAVE_S3C2410_WATCHDOG
216 Watchdog timer block in the Samsung SoCs. This will reboot
217 the system when the timer expires with the watchdog enabled.
219 The driver is limited by the speed of the system's PCLK
220 signal, so with reasonably fast systems (PCLK around 50-66MHz)
221 then watchdog intervals of over approximately 20seconds are
224 The driver can be built as a module by choosing M, and will
225 be called s3c2410_wdt
227 config SA1100_WATCHDOG
228 tristate "SA1100/PXA2xx watchdog"
229 depends on ARCH_SA1100 || ARCH_PXA
231 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
232 reboot your system when timeout is reached.
234 NOTE: once enabled, this timer cannot be disabled.
236 To compile this driver as a module, choose M here: the
237 module will be called sa1100_wdt.
240 tristate "Synopsys DesignWare watchdog"
241 depends on ARM && HAVE_CLK
243 Say Y here if to include support for the Synopsys DesignWare
244 watchdog timer found in many ARM chips.
245 To compile this driver as a module, choose M here: the
246 module will be called dw_wdt.
248 config MPCORE_WATCHDOG
249 tristate "MPcore watchdog"
250 depends on HAVE_ARM_TWD
252 Watchdog timer embedded into the MPcore system.
254 To compile this driver as a module, choose M here: the
255 module will be called mpcore_wdt.
257 config EP93XX_WATCHDOG
258 tristate "EP93xx Watchdog"
259 depends on ARCH_EP93XX
262 Say Y here if to include support for the watchdog timer
263 embedded in the Cirrus Logic EP93xx family of devices.
265 To compile this driver as a module, choose M here: the
266 module will be called ep93xx_wdt.
269 tristate "OMAP Watchdog"
270 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
273 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
274 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
276 config PNX4008_WATCHDOG
277 tristate "LPC32XX Watchdog"
278 depends on ARCH_LPC32XX
281 Say Y here if to include support for the watchdog timer
282 in the LPC32XX processor.
283 This driver can be built as a module by choosing M. The module
284 will be called pnx4008_wdt.
286 Say N if you are unsure.
289 tristate "IOP Watchdog"
291 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
293 Say Y here if to include support for the watchdog timer
294 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
295 be built as a module by choosing M. The module will
298 Note: The IOP13XX watchdog does an Internal Bus Reset which will
299 affect both cores and the peripherals of the IOP. The ATU-X
300 and/or ATUe configuration registers will remain intact, but if
301 operating as an Root Complex and/or Central Resource, the PCI-X
302 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
304 config DAVINCI_WATCHDOG
305 tristate "DaVinci watchdog"
306 depends on ARCH_DAVINCI
308 Say Y here if to include support for the watchdog timer
309 in the DaVinci DM644x/DM646x processors.
310 To compile this driver as a module, choose M here: the
311 module will be called davinci_wdt.
313 NOTE: once enabled, this timer cannot be disabled.
314 Say N if you are unsure.
316 config ORION_WATCHDOG
317 tristate "Orion watchdog"
318 depends on ARCH_ORION5X || ARCH_KIRKWOOD
321 Say Y here if to include support for the watchdog timer
322 in the Marvell Orion5x and Kirkwood ARM SoCs.
323 To compile this driver as a module, choose M here: the
324 module will be called orion_wdt.
326 config COH901327_WATCHDOG
327 bool "ST-Ericsson COH 901 327 watchdog"
329 default y if MACH_U300
332 Say Y here to include Watchdog timer support for the
333 watchdog embedded into the ST-Ericsson U300 series platforms.
334 This watchdog is used to reset the system and thus cannot be
335 compiled as a module.
337 config TWL4030_WATCHDOG
338 tristate "TWL4030 Watchdog"
339 depends on TWL4030_CORE
342 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
343 watchdog timer support for TWL4030 chips.
345 config STMP3XXX_RTC_WATCHDOG
346 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
347 depends on RTC_DRV_STMP
350 Say Y here to include support for the watchdog timer inside
351 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
352 To compile this driver as a module, choose M here: the
353 module will be called stmp3xxx_rtc_wdt.
355 config NUC900_WATCHDOG
356 tristate "Nuvoton NUC900 watchdog"
357 depends on ARCH_W90X900
359 Say Y here if to include support for the watchdog timer
360 for the Nuvoton NUC900 series SoCs.
361 To compile this driver as a module, choose M here: the
362 module will be called nuc900_wdt.
364 config TS72XX_WATCHDOG
365 tristate "TS-72XX SBC Watchdog"
366 depends on MACH_TS72XX
368 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
369 watchdog timer implemented in a external CPLD chip. Say Y here
370 if you want to support for the watchdog timer on TS-72XX boards.
372 To compile this driver as a module, choose M here: the
373 module will be called ts72xx_wdt.
375 config MAX63XX_WATCHDOG
376 tristate "Max63xx watchdog"
377 depends on ARM && HAS_IOMEM
380 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
383 tristate "IMX2+ Watchdog"
386 This is the driver for the hardware watchdog
387 on the Freescale IMX2 and later processors.
388 If you have one of these processors and wish to have
389 watchdog support enabled, say Y, otherwise say N.
391 To compile this driver as a module, choose M here: the
392 module will be called imx2_wdt.
394 config UX500_WATCHDOG
395 tristate "ST-Ericsson Ux500 watchdog"
396 depends on MFD_DB8500_PRCMU
400 Say Y here to include Watchdog timer support for the watchdog
401 existing in the prcmu of ST-Ericsson Ux500 series platforms.
403 To compile this driver as a module, choose M here: the
404 module will be called ux500_wdt.
407 tristate "Retu watchdog"
411 Retu watchdog driver for Nokia Internet Tablets (770, N800,
412 N810). At least on N800 the watchdog cannot be disabled, so
413 this driver is essential and you should enable it.
415 To compile this driver as a module, choose M here: the
416 module will be called retu_wdt.
420 config AT32AP700X_WDT
421 tristate "AT32AP700x watchdog"
422 depends on CPU_AT32AP700X
424 Watchdog timer embedded into AT32AP700x devices. This will reboot
425 your system when the timeout is reached.
427 # BLACKFIN Architecture
430 tristate "Blackfin On-Chip Watchdog Timer"
433 If you say yes here you will get support for the Blackfin On-Chip
434 Watchdog Timer. If you have one of these processors and wish to
435 have watchdog support enabled, say Y, otherwise say N.
437 To compile this driver as a module, choose M here: the
438 module will be called bfin_wdt.
446 # X86 (i386 + ia64 + x86_64) Architecture
449 tristate "Acquire SBC Watchdog Timer"
452 This is the driver for the hardware watchdog on Single Board
453 Computers produced by Acquire Inc (and others). This watchdog
454 simply watches your kernel to make sure it doesn't freeze, and if
455 it does, it reboots your computer after a certain amount of time.
457 To compile this driver as a module, choose M here: the
458 module will be called acquirewdt.
460 Most people will say N.
463 tristate "Advantech SBC Watchdog Timer"
466 If you are configuring a Linux kernel for the Advantech single-board
467 computer, say `Y' here to support its built-in watchdog timer
468 feature. More information can be found at
469 <http://www.advantech.com.tw/products/>
472 tristate "ALi M1535 PMU Watchdog Timer"
473 depends on X86 && PCI
475 This is the driver for the hardware watchdog on the ALi M1535 PMU.
477 To compile this driver as a module, choose M here: the
478 module will be called alim1535_wdt.
480 Most people will say N.
483 tristate "ALi M7101 PMU Computer Watchdog"
486 This is the driver for the hardware watchdog on the ALi M7101 PMU
487 as used in the x86 Cobalt servers and also found in some
488 SPARC Netra servers too.
490 To compile this driver as a module, choose M here: the
491 module will be called alim7101_wdt.
493 Most people will say N.
496 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
499 This is the driver for the hardware watchdog on the Fintek
500 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
502 You can compile this driver directly into the kernel, or use
503 it as a module. The module will be called f71808e_wdt.
506 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
507 depends on X86 && PCI
509 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
510 (Total Cost of Ownership) timer is a watchdog timer that will reboot
511 the machine after its expiration. The expiration time can be
512 configured with the "heartbeat" parameter.
514 To compile this driver as a module, choose M here: the
515 module will be called sp5100_tco.
518 tristate "AMD Geode CS5535/CS5536 Watchdog"
519 depends on CS5535_MFGPT
521 This driver enables a watchdog capability built into the
522 CS5535/CS5536 companion chips for the AMD Geode GX and LX
523 processors. This watchdog watches your kernel to make sure
524 it doesn't freeze, and if it does, it reboots your computer after
525 a certain amount of time.
527 You can compile this driver directly into the kernel, or use
528 it as a module. The module will be called geodewdt.
531 tristate "AMD Elan SC520 processor Watchdog"
534 This is the driver for the hardware watchdog built in to the
535 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
536 This watchdog simply watches your kernel to make sure it doesn't
537 freeze, and if it does, it reboots your computer after a certain
540 You can compile this driver directly into the kernel, or use
541 it as a module. The module will be called sc520_wdt.
543 config SBC_FITPC2_WATCHDOG
544 tristate "Compulab SBC-FITPC2 watchdog"
547 This is the driver for the built-in watchdog timer on the fit-PC2,
548 fit-PC2i, CM-iAM single-board computers made by Compulab.
550 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
551 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
553 Entering BIOS setup temporary disables watchdog operation regardless to current state,
554 so system will not be restarted while user in BIOS setup.
556 Once watchdog was enabled the system will be restarted every
557 "Watchdog Timer Value" period, so to prevent it user can restart or
558 disable the watchdog.
560 To compile this driver as a module, choose M here: the
561 module will be called sbc_fitpc2_wdt.
563 Most people will say N.
566 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
569 Enable support for the watchdog timer on the Eurotech CPU-1220 and
570 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
571 information are at <http://www.eurotech.it/>.
574 tristate "IB700 SBC Watchdog Timer"
577 This is the driver for the hardware watchdog on the IB700 Single
578 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
579 simply watches your kernel to make sure it doesn't freeze, and if
580 it does, it reboots your computer after a certain amount of time.
582 This driver is like the WDT501 driver but for slightly different hardware.
584 To compile this driver as a module, choose M here: the
585 module will be called ib700wdt.
587 Most people will say N.
590 tristate "IBM Automatic Server Restart"
593 This is the driver for the IBM Automatic Server Restart watchdog
594 timer built-in into some eServer xSeries machines.
596 To compile this driver as a module, choose M here: the
597 module will be called ibmasr.
600 tristate "ICP Single Board Computer Watchdog Timer"
603 This is a driver for the hardware watchdog on the ICP Single
604 Board Computer. This driver is working on (at least) the following
605 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
607 To compile this driver as a module, choose M here: the
608 module will be called wafer5823wdt.
611 tristate "Intel 6300ESB Timer/Watchdog"
614 Hardware driver for the watchdog timer built into the Intel
615 6300ESB controller hub.
617 To compile this driver as a module, choose M here: the
618 module will be called i6300esb.
621 tristate "Intel Atom E6xx Watchdog"
622 depends on X86 && PCI
627 Hardware driver for the watchdog timer built into the Intel
628 Atom E6XX (TunnelCreek) processor.
630 To compile this driver as a module, choose M here: the
631 module will be called ie6xx_wdt.
633 config INTEL_SCU_WATCHDOG
634 bool "Intel SCU Watchdog for Mobile Platforms"
635 depends on X86_INTEL_MID
637 Hardware driver for the watchdog time built into the Intel SCU
638 for Intel Mobile Platforms.
640 To compile this driver as a module, choose M here.
643 tristate "Intel TCO Timer/Watchdog"
644 depends on (X86 || IA64) && PCI
648 Hardware driver for the intel TCO timer based watchdog devices.
649 These drivers are included in the Intel 82801 I/O Controller
650 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
653 The TCO (Total Cost of Ownership) timer is a watchdog timer
654 that will reboot the machine after its second expiration. The
655 expiration time can be configured with the "heartbeat" parameter.
657 On some motherboards the driver may fail to reset the chipset's
658 NO_REBOOT flag which prevents the watchdog from rebooting the
659 machine. If this is the case you will get a kernel message like
660 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
662 To compile this driver as a module, choose M here: the
663 module will be called iTCO_wdt.
665 config ITCO_VENDOR_SUPPORT
666 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
669 Add vendor specific support to the intel TCO timer based watchdog
670 devices. At this moment we only have additional support for some
671 SuperMicro Inc. motherboards.
674 tristate "IT8712F (Smart Guardian) Watchdog Timer"
677 This is the driver for the built-in watchdog timer on the IT8712F
678 Super I/0 chipset used on many motherboards.
680 If the driver does not work, then make sure that the game port in
683 To compile this driver as a module, choose M here: the
684 module will be called it8712f_wdt.
687 tristate "IT87 Watchdog Timer"
690 This is the driver for the hardware watchdog on the ITE IT8702,
691 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
694 If the driver does not work, then make sure that the game port in
697 This watchdog simply watches your kernel to make sure it doesn't
698 freeze, and if it does, it reboots your computer after a certain
701 To compile this driver as a module, choose M here: the module will
705 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
706 depends on X86 && PCI
708 A software monitoring watchdog and NMI sourcing driver. This driver
709 will detect lockups and provide a stack trace. This is a driver that
710 will only load on an HP ProLiant system with a minimum of iLO2 support.
711 To compile this driver as a module, choose M here: the module will be
714 config HPWDT_NMI_DECODING
715 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
716 depends on HP_WATCHDOG
719 When an NMI occurs this feature will make the necessary BIOS calls to
720 log the cause of the NMI.
723 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
726 This is a driver for National Semiconductor PC87307/PC97307 hardware
727 watchdog cards as found on the SC1200. This watchdog is mainly used
728 for power management purposes and can be used to power down the device
729 during inactivity periods (includes interrupt activity monitoring).
731 To compile this driver as a module, choose M here: the
732 module will be called sc1200wdt.
734 Most people will say N.
737 tristate "National Semiconductor SCx200 Watchdog"
738 depends on SCx200 && PCI
740 Enable the built-in watchdog timer support on the National
741 Semiconductor SCx200 processors.
743 If compiled as a module, it will be called scx200_wdt.
746 tristate "NS PC87413 watchdog"
749 This is the driver for the hardware watchdog on the PC87413 chipset
750 This watchdog simply watches your kernel to make sure it doesn't
751 freeze, and if it does, it reboots your computer after a certain
754 To compile this driver as a module, choose M here: the
755 module will be called pc87413_wdt.
757 Most people will say N.
760 tristate "nVidia TCO Timer/Watchdog"
761 depends on X86 && PCI
763 Hardware driver for the TCO timer built into the nVidia Hub family
764 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
765 watchdog timer that will reboot the machine after its second
766 expiration. The expiration time can be configured with the
767 "heartbeat" parameter.
769 On some motherboards the driver may fail to reset the chipset's
770 NO_REBOOT flag which prevents the watchdog from rebooting the
771 machine. If this is the case you will get a kernel message like
772 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
774 To compile this driver as a module, choose M here: the
775 module will be called nv_tco.
778 tristate "RDC R-321x SoC watchdog"
779 depends on X86_RDC321X
781 This is the driver for the built in hardware watchdog
782 in the RDC R-321x SoC.
784 To compile this driver as a module, choose M here: the
785 module will be called rdc321x_wdt.
788 tristate "SBC-60XX Watchdog Timer"
791 This driver can be used with the watchdog timer found on some
792 single board computers, namely the 6010 PII based computer.
793 It may well work with other cards. It reads port 0x443 to enable
794 and re-set the watchdog timer, and reads port 0x45 to disable
795 the watchdog. If you have a card that behave in similar ways,
796 you can probably make this driver work with your card as well.
798 You can compile this driver directly into the kernel, or use
799 it as a module. The module will be called sbc60xxwdt.
802 tristate "SBC8360 Watchdog Timer"
806 This is the driver for the hardware watchdog on the SBC8360 Single
807 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
809 To compile this driver as a module, choose M here: the
810 module will be called sbc8360.
812 Most people will say N.
815 tristate "SBC Nano 7240 Watchdog Timer"
816 depends on X86_32 && !UML
818 This is the driver for the hardware watchdog found on the IEI
819 single board computers EPIC Nano 7240 (and likely others). This
820 watchdog simply watches your kernel to make sure it doesn't freeze,
821 and if it does, it reboots your computer after a certain amount of
824 To compile this driver as a module, choose M here: the
825 module will be called sbc7240_wdt.
828 tristate "SMA CPU5 Watchdog"
832 To compile this driver as a module, choose M here: the
833 module will be called cpu5wdt.
835 config SMSC_SCH311X_WDT
836 tristate "SMSC SCH311X Watchdog Timer"
839 This is the driver for the hardware watchdog timer on the
840 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
841 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
844 To compile this driver as a module, choose M here: the
845 module will be called sch311x_wdt.
847 config SMSC37B787_WDT
848 tristate "Winbond SMsC37B787 Watchdog Timer"
851 This is the driver for the hardware watchdog component on the
852 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
853 from Vision Systems and maybe others.
855 This watchdog simply watches your kernel to make sure it doesn't
856 freeze, and if it does, it reboots your computer after a certain
859 Usually a userspace daemon will notify the kernel WDT driver that
860 userspace is still alive, at regular intervals.
862 To compile this driver as a module, choose M here: the
863 module will be called smsc37b787_wdt.
865 Most people will say N.
868 tristate "VIA Watchdog Timer"
869 depends on X86 && PCI
872 This is the driver for the hardware watchdog timer on VIA
873 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
875 To compile this driver as a module, choose M here; the module
876 will be called via_wdt.
878 Most people will say N.
881 tristate "W83627HF/W83627DHG Watchdog Timer"
884 This is the driver for the hardware watchdog on the W83627HF chipset
885 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
886 (and likely others). The driver also supports the W83627DHG chip.
887 This watchdog simply watches your kernel to make sure it doesn't
888 freeze, and if it does, it reboots your computer after a certain
891 To compile this driver as a module, choose M here: the
892 module will be called w83627hf_wdt.
894 Most people will say N.
897 tristate "W83697HF/W83697HG Watchdog Timer"
900 This is the driver for the hardware watchdog on the W83697HF/HG
901 chipset as used in Dedibox/VIA motherboards (and likely others).
902 This watchdog simply watches your kernel to make sure it doesn't
903 freeze, and if it does, it reboots your computer after a certain
906 To compile this driver as a module, choose M here: the
907 module will be called w83697hf_wdt.
909 Most people will say N.
912 tristate "W83697UG/W83697UF Watchdog Timer"
915 This is the driver for the hardware watchdog on the W83697UG/UF
916 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
917 This watchdog simply watches your kernel to make sure it doesn't
918 freeze, and if it does, it reboots your computer after a certain
921 To compile this driver as a module, choose M here: the
922 module will be called w83697ug_wdt.
924 Most people will say N.
927 tristate "W83877F (EMACS) Watchdog Timer"
930 This is the driver for the hardware watchdog on the W83877F chipset
931 as used in EMACS PC-104 motherboards (and likely others). This
932 watchdog simply watches your kernel to make sure it doesn't freeze,
933 and if it does, it reboots your computer after a certain amount of
936 To compile this driver as a module, choose M here: the
937 module will be called w83877f_wdt.
939 Most people will say N.
942 tristate "W83977F (PCM-5335) Watchdog Timer"
945 This is the driver for the hardware watchdog on the W83977F I/O chip
946 as used in AAEON's PCM-5335 SBC (and likely others). This
947 watchdog simply watches your kernel to make sure it doesn't freeze,
948 and if it does, it reboots your computer after a certain amount of
951 To compile this driver as a module, choose M here: the
952 module will be called w83977f_wdt.
955 tristate "ZF MachZ Watchdog"
958 If you are using a ZF Micro MachZ processor, say Y here, otherwise
959 N. This is the driver for the watchdog timer built-in on that
960 processor using ZF-Logic interface. This watchdog simply watches
961 your kernel to make sure it doesn't freeze, and if it does, it
962 reboots your computer after a certain amount of time.
964 To compile this driver as a module, choose M here: the
965 module will be called machzwd.
967 config SBC_EPX_C3_WATCHDOG
968 tristate "Winsystems SBC EPX-C3 watchdog"
971 This is the driver for the built-in watchdog timer on the EPX-C3
972 Single-board computer made by Winsystems, Inc.
974 *Note*: This hardware watchdog is not probeable and thus there
975 is no way to know if writing to its IO address will corrupt
976 your system or have any real effect. The only way to be sure
977 that this driver does what you want is to make sure you
978 are running it on an EPX-C3 from Winsystems with the watchdog
979 timer at IO address 0x1ee and 0x1ef. It will write to both those
980 IO ports. Basically, the assumption is made that if you compile
981 this driver into your kernel and/or load it as a module, that you
982 know what you are doing and that you are in fact running on an
985 To compile this driver as a module, choose M here: the
986 module will be called sbc_epx_c3.
992 config M54xx_WATCHDOG
993 tristate "MCF54xx watchdog support"
996 To compile this driver as a module, choose M here: the
997 module will be called m54xx_wdt.
999 # MicroBlaze Architecture
1001 config XILINX_WATCHDOG
1002 tristate "Xilinx Watchdog timer"
1003 depends on MICROBLAZE
1005 Watchdog driver for the xps_timebase_wdt ip core.
1007 IMPORTANT: The xps_timebase_wdt parent must have the property
1008 "clock-frequency" at device tree.
1010 To compile this driver as a module, choose M here: the
1011 module will be called of_xilinx_wdt.
1016 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1019 Hardware driver for the built-in watchdog timer on the Atheros
1020 AR71XX/AR724X/AR913X SoCs.
1023 tristate "Broadcom BCM47xx Watchdog Timer"
1025 select WATCHDOG_CORE
1027 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1030 tristate "IDT RC32434 SoC Watchdog Timer"
1031 depends on MIKROTIK_RB532
1033 Hardware driver for the IDT RC32434 SoC built-in
1036 To compile this driver as a module, choose M here: the
1037 module will be called rc32434_wdt.
1040 tristate "Indy/I2 Hardware Watchdog"
1041 depends on SGI_HAS_INDYDOG
1043 Hardware driver for the Indy's/I2's watchdog. This is a
1044 watchdog timer that will reboot the machine after a 60 second
1045 timer expired and no process has written to /dev/watchdog during
1049 tristate "Ingenic jz4740 SoC hardware watchdog"
1050 depends on MACH_JZ4740
1051 select WATCHDOG_CORE
1053 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1056 tristate "MTX-1 Hardware Watchdog"
1057 depends on MIPS_MTX1
1059 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1060 will reboot the machine after a 100 seconds timer expired.
1063 tristate "PNX833x Hardware Watchdog"
1064 depends on SOC_PNX8335
1066 Hardware driver for the PNX833x's watchdog. This is a
1067 watchdog timer that will reboot the machine after a programmable
1068 timer has expired and no process has written to /dev/watchdog during
1072 tristate "Sibyte SoC hardware watchdog"
1075 Watchdog driver for the built in watchdog hardware in Sibyte
1076 SoC processors. There are apparently two watchdog timers
1077 on such processors; this driver supports only the first one,
1078 because currently Linux only supports exporting one watchdog
1081 To compile this driver as a loadable module, choose M here.
1082 The module will be called sb_wdog.
1085 tristate "TI AR7 Watchdog Timer"
1088 Hardware driver for the TI AR7 Watchdog Timer.
1091 tristate "Toshiba TXx9 Watchdog Timer"
1092 depends on CPU_TX39XX || CPU_TX49XX
1093 select WATCHDOG_CORE
1095 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1098 tristate "Cavium OCTEON SOC family Watchdog Timer"
1099 depends on CPU_CAVIUM_OCTEON
1101 select EXPORT_UASM if OCTEON_WDT = m
1103 Hardware driver for OCTEON's on chip watchdog timer.
1104 Enables the watchdog for all cores running Linux. It
1105 installs a NMI handler and pokes the watchdog based on an
1106 interrupt. On first expiration of the watchdog, the
1107 interrupt handler pokes it. The second expiration causes an
1108 NMI that prints a message. The third expiration causes a
1111 When userspace has /dev/watchdog open, no poking is done
1112 from the first interrupt, it is then only poked when the
1116 tristate "Broadcom BCM63xx hardware watchdog"
1119 Watchdog driver for the built in watchdog hardware in Broadcom
1122 To compile this driver as a loadable module, choose M here.
1123 The module will be called bcm63xx_wdt.
1126 tristate "Lantiq SoC watchdog"
1129 Hardware driver for the Lantiq SoC Watchdog Timer.
1131 # PARISC Architecture
1133 # POWERPC Architecture
1136 tristate "GE Watchdog Timer"
1139 Watchdog timer found in a number of GE single board computers.
1142 bool "MPC52xx Watchdog Timer"
1143 depends on PPC_MPC52xx
1145 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1148 tristate "MPC8xxx Platform Watchdog Timer"
1149 depends on PPC_8xx || PPC_83xx || PPC_86xx
1151 This driver is for a SoC level watchdog that exists on some
1152 Freescale PowerPC processors. So far this driver supports:
1157 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1160 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1164 tristate "PIKA FPGA Watchdog"
1168 This enables the watchdog in the PIKA FPGA. Currently used on
1172 tristate "PowerPC Book-E Watchdog Timer"
1173 depends on BOOKE || 4xx
1174 select WATCHDOG_CORE
1176 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1177 MPC85xx SOCs and the IBM PowerPC 440.
1179 Please see Documentation/watchdog/watchdog-api.txt for
1182 config BOOKE_WDT_DEFAULT_TIMEOUT
1183 int "PowerPC Book-E Watchdog Timer Default Timeout"
1184 depends on BOOKE_WDT
1185 default 38 if PPC_FSL_BOOK3E
1186 range 0 63 if PPC_FSL_BOOK3E
1187 default 3 if !PPC_FSL_BOOK3E
1188 range 0 3 if !PPC_FSL_BOOK3E
1190 Select the default watchdog timer period to be used by the PowerPC
1191 Book-E watchdog driver. A watchdog "event" occurs when the bit
1192 position represented by this number transitions from zero to one.
1194 For Freescale Book-E processors, this is a number between 0 and 63.
1195 For other Book-E processors, this is a number between 0 and 3.
1197 The value can be overridden by the wdt_period command-line parameter.
1199 # PPC64 Architecture
1201 config WATCHDOG_RTAS
1202 tristate "RTAS watchdog"
1205 This driver adds watchdog support for the RTAS watchdog.
1207 To compile this driver as a module, choose M here. The module
1208 will be called wdrtas.
1213 tristate "z/VM Watchdog Timer"
1216 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1217 provide a virtual watchdog timer to their guest that cause a
1218 user define Control Program command to be executed after a
1221 To compile this driver as a module, choose M here. The module
1222 will be called vmwatchdog.
1224 # SUPERH (sh + sh64) Architecture
1227 tristate "SuperH Watchdog"
1228 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1229 select WATCHDOG_CORE
1231 This driver adds watchdog support for the integrated watchdog in the
1232 SuperH processors. If you have one of these processors and wish
1233 to have watchdog support enabled, say Y, otherwise say N.
1235 As a side note, saying Y here will automatically boost HZ to 1000
1236 so that the timer has a chance to clear the overflow counter. On
1237 slower systems (such as the SH-2 and SH-3) this will likely yield
1238 some performance issues. As such, the WDT should be avoided here
1239 unless it is absolutely necessary.
1241 To compile this driver as a module, choose M here: the
1242 module will be called shwdt.
1244 # SPARC Architecture
1246 # SPARC64 Architecture
1248 config WATCHDOG_CP1XXX
1249 tristate "CP1XXX Hardware Watchdog support"
1250 depends on SPARC64 && PCI
1252 This is the driver for the hardware watchdog timers present on
1253 Sun Microsystems CompactPCI models CP1400 and CP1500.
1255 To compile this driver as a module, choose M here: the
1256 module will be called cpwatchdog.
1258 If you do not have a CompactPCI model CP1400 or CP1500, or
1259 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1260 you should say N to this option.
1263 tristate "RIO Hardware Watchdog support"
1264 depends on SPARC64 && PCI
1266 Say Y here to support the hardware watchdog capability on Sun RIO
1267 machines. The watchdog timeout period is normally one minute but
1268 can be changed with a boot-time parameter.
1270 # XTENSA Architecture
1275 tristate "Xen Watchdog support"
1278 Say Y here to support the hypervisor watchdog capability provided
1279 by Xen 4.0 and newer. The watchdog timeout period is normally one
1280 minute but can be changed with a boot-time parameter.
1283 tristate "UML watchdog"
1287 # ISA-based Watchdog Cards
1290 comment "ISA-based Watchdog Cards"
1294 tristate "Berkshire Products ISA-PC Watchdog"
1297 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1298 This card simply watches your kernel to make sure it doesn't freeze,
1299 and if it does, it reboots your computer after a certain amount of
1300 time. This driver is like the WDT501 driver but for different
1301 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1302 watchdog cards can be ordered from <http://www.berkprod.com/>.
1304 To compile this driver as a module, choose M here: the
1305 module will be called pcwd.
1307 Most people will say N.
1310 tristate "Mixcom Watchdog"
1313 This is a driver for the Mixcom hardware watchdog cards. This
1314 watchdog simply watches your kernel to make sure it doesn't freeze,
1315 and if it does, it reboots your computer after a certain amount of
1318 To compile this driver as a module, choose M here: the
1319 module will be called mixcomwd.
1321 Most people will say N.
1324 tristate "WDT Watchdog timer"
1327 If you have a WDT500P or WDT501P watchdog board, say Y here,
1328 otherwise N. It is not possible to probe for this board, which means
1329 that you have to inform the kernel about the IO port and IRQ that
1330 is needed (you can do this via the io and irq parameters)
1332 To compile this driver as a module, choose M here: the
1333 module will be called wdt.
1336 # PCI-based Watchdog Cards
1339 comment "PCI-based Watchdog Cards"
1342 config PCIPCWATCHDOG
1343 tristate "Berkshire Products PCI-PC Watchdog"
1346 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1347 This card simply watches your kernel to make sure it doesn't freeze,
1348 and if it does, it reboots your computer after a certain amount of
1349 time. The card can also monitor the internal temperature of the PC.
1350 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1352 To compile this driver as a module, choose M here: the
1353 module will be called pcwd_pci.
1355 Most people will say N.
1358 tristate "PCI-WDT500/501 Watchdog timer"
1361 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1363 If you have a PCI-WDT501 watchdog board then you can enable the
1364 temperature sensor by setting the type parameter to 501.
1366 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1367 can do this via the tachometer parameter. Only do this if you have a
1368 fan tachometer actually set up.
1370 To compile this driver as a module, choose M here: the
1371 module will be called wdt_pci.
1374 # USB-based Watchdog Cards
1377 comment "USB-based Watchdog Cards"
1380 config USBPCWATCHDOG
1381 tristate "Berkshire Products USB-PC Watchdog"
1384 This is the driver for the Berkshire Products USB-PC Watchdog card.
1385 This card simply watches your kernel to make sure it doesn't freeze,
1386 and if it does, it reboots your computer after a certain amount of
1387 time. The card can also monitor the internal temperature of the PC.
1388 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1390 To compile this driver as a module, choose M here: the
1391 module will be called pcwd_usb.
1393 Most people will say N.