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.
91 tristate "Watchdog device controlled through GPIO-line"
95 If you say yes here you get support for watchdog device
96 controlled through GPIO-line.
98 config WM831X_WATCHDOG
99 tristate "WM831x watchdog"
100 depends on MFD_WM831X
103 Support for the watchdog in the WM831x AudioPlus PMICs. When
104 the watchdog triggers the system will be reset.
106 config WM8350_WATCHDOG
107 tristate "WM8350 watchdog"
108 depends on MFD_WM8350
111 Support for the watchdog in the WM8350 AudioPlus PMIC. When
112 the watchdog triggers the system will be reset.
114 config XILINX_WATCHDOG
115 tristate "Xilinx Watchdog timer"
118 Watchdog driver for the xps_timebase_wdt ip core.
120 To compile this driver as a module, choose M here: the
121 module will be called of_xilinx_wdt.
127 config ARM_SP805_WATCHDOG
128 tristate "ARM SP805 Watchdog"
129 depends on (ARM || ARM64) && ARM_AMBA
132 ARM Primecell SP805 Watchdog timer. This will reboot your system when
133 the timeout is reached.
135 config AT91RM9200_WATCHDOG
136 tristate "AT91RM9200 watchdog"
137 depends on ARCH_AT91RM9200
139 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
140 system when the timeout is reached.
142 config AT91SAM9X_WATCHDOG
143 tristate "AT91SAM9X / AT91CAP9 watchdog"
144 depends on ARCH_AT91 && !ARCH_AT91RM9200
147 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
148 reboot your system when the timeout is reached.
150 config 21285_WATCHDOG
151 tristate "DC21285 watchdog"
152 depends on FOOTBRIDGE
154 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
155 here if you wish to use this. Alternatively say M to compile the
156 driver as a module, which will be called wdt285.
158 This driver does not work on all machines. In particular, early CATS
159 boards have hardware problems that will cause the machine to simply
160 lock up if the watchdog fires.
162 "If in doubt, leave it out" - say N.
165 tristate "NetWinder WB83C977 watchdog"
166 depends on FOOTBRIDGE && ARCH_NETWINDER
168 Say Y here to include support for the WB977 watchdog included in
169 NetWinder machines. Alternatively say M to compile the driver as
170 a module, which will be called wdt977.
172 Not sure? It's safe to say N.
174 config IXP4XX_WATCHDOG
175 tristate "IXP4xx Watchdog"
176 depends on ARCH_IXP4XX
178 Say Y here if to include support for the watchdog timer
179 in the Intel IXP4xx network processors. This driver can
180 be built as a module by choosing M. The module will
181 be called ixp4xx_wdt.
183 Note: The internal IXP4xx watchdog does a soft CPU reset
184 which doesn't reset any peripherals. There are circumstances
185 where the watchdog will fail to reset the board correctly
186 (e.g., if the boot ROM is in an unreadable state).
188 Say N if you are unsure.
190 config KS8695_WATCHDOG
191 tristate "KS8695 watchdog"
192 depends on ARCH_KS8695
194 Watchdog timer embedded into KS8695 processor. This will reboot your
195 system when the timeout is reached.
197 config HAVE_S3C2410_WATCHDOG
200 This will include watchdog timer support for Samsung SoCs. If
201 you want to include watchdog support for any machine, kindly
202 select this in the respective mach-XXXX/Kconfig file.
204 config S3C2410_WATCHDOG
205 tristate "S3C2410 Watchdog"
206 depends on HAVE_S3C2410_WATCHDOG
208 select MFD_SYSCON if ARCH_EXYNOS5
210 Watchdog timer block in the Samsung SoCs. This will reboot
211 the system when the timer expires with the watchdog enabled.
213 The driver is limited by the speed of the system's PCLK
214 signal, so with reasonably fast systems (PCLK around 50-66MHz)
215 then watchdog intervals of over approximately 20seconds are
218 The driver can be built as a module by choosing M, and will
219 be called s3c2410_wdt
221 config SA1100_WATCHDOG
222 tristate "SA1100/PXA2xx watchdog"
223 depends on ARCH_SA1100 || ARCH_PXA
225 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
226 reboot your system when timeout is reached.
228 NOTE: once enabled, this timer cannot be disabled.
230 To compile this driver as a module, choose M here: the
231 module will be called sa1100_wdt.
234 tristate "Synopsys DesignWare watchdog"
237 Say Y here if to include support for the Synopsys DesignWare
238 watchdog timer found in many chips.
239 To compile this driver as a module, choose M here: the
240 module will be called dw_wdt.
242 config EP93XX_WATCHDOG
243 tristate "EP93xx Watchdog"
244 depends on ARCH_EP93XX
247 Say Y here if to include support for the watchdog timer
248 embedded in the Cirrus Logic EP93xx family of devices.
250 To compile this driver as a module, choose M here: the
251 module will be called ep93xx_wdt.
254 tristate "OMAP Watchdog"
255 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
258 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
259 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
261 config PNX4008_WATCHDOG
262 tristate "LPC32XX Watchdog"
263 depends on ARCH_LPC32XX
266 Say Y here if to include support for the watchdog timer
267 in the LPC32XX processor.
268 This driver can be built as a module by choosing M. The module
269 will be called pnx4008_wdt.
271 Say N if you are unsure.
274 tristate "IOP Watchdog"
276 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
278 Say Y here if to include support for the watchdog timer
279 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
280 be built as a module by choosing M. The module will
283 Note: The IOP13XX watchdog does an Internal Bus Reset which will
284 affect both cores and the peripherals of the IOP. The ATU-X
285 and/or ATUe configuration registers will remain intact, but if
286 operating as an Root Complex and/or Central Resource, the PCI-X
287 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
289 config DAVINCI_WATCHDOG
290 tristate "DaVinci watchdog"
291 depends on ARCH_DAVINCI || ARCH_KEYSTONE
294 Say Y here if to include support for the watchdog timer
295 in the DaVinci DM644x/DM646x or Keystone processors.
296 To compile this driver as a module, choose M here: the
297 module will be called davinci_wdt.
299 NOTE: once enabled, this timer cannot be disabled.
300 Say N if you are unsure.
302 config ORION_WATCHDOG
303 tristate "Orion watchdog"
304 depends on ARCH_ORION5X || ARCH_KIRKWOOD || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
307 Say Y here if to include support for the watchdog timer
308 in the Marvell Orion5x and Kirkwood ARM SoCs.
309 To compile this driver as a module, choose M here: the
310 module will be called orion_wdt.
312 config SUNXI_WATCHDOG
313 tristate "Allwinner SoCs watchdog support"
314 depends on ARCH_SUNXI
317 Say Y here to include support for the watchdog timer
319 To compile this driver as a module, choose M here: the
320 module will be called sunxi_wdt.
322 config COH901327_WATCHDOG
323 bool "ST-Ericsson COH 901 327 watchdog"
325 default y if MACH_U300
328 Say Y here to include Watchdog timer support for the
329 watchdog embedded into the ST-Ericsson U300 series platforms.
330 This watchdog is used to reset the system and thus cannot be
331 compiled as a module.
333 config TWL4030_WATCHDOG
334 tristate "TWL4030 Watchdog"
335 depends on TWL4030_CORE
338 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
339 watchdog timer support for TWL4030 chips.
341 config STMP3XXX_RTC_WATCHDOG
342 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
343 depends on RTC_DRV_STMP
346 Say Y here to include support for the watchdog timer inside
347 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
348 To compile this driver as a module, choose M here: the
349 module will be called stmp3xxx_rtc_wdt.
351 config NUC900_WATCHDOG
352 tristate "Nuvoton NUC900 watchdog"
353 depends on ARCH_W90X900
355 Say Y here if to include support for the watchdog timer
356 for the Nuvoton NUC900 series SoCs.
357 To compile this driver as a module, choose M here: the
358 module will be called nuc900_wdt.
360 config TS72XX_WATCHDOG
361 tristate "TS-72XX SBC Watchdog"
362 depends on MACH_TS72XX
364 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
365 watchdog timer implemented in a external CPLD chip. Say Y here
366 if you want to support for the watchdog timer on TS-72XX boards.
368 To compile this driver as a module, choose M here: the
369 module will be called ts72xx_wdt.
371 config MAX63XX_WATCHDOG
372 tristate "Max63xx watchdog"
373 depends on ARM && HAS_IOMEM
376 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
379 tristate "IMX2+ Watchdog"
382 This is the driver for the hardware watchdog
383 on the Freescale IMX2 and later processors.
384 If you have one of these processors and wish to have
385 watchdog support enabled, say Y, otherwise say N.
387 To compile this driver as a module, choose M here: the
388 module will be called imx2_wdt.
390 config UX500_WATCHDOG
391 tristate "ST-Ericsson Ux500 watchdog"
392 depends on MFD_DB8500_PRCMU
396 Say Y here to include Watchdog timer support for the watchdog
397 existing in the prcmu of ST-Ericsson Ux500 series platforms.
399 To compile this driver as a module, choose M here: the
400 module will be called ux500_wdt.
403 tristate "Retu watchdog"
407 Retu watchdog driver for Nokia Internet Tablets (770, N800,
408 N810). At least on N800 the watchdog cannot be disabled, so
409 this driver is essential and you should enable it.
411 To compile this driver as a module, choose M here: the
412 module will be called retu_wdt.
415 tristate "MOXART watchdog"
416 depends on ARCH_MOXART
418 Say Y here to include Watchdog timer support for the watchdog
419 existing on the MOXA ART SoC series platforms.
421 To compile this driver as a module, choose M here: the
422 module will be called moxart_wdt.
424 config SIRFSOC_WATCHDOG
425 tristate "SiRFSOC watchdog"
430 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
431 the watchdog triggers the system will be reset.
433 config TEGRA_WATCHDOG
434 tristate "Tegra watchdog"
435 depends on ARCH_TEGRA || COMPILE_TEST
438 Say Y here to include support for the watchdog timer
439 embedded in NVIDIA Tegra SoCs.
441 To compile this driver as a module, choose M here: the
442 module will be called tegra_wdt.
446 config AT32AP700X_WDT
447 tristate "AT32AP700x watchdog"
448 depends on CPU_AT32AP700X
450 Watchdog timer embedded into AT32AP700x devices. This will reboot
451 your system when the timeout is reached.
453 # BLACKFIN Architecture
456 tristate "Blackfin On-Chip Watchdog Timer"
459 If you say yes here you will get support for the Blackfin On-Chip
460 Watchdog Timer. If you have one of these processors and wish to
461 have watchdog support enabled, say Y, otherwise say N.
463 To compile this driver as a module, choose M here: the
464 module will be called bfin_wdt.
470 # X86 (i386 + ia64 + x86_64) Architecture
473 tristate "Acquire SBC Watchdog Timer"
476 This is the driver for the hardware watchdog on Single Board
477 Computers produced by Acquire Inc (and others). This watchdog
478 simply watches your kernel to make sure it doesn't freeze, and if
479 it does, it reboots your computer after a certain amount of time.
481 To compile this driver as a module, choose M here: the
482 module will be called acquirewdt.
484 Most people will say N.
487 tristate "Advantech SBC Watchdog Timer"
490 If you are configuring a Linux kernel for the Advantech single-board
491 computer, say `Y' here to support its built-in watchdog timer
492 feature. More information can be found at
493 <http://www.advantech.com.tw/products/>
496 tristate "ALi M1535 PMU Watchdog Timer"
497 depends on X86 && PCI
499 This is the driver for the hardware watchdog on the ALi M1535 PMU.
501 To compile this driver as a module, choose M here: the
502 module will be called alim1535_wdt.
504 Most people will say N.
507 tristate "ALi M7101 PMU Computer Watchdog"
510 This is the driver for the hardware watchdog on the ALi M7101 PMU
511 as used in the x86 Cobalt servers and also found in some
512 SPARC Netra servers too.
514 To compile this driver as a module, choose M here: the
515 module will be called alim7101_wdt.
517 Most people will say N.
520 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
523 This is the driver for the hardware watchdog on the Fintek
524 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
526 You can compile this driver directly into the kernel, or use
527 it as a module. The module will be called f71808e_wdt.
530 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
531 depends on X86 && PCI
533 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
534 (Total Cost of Ownership) timer is a watchdog timer that will reboot
535 the machine after its expiration. The expiration time can be
536 configured with the "heartbeat" parameter.
538 To compile this driver as a module, choose M here: the
539 module will be called sp5100_tco.
542 tristate "AMD Geode CS5535/CS5536 Watchdog"
543 depends on CS5535_MFGPT
545 This driver enables a watchdog capability built into the
546 CS5535/CS5536 companion chips for the AMD Geode GX and LX
547 processors. This watchdog watches your kernel to make sure
548 it doesn't freeze, and if it does, it reboots your computer after
549 a certain amount of time.
551 You can compile this driver directly into the kernel, or use
552 it as a module. The module will be called geodewdt.
555 tristate "AMD Elan SC520 processor Watchdog"
558 This is the driver for the hardware watchdog built in to the
559 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
560 This watchdog simply watches your kernel to make sure it doesn't
561 freeze, and if it does, it reboots your computer after a certain
564 You can compile this driver directly into the kernel, or use
565 it as a module. The module will be called sc520_wdt.
567 config SBC_FITPC2_WATCHDOG
568 tristate "Compulab SBC-FITPC2 watchdog"
571 This is the driver for the built-in watchdog timer on the fit-PC2,
572 fit-PC2i, CM-iAM single-board computers made by Compulab.
574 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
575 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
577 Entering BIOS setup temporary disables watchdog operation regardless to current state,
578 so system will not be restarted while user in BIOS setup.
580 Once watchdog was enabled the system will be restarted every
581 "Watchdog Timer Value" period, so to prevent it user can restart or
582 disable the watchdog.
584 To compile this driver as a module, choose M here: the
585 module will be called sbc_fitpc2_wdt.
587 Most people will say N.
590 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
593 Enable support for the watchdog timer on the Eurotech CPU-1220 and
594 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
595 information are at <http://www.eurotech.it/>.
598 tristate "IB700 SBC Watchdog Timer"
601 This is the driver for the hardware watchdog on the IB700 Single
602 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
603 simply watches your kernel to make sure it doesn't freeze, and if
604 it does, it reboots your computer after a certain amount of time.
606 This driver is like the WDT501 driver but for slightly different hardware.
608 To compile this driver as a module, choose M here: the
609 module will be called ib700wdt.
611 Most people will say N.
614 tristate "IBM Automatic Server Restart"
617 This is the driver for the IBM Automatic Server Restart watchdog
618 timer built-in into some eServer xSeries machines.
620 To compile this driver as a module, choose M here: the
621 module will be called ibmasr.
624 tristate "ICP Single Board Computer Watchdog Timer"
627 This is a driver for the hardware watchdog on the ICP Single
628 Board Computer. This driver is working on (at least) the following
629 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
631 To compile this driver as a module, choose M here: the
632 module will be called wafer5823wdt.
635 tristate "Intel 6300ESB Timer/Watchdog"
638 Hardware driver for the watchdog timer built into the Intel
639 6300ESB controller hub.
641 To compile this driver as a module, choose M here: the
642 module will be called i6300esb.
645 tristate "Intel Atom E6xx Watchdog"
646 depends on X86 && PCI
651 Hardware driver for the watchdog timer built into the Intel
652 Atom E6XX (TunnelCreek) processor.
654 To compile this driver as a module, choose M here: the
655 module will be called ie6xx_wdt.
657 config INTEL_SCU_WATCHDOG
658 bool "Intel SCU Watchdog for Mobile Platforms"
659 depends on X86_INTEL_MID
661 Hardware driver for the watchdog time built into the Intel SCU
662 for Intel Mobile Platforms.
664 To compile this driver as a module, choose M here.
667 tristate "Intel TCO Timer/Watchdog"
668 depends on (X86 || IA64) && PCI
672 Hardware driver for the intel TCO timer based watchdog devices.
673 These drivers are included in the Intel 82801 I/O Controller
674 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
677 The TCO (Total Cost of Ownership) timer is a watchdog timer
678 that will reboot the machine after its second expiration. The
679 expiration time can be configured with the "heartbeat" parameter.
681 On some motherboards the driver may fail to reset the chipset's
682 NO_REBOOT flag which prevents the watchdog from rebooting the
683 machine. If this is the case you will get a kernel message like
684 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
686 To compile this driver as a module, choose M here: the
687 module will be called iTCO_wdt.
689 config ITCO_VENDOR_SUPPORT
690 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
693 Add vendor specific support to the intel TCO timer based watchdog
694 devices. At this moment we only have additional support for some
695 SuperMicro Inc. motherboards.
698 tristate "IT8712F (Smart Guardian) Watchdog Timer"
701 This is the driver for the built-in watchdog timer on the IT8712F
702 Super I/0 chipset used on many motherboards.
704 If the driver does not work, then make sure that the game port in
707 To compile this driver as a module, choose M here: the
708 module will be called it8712f_wdt.
711 tristate "IT87 Watchdog Timer"
714 This is the driver for the hardware watchdog on the ITE IT8702,
715 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
718 If the driver does not work, then make sure that the game port in
721 This watchdog simply watches your kernel to make sure it doesn't
722 freeze, and if it does, it reboots your computer after a certain
725 To compile this driver as a module, choose M here: the module will
729 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
730 depends on X86 && PCI
732 A software monitoring watchdog and NMI sourcing driver. This driver
733 will detect lockups and provide a stack trace. This is a driver that
734 will only load on an HP ProLiant system with a minimum of iLO2 support.
735 To compile this driver as a module, choose M here: the module will be
739 tristate "Kontron COM Watchdog Timer"
740 depends on MFD_KEMPLD
743 Support for the PLD watchdog on some Kontron ETX and COMexpress
746 This driver can also be built as a module. If so, the module will be
749 config HPWDT_NMI_DECODING
750 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
751 depends on HP_WATCHDOG
754 When an NMI occurs this feature will make the necessary BIOS calls to
755 log the cause of the NMI.
758 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
761 This is a driver for National Semiconductor PC87307/PC97307 hardware
762 watchdog cards as found on the SC1200. This watchdog is mainly used
763 for power management purposes and can be used to power down the device
764 during inactivity periods (includes interrupt activity monitoring).
766 To compile this driver as a module, choose M here: the
767 module will be called sc1200wdt.
769 Most people will say N.
772 tristate "National Semiconductor SCx200 Watchdog"
773 depends on SCx200 && PCI
775 Enable the built-in watchdog timer support on the National
776 Semiconductor SCx200 processors.
778 If compiled as a module, it will be called scx200_wdt.
781 tristate "NS PC87413 watchdog"
784 This is the driver for the hardware watchdog on the PC87413 chipset
785 This watchdog simply watches your kernel to make sure it doesn't
786 freeze, and if it does, it reboots your computer after a certain
789 To compile this driver as a module, choose M here: the
790 module will be called pc87413_wdt.
792 Most people will say N.
795 tristate "nVidia TCO Timer/Watchdog"
796 depends on X86 && PCI
798 Hardware driver for the TCO timer built into the nVidia Hub family
799 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
800 watchdog timer that will reboot the machine after its second
801 expiration. The expiration time can be configured with the
802 "heartbeat" parameter.
804 On some motherboards the driver may fail to reset the chipset's
805 NO_REBOOT flag which prevents the watchdog from rebooting the
806 machine. If this is the case you will get a kernel message like
807 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
809 To compile this driver as a module, choose M here: the
810 module will be called nv_tco.
813 tristate "RDC R-321x SoC watchdog"
814 depends on X86_RDC321X
816 This is the driver for the built in hardware watchdog
817 in the RDC R-321x SoC.
819 To compile this driver as a module, choose M here: the
820 module will be called rdc321x_wdt.
823 tristate "SBC-60XX Watchdog Timer"
826 This driver can be used with the watchdog timer found on some
827 single board computers, namely the 6010 PII based computer.
828 It may well work with other cards. It reads port 0x443 to enable
829 and re-set the watchdog timer, and reads port 0x45 to disable
830 the watchdog. If you have a card that behave in similar ways,
831 you can probably make this driver work with your card as well.
833 You can compile this driver directly into the kernel, or use
834 it as a module. The module will be called sbc60xxwdt.
837 tristate "SBC8360 Watchdog Timer"
841 This is the driver for the hardware watchdog on the SBC8360 Single
842 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
844 To compile this driver as a module, choose M here: the
845 module will be called sbc8360.
847 Most people will say N.
850 tristate "SBC Nano 7240 Watchdog Timer"
851 depends on X86_32 && !UML
853 This is the driver for the hardware watchdog found on the IEI
854 single board computers EPIC Nano 7240 (and likely others). This
855 watchdog simply watches your kernel to make sure it doesn't freeze,
856 and if it does, it reboots your computer after a certain amount of
859 To compile this driver as a module, choose M here: the
860 module will be called sbc7240_wdt.
863 tristate "SMA CPU5 Watchdog"
867 To compile this driver as a module, choose M here: the
868 module will be called cpu5wdt.
870 config SMSC_SCH311X_WDT
871 tristate "SMSC SCH311X Watchdog Timer"
874 This is the driver for the hardware watchdog timer on the
875 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
876 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
879 To compile this driver as a module, choose M here: the
880 module will be called sch311x_wdt.
882 config SMSC37B787_WDT
883 tristate "Winbond SMsC37B787 Watchdog Timer"
886 This is the driver for the hardware watchdog component on the
887 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
888 from Vision Systems and maybe 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 Usually a userspace daemon will notify the kernel WDT driver that
895 userspace is still alive, at regular intervals.
897 To compile this driver as a module, choose M here: the
898 module will be called smsc37b787_wdt.
900 Most people will say N.
903 tristate "VIA Watchdog Timer"
904 depends on X86 && PCI
907 This is the driver for the hardware watchdog timer on VIA
908 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
910 To compile this driver as a module, choose M here; the module
911 will be called via_wdt.
913 Most people will say N.
916 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
920 This is the driver for the hardware watchdog on the following
922 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
932 This watchdog simply watches your kernel to make sure it doesn't
933 freeze, and if it does, it reboots your computer after a certain
936 To compile this driver as a module, choose M here: the
937 module will be called w83627hf_wdt.
939 Most people will say N.
942 tristate "W83697HF/W83697HG Watchdog Timer"
945 This is the driver for the hardware watchdog on the W83697HF/HG
946 chipset as used in Dedibox/VIA motherboards (and likely others).
947 This watchdog simply watches your kernel to make sure it doesn't
948 freeze, and if it does, it reboots your computer after a certain
951 To compile this driver as a module, choose M here: the
952 module will be called w83697hf_wdt.
954 Most people will say N.
957 tristate "W83697UG/W83697UF Watchdog Timer"
960 This is the driver for the hardware watchdog on the W83697UG/UF
961 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
962 This watchdog simply watches your kernel to make sure it doesn't
963 freeze, and if it does, it reboots your computer after a certain
966 To compile this driver as a module, choose M here: the
967 module will be called w83697ug_wdt.
969 Most people will say N.
972 tristate "W83877F (EMACS) Watchdog Timer"
975 This is the driver for the hardware watchdog on the W83877F chipset
976 as used in EMACS PC-104 motherboards (and likely others). This
977 watchdog simply watches your kernel to make sure it doesn't freeze,
978 and if it does, it reboots your computer after a certain amount of
981 To compile this driver as a module, choose M here: the
982 module will be called w83877f_wdt.
984 Most people will say N.
987 tristate "W83977F (PCM-5335) Watchdog Timer"
990 This is the driver for the hardware watchdog on the W83977F I/O chip
991 as used in AAEON's PCM-5335 SBC (and likely others). This
992 watchdog simply watches your kernel to make sure it doesn't freeze,
993 and if it does, it reboots your computer after a certain amount of
996 To compile this driver as a module, choose M here: the
997 module will be called w83977f_wdt.
1000 tristate "ZF MachZ Watchdog"
1003 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1004 N. This is the driver for the watchdog timer built-in on that
1005 processor using ZF-Logic interface. This watchdog simply watches
1006 your kernel to make sure it doesn't freeze, and if it does, it
1007 reboots your computer after a certain amount of time.
1009 To compile this driver as a module, choose M here: the
1010 module will be called machzwd.
1012 config SBC_EPX_C3_WATCHDOG
1013 tristate "Winsystems SBC EPX-C3 watchdog"
1016 This is the driver for the built-in watchdog timer on the EPX-C3
1017 Single-board computer made by Winsystems, Inc.
1019 *Note*: This hardware watchdog is not probeable and thus there
1020 is no way to know if writing to its IO address will corrupt
1021 your system or have any real effect. The only way to be sure
1022 that this driver does what you want is to make sure you
1023 are running it on an EPX-C3 from Winsystems with the watchdog
1024 timer at IO address 0x1ee and 0x1ef. It will write to both those
1025 IO ports. Basically, the assumption is made that if you compile
1026 this driver into your kernel and/or load it as a module, that you
1027 know what you are doing and that you are in fact running on an
1030 To compile this driver as a module, choose M here: the
1031 module will be called sbc_epx_c3.
1037 config M54xx_WATCHDOG
1038 tristate "MCF54xx watchdog support"
1041 To compile this driver as a module, choose M here: the
1042 module will be called m54xx_wdt.
1044 # MicroBlaze Architecture
1049 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1052 Hardware driver for the built-in watchdog timer on the Atheros
1053 AR71XX/AR724X/AR913X SoCs.
1056 tristate "Broadcom BCM47xx Watchdog Timer"
1058 select WATCHDOG_CORE
1060 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1063 tristate "IDT RC32434 SoC Watchdog Timer"
1064 depends on MIKROTIK_RB532
1066 Hardware driver for the IDT RC32434 SoC built-in
1069 To compile this driver as a module, choose M here: the
1070 module will be called rc32434_wdt.
1073 tristate "Indy/I2 Hardware Watchdog"
1074 depends on SGI_HAS_INDYDOG
1076 Hardware driver for the Indy's/I2's watchdog. This is a
1077 watchdog timer that will reboot the machine after a 60 second
1078 timer expired and no process has written to /dev/watchdog during
1082 tristate "Ingenic jz4740 SoC hardware watchdog"
1083 depends on MACH_JZ4740
1084 select WATCHDOG_CORE
1086 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1089 tristate "MTX-1 Hardware Watchdog"
1090 depends on MIPS_MTX1
1092 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1093 will reboot the machine after a 100 seconds timer expired.
1096 tristate "PNX833x Hardware Watchdog"
1097 depends on SOC_PNX8335
1099 Hardware driver for the PNX833x's watchdog. This is a
1100 watchdog timer that will reboot the machine after a programmable
1101 timer has expired and no process has written to /dev/watchdog during
1105 tristate "Sibyte SoC hardware watchdog"
1108 Watchdog driver for the built in watchdog hardware in Sibyte
1109 SoC processors. There are apparently two watchdog timers
1110 on such processors; this driver supports only the first one,
1111 because currently Linux only supports exporting one watchdog
1114 To compile this driver as a loadable module, choose M here.
1115 The module will be called sb_wdog.
1118 tristate "TI AR7 Watchdog Timer"
1121 Hardware driver for the TI AR7 Watchdog Timer.
1124 tristate "Toshiba TXx9 Watchdog Timer"
1125 depends on CPU_TX39XX || CPU_TX49XX
1126 select WATCHDOG_CORE
1128 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1131 tristate "Cavium OCTEON SOC family Watchdog Timer"
1132 depends on CAVIUM_OCTEON_SOC
1134 select EXPORT_UASM if OCTEON_WDT = m
1136 Hardware driver for OCTEON's on chip watchdog timer.
1137 Enables the watchdog for all cores running Linux. It
1138 installs a NMI handler and pokes the watchdog based on an
1139 interrupt. On first expiration of the watchdog, the
1140 interrupt handler pokes it. The second expiration causes an
1141 NMI that prints a message. The third expiration causes a
1144 When userspace has /dev/watchdog open, no poking is done
1145 from the first interrupt, it is then only poked when the
1149 tristate "Broadcom BCM63xx hardware watchdog"
1152 Watchdog driver for the built in watchdog hardware in Broadcom
1155 To compile this driver as a loadable module, choose M here.
1156 The module will be called bcm63xx_wdt.
1159 tristate "Broadcom BCM2835 hardware watchdog"
1160 depends on ARCH_BCM2835
1161 select WATCHDOG_CORE
1163 Watchdog driver for the built in watchdog hardware in Broadcom
1166 To compile this driver as a loadable module, choose M here.
1167 The module will be called bcm2835_wdt.
1170 tristate "BCM Kona Watchdog"
1171 depends on ARCH_BCM_MOBILE
1172 select WATCHDOG_CORE
1174 Support for the watchdog timer on the following Broadcom BCM281xx
1175 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1178 Say 'Y' or 'M' here to enable the driver. The module will be called
1181 config BCM_KONA_WDT_DEBUG
1182 bool "DEBUGFS support for BCM Kona Watchdog"
1183 depends on BCM_KONA_WDT
1185 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1186 access to the driver's internal data structures as well as watchdog
1187 timer hardware registres.
1189 If in doubt, say 'N'.
1192 tristate "Lantiq SoC watchdog"
1195 Hardware driver for the Lantiq SoC Watchdog Timer.
1198 tristate "Ralink SoC watchdog"
1199 select WATCHDOG_CORE
1202 Hardware driver for the Ralink SoC Watchdog Timer.
1204 # PARISC Architecture
1206 # POWERPC Architecture
1209 tristate "GE Watchdog Timer"
1212 Watchdog timer found in a number of GE single board computers.
1215 bool "MPC52xx Watchdog Timer"
1216 depends on PPC_MPC52xx
1218 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1221 tristate "MPC8xxx Platform Watchdog Timer"
1222 depends on PPC_8xx || PPC_83xx || PPC_86xx
1223 select WATCHDOG_CORE
1225 This driver is for a SoC level watchdog that exists on some
1226 Freescale PowerPC processors. So far this driver supports:
1231 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1234 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1238 tristate "PIKA FPGA Watchdog"
1242 This enables the watchdog in the PIKA FPGA. Currently used on
1246 tristate "PowerPC Book-E Watchdog Timer"
1247 depends on BOOKE || 4xx
1248 select WATCHDOG_CORE
1250 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1251 MPC85xx SOCs and the IBM PowerPC 440.
1253 Please see Documentation/watchdog/watchdog-api.txt for
1256 config BOOKE_WDT_DEFAULT_TIMEOUT
1257 int "PowerPC Book-E Watchdog Timer Default Timeout"
1258 depends on BOOKE_WDT
1259 default 38 if PPC_FSL_BOOK3E
1260 range 0 63 if PPC_FSL_BOOK3E
1261 default 3 if !PPC_FSL_BOOK3E
1262 range 0 3 if !PPC_FSL_BOOK3E
1264 Select the default watchdog timer period to be used by the PowerPC
1265 Book-E watchdog driver. A watchdog "event" occurs when the bit
1266 position represented by this number transitions from zero to one.
1268 For Freescale Book-E processors, this is a number between 0 and 63.
1269 For other Book-E processors, this is a number between 0 and 3.
1271 The value can be overridden by the wdt_period command-line parameter.
1274 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1275 select WATCHDOG_CORE
1278 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1280 The driver can also be built as a module. If so, the module will be
1283 If unsure select N here.
1285 # PPC64 Architecture
1287 config WATCHDOG_RTAS
1288 tristate "RTAS watchdog"
1291 This driver adds watchdog support for the RTAS watchdog.
1293 To compile this driver as a module, choose M here. The module
1294 will be called wdrtas.
1299 tristate "z/VM Watchdog Timer"
1302 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1303 provide a virtual watchdog timer to their guest that cause a
1304 user define Control Program command to be executed after a
1307 To compile this driver as a module, choose M here. The module
1308 will be called vmwatchdog.
1310 # SUPERH (sh + sh64) Architecture
1313 tristate "SuperH Watchdog"
1314 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1315 select WATCHDOG_CORE
1317 This driver adds watchdog support for the integrated watchdog in the
1318 SuperH processors. If you have one of these processors and wish
1319 to have watchdog support enabled, say Y, otherwise say N.
1321 As a side note, saying Y here will automatically boost HZ to 1000
1322 so that the timer has a chance to clear the overflow counter. On
1323 slower systems (such as the SH-2 and SH-3) this will likely yield
1324 some performance issues. As such, the WDT should be avoided here
1325 unless it is absolutely necessary.
1327 To compile this driver as a module, choose M here: the
1328 module will be called shwdt.
1330 # SPARC Architecture
1332 # SPARC64 Architecture
1334 config WATCHDOG_CP1XXX
1335 tristate "CP1XXX Hardware Watchdog support"
1336 depends on SPARC64 && PCI
1338 This is the driver for the hardware watchdog timers present on
1339 Sun Microsystems CompactPCI models CP1400 and CP1500.
1341 To compile this driver as a module, choose M here: the
1342 module will be called cpwatchdog.
1344 If you do not have a CompactPCI model CP1400 or CP1500, or
1345 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1346 you should say N to this option.
1349 tristate "RIO Hardware Watchdog support"
1350 depends on SPARC64 && PCI
1352 Say Y here to support the hardware watchdog capability on Sun RIO
1353 machines. The watchdog timeout period is normally one minute but
1354 can be changed with a boot-time parameter.
1356 # XTENSA Architecture
1361 tristate "Xen Watchdog support"
1364 Say Y here to support the hypervisor watchdog capability provided
1365 by Xen 4.0 and newer. The watchdog timeout period is normally one
1366 minute but can be changed with a boot-time parameter.
1369 tristate "UML watchdog"
1373 # ISA-based Watchdog Cards
1376 comment "ISA-based Watchdog Cards"
1380 tristate "Berkshire Products ISA-PC Watchdog"
1383 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1384 This card simply watches your kernel to make sure it doesn't freeze,
1385 and if it does, it reboots your computer after a certain amount of
1386 time. This driver is like the WDT501 driver but for different
1387 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1388 watchdog cards can be ordered from <http://www.berkprod.com/>.
1390 To compile this driver as a module, choose M here: the
1391 module will be called pcwd.
1393 Most people will say N.
1396 tristate "Mixcom Watchdog"
1399 This is a driver for the Mixcom hardware watchdog cards. This
1400 watchdog simply watches your kernel to make sure it doesn't freeze,
1401 and if it does, it reboots your computer after a certain amount of
1404 To compile this driver as a module, choose M here: the
1405 module will be called mixcomwd.
1407 Most people will say N.
1410 tristate "WDT Watchdog timer"
1413 If you have a WDT500P or WDT501P watchdog board, say Y here,
1414 otherwise N. It is not possible to probe for this board, which means
1415 that you have to inform the kernel about the IO port and IRQ that
1416 is needed (you can do this via the io and irq parameters)
1418 To compile this driver as a module, choose M here: the
1419 module will be called wdt.
1422 # PCI-based Watchdog Cards
1425 comment "PCI-based Watchdog Cards"
1428 config PCIPCWATCHDOG
1429 tristate "Berkshire Products PCI-PC Watchdog"
1432 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1433 This card simply watches your kernel to make sure it doesn't freeze,
1434 and if it does, it reboots your computer after a certain amount of
1435 time. The card can also monitor the internal temperature of the PC.
1436 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1438 To compile this driver as a module, choose M here: the
1439 module will be called pcwd_pci.
1441 Most people will say N.
1444 tristate "PCI-WDT500/501 Watchdog timer"
1447 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1449 If you have a PCI-WDT501 watchdog board then you can enable the
1450 temperature sensor by setting the type parameter to 501.
1452 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1453 can do this via the tachometer parameter. Only do this if you have a
1454 fan tachometer actually set up.
1456 To compile this driver as a module, choose M here: the
1457 module will be called wdt_pci.
1460 # USB-based Watchdog Cards
1463 comment "USB-based Watchdog Cards"
1466 config USBPCWATCHDOG
1467 tristate "Berkshire Products USB-PC Watchdog"
1470 This is the driver for the Berkshire Products USB-PC Watchdog card.
1471 This card simply watches your kernel to make sure it doesn't freeze,
1472 and if it does, it reboots your computer after a certain amount of
1473 time. The card can also monitor the internal temperature of the PC.
1474 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1476 To compile this driver as a module, choose M here: the
1477 module will be called pcwd_usb.
1479 Most people will say N.