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"
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
129 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
130 reboot your system when the timeout is reached.
132 config 21285_WATCHDOG
133 tristate "DC21285 watchdog"
134 depends on FOOTBRIDGE
136 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
137 here if you wish to use this. Alternatively say M to compile the
138 driver as a module, which will be called wdt285.
140 This driver does not work on all machines. In particular, early CATS
141 boards have hardware problems that will cause the machine to simply
142 lock up if the watchdog fires.
144 "If in doubt, leave it out" - say N.
147 tristate "NetWinder WB83C977 watchdog"
148 depends on FOOTBRIDGE && ARCH_NETWINDER
150 Say Y here to include support for the WB977 watchdog included in
151 NetWinder machines. Alternatively say M to compile the driver as
152 a module, which will be called wdt977.
154 Not sure? It's safe to say N.
156 config IXP4XX_WATCHDOG
157 tristate "IXP4xx Watchdog"
158 depends on ARCH_IXP4XX
160 Say Y here if to include support for the watchdog timer
161 in the Intel IXP4xx network processors. This driver can
162 be built as a module by choosing M. The module will
163 be called ixp4xx_wdt.
165 Note: The internal IXP4xx watchdog does a soft CPU reset
166 which doesn't reset any peripherals. There are circumstances
167 where the watchdog will fail to reset the board correctly
168 (e.g., if the boot ROM is in an unreadable state).
170 Say N if you are unsure.
172 config KS8695_WATCHDOG
173 tristate "KS8695 watchdog"
174 depends on ARCH_KS8695
176 Watchdog timer embedded into KS8695 processor. This will reboot your
177 system when the timeout is reached.
179 config HAVE_S3C2410_WATCHDOG
182 This will include watchdog timer support for Samsung SoCs. If
183 you want to include watchdog support for any machine, kindly
184 select this in the respective mach-XXXX/Kconfig file.
186 config S3C2410_WATCHDOG
187 tristate "S3C2410 Watchdog"
188 depends on HAVE_S3C2410_WATCHDOG
191 Watchdog timer block in the Samsung SoCs. This will reboot
192 the system when the timer expires with the watchdog enabled.
194 The driver is limited by the speed of the system's PCLK
195 signal, so with reasonably fast systems (PCLK around 50-66MHz)
196 then watchdog intervals of over approximately 20seconds are
199 The driver can be built as a module by choosing M, and will
200 be called s3c2410_wdt
202 config SA1100_WATCHDOG
203 tristate "SA1100/PXA2xx watchdog"
204 depends on ARCH_SA1100 || ARCH_PXA
206 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
207 reboot your system when timeout is reached.
209 NOTE: once enabled, this timer cannot be disabled.
211 To compile this driver as a module, choose M here: the
212 module will be called sa1100_wdt.
215 tristate "Synopsys DesignWare watchdog"
216 depends on ARM && HAVE_CLK
218 Say Y here if to include support for the Synopsys DesignWare
219 watchdog timer found in many ARM chips.
220 To compile this driver as a module, choose M here: the
221 module will be called dw_wdt.
223 config MPCORE_WATCHDOG
224 tristate "MPcore watchdog"
225 depends on HAVE_ARM_TWD
227 Watchdog timer embedded into the MPcore system.
229 To compile this driver as a module, choose M here: the
230 module will be called mpcore_wdt.
232 config EP93XX_WATCHDOG
233 tristate "EP93xx Watchdog"
234 depends on ARCH_EP93XX
237 Say Y here if to include support for the watchdog timer
238 embedded in the Cirrus Logic EP93xx family of devices.
240 To compile this driver as a module, choose M here: the
241 module will be called ep93xx_wdt.
244 tristate "OMAP Watchdog"
245 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
248 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
249 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
251 config PNX4008_WATCHDOG
252 tristate "LPC32XX Watchdog"
253 depends on ARCH_LPC32XX
256 Say Y here if to include support for the watchdog timer
257 in the LPC32XX processor.
258 This driver can be built as a module by choosing M. The module
259 will be called pnx4008_wdt.
261 Say N if you are unsure.
264 tristate "IOP Watchdog"
266 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
268 Say Y here if to include support for the watchdog timer
269 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
270 be built as a module by choosing M. The module will
273 Note: The IOP13XX watchdog does an Internal Bus Reset which will
274 affect both cores and the peripherals of the IOP. The ATU-X
275 and/or ATUe configuration registers will remain intact, but if
276 operating as an Root Complex and/or Central Resource, the PCI-X
277 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
279 config DAVINCI_WATCHDOG
280 tristate "DaVinci watchdog"
281 depends on ARCH_DAVINCI
283 Say Y here if to include support for the watchdog timer
284 in the DaVinci DM644x/DM646x processors.
285 To compile this driver as a module, choose M here: the
286 module will be called davinci_wdt.
288 NOTE: once enabled, this timer cannot be disabled.
289 Say N if you are unsure.
291 config ORION_WATCHDOG
292 tristate "Orion watchdog"
293 depends on ARCH_ORION5X || ARCH_KIRKWOOD
296 Say Y here if to include support for the watchdog timer
297 in the Marvell Orion5x and Kirkwood ARM SoCs.
298 To compile this driver as a module, choose M here: the
299 module will be called orion_wdt.
301 config COH901327_WATCHDOG
302 bool "ST-Ericsson COH 901 327 watchdog"
304 default y if MACH_U300
307 Say Y here to include Watchdog timer support for the
308 watchdog embedded into the ST-Ericsson U300 series platforms.
309 This watchdog is used to reset the system and thus cannot be
310 compiled as a module.
312 config TWL4030_WATCHDOG
313 tristate "TWL4030 Watchdog"
314 depends on TWL4030_CORE
317 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
318 watchdog timer support for TWL4030 chips.
320 config STMP3XXX_WATCHDOG
321 tristate "Freescale STMP3XXX watchdog"
322 depends on ARCH_STMP3XXX
324 Say Y here if to include support for the watchdog timer
325 for the Sigmatel STMP37XX/378X SoC.
326 To compile this driver as a module, choose M here: the
327 module will be called stmp3xxx_wdt.
329 config NUC900_WATCHDOG
330 tristate "Nuvoton NUC900 watchdog"
331 depends on ARCH_W90X900
333 Say Y here if to include support for the watchdog timer
334 for the Nuvoton NUC900 series SoCs.
335 To compile this driver as a module, choose M here: the
336 module will be called nuc900_wdt.
338 config TS72XX_WATCHDOG
339 tristate "TS-72XX SBC Watchdog"
340 depends on MACH_TS72XX
342 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
343 watchdog timer implemented in a external CPLD chip. Say Y here
344 if you want to support for the watchdog timer on TS-72XX boards.
346 To compile this driver as a module, choose M here: the
347 module will be called ts72xx_wdt.
349 config MAX63XX_WATCHDOG
350 tristate "Max63xx watchdog"
351 depends on ARM && HAS_IOMEM
354 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
357 tristate "IMX2+ Watchdog"
360 This is the driver for the hardware watchdog
361 on the Freescale IMX2 and later processors.
362 If you have one of these processors and wish to have
363 watchdog support enabled, say Y, otherwise say N.
365 To compile this driver as a module, choose M here: the
366 module will be called imx2_wdt.
368 config UX500_WATCHDOG
369 tristate "ST-Ericsson Ux500 watchdog"
370 depends on MFD_DB8500_PRCMU
374 Say Y here to include Watchdog timer support for the watchdog
375 existing in the prcmu of ST-Ericsson Ux500 series platforms.
377 To compile this driver as a module, choose M here: the
378 module will be called ux500_wdt.
382 config AT32AP700X_WDT
383 tristate "AT32AP700x watchdog"
384 depends on CPU_AT32AP700X
386 Watchdog timer embedded into AT32AP700x devices. This will reboot
387 your system when the timeout is reached.
389 # BLACKFIN Architecture
392 tristate "Blackfin On-Chip Watchdog Timer"
395 If you say yes here you will get support for the Blackfin On-Chip
396 Watchdog Timer. If you have one of these processors and wish to
397 have watchdog support enabled, say Y, otherwise say N.
399 To compile this driver as a module, choose M here: the
400 module will be called bfin_wdt.
408 # X86 (i386 + ia64 + x86_64) Architecture
411 tristate "Acquire SBC Watchdog Timer"
414 This is the driver for the hardware watchdog on Single Board
415 Computers produced by Acquire Inc (and others). This watchdog
416 simply watches your kernel to make sure it doesn't freeze, and if
417 it does, it reboots your computer after a certain amount of time.
419 To compile this driver as a module, choose M here: the
420 module will be called acquirewdt.
422 Most people will say N.
425 tristate "Advantech SBC Watchdog Timer"
428 If you are configuring a Linux kernel for the Advantech single-board
429 computer, say `Y' here to support its built-in watchdog timer
430 feature. More information can be found at
431 <http://www.advantech.com.tw/products/>
434 tristate "ALi M1535 PMU Watchdog Timer"
435 depends on X86 && PCI
437 This is the driver for the hardware watchdog on the ALi M1535 PMU.
439 To compile this driver as a module, choose M here: the
440 module will be called alim1535_wdt.
442 Most people will say N.
445 tristate "ALi M7101 PMU Computer Watchdog"
448 This is the driver for the hardware watchdog on the ALi M7101 PMU
449 as used in the x86 Cobalt servers and also found in some
450 SPARC Netra servers too.
452 To compile this driver as a module, choose M here: the
453 module will be called alim7101_wdt.
455 Most people will say N.
458 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
461 This is the driver for the hardware watchdog on the Fintek
462 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
464 You can compile this driver directly into the kernel, or use
465 it as a module. The module will be called f71808e_wdt.
468 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
469 depends on X86 && PCI
471 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
472 (Total Cost of Ownership) timer is a watchdog timer that will reboot
473 the machine after its expiration. The expiration time can be
474 configured with the "heartbeat" parameter.
476 To compile this driver as a module, choose M here: the
477 module will be called sp5100_tco.
480 tristate "AMD Geode CS5535/CS5536 Watchdog"
481 depends on CS5535_MFGPT
483 This driver enables a watchdog capability built into the
484 CS5535/CS5536 companion chips for the AMD Geode GX and LX
485 processors. This watchdog watches your kernel to make sure
486 it doesn't freeze, and if it does, it reboots your computer after
487 a certain amount of time.
489 You can compile this driver directly into the kernel, or use
490 it as a module. The module will be called geodewdt.
493 tristate "AMD Elan SC520 processor Watchdog"
496 This is the driver for the hardware watchdog built in to the
497 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
498 This watchdog simply watches your kernel to make sure it doesn't
499 freeze, and if it does, it reboots your computer after a certain
502 You can compile this driver directly into the kernel, or use
503 it as a module. The module will be called sc520_wdt.
505 config SBC_FITPC2_WATCHDOG
506 tristate "Compulab SBC-FITPC2 watchdog"
509 This is the driver for the built-in watchdog timer on the fit-PC2,
510 fit-PC2i, CM-iAM single-board computers made by Compulab.
512 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
513 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
515 Entering BIOS setup temporary disables watchdog operation regardless to current state,
516 so system will not be restarted while user in BIOS setup.
518 Once watchdog was enabled the system will be restarted every
519 "Watchdog Timer Value" period, so to prevent it user can restart or
520 disable the watchdog.
522 To compile this driver as a module, choose M here: the
523 module will be called sbc_fitpc2_wdt.
525 Most people will say N.
528 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
531 Enable support for the watchdog timer on the Eurotech CPU-1220 and
532 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
533 information are at <http://www.eurotech.it/>.
536 tristate "IB700 SBC Watchdog Timer"
539 This is the driver for the hardware watchdog on the IB700 Single
540 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
541 simply watches your kernel to make sure it doesn't freeze, and if
542 it does, it reboots your computer after a certain amount of time.
544 This driver is like the WDT501 driver but for slightly different hardware.
546 To compile this driver as a module, choose M here: the
547 module will be called ib700wdt.
549 Most people will say N.
552 tristate "IBM Automatic Server Restart"
555 This is the driver for the IBM Automatic Server Restart watchdog
556 timer built-in into some eServer xSeries machines.
558 To compile this driver as a module, choose M here: the
559 module will be called ibmasr.
562 tristate "ICP Single Board Computer Watchdog Timer"
565 This is a driver for the hardware watchdog on the ICP Single
566 Board Computer. This driver is working on (at least) the following
567 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
569 To compile this driver as a module, choose M here: the
570 module will be called wafer5823wdt.
573 tristate "Intel 6300ESB Timer/Watchdog"
576 Hardware driver for the watchdog timer built into the Intel
577 6300ESB controller hub.
579 To compile this driver as a module, choose M here: the
580 module will be called i6300esb.
583 tristate "Intel Atom E6xx Watchdog"
584 depends on X86 && PCI
589 Hardware driver for the watchdog timer built into the Intel
590 Atom E6XX (TunnelCreek) processor.
592 To compile this driver as a module, choose M here: the
593 module will be called ie6xx_wdt.
595 config INTEL_SCU_WATCHDOG
596 bool "Intel SCU Watchdog for Mobile Platforms"
599 Hardware driver for the watchdog time built into the Intel SCU
600 for Intel Mobile Platforms.
602 To compile this driver as a module, choose M here.
605 tristate "Intel TCO Timer/Watchdog"
606 depends on (X86 || IA64) && PCI
610 Hardware driver for the intel TCO timer based watchdog devices.
611 These drivers are included in the Intel 82801 I/O Controller
612 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
615 The TCO (Total Cost of Ownership) timer is a watchdog timer
616 that will reboot the machine after its second expiration. The
617 expiration time can be configured with the "heartbeat" parameter.
619 On some motherboards the driver may fail to reset the chipset's
620 NO_REBOOT flag which prevents the watchdog from rebooting the
621 machine. If this is the case you will get a kernel message like
622 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
624 To compile this driver as a module, choose M here: the
625 module will be called iTCO_wdt.
627 config ITCO_VENDOR_SUPPORT
628 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
631 Add vendor specific support to the intel TCO timer based watchdog
632 devices. At this moment we only have additional support for some
633 SuperMicro Inc. motherboards.
636 tristate "IT8712F (Smart Guardian) Watchdog Timer"
639 This is the driver for the built-in watchdog timer on the IT8712F
640 Super I/0 chipset used on many motherboards.
642 If the driver does not work, then make sure that the game port in
645 To compile this driver as a module, choose M here: the
646 module will be called it8712f_wdt.
649 tristate "IT87 Watchdog Timer"
652 This is the driver for the hardware watchdog on the ITE IT8702,
653 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
656 If the driver does not work, then make sure that the game port in
659 This watchdog simply watches your kernel to make sure it doesn't
660 freeze, and if it does, it reboots your computer after a certain
663 To compile this driver as a module, choose M here: the module will
667 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
668 depends on X86 && PCI
670 A software monitoring watchdog and NMI sourcing driver. This driver
671 will detect lockups and provide a stack trace. This is a driver that
672 will only load on an HP ProLiant system with a minimum of iLO2 support.
673 To compile this driver as a module, choose M here: the module will be
676 config HPWDT_NMI_DECODING
677 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
678 depends on HP_WATCHDOG
681 When an NMI occurs this feature will make the necessary BIOS calls to
682 log the cause of the NMI.
685 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
688 This is a driver for National Semiconductor PC87307/PC97307 hardware
689 watchdog cards as found on the SC1200. This watchdog is mainly used
690 for power management purposes and can be used to power down the device
691 during inactivity periods (includes interrupt activity monitoring).
693 To compile this driver as a module, choose M here: the
694 module will be called sc1200wdt.
696 Most people will say N.
699 tristate "National Semiconductor SCx200 Watchdog"
700 depends on SCx200 && PCI
702 Enable the built-in watchdog timer support on the National
703 Semiconductor SCx200 processors.
705 If compiled as a module, it will be called scx200_wdt.
708 tristate "NS PC87413 watchdog"
711 This is the driver for the hardware watchdog on the PC87413 chipset
712 This watchdog simply watches your kernel to make sure it doesn't
713 freeze, and if it does, it reboots your computer after a certain
716 To compile this driver as a module, choose M here: the
717 module will be called pc87413_wdt.
719 Most people will say N.
722 tristate "nVidia TCO Timer/Watchdog"
723 depends on X86 && PCI
725 Hardware driver for the TCO timer built into the nVidia Hub family
726 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
727 watchdog timer that will reboot the machine after its second
728 expiration. The expiration time can be configured with the
729 "heartbeat" parameter.
731 On some motherboards the driver may fail to reset the chipset's
732 NO_REBOOT flag which prevents the watchdog from rebooting the
733 machine. If this is the case you will get a kernel message like
734 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
736 To compile this driver as a module, choose M here: the
737 module will be called nv_tco.
740 tristate "RDC R-321x SoC watchdog"
741 depends on X86_RDC321X
743 This is the driver for the built in hardware watchdog
744 in the RDC R-321x SoC.
746 To compile this driver as a module, choose M here: the
747 module will be called rdc321x_wdt.
750 tristate "SBC-60XX Watchdog Timer"
753 This driver can be used with the watchdog timer found on some
754 single board computers, namely the 6010 PII based computer.
755 It may well work with other cards. It reads port 0x443 to enable
756 and re-set the watchdog timer, and reads port 0x45 to disable
757 the watchdog. If you have a card that behave in similar ways,
758 you can probably make this driver work with your card as well.
760 You can compile this driver directly into the kernel, or use
761 it as a module. The module will be called sbc60xxwdt.
764 tristate "SBC8360 Watchdog Timer"
768 This is the driver for the hardware watchdog on the SBC8360 Single
769 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
771 To compile this driver as a module, choose M here: the
772 module will be called sbc8360.
774 Most people will say N.
777 tristate "SBC Nano 7240 Watchdog Timer"
778 depends on X86_32 && !UML
780 This is the driver for the hardware watchdog found on the IEI
781 single board computers EPIC Nano 7240 (and likely others). This
782 watchdog simply watches your kernel to make sure it doesn't freeze,
783 and if it does, it reboots your computer after a certain amount of
786 To compile this driver as a module, choose M here: the
787 module will be called sbc7240_wdt.
790 tristate "SMA CPU5 Watchdog"
794 To compile this driver as a module, choose M here: the
795 module will be called cpu5wdt.
797 config SMSC_SCH311X_WDT
798 tristate "SMSC SCH311X Watchdog Timer"
801 This is the driver for the hardware watchdog timer on the
802 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
803 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
806 To compile this driver as a module, choose M here: the
807 module will be called sch311x_wdt.
809 config SMSC37B787_WDT
810 tristate "Winbond SMsC37B787 Watchdog Timer"
813 This is the driver for the hardware watchdog component on the
814 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
815 from Vision Systems and maybe others.
817 This watchdog simply watches your kernel to make sure it doesn't
818 freeze, and if it does, it reboots your computer after a certain
821 Usually a userspace daemon will notify the kernel WDT driver that
822 userspace is still alive, at regular intervals.
824 To compile this driver as a module, choose M here: the
825 module will be called smsc37b787_wdt.
827 Most people will say N.
830 tristate "VIA Watchdog Timer"
831 depends on X86 && PCI
834 This is the driver for the hardware watchdog timer on VIA
835 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
837 To compile this driver as a module, choose M here; the module
838 will be called via_wdt.
840 Most people will say N.
843 tristate "W83627HF/W83627DHG Watchdog Timer"
846 This is the driver for the hardware watchdog on the W83627HF chipset
847 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
848 (and likely others). The driver also supports the W83627DHG chip.
849 This watchdog simply watches your kernel to make sure it doesn't
850 freeze, and if it does, it reboots your computer after a certain
853 To compile this driver as a module, choose M here: the
854 module will be called w83627hf_wdt.
856 Most people will say N.
859 tristate "W83697HF/W83697HG Watchdog Timer"
862 This is the driver for the hardware watchdog on the W83697HF/HG
863 chipset as used in Dedibox/VIA motherboards (and likely others).
864 This watchdog simply watches your kernel to make sure it doesn't
865 freeze, and if it does, it reboots your computer after a certain
868 To compile this driver as a module, choose M here: the
869 module will be called w83697hf_wdt.
871 Most people will say N.
874 tristate "W83697UG/W83697UF Watchdog Timer"
877 This is the driver for the hardware watchdog on the W83697UG/UF
878 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
879 This watchdog simply watches your kernel to make sure it doesn't
880 freeze, and if it does, it reboots your computer after a certain
883 To compile this driver as a module, choose M here: the
884 module will be called w83697ug_wdt.
886 Most people will say N.
889 tristate "W83877F (EMACS) Watchdog Timer"
892 This is the driver for the hardware watchdog on the W83877F chipset
893 as used in EMACS PC-104 motherboards (and likely others). This
894 watchdog simply watches your kernel to make sure it doesn't freeze,
895 and if it does, it reboots your computer after a certain amount of
898 To compile this driver as a module, choose M here: the
899 module will be called w83877f_wdt.
901 Most people will say N.
904 tristate "W83977F (PCM-5335) Watchdog Timer"
907 This is the driver for the hardware watchdog on the W83977F I/O chip
908 as used in AAEON's PCM-5335 SBC (and likely others). This
909 watchdog simply watches your kernel to make sure it doesn't freeze,
910 and if it does, it reboots your computer after a certain amount of
913 To compile this driver as a module, choose M here: the
914 module will be called w83977f_wdt.
917 tristate "ZF MachZ Watchdog"
920 If you are using a ZF Micro MachZ processor, say Y here, otherwise
921 N. This is the driver for the watchdog timer built-in on that
922 processor using ZF-Logic interface. This watchdog simply watches
923 your kernel to make sure it doesn't freeze, and if it does, it
924 reboots your computer after a certain amount of time.
926 To compile this driver as a module, choose M here: the
927 module will be called machzwd.
929 config SBC_EPX_C3_WATCHDOG
930 tristate "Winsystems SBC EPX-C3 watchdog"
933 This is the driver for the built-in watchdog timer on the EPX-C3
934 Single-board computer made by Winsystems, Inc.
936 *Note*: This hardware watchdog is not probeable and thus there
937 is no way to know if writing to its IO address will corrupt
938 your system or have any real effect. The only way to be sure
939 that this driver does what you want is to make sure you
940 are running it on an EPX-C3 from Winsystems with the watchdog
941 timer at IO address 0x1ee and 0x1ef. It will write to both those
942 IO ports. Basically, the assumption is made that if you compile
943 this driver into your kernel and/or load it as a module, that you
944 know what you are doing and that you are in fact running on an
947 To compile this driver as a module, choose M here: the
948 module will be called sbc_epx_c3.
954 config M54xx_WATCHDOG
955 tristate "MCF54xx watchdog support"
958 To compile this driver as a module, choose M here: the
959 module will be called m54xx_wdt.
961 # MicroBlaze Architecture
963 config XILINX_WATCHDOG
964 tristate "Xilinx Watchdog timer"
965 depends on MICROBLAZE
967 Watchdog driver for the xps_timebase_wdt ip core.
969 IMPORTANT: The xps_timebase_wdt parent must have the property
970 "clock-frequency" at device tree.
972 To compile this driver as a module, choose M here: the
973 module will be called of_xilinx_wdt.
978 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
981 Hardware driver for the built-in watchdog timer on the Atheros
982 AR71XX/AR724X/AR913X SoCs.
985 tristate "Broadcom BCM47xx Watchdog Timer"
988 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
991 tristate "IDT RC32434 SoC Watchdog Timer"
992 depends on MIKROTIK_RB532
994 Hardware driver for the IDT RC32434 SoC built-in
997 To compile this driver as a module, choose M here: the
998 module will be called rc32434_wdt.
1001 tristate "Indy/I2 Hardware Watchdog"
1002 depends on SGI_HAS_INDYDOG
1004 Hardware driver for the Indy's/I2's watchdog. This is a
1005 watchdog timer that will reboot the machine after a 60 second
1006 timer expired and no process has written to /dev/watchdog during
1010 tristate "Ingenic jz4740 SoC hardware watchdog"
1011 depends on MACH_JZ4740
1012 select WATCHDOG_CORE
1014 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1017 tristate "MTX-1 Hardware Watchdog"
1018 depends on MIPS_MTX1
1020 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1021 will reboot the machine after a 100 seconds timer expired.
1024 tristate "PNX833x Hardware Watchdog"
1025 depends on SOC_PNX8335
1027 Hardware driver for the PNX833x's watchdog. This is a
1028 watchdog timer that will reboot the machine after a programmable
1029 timer has expired and no process has written to /dev/watchdog during
1033 tristate "Sibyte SoC hardware watchdog"
1036 Watchdog driver for the built in watchdog hardware in Sibyte
1037 SoC processors. There are apparently two watchdog timers
1038 on such processors; this driver supports only the first one,
1039 because currently Linux only supports exporting one watchdog
1042 To compile this driver as a loadable module, choose M here.
1043 The module will be called sb_wdog.
1046 tristate "TI AR7 Watchdog Timer"
1049 Hardware driver for the TI AR7 Watchdog Timer.
1052 tristate "Toshiba TXx9 Watchdog Timer"
1053 depends on CPU_TX39XX || CPU_TX49XX
1054 select WATCHDOG_CORE
1056 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1059 tristate "Cavium OCTEON SOC family Watchdog Timer"
1060 depends on CPU_CAVIUM_OCTEON
1062 select EXPORT_UASM if OCTEON_WDT = m
1064 Hardware driver for OCTEON's on chip watchdog timer.
1065 Enables the watchdog for all cores running Linux. It
1066 installs a NMI handler and pokes the watchdog based on an
1067 interrupt. On first expiration of the watchdog, the
1068 interrupt handler pokes it. The second expiration causes an
1069 NMI that prints a message. The third expiration causes a
1072 When userspace has /dev/watchdog open, no poking is done
1073 from the first interrupt, it is then only poked when the
1077 tristate "Broadcom BCM63xx hardware watchdog"
1080 Watchdog driver for the built in watchdog hardware in Broadcom
1083 To compile this driver as a loadable module, choose M here.
1084 The module will be called bcm63xx_wdt.
1087 tristate "Lantiq SoC watchdog"
1090 Hardware driver for the Lantiq SoC Watchdog Timer.
1092 # PARISC Architecture
1094 # POWERPC Architecture
1097 tristate "GE Watchdog Timer"
1100 Watchdog timer found in a number of GE single board computers.
1103 bool "MPC52xx Watchdog Timer"
1104 depends on PPC_MPC52xx
1106 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1109 tristate "MPC8xxx Platform Watchdog Timer"
1110 depends on PPC_8xx || PPC_83xx || PPC_86xx
1112 This driver is for a SoC level watchdog that exists on some
1113 Freescale PowerPC processors. So far this driver supports:
1118 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1121 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1125 tristate "PIKA FPGA Watchdog"
1129 This enables the watchdog in the PIKA FPGA. Currently used on
1133 tristate "PowerPC Book-E Watchdog Timer"
1134 depends on BOOKE || 4xx
1136 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1137 MPC85xx SOCs and the IBM PowerPC 440.
1139 Please see Documentation/watchdog/watchdog-api.txt for
1142 config BOOKE_WDT_DEFAULT_TIMEOUT
1143 int "PowerPC Book-E Watchdog Timer Default Timeout"
1144 depends on BOOKE_WDT
1145 default 38 if PPC_FSL_BOOK3E
1146 range 0 63 if PPC_FSL_BOOK3E
1147 default 3 if !PPC_FSL_BOOK3E
1148 range 0 3 if !PPC_FSL_BOOK3E
1150 Select the default watchdog timer period to be used by the PowerPC
1151 Book-E watchdog driver. A watchdog "event" occurs when the bit
1152 position represented by this number transitions from zero to one.
1154 For Freescale Book-E processors, this is a number between 0 and 63.
1155 For other Book-E processors, this is a number between 0 and 3.
1157 The value can be overridden by the wdt_period command-line parameter.
1159 # PPC64 Architecture
1161 config WATCHDOG_RTAS
1162 tristate "RTAS watchdog"
1165 This driver adds watchdog support for the RTAS watchdog.
1167 To compile this driver as a module, choose M here. The module
1168 will be called wdrtas.
1173 tristate "z/VM Watchdog Timer"
1176 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1177 provide a virtual watchdog timer to their guest that cause a
1178 user define Control Program command to be executed after a
1181 To compile this driver as a module, choose M here. The module
1182 will be called vmwatchdog.
1184 # SUPERH (sh + sh64) Architecture
1187 tristate "SuperH Watchdog"
1188 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1189 select WATCHDOG_CORE
1191 This driver adds watchdog support for the integrated watchdog in the
1192 SuperH processors. If you have one of these processors and wish
1193 to have watchdog support enabled, say Y, otherwise say N.
1195 As a side note, saying Y here will automatically boost HZ to 1000
1196 so that the timer has a chance to clear the overflow counter. On
1197 slower systems (such as the SH-2 and SH-3) this will likely yield
1198 some performance issues. As such, the WDT should be avoided here
1199 unless it is absolutely necessary.
1201 To compile this driver as a module, choose M here: the
1202 module will be called shwdt.
1204 # SPARC Architecture
1206 # SPARC64 Architecture
1208 config WATCHDOG_CP1XXX
1209 tristate "CP1XXX Hardware Watchdog support"
1210 depends on SPARC64 && PCI
1212 This is the driver for the hardware watchdog timers present on
1213 Sun Microsystems CompactPCI models CP1400 and CP1500.
1215 To compile this driver as a module, choose M here: the
1216 module will be called cpwatchdog.
1218 If you do not have a CompactPCI model CP1400 or CP1500, or
1219 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1220 you should say N to this option.
1223 tristate "RIO Hardware Watchdog support"
1224 depends on SPARC64 && PCI
1226 Say Y here to support the hardware watchdog capability on Sun RIO
1227 machines. The watchdog timeout period is normally one minute but
1228 can be changed with a boot-time parameter.
1230 # XTENSA Architecture
1235 tristate "Xen Watchdog support"
1238 Say Y here to support the hypervisor watchdog capability provided
1239 by Xen 4.0 and newer. The watchdog timeout period is normally one
1240 minute but can be changed with a boot-time parameter.
1243 tristate "UML watchdog"
1247 # ISA-based Watchdog Cards
1250 comment "ISA-based Watchdog Cards"
1254 tristate "Berkshire Products ISA-PC Watchdog"
1257 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1258 This card simply watches your kernel to make sure it doesn't freeze,
1259 and if it does, it reboots your computer after a certain amount of
1260 time. This driver is like the WDT501 driver but for different
1261 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1262 watchdog cards can be ordered from <http://www.berkprod.com/>.
1264 To compile this driver as a module, choose M here: the
1265 module will be called pcwd.
1267 Most people will say N.
1270 tristate "Mixcom Watchdog"
1273 This is a driver for the Mixcom hardware watchdog cards. This
1274 watchdog 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
1278 To compile this driver as a module, choose M here: the
1279 module will be called mixcomwd.
1281 Most people will say N.
1284 tristate "WDT Watchdog timer"
1287 If you have a WDT500P or WDT501P watchdog board, say Y here,
1288 otherwise N. It is not possible to probe for this board, which means
1289 that you have to inform the kernel about the IO port and IRQ that
1290 is needed (you can do this via the io and irq parameters)
1292 To compile this driver as a module, choose M here: the
1293 module will be called wdt.
1296 # PCI-based Watchdog Cards
1299 comment "PCI-based Watchdog Cards"
1302 config PCIPCWATCHDOG
1303 tristate "Berkshire Products PCI-PC Watchdog"
1306 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1307 This card simply watches your kernel to make sure it doesn't freeze,
1308 and if it does, it reboots your computer after a certain amount of
1309 time. The card can also monitor the internal temperature of the PC.
1310 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1312 To compile this driver as a module, choose M here: the
1313 module will be called pcwd_pci.
1315 Most people will say N.
1318 tristate "PCI-WDT500/501 Watchdog timer"
1321 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1323 If you have a PCI-WDT501 watchdog board then you can enable the
1324 temperature sensor by setting the type parameter to 501.
1326 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1327 can do this via the tachometer parameter. Only do this if you have a
1328 fan tachometer actually set up.
1330 To compile this driver as a module, choose M here: the
1331 module will be called wdt_pci.
1334 # USB-based Watchdog Cards
1337 comment "USB-based Watchdog Cards"
1340 config USBPCWATCHDOG
1341 tristate "Berkshire Products USB-PC Watchdog"
1344 This is the driver for the Berkshire Products USB-PC Watchdog card.
1345 This card simply watches your kernel to make sure it doesn't freeze,
1346 and if it does, it reboots your computer after a certain amount of
1347 time. The card can also monitor the internal temperature of the PC.
1348 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1350 To compile this driver as a module, choose M here: the
1351 module will be called pcwd_usb.
1353 Most people will say N.