2 # Watchdog device configuration
6 bool "Watchdog Timer Support"
8 If you say Y here (and to one of the following options) and create a
9 character special file /dev/watchdog with major number 10 and minor
10 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
11 subsequently opening the file and then failing to write to it for
12 longer than 1 minute will result in rebooting the machine. This
13 could be useful for a networked machine that needs to come back
14 on-line as fast as possible after a lock-up. There's both a watchdog
15 implementation entirely in software (which can sometimes fail to
16 reboot the machine) and a driver for hardware watchdog boards, which
17 are more robust and can also keep track of the temperature inside
18 your computer. For details, read
19 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
21 The watchdog is usually used together with the watchdog daemon
22 which is available from
23 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
24 also monitor NFS connections and can reboot the machine when the process
32 bool "WatchDog Timer Driver Core"
34 Say Y here if you want to use the new watchdog timer driver core.
35 This driver provides a framework for all watchdog timer drivers
36 and gives them the /dev/watchdog interface (and later also the
39 config WATCHDOG_NOWAYOUT
40 bool "Disable watchdog shutdown on close"
42 The default watchdog behaviour (which you get if you say N here) is
43 to stop the timer if the process managing it closes the file
44 /dev/watchdog. It's always remotely possible that this process might
45 get killed. If you say Y here, the watchdog cannot be stopped once
49 # General Watchdog drivers
52 comment "Watchdog Device Drivers"
54 # Architecture Independent
57 tristate "Software watchdog"
60 A software monitoring watchdog. This will fail to reboot your system
61 from some situations that the hardware watchdog will recover
62 from. Equally it's a lot cheaper to install.
64 To compile this driver as a module, choose M here: the
65 module will be called softdog.
67 config DA9052_WATCHDOG
68 tristate "Dialog DA9052 Watchdog"
69 depends on PMIC_DA9052
72 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
75 Say Y here to include support for the DA9052 watchdog.
76 Alternatively say M to compile the driver as a module,
77 which will be called da9052_wdt.
79 config DA9055_WATCHDOG
80 tristate "Dialog Semiconductor DA9055 Watchdog"
84 If you say yes here you get support for watchdog on the Dialog
85 Semiconductor DA9055 PMIC.
87 This driver can also be built as a module. If so, the module
88 will be called da9055_wdt.
90 config WM831X_WATCHDOG
91 tristate "WM831x watchdog"
95 Support for the watchdog in the WM831x AudioPlus PMICs. When
96 the watchdog triggers the system will be reset.
98 config WM8350_WATCHDOG
99 tristate "WM8350 watchdog"
100 depends on MFD_WM8350
103 Support for the watchdog in the WM8350 AudioPlus PMIC. When
104 the watchdog triggers the system will be reset.
110 config ARM_SP805_WATCHDOG
111 tristate "ARM SP805 Watchdog"
112 depends on ARM && ARM_AMBA
115 ARM Primecell SP805 Watchdog timer. This will reboot your system when
116 the timeout is reached.
118 config AT91RM9200_WATCHDOG
119 tristate "AT91RM9200 watchdog"
120 depends on ARCH_AT91RM9200
122 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
123 system when the timeout is reached.
125 config AT91SAM9X_WATCHDOG
126 tristate "AT91SAM9X / AT91CAP9 watchdog"
127 depends on ARCH_AT91 && !ARCH_AT91RM9200
130 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
131 reboot your system when the timeout is reached.
133 config 21285_WATCHDOG
134 tristate "DC21285 watchdog"
135 depends on FOOTBRIDGE
137 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
138 here if you wish to use this. Alternatively say M to compile the
139 driver as a module, which will be called wdt285.
141 This driver does not work on all machines. In particular, early CATS
142 boards have hardware problems that will cause the machine to simply
143 lock up if the watchdog fires.
145 "If in doubt, leave it out" - say N.
148 tristate "NetWinder WB83C977 watchdog"
149 depends on FOOTBRIDGE && ARCH_NETWINDER
151 Say Y here to include support for the WB977 watchdog included in
152 NetWinder machines. Alternatively say M to compile the driver as
153 a module, which will be called wdt977.
155 Not sure? It's safe to say N.
157 config IXP4XX_WATCHDOG
158 tristate "IXP4xx Watchdog"
159 depends on ARCH_IXP4XX
161 Say Y here if to include support for the watchdog timer
162 in the Intel IXP4xx network processors. This driver can
163 be built as a module by choosing M. The module will
164 be called ixp4xx_wdt.
166 Note: The internal IXP4xx watchdog does a soft CPU reset
167 which doesn't reset any peripherals. There are circumstances
168 where the watchdog will fail to reset the board correctly
169 (e.g., if the boot ROM is in an unreadable state).
171 Say N if you are unsure.
173 config KS8695_WATCHDOG
174 tristate "KS8695 watchdog"
175 depends on ARCH_KS8695
177 Watchdog timer embedded into KS8695 processor. This will reboot your
178 system when the timeout is reached.
180 config HAVE_S3C2410_WATCHDOG
183 This will include watchdog timer support for Samsung SoCs. If
184 you want to include watchdog support for any machine, kindly
185 select this in the respective mach-XXXX/Kconfig file.
187 config S3C2410_WATCHDOG
188 tristate "S3C2410 Watchdog"
189 depends on HAVE_S3C2410_WATCHDOG
192 Watchdog timer block in the Samsung SoCs. This will reboot
193 the system when the timer expires with the watchdog enabled.
195 The driver is limited by the speed of the system's PCLK
196 signal, so with reasonably fast systems (PCLK around 50-66MHz)
197 then watchdog intervals of over approximately 20seconds are
200 The driver can be built as a module by choosing M, and will
201 be called s3c2410_wdt
203 config SA1100_WATCHDOG
204 tristate "SA1100/PXA2xx watchdog"
205 depends on ARCH_SA1100 || ARCH_PXA
207 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
208 reboot your system when timeout is reached.
210 NOTE: once enabled, this timer cannot be disabled.
212 To compile this driver as a module, choose M here: the
213 module will be called sa1100_wdt.
216 tristate "Synopsys DesignWare watchdog"
217 depends on ARM && HAVE_CLK
219 Say Y here if to include support for the Synopsys DesignWare
220 watchdog timer found in many ARM chips.
221 To compile this driver as a module, choose M here: the
222 module will be called dw_wdt.
224 config EP93XX_WATCHDOG
225 tristate "EP93xx Watchdog"
226 depends on ARCH_EP93XX
229 Say Y here if to include support for the watchdog timer
230 embedded in the Cirrus Logic EP93xx family of devices.
232 To compile this driver as a module, choose M here: the
233 module will be called ep93xx_wdt.
236 tristate "OMAP Watchdog"
237 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
240 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
241 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
243 config PNX4008_WATCHDOG
244 tristate "LPC32XX Watchdog"
245 depends on ARCH_LPC32XX
248 Say Y here if to include support for the watchdog timer
249 in the LPC32XX processor.
250 This driver can be built as a module by choosing M. The module
251 will be called pnx4008_wdt.
253 Say N if you are unsure.
256 tristate "IOP Watchdog"
258 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
260 Say Y here if to include support for the watchdog timer
261 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
262 be built as a module by choosing M. The module will
265 Note: The IOP13XX watchdog does an Internal Bus Reset which will
266 affect both cores and the peripherals of the IOP. The ATU-X
267 and/or ATUe configuration registers will remain intact, but if
268 operating as an Root Complex and/or Central Resource, the PCI-X
269 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
271 config DAVINCI_WATCHDOG
272 tristate "DaVinci watchdog"
273 depends on ARCH_DAVINCI
275 Say Y here if to include support for the watchdog timer
276 in the DaVinci DM644x/DM646x processors.
277 To compile this driver as a module, choose M here: the
278 module will be called davinci_wdt.
280 NOTE: once enabled, this timer cannot be disabled.
281 Say N if you are unsure.
283 config ORION_WATCHDOG
284 tristate "Orion watchdog"
285 depends on ARCH_ORION5X || ARCH_KIRKWOOD || ARCH_DOVE
288 Say Y here if to include support for the watchdog timer
289 in the Marvell Orion5x and Kirkwood ARM SoCs.
290 To compile this driver as a module, choose M here: the
291 module will be called orion_wdt.
293 config SUNXI_WATCHDOG
294 tristate "Allwinner SoCs watchdog support"
295 depends on ARCH_SUNXI
298 Say Y here to include support for the watchdog timer
300 To compile this driver as a module, choose M here: the
301 module will be called sunxi_wdt.
303 config COH901327_WATCHDOG
304 bool "ST-Ericsson COH 901 327 watchdog"
306 default y if MACH_U300
309 Say Y here to include Watchdog timer support for the
310 watchdog embedded into the ST-Ericsson U300 series platforms.
311 This watchdog is used to reset the system and thus cannot be
312 compiled as a module.
314 config TWL4030_WATCHDOG
315 tristate "TWL4030 Watchdog"
316 depends on TWL4030_CORE
319 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
320 watchdog timer support for TWL4030 chips.
322 config STMP3XXX_RTC_WATCHDOG
323 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
324 depends on RTC_DRV_STMP
327 Say Y here to include support for the watchdog timer inside
328 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
329 To compile this driver as a module, choose M here: the
330 module will be called stmp3xxx_rtc_wdt.
332 config NUC900_WATCHDOG
333 tristate "Nuvoton NUC900 watchdog"
334 depends on ARCH_W90X900
336 Say Y here if to include support for the watchdog timer
337 for the Nuvoton NUC900 series SoCs.
338 To compile this driver as a module, choose M here: the
339 module will be called nuc900_wdt.
341 config TS72XX_WATCHDOG
342 tristate "TS-72XX SBC Watchdog"
343 depends on MACH_TS72XX
345 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
346 watchdog timer implemented in a external CPLD chip. Say Y here
347 if you want to support for the watchdog timer on TS-72XX boards.
349 To compile this driver as a module, choose M here: the
350 module will be called ts72xx_wdt.
352 config MAX63XX_WATCHDOG
353 tristate "Max63xx watchdog"
354 depends on ARM && HAS_IOMEM
357 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
360 tristate "IMX2+ Watchdog"
363 This is the driver for the hardware watchdog
364 on the Freescale IMX2 and later processors.
365 If you have one of these processors and wish to have
366 watchdog support enabled, say Y, otherwise say N.
368 To compile this driver as a module, choose M here: the
369 module will be called imx2_wdt.
371 config UX500_WATCHDOG
372 tristate "ST-Ericsson Ux500 watchdog"
373 depends on MFD_DB8500_PRCMU
377 Say Y here to include Watchdog timer support for the watchdog
378 existing in the prcmu of ST-Ericsson Ux500 series platforms.
380 To compile this driver as a module, choose M here: the
381 module will be called ux500_wdt.
384 tristate "Retu watchdog"
388 Retu watchdog driver for Nokia Internet Tablets (770, N800,
389 N810). At least on N800 the watchdog cannot be disabled, so
390 this driver is essential and you should enable it.
392 To compile this driver as a module, choose M here: the
393 module will be called retu_wdt.
397 config AT32AP700X_WDT
398 tristate "AT32AP700x watchdog"
399 depends on CPU_AT32AP700X
401 Watchdog timer embedded into AT32AP700x devices. This will reboot
402 your system when the timeout is reached.
404 # BLACKFIN Architecture
407 tristate "Blackfin On-Chip Watchdog Timer"
410 If you say yes here you will get support for the Blackfin On-Chip
411 Watchdog Timer. If you have one of these processors and wish to
412 have watchdog support enabled, say Y, otherwise say N.
414 To compile this driver as a module, choose M here: the
415 module will be called bfin_wdt.
423 # X86 (i386 + ia64 + x86_64) Architecture
426 tristate "Acquire SBC Watchdog Timer"
429 This is the driver for the hardware watchdog on Single Board
430 Computers produced by Acquire Inc (and others). This watchdog
431 simply watches your kernel to make sure it doesn't freeze, and if
432 it does, it reboots your computer after a certain amount of time.
434 To compile this driver as a module, choose M here: the
435 module will be called acquirewdt.
437 Most people will say N.
440 tristate "Advantech SBC Watchdog Timer"
443 If you are configuring a Linux kernel for the Advantech single-board
444 computer, say `Y' here to support its built-in watchdog timer
445 feature. More information can be found at
446 <http://www.advantech.com.tw/products/>
449 tristate "ALi M1535 PMU Watchdog Timer"
450 depends on X86 && PCI
452 This is the driver for the hardware watchdog on the ALi M1535 PMU.
454 To compile this driver as a module, choose M here: the
455 module will be called alim1535_wdt.
457 Most people will say N.
460 tristate "ALi M7101 PMU Computer Watchdog"
463 This is the driver for the hardware watchdog on the ALi M7101 PMU
464 as used in the x86 Cobalt servers and also found in some
465 SPARC Netra servers too.
467 To compile this driver as a module, choose M here: the
468 module will be called alim7101_wdt.
470 Most people will say N.
473 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
476 This is the driver for the hardware watchdog on the Fintek
477 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
479 You can compile this driver directly into the kernel, or use
480 it as a module. The module will be called f71808e_wdt.
483 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
484 depends on X86 && PCI
486 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
487 (Total Cost of Ownership) timer is a watchdog timer that will reboot
488 the machine after its expiration. The expiration time can be
489 configured with the "heartbeat" parameter.
491 To compile this driver as a module, choose M here: the
492 module will be called sp5100_tco.
495 tristate "AMD Geode CS5535/CS5536 Watchdog"
496 depends on CS5535_MFGPT
498 This driver enables a watchdog capability built into the
499 CS5535/CS5536 companion chips for the AMD Geode GX and LX
500 processors. This watchdog watches your kernel to make sure
501 it doesn't freeze, and if it does, it reboots your computer after
502 a certain amount of time.
504 You can compile this driver directly into the kernel, or use
505 it as a module. The module will be called geodewdt.
508 tristate "AMD Elan SC520 processor Watchdog"
511 This is the driver for the hardware watchdog built in to the
512 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
513 This watchdog simply watches your kernel to make sure it doesn't
514 freeze, and if it does, it reboots your computer after a certain
517 You can compile this driver directly into the kernel, or use
518 it as a module. The module will be called sc520_wdt.
520 config SBC_FITPC2_WATCHDOG
521 tristate "Compulab SBC-FITPC2 watchdog"
524 This is the driver for the built-in watchdog timer on the fit-PC2,
525 fit-PC2i, CM-iAM single-board computers made by Compulab.
527 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
528 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
530 Entering BIOS setup temporary disables watchdog operation regardless to current state,
531 so system will not be restarted while user in BIOS setup.
533 Once watchdog was enabled the system will be restarted every
534 "Watchdog Timer Value" period, so to prevent it user can restart or
535 disable the watchdog.
537 To compile this driver as a module, choose M here: the
538 module will be called sbc_fitpc2_wdt.
540 Most people will say N.
543 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
546 Enable support for the watchdog timer on the Eurotech CPU-1220 and
547 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
548 information are at <http://www.eurotech.it/>.
551 tristate "IB700 SBC Watchdog Timer"
554 This is the driver for the hardware watchdog on the IB700 Single
555 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
556 simply watches your kernel to make sure it doesn't freeze, and if
557 it does, it reboots your computer after a certain amount of time.
559 This driver is like the WDT501 driver but for slightly different hardware.
561 To compile this driver as a module, choose M here: the
562 module will be called ib700wdt.
564 Most people will say N.
567 tristate "IBM Automatic Server Restart"
570 This is the driver for the IBM Automatic Server Restart watchdog
571 timer built-in into some eServer xSeries machines.
573 To compile this driver as a module, choose M here: the
574 module will be called ibmasr.
577 tristate "ICP Single Board Computer Watchdog Timer"
580 This is a driver for the hardware watchdog on the ICP Single
581 Board Computer. This driver is working on (at least) the following
582 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
584 To compile this driver as a module, choose M here: the
585 module will be called wafer5823wdt.
588 tristate "Intel 6300ESB Timer/Watchdog"
591 Hardware driver for the watchdog timer built into the Intel
592 6300ESB controller hub.
594 To compile this driver as a module, choose M here: the
595 module will be called i6300esb.
598 tristate "Intel Atom E6xx Watchdog"
599 depends on X86 && PCI
604 Hardware driver for the watchdog timer built into the Intel
605 Atom E6XX (TunnelCreek) processor.
607 To compile this driver as a module, choose M here: the
608 module will be called ie6xx_wdt.
610 config INTEL_SCU_WATCHDOG
611 bool "Intel SCU Watchdog for Mobile Platforms"
612 depends on X86_INTEL_MID
614 Hardware driver for the watchdog time built into the Intel SCU
615 for Intel Mobile Platforms.
617 To compile this driver as a module, choose M here.
620 tristate "Intel TCO Timer/Watchdog"
621 depends on (X86 || IA64) && PCI
625 Hardware driver for the intel TCO timer based watchdog devices.
626 These drivers are included in the Intel 82801 I/O Controller
627 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
630 The TCO (Total Cost of Ownership) timer is a watchdog timer
631 that will reboot the machine after its second expiration. The
632 expiration time can be configured with the "heartbeat" parameter.
634 On some motherboards the driver may fail to reset the chipset's
635 NO_REBOOT flag which prevents the watchdog from rebooting the
636 machine. If this is the case you will get a kernel message like
637 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
639 To compile this driver as a module, choose M here: the
640 module will be called iTCO_wdt.
642 config ITCO_VENDOR_SUPPORT
643 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
646 Add vendor specific support to the intel TCO timer based watchdog
647 devices. At this moment we only have additional support for some
648 SuperMicro Inc. motherboards.
651 tristate "IT8712F (Smart Guardian) Watchdog Timer"
654 This is the driver for the built-in watchdog timer on the IT8712F
655 Super I/0 chipset used on many motherboards.
657 If the driver does not work, then make sure that the game port in
660 To compile this driver as a module, choose M here: the
661 module will be called it8712f_wdt.
664 tristate "IT87 Watchdog Timer"
667 This is the driver for the hardware watchdog on the ITE IT8702,
668 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
671 If the driver does not work, then make sure that the game port in
674 This watchdog simply watches your kernel to make sure it doesn't
675 freeze, and if it does, it reboots your computer after a certain
678 To compile this driver as a module, choose M here: the module will
682 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
683 depends on X86 && PCI
685 A software monitoring watchdog and NMI sourcing driver. This driver
686 will detect lockups and provide a stack trace. This is a driver that
687 will only load on an HP ProLiant system with a minimum of iLO2 support.
688 To compile this driver as a module, choose M here: the module will be
692 tristate "Kontron COM Watchdog Timer"
693 depends on MFD_KEMPLD
696 Support for the PLD watchdog on some Kontron ETX and COMexpress
699 This driver can also be built as a module. If so, the module will be
702 config HPWDT_NMI_DECODING
703 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
704 depends on HP_WATCHDOG
707 When an NMI occurs this feature will make the necessary BIOS calls to
708 log the cause of the NMI.
711 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
714 This is a driver for National Semiconductor PC87307/PC97307 hardware
715 watchdog cards as found on the SC1200. This watchdog is mainly used
716 for power management purposes and can be used to power down the device
717 during inactivity periods (includes interrupt activity monitoring).
719 To compile this driver as a module, choose M here: the
720 module will be called sc1200wdt.
722 Most people will say N.
725 tristate "National Semiconductor SCx200 Watchdog"
726 depends on SCx200 && PCI
728 Enable the built-in watchdog timer support on the National
729 Semiconductor SCx200 processors.
731 If compiled as a module, it will be called scx200_wdt.
734 tristate "NS PC87413 watchdog"
737 This is the driver for the hardware watchdog on the PC87413 chipset
738 This watchdog simply watches your kernel to make sure it doesn't
739 freeze, and if it does, it reboots your computer after a certain
742 To compile this driver as a module, choose M here: the
743 module will be called pc87413_wdt.
745 Most people will say N.
748 tristate "nVidia TCO Timer/Watchdog"
749 depends on X86 && PCI
751 Hardware driver for the TCO timer built into the nVidia Hub family
752 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
753 watchdog timer that will reboot the machine after its second
754 expiration. The expiration time can be configured with the
755 "heartbeat" parameter.
757 On some motherboards the driver may fail to reset the chipset's
758 NO_REBOOT flag which prevents the watchdog from rebooting the
759 machine. If this is the case you will get a kernel message like
760 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
762 To compile this driver as a module, choose M here: the
763 module will be called nv_tco.
766 tristate "RDC R-321x SoC watchdog"
767 depends on X86_RDC321X
769 This is the driver for the built in hardware watchdog
770 in the RDC R-321x SoC.
772 To compile this driver as a module, choose M here: the
773 module will be called rdc321x_wdt.
776 tristate "SBC-60XX Watchdog Timer"
779 This driver can be used with the watchdog timer found on some
780 single board computers, namely the 6010 PII based computer.
781 It may well work with other cards. It reads port 0x443 to enable
782 and re-set the watchdog timer, and reads port 0x45 to disable
783 the watchdog. If you have a card that behave in similar ways,
784 you can probably make this driver work with your card as well.
786 You can compile this driver directly into the kernel, or use
787 it as a module. The module will be called sbc60xxwdt.
790 tristate "SBC8360 Watchdog Timer"
794 This is the driver for the hardware watchdog on the SBC8360 Single
795 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
797 To compile this driver as a module, choose M here: the
798 module will be called sbc8360.
800 Most people will say N.
803 tristate "SBC Nano 7240 Watchdog Timer"
804 depends on X86_32 && !UML
806 This is the driver for the hardware watchdog found on the IEI
807 single board computers EPIC Nano 7240 (and likely others). This
808 watchdog simply watches your kernel to make sure it doesn't freeze,
809 and if it does, it reboots your computer after a certain amount of
812 To compile this driver as a module, choose M here: the
813 module will be called sbc7240_wdt.
816 tristate "SMA CPU5 Watchdog"
820 To compile this driver as a module, choose M here: the
821 module will be called cpu5wdt.
823 config SMSC_SCH311X_WDT
824 tristate "SMSC SCH311X Watchdog Timer"
827 This is the driver for the hardware watchdog timer on the
828 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
829 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
832 To compile this driver as a module, choose M here: the
833 module will be called sch311x_wdt.
835 config SMSC37B787_WDT
836 tristate "Winbond SMsC37B787 Watchdog Timer"
839 This is the driver for the hardware watchdog component on the
840 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
841 from Vision Systems and maybe others.
843 This watchdog simply watches your kernel to make sure it doesn't
844 freeze, and if it does, it reboots your computer after a certain
847 Usually a userspace daemon will notify the kernel WDT driver that
848 userspace is still alive, at regular intervals.
850 To compile this driver as a module, choose M here: the
851 module will be called smsc37b787_wdt.
853 Most people will say N.
856 tristate "VIA Watchdog Timer"
857 depends on X86 && PCI
860 This is the driver for the hardware watchdog timer on VIA
861 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
863 To compile this driver as a module, choose M here; the module
864 will be called via_wdt.
866 Most people will say N.
869 tristate "W83627HF/W83627DHG Watchdog Timer"
872 This is the driver for the hardware watchdog on the W83627HF chipset
873 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
874 (and likely others). The driver also supports the W83627DHG chip.
875 This watchdog simply watches your kernel to make sure it doesn't
876 freeze, and if it does, it reboots your computer after a certain
879 To compile this driver as a module, choose M here: the
880 module will be called w83627hf_wdt.
882 Most people will say N.
885 tristate "W83697HF/W83697HG Watchdog Timer"
888 This is the driver for the hardware watchdog on the W83697HF/HG
889 chipset as used in Dedibox/VIA motherboards (and likely others).
890 This watchdog simply watches your kernel to make sure it doesn't
891 freeze, and if it does, it reboots your computer after a certain
894 To compile this driver as a module, choose M here: the
895 module will be called w83697hf_wdt.
897 Most people will say N.
900 tristate "W83697UG/W83697UF Watchdog Timer"
903 This is the driver for the hardware watchdog on the W83697UG/UF
904 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
905 This watchdog simply watches your kernel to make sure it doesn't
906 freeze, and if it does, it reboots your computer after a certain
909 To compile this driver as a module, choose M here: the
910 module will be called w83697ug_wdt.
912 Most people will say N.
915 tristate "W83877F (EMACS) Watchdog Timer"
918 This is the driver for the hardware watchdog on the W83877F chipset
919 as used in EMACS PC-104 motherboards (and likely others). This
920 watchdog simply watches your kernel to make sure it doesn't freeze,
921 and if it does, it reboots your computer after a certain amount of
924 To compile this driver as a module, choose M here: the
925 module will be called w83877f_wdt.
927 Most people will say N.
930 tristate "W83977F (PCM-5335) Watchdog Timer"
933 This is the driver for the hardware watchdog on the W83977F I/O chip
934 as used in AAEON's PCM-5335 SBC (and likely others). This
935 watchdog simply watches your kernel to make sure it doesn't freeze,
936 and if it does, it reboots your computer after a certain amount of
939 To compile this driver as a module, choose M here: the
940 module will be called w83977f_wdt.
943 tristate "ZF MachZ Watchdog"
946 If you are using a ZF Micro MachZ processor, say Y here, otherwise
947 N. This is the driver for the watchdog timer built-in on that
948 processor using ZF-Logic interface. This watchdog simply watches
949 your kernel to make sure it doesn't freeze, and if it does, it
950 reboots your computer after a certain amount of time.
952 To compile this driver as a module, choose M here: the
953 module will be called machzwd.
955 config SBC_EPX_C3_WATCHDOG
956 tristate "Winsystems SBC EPX-C3 watchdog"
959 This is the driver for the built-in watchdog timer on the EPX-C3
960 Single-board computer made by Winsystems, Inc.
962 *Note*: This hardware watchdog is not probeable and thus there
963 is no way to know if writing to its IO address will corrupt
964 your system or have any real effect. The only way to be sure
965 that this driver does what you want is to make sure you
966 are running it on an EPX-C3 from Winsystems with the watchdog
967 timer at IO address 0x1ee and 0x1ef. It will write to both those
968 IO ports. Basically, the assumption is made that if you compile
969 this driver into your kernel and/or load it as a module, that you
970 know what you are doing and that you are in fact running on an
973 To compile this driver as a module, choose M here: the
974 module will be called sbc_epx_c3.
980 config M54xx_WATCHDOG
981 tristate "MCF54xx watchdog support"
984 To compile this driver as a module, choose M here: the
985 module will be called m54xx_wdt.
987 # MicroBlaze Architecture
989 config XILINX_WATCHDOG
990 tristate "Xilinx Watchdog timer"
991 depends on MICROBLAZE
993 Watchdog driver for the xps_timebase_wdt ip core.
995 IMPORTANT: The xps_timebase_wdt parent must have the property
996 "clock-frequency" at device tree.
998 To compile this driver as a module, choose M here: the
999 module will be called of_xilinx_wdt.
1004 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1007 Hardware driver for the built-in watchdog timer on the Atheros
1008 AR71XX/AR724X/AR913X SoCs.
1011 tristate "Broadcom BCM47xx Watchdog Timer"
1013 select WATCHDOG_CORE
1015 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1018 tristate "IDT RC32434 SoC Watchdog Timer"
1019 depends on MIKROTIK_RB532
1021 Hardware driver for the IDT RC32434 SoC built-in
1024 To compile this driver as a module, choose M here: the
1025 module will be called rc32434_wdt.
1028 tristate "Indy/I2 Hardware Watchdog"
1029 depends on SGI_HAS_INDYDOG
1031 Hardware driver for the Indy's/I2's watchdog. This is a
1032 watchdog timer that will reboot the machine after a 60 second
1033 timer expired and no process has written to /dev/watchdog during
1037 tristate "Ingenic jz4740 SoC hardware watchdog"
1038 depends on MACH_JZ4740
1039 select WATCHDOG_CORE
1041 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1044 tristate "MTX-1 Hardware Watchdog"
1045 depends on MIPS_MTX1
1047 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1048 will reboot the machine after a 100 seconds timer expired.
1051 tristate "PNX833x Hardware Watchdog"
1052 depends on SOC_PNX8335
1054 Hardware driver for the PNX833x's watchdog. This is a
1055 watchdog timer that will reboot the machine after a programmable
1056 timer has expired and no process has written to /dev/watchdog during
1060 tristate "Sibyte SoC hardware watchdog"
1063 Watchdog driver for the built in watchdog hardware in Sibyte
1064 SoC processors. There are apparently two watchdog timers
1065 on such processors; this driver supports only the first one,
1066 because currently Linux only supports exporting one watchdog
1069 To compile this driver as a loadable module, choose M here.
1070 The module will be called sb_wdog.
1073 tristate "TI AR7 Watchdog Timer"
1076 Hardware driver for the TI AR7 Watchdog Timer.
1079 tristate "Toshiba TXx9 Watchdog Timer"
1080 depends on CPU_TX39XX || CPU_TX49XX
1081 select WATCHDOG_CORE
1083 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1086 tristate "Cavium OCTEON SOC family Watchdog Timer"
1087 depends on CAVIUM_OCTEON_SOC
1089 select EXPORT_UASM if OCTEON_WDT = m
1091 Hardware driver for OCTEON's on chip watchdog timer.
1092 Enables the watchdog for all cores running Linux. It
1093 installs a NMI handler and pokes the watchdog based on an
1094 interrupt. On first expiration of the watchdog, the
1095 interrupt handler pokes it. The second expiration causes an
1096 NMI that prints a message. The third expiration causes a
1099 When userspace has /dev/watchdog open, no poking is done
1100 from the first interrupt, it is then only poked when the
1104 tristate "Broadcom BCM63xx hardware watchdog"
1107 Watchdog driver for the built in watchdog hardware in Broadcom
1110 To compile this driver as a loadable module, choose M here.
1111 The module will be called bcm63xx_wdt.
1114 tristate "Broadcom BCM2835 hardware watchdog"
1115 depends on ARCH_BCM2835
1116 select WATCHDOG_CORE
1118 Watchdog driver for the built in watchdog hardware in Broadcom
1121 To compile this driver as a loadable module, choose M here.
1122 The module will be called bcm2835_wdt.
1125 tristate "Lantiq SoC watchdog"
1128 Hardware driver for the Lantiq SoC Watchdog Timer.
1130 # PARISC Architecture
1132 # POWERPC Architecture
1135 tristate "GE Watchdog Timer"
1138 Watchdog timer found in a number of GE single board computers.
1141 bool "MPC52xx Watchdog Timer"
1142 depends on PPC_MPC52xx
1144 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1147 tristate "MPC8xxx Platform Watchdog Timer"
1148 depends on PPC_8xx || PPC_83xx || PPC_86xx
1150 This driver is for a SoC level watchdog that exists on some
1151 Freescale PowerPC processors. So far this driver supports:
1156 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1159 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1163 tristate "PIKA FPGA Watchdog"
1167 This enables the watchdog in the PIKA FPGA. Currently used on
1171 tristate "PowerPC Book-E Watchdog Timer"
1172 depends on BOOKE || 4xx
1173 select WATCHDOG_CORE
1175 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1176 MPC85xx SOCs and the IBM PowerPC 440.
1178 Please see Documentation/watchdog/watchdog-api.txt for
1181 config BOOKE_WDT_DEFAULT_TIMEOUT
1182 int "PowerPC Book-E Watchdog Timer Default Timeout"
1183 depends on BOOKE_WDT
1184 default 38 if PPC_FSL_BOOK3E
1185 range 0 63 if PPC_FSL_BOOK3E
1186 default 3 if !PPC_FSL_BOOK3E
1187 range 0 3 if !PPC_FSL_BOOK3E
1189 Select the default watchdog timer period to be used by the PowerPC
1190 Book-E watchdog driver. A watchdog "event" occurs when the bit
1191 position represented by this number transitions from zero to one.
1193 For Freescale Book-E processors, this is a number between 0 and 63.
1194 For other Book-E processors, this is a number between 0 and 3.
1196 The value can be overridden by the wdt_period command-line parameter.
1199 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1200 select WATCHDOG_CORE
1203 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1205 The driver can also be built as a module. If so, the module will be
1208 If unsure select N here.
1210 # PPC64 Architecture
1212 config WATCHDOG_RTAS
1213 tristate "RTAS watchdog"
1216 This driver adds watchdog support for the RTAS watchdog.
1218 To compile this driver as a module, choose M here. The module
1219 will be called wdrtas.
1224 tristate "z/VM Watchdog Timer"
1227 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1228 provide a virtual watchdog timer to their guest that cause a
1229 user define Control Program command to be executed after a
1232 To compile this driver as a module, choose M here. The module
1233 will be called vmwatchdog.
1235 # SUPERH (sh + sh64) Architecture
1238 tristate "SuperH Watchdog"
1239 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1240 select WATCHDOG_CORE
1242 This driver adds watchdog support for the integrated watchdog in the
1243 SuperH processors. If you have one of these processors and wish
1244 to have watchdog support enabled, say Y, otherwise say N.
1246 As a side note, saying Y here will automatically boost HZ to 1000
1247 so that the timer has a chance to clear the overflow counter. On
1248 slower systems (such as the SH-2 and SH-3) this will likely yield
1249 some performance issues. As such, the WDT should be avoided here
1250 unless it is absolutely necessary.
1252 To compile this driver as a module, choose M here: the
1253 module will be called shwdt.
1255 # SPARC Architecture
1257 # SPARC64 Architecture
1259 config WATCHDOG_CP1XXX
1260 tristate "CP1XXX Hardware Watchdog support"
1261 depends on SPARC64 && PCI
1263 This is the driver for the hardware watchdog timers present on
1264 Sun Microsystems CompactPCI models CP1400 and CP1500.
1266 To compile this driver as a module, choose M here: the
1267 module will be called cpwatchdog.
1269 If you do not have a CompactPCI model CP1400 or CP1500, or
1270 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1271 you should say N to this option.
1274 tristate "RIO Hardware Watchdog support"
1275 depends on SPARC64 && PCI
1277 Say Y here to support the hardware watchdog capability on Sun RIO
1278 machines. The watchdog timeout period is normally one minute but
1279 can be changed with a boot-time parameter.
1281 # XTENSA Architecture
1286 tristate "Xen Watchdog support"
1289 Say Y here to support the hypervisor watchdog capability provided
1290 by Xen 4.0 and newer. The watchdog timeout period is normally one
1291 minute but can be changed with a boot-time parameter.
1294 tristate "UML watchdog"
1298 # ISA-based Watchdog Cards
1301 comment "ISA-based Watchdog Cards"
1305 tristate "Berkshire Products ISA-PC Watchdog"
1308 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1309 This card simply watches your kernel to make sure it doesn't freeze,
1310 and if it does, it reboots your computer after a certain amount of
1311 time. This driver is like the WDT501 driver but for different
1312 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1313 watchdog cards can be ordered from <http://www.berkprod.com/>.
1315 To compile this driver as a module, choose M here: the
1316 module will be called pcwd.
1318 Most people will say N.
1321 tristate "Mixcom Watchdog"
1324 This is a driver for the Mixcom hardware watchdog cards. This
1325 watchdog simply watches your kernel to make sure it doesn't freeze,
1326 and if it does, it reboots your computer after a certain amount of
1329 To compile this driver as a module, choose M here: the
1330 module will be called mixcomwd.
1332 Most people will say N.
1335 tristate "WDT Watchdog timer"
1338 If you have a WDT500P or WDT501P watchdog board, say Y here,
1339 otherwise N. It is not possible to probe for this board, which means
1340 that you have to inform the kernel about the IO port and IRQ that
1341 is needed (you can do this via the io and irq parameters)
1343 To compile this driver as a module, choose M here: the
1344 module will be called wdt.
1347 # PCI-based Watchdog Cards
1350 comment "PCI-based Watchdog Cards"
1353 config PCIPCWATCHDOG
1354 tristate "Berkshire Products PCI-PC Watchdog"
1357 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1358 This card simply watches your kernel to make sure it doesn't freeze,
1359 and if it does, it reboots your computer after a certain amount of
1360 time. The card can also monitor the internal temperature of the PC.
1361 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1363 To compile this driver as a module, choose M here: the
1364 module will be called pcwd_pci.
1366 Most people will say N.
1369 tristate "PCI-WDT500/501 Watchdog timer"
1372 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1374 If you have a PCI-WDT501 watchdog board then you can enable the
1375 temperature sensor by setting the type parameter to 501.
1377 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1378 can do this via the tachometer parameter. Only do this if you have a
1379 fan tachometer actually set up.
1381 To compile this driver as a module, choose M here: the
1382 module will be called wdt_pci.
1385 # USB-based Watchdog Cards
1388 comment "USB-based Watchdog Cards"
1391 config USBPCWATCHDOG
1392 tristate "Berkshire Products USB-PC Watchdog"
1395 This is the driver for the Berkshire Products USB-PC Watchdog card.
1396 This card simply watches your kernel to make sure it doesn't freeze,
1397 and if it does, it reboots your computer after a certain amount of
1398 time. The card can also monitor the internal temperature of the PC.
1399 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1401 To compile this driver as a module, choose M here: the
1402 module will be called pcwd_usb.
1404 Most people will say N.