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 MENF21BMC_WATCHDOG
99 tristate "MEN 14F021P00 BMC Watchdog"
100 depends on MFD_MENF21BMC
103 Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
105 This driver can also be built as a module. If so the module
106 will be called menf21bmc_wdt.
108 config WM831X_WATCHDOG
109 tristate "WM831x watchdog"
110 depends on MFD_WM831X
113 Support for the watchdog in the WM831x AudioPlus PMICs. When
114 the watchdog triggers the system will be reset.
116 config WM8350_WATCHDOG
117 tristate "WM8350 watchdog"
118 depends on MFD_WM8350
121 Support for the watchdog in the WM8350 AudioPlus PMIC. When
122 the watchdog triggers the system will be reset.
124 config XILINX_WATCHDOG
125 tristate "Xilinx Watchdog timer"
128 Watchdog driver for the xps_timebase_wdt ip core.
130 To compile this driver as a module, choose M here: the
131 module will be called of_xilinx_wdt.
137 config ARM_SP805_WATCHDOG
138 tristate "ARM SP805 Watchdog"
139 depends on (ARM || ARM64) && ARM_AMBA
142 ARM Primecell SP805 Watchdog timer. This will reboot your system when
143 the timeout is reached.
145 config AT91RM9200_WATCHDOG
146 tristate "AT91RM9200 watchdog"
147 depends on ARCH_AT91RM9200
149 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
150 system when the timeout is reached.
152 config AT91SAM9X_WATCHDOG
153 tristate "AT91SAM9X / AT91CAP9 watchdog"
154 depends on ARCH_AT91 && !ARCH_AT91RM9200
157 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
158 reboot your system when the timeout is reached.
160 config CADENCE_WATCHDOG
161 tristate "Cadence Watchdog Timer"
165 Say Y here if you want to include support for the watchdog
166 timer in the Xilinx Zynq.
168 config 21285_WATCHDOG
169 tristate "DC21285 watchdog"
170 depends on FOOTBRIDGE
172 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
173 here if you wish to use this. Alternatively say M to compile the
174 driver as a module, which will be called wdt285.
176 This driver does not work on all machines. In particular, early CATS
177 boards have hardware problems that will cause the machine to simply
178 lock up if the watchdog fires.
180 "If in doubt, leave it out" - say N.
183 tristate "NetWinder WB83C977 watchdog"
184 depends on FOOTBRIDGE && ARCH_NETWINDER
186 Say Y here to include support for the WB977 watchdog included in
187 NetWinder machines. Alternatively say M to compile the driver as
188 a module, which will be called wdt977.
190 Not sure? It's safe to say N.
192 config IXP4XX_WATCHDOG
193 tristate "IXP4xx Watchdog"
194 depends on ARCH_IXP4XX
196 Say Y here if to include support for the watchdog timer
197 in the Intel IXP4xx network processors. This driver can
198 be built as a module by choosing M. The module will
199 be called ixp4xx_wdt.
201 Note: The internal IXP4xx watchdog does a soft CPU reset
202 which doesn't reset any peripherals. There are circumstances
203 where the watchdog will fail to reset the board correctly
204 (e.g., if the boot ROM is in an unreadable state).
206 Say N if you are unsure.
208 config KS8695_WATCHDOG
209 tristate "KS8695 watchdog"
210 depends on ARCH_KS8695
212 Watchdog timer embedded into KS8695 processor. This will reboot your
213 system when the timeout is reached.
215 config HAVE_S3C2410_WATCHDOG
218 This will include watchdog timer support for Samsung SoCs. If
219 you want to include watchdog support for any machine, kindly
220 select this in the respective mach-XXXX/Kconfig file.
222 config S3C2410_WATCHDOG
223 tristate "S3C2410 Watchdog"
224 depends on HAVE_S3C2410_WATCHDOG
226 select MFD_SYSCON if ARCH_EXYNOS5
228 Watchdog timer block in the Samsung SoCs. This will reboot
229 the system when the timer expires with the watchdog enabled.
231 The driver is limited by the speed of the system's PCLK
232 signal, so with reasonably fast systems (PCLK around 50-66MHz)
233 then watchdog intervals of over approximately 20seconds are
236 The driver can be built as a module by choosing M, and will
237 be called s3c2410_wdt
239 config SA1100_WATCHDOG
240 tristate "SA1100/PXA2xx watchdog"
241 depends on ARCH_SA1100 || ARCH_PXA
243 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
244 reboot your system when timeout is reached.
246 NOTE: once enabled, this timer cannot be disabled.
248 To compile this driver as a module, choose M here: the
249 module will be called sa1100_wdt.
252 tristate "Synopsys DesignWare watchdog"
255 Say Y here if to include support for the Synopsys DesignWare
256 watchdog timer found in many chips.
257 To compile this driver as a module, choose M here: the
258 module will be called dw_wdt.
260 config EP93XX_WATCHDOG
261 tristate "EP93xx Watchdog"
262 depends on ARCH_EP93XX
265 Say Y here if to include support for the watchdog timer
266 embedded in the Cirrus Logic EP93xx family of devices.
268 To compile this driver as a module, choose M here: the
269 module will be called ep93xx_wdt.
272 tristate "OMAP Watchdog"
273 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
276 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
277 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
279 config PNX4008_WATCHDOG
280 tristate "LPC32XX Watchdog"
281 depends on ARCH_LPC32XX
284 Say Y here if to include support for the watchdog timer
285 in the LPC32XX processor.
286 This driver can be built as a module by choosing M. The module
287 will be called pnx4008_wdt.
289 Say N if you are unsure.
292 tristate "IOP Watchdog"
293 depends on ARCH_IOP13XX
294 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
296 Say Y here if to include support for the watchdog timer
297 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
298 be built as a module by choosing M. The module will
301 Note: The IOP13XX watchdog does an Internal Bus Reset which will
302 affect both cores and the peripherals of the IOP. The ATU-X
303 and/or ATUe configuration registers will remain intact, but if
304 operating as an Root Complex and/or Central Resource, the PCI-X
305 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
307 config DAVINCI_WATCHDOG
308 tristate "DaVinci watchdog"
309 depends on ARCH_DAVINCI || ARCH_KEYSTONE
312 Say Y here if to include support for the watchdog timer
313 in the DaVinci DM644x/DM646x or Keystone processors.
314 To compile this driver as a module, choose M here: the
315 module will be called davinci_wdt.
317 NOTE: once enabled, this timer cannot be disabled.
318 Say N if you are unsure.
320 config ORION_WATCHDOG
321 tristate "Orion watchdog"
322 depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
325 Say Y here if to include support for the watchdog timer
326 in the Marvell Orion5x and Kirkwood ARM SoCs.
327 To compile this driver as a module, choose M here: the
328 module will be called orion_wdt.
330 config SUNXI_WATCHDOG
331 tristate "Allwinner SoCs watchdog support"
332 depends on ARCH_SUNXI
335 Say Y here to include support for the watchdog timer
337 To compile this driver as a module, choose M here: the
338 module will be called sunxi_wdt.
340 config COH901327_WATCHDOG
341 bool "ST-Ericsson COH 901 327 watchdog"
343 default y if MACH_U300
346 Say Y here to include Watchdog timer support for the
347 watchdog embedded into the ST-Ericsson U300 series platforms.
348 This watchdog is used to reset the system and thus cannot be
349 compiled as a module.
351 config TWL4030_WATCHDOG
352 tristate "TWL4030 Watchdog"
353 depends on TWL4030_CORE
356 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
357 watchdog timer support for TWL4030 chips.
359 config STMP3XXX_RTC_WATCHDOG
360 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
361 depends on RTC_DRV_STMP
364 Say Y here to include support for the watchdog timer inside
365 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
366 To compile this driver as a module, choose M here: the
367 module will be called stmp3xxx_rtc_wdt.
369 config NUC900_WATCHDOG
370 tristate "Nuvoton NUC900 watchdog"
371 depends on ARCH_W90X900
373 Say Y here if to include support for the watchdog timer
374 for the Nuvoton NUC900 series SoCs.
375 To compile this driver as a module, choose M here: the
376 module will be called nuc900_wdt.
378 config TS72XX_WATCHDOG
379 tristate "TS-72XX SBC Watchdog"
380 depends on MACH_TS72XX
382 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
383 watchdog timer implemented in a external CPLD chip. Say Y here
384 if you want to support for the watchdog timer on TS-72XX boards.
386 To compile this driver as a module, choose M here: the
387 module will be called ts72xx_wdt.
389 config MAX63XX_WATCHDOG
390 tristate "Max63xx watchdog"
391 depends on ARM && HAS_IOMEM
394 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
397 tristate "IMX2+ Watchdog"
402 This is the driver for the hardware watchdog
403 on the Freescale IMX2 and later processors.
404 If you have one of these processors and wish to have
405 watchdog support enabled, say Y, otherwise say N.
407 To compile this driver as a module, choose M here: the
408 module will be called imx2_wdt.
410 config UX500_WATCHDOG
411 tristate "ST-Ericsson Ux500 watchdog"
412 depends on MFD_DB8500_PRCMU
416 Say Y here to include Watchdog timer support for the watchdog
417 existing in the prcmu of ST-Ericsson Ux500 series platforms.
419 To compile this driver as a module, choose M here: the
420 module will be called ux500_wdt.
423 tristate "Retu watchdog"
427 Retu watchdog driver for Nokia Internet Tablets (770, N800,
428 N810). At least on N800 the watchdog cannot be disabled, so
429 this driver is essential and you should enable it.
431 To compile this driver as a module, choose M here: the
432 module will be called retu_wdt.
435 tristate "MOXART watchdog"
436 depends on ARCH_MOXART
438 Say Y here to include Watchdog timer support for the watchdog
439 existing on the MOXA ART SoC series platforms.
441 To compile this driver as a module, choose M here: the
442 module will be called moxart_wdt.
444 config SIRFSOC_WATCHDOG
445 tristate "SiRFSOC watchdog"
450 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
451 the watchdog triggers the system will be reset.
453 config TEGRA_WATCHDOG
454 tristate "Tegra watchdog"
455 depends on ARCH_TEGRA || COMPILE_TEST
458 Say Y here to include support for the watchdog timer
459 embedded in NVIDIA Tegra SoCs.
461 To compile this driver as a module, choose M here: the
462 module will be called tegra_wdt.
466 config AT32AP700X_WDT
467 tristate "AT32AP700x watchdog"
468 depends on CPU_AT32AP700X
470 Watchdog timer embedded into AT32AP700x devices. This will reboot
471 your system when the timeout is reached.
473 # BLACKFIN Architecture
476 tristate "Blackfin On-Chip Watchdog Timer"
479 If you say yes here you will get support for the Blackfin On-Chip
480 Watchdog Timer. If you have one of these processors and wish to
481 have watchdog support enabled, say Y, otherwise say N.
483 To compile this driver as a module, choose M here: the
484 module will be called bfin_wdt.
490 # X86 (i386 + ia64 + x86_64) Architecture
493 tristate "Acquire SBC Watchdog Timer"
496 This is the driver for the hardware watchdog on Single Board
497 Computers produced by Acquire Inc (and others). This watchdog
498 simply watches your kernel to make sure it doesn't freeze, and if
499 it does, it reboots your computer after a certain amount of time.
501 To compile this driver as a module, choose M here: the
502 module will be called acquirewdt.
504 Most people will say N.
507 tristate "Advantech SBC Watchdog Timer"
510 If you are configuring a Linux kernel for the Advantech single-board
511 computer, say `Y' here to support its built-in watchdog timer
512 feature. More information can be found at
513 <http://www.advantech.com.tw/products/>
516 tristate "ALi M1535 PMU Watchdog Timer"
517 depends on X86 && PCI
519 This is the driver for the hardware watchdog on the ALi M1535 PMU.
521 To compile this driver as a module, choose M here: the
522 module will be called alim1535_wdt.
524 Most people will say N.
527 tristate "ALi M7101 PMU Computer Watchdog"
530 This is the driver for the hardware watchdog on the ALi M7101 PMU
531 as used in the x86 Cobalt servers and also found in some
532 SPARC Netra servers too.
534 To compile this driver as a module, choose M here: the
535 module will be called alim7101_wdt.
537 Most people will say N.
540 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
543 This is the driver for the hardware watchdog on the Fintek
544 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
546 You can compile this driver directly into the kernel, or use
547 it as a module. The module will be called f71808e_wdt.
550 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
551 depends on X86 && PCI
553 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
554 (Total Cost of Ownership) timer is a watchdog timer that will reboot
555 the machine after its expiration. The expiration time can be
556 configured with the "heartbeat" parameter.
558 To compile this driver as a module, choose M here: the
559 module will be called sp5100_tco.
562 tristate "AMD Geode CS5535/CS5536 Watchdog"
563 depends on CS5535_MFGPT
565 This driver enables a watchdog capability built into the
566 CS5535/CS5536 companion chips for the AMD Geode GX and LX
567 processors. This watchdog watches your kernel to make sure
568 it doesn't freeze, and if it does, it reboots your computer after
569 a certain amount of time.
571 You can compile this driver directly into the kernel, or use
572 it as a module. The module will be called geodewdt.
575 tristate "AMD Elan SC520 processor Watchdog"
578 This is the driver for the hardware watchdog built in to the
579 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
580 This watchdog simply watches your kernel to make sure it doesn't
581 freeze, and if it does, it reboots your computer after a certain
584 You can compile this driver directly into the kernel, or use
585 it as a module. The module will be called sc520_wdt.
587 config SBC_FITPC2_WATCHDOG
588 tristate "Compulab SBC-FITPC2 watchdog"
591 This is the driver for the built-in watchdog timer on the fit-PC2,
592 fit-PC2i, CM-iAM single-board computers made by Compulab.
594 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
595 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
597 Entering BIOS setup temporary disables watchdog operation regardless to current state,
598 so system will not be restarted while user in BIOS setup.
600 Once watchdog was enabled the system will be restarted every
601 "Watchdog Timer Value" period, so to prevent it user can restart or
602 disable the watchdog.
604 To compile this driver as a module, choose M here: the
605 module will be called sbc_fitpc2_wdt.
607 Most people will say N.
610 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
613 Enable support for the watchdog timer on the Eurotech CPU-1220 and
614 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
615 information are at <http://www.eurotech.it/>.
618 tristate "IB700 SBC Watchdog Timer"
621 This is the driver for the hardware watchdog on the IB700 Single
622 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
623 simply watches your kernel to make sure it doesn't freeze, and if
624 it does, it reboots your computer after a certain amount of time.
626 This driver is like the WDT501 driver but for slightly different hardware.
628 To compile this driver as a module, choose M here: the
629 module will be called ib700wdt.
631 Most people will say N.
634 tristate "IBM Automatic Server Restart"
637 This is the driver for the IBM Automatic Server Restart watchdog
638 timer built-in into some eServer xSeries machines.
640 To compile this driver as a module, choose M here: the
641 module will be called ibmasr.
644 tristate "ICP Single Board Computer Watchdog Timer"
647 This is a driver for the hardware watchdog on the ICP Single
648 Board Computer. This driver is working on (at least) the following
649 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
651 To compile this driver as a module, choose M here: the
652 module will be called wafer5823wdt.
655 tristate "Intel 6300ESB Timer/Watchdog"
658 Hardware driver for the watchdog timer built into the Intel
659 6300ESB controller hub.
661 To compile this driver as a module, choose M here: the
662 module will be called i6300esb.
665 tristate "Intel Atom E6xx Watchdog"
666 depends on X86 && PCI
671 Hardware driver for the watchdog timer built into the Intel
672 Atom E6XX (TunnelCreek) processor.
674 To compile this driver as a module, choose M here: the
675 module will be called ie6xx_wdt.
677 config INTEL_SCU_WATCHDOG
678 bool "Intel SCU Watchdog for Mobile Platforms"
679 depends on X86_INTEL_MID
681 Hardware driver for the watchdog time built into the Intel SCU
682 for Intel Mobile Platforms.
684 To compile this driver as a module, choose M here.
686 config INTEL_MID_WATCHDOG
687 tristate "Intel MID Watchdog Timer"
688 depends on X86_INTEL_MID
691 Watchdog timer driver built into the Intel SCU for Intel MID
694 This driver currently supports only the watchdog evolution
695 implementation in SCU, available for Merrifield generation.
697 To compile this driver as a module, choose M here.
700 tristate "Intel TCO Timer/Watchdog"
701 depends on (X86 || IA64) && PCI
705 Hardware driver for the intel TCO timer based watchdog devices.
706 These drivers are included in the Intel 82801 I/O Controller
707 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
710 The TCO (Total Cost of Ownership) timer is a watchdog timer
711 that will reboot the machine after its second expiration. The
712 expiration time can be configured with the "heartbeat" parameter.
714 On some motherboards the driver may fail to reset the chipset's
715 NO_REBOOT flag which prevents the watchdog from rebooting the
716 machine. If this is the case you will get a kernel message like
717 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
719 To compile this driver as a module, choose M here: the
720 module will be called iTCO_wdt.
722 config ITCO_VENDOR_SUPPORT
723 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
726 Add vendor specific support to the intel TCO timer based watchdog
727 devices. At this moment we only have additional support for some
728 SuperMicro Inc. motherboards.
731 tristate "IT8712F (Smart Guardian) Watchdog Timer"
734 This is the driver for the built-in watchdog timer on the IT8712F
735 Super I/0 chipset used on many motherboards.
737 If the driver does not work, then make sure that the game port in
740 To compile this driver as a module, choose M here: the
741 module will be called it8712f_wdt.
744 tristate "IT87 Watchdog Timer"
747 This is the driver for the hardware watchdog on the ITE IT8702,
748 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
751 If the driver does not work, then make sure that the game port in
754 This watchdog simply watches your kernel to make sure it doesn't
755 freeze, and if it does, it reboots your computer after a certain
758 To compile this driver as a module, choose M here: the module will
762 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
763 depends on X86 && PCI
765 A software monitoring watchdog and NMI sourcing driver. This driver
766 will detect lockups and provide a stack trace. This is a driver that
767 will only load on an HP ProLiant system with a minimum of iLO2 support.
768 To compile this driver as a module, choose M here: the module will be
772 tristate "Kontron COM Watchdog Timer"
773 depends on MFD_KEMPLD
776 Support for the PLD watchdog on some Kontron ETX and COMexpress
779 This driver can also be built as a module. If so, the module will be
782 config HPWDT_NMI_DECODING
783 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
784 depends on HP_WATCHDOG
787 When an NMI occurs this feature will make the necessary BIOS calls to
788 log the cause of the NMI.
791 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
794 This is a driver for National Semiconductor PC87307/PC97307 hardware
795 watchdog cards as found on the SC1200. This watchdog is mainly used
796 for power management purposes and can be used to power down the device
797 during inactivity periods (includes interrupt activity monitoring).
799 To compile this driver as a module, choose M here: the
800 module will be called sc1200wdt.
802 Most people will say N.
805 tristate "National Semiconductor SCx200 Watchdog"
806 depends on SCx200 && PCI
808 Enable the built-in watchdog timer support on the National
809 Semiconductor SCx200 processors.
811 If compiled as a module, it will be called scx200_wdt.
814 tristate "NS PC87413 watchdog"
817 This is the driver for the hardware watchdog on the PC87413 chipset
818 This watchdog simply watches your kernel to make sure it doesn't
819 freeze, and if it does, it reboots your computer after a certain
822 To compile this driver as a module, choose M here: the
823 module will be called pc87413_wdt.
825 Most people will say N.
828 tristate "nVidia TCO Timer/Watchdog"
829 depends on X86 && PCI
831 Hardware driver for the TCO timer built into the nVidia Hub family
832 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
833 watchdog timer that will reboot the machine after its second
834 expiration. The expiration time can be configured with the
835 "heartbeat" parameter.
837 On some motherboards the driver may fail to reset the chipset's
838 NO_REBOOT flag which prevents the watchdog from rebooting the
839 machine. If this is the case you will get a kernel message like
840 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
842 To compile this driver as a module, choose M here: the
843 module will be called nv_tco.
846 tristate "RDC R-321x SoC watchdog"
847 depends on X86_RDC321X
849 This is the driver for the built in hardware watchdog
850 in the RDC R-321x SoC.
852 To compile this driver as a module, choose M here: the
853 module will be called rdc321x_wdt.
856 tristate "SBC-60XX Watchdog Timer"
859 This driver can be used with the watchdog timer found on some
860 single board computers, namely the 6010 PII based computer.
861 It may well work with other cards. It reads port 0x443 to enable
862 and re-set the watchdog timer, and reads port 0x45 to disable
863 the watchdog. If you have a card that behave in similar ways,
864 you can probably make this driver work with your card as well.
866 You can compile this driver directly into the kernel, or use
867 it as a module. The module will be called sbc60xxwdt.
870 tristate "SBC8360 Watchdog Timer"
874 This is the driver for the hardware watchdog on the SBC8360 Single
875 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
877 To compile this driver as a module, choose M here: the
878 module will be called sbc8360.
880 Most people will say N.
883 tristate "SBC Nano 7240 Watchdog Timer"
884 depends on X86_32 && !UML
886 This is the driver for the hardware watchdog found on the IEI
887 single board computers EPIC Nano 7240 (and likely others). This
888 watchdog simply watches your kernel to make sure it doesn't freeze,
889 and if it does, it reboots your computer after a certain amount of
892 To compile this driver as a module, choose M here: the
893 module will be called sbc7240_wdt.
896 tristate "SMA CPU5 Watchdog"
900 To compile this driver as a module, choose M here: the
901 module will be called cpu5wdt.
903 config SMSC_SCH311X_WDT
904 tristate "SMSC SCH311X Watchdog Timer"
907 This is the driver for the hardware watchdog timer on the
908 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
909 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
912 To compile this driver as a module, choose M here: the
913 module will be called sch311x_wdt.
915 config SMSC37B787_WDT
916 tristate "Winbond SMsC37B787 Watchdog Timer"
919 This is the driver for the hardware watchdog component on the
920 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
921 from Vision Systems and maybe others.
923 This watchdog simply watches your kernel to make sure it doesn't
924 freeze, and if it does, it reboots your computer after a certain
927 Usually a userspace daemon will notify the kernel WDT driver that
928 userspace is still alive, at regular intervals.
930 To compile this driver as a module, choose M here: the
931 module will be called smsc37b787_wdt.
933 Most people will say N.
936 tristate "VIA Watchdog Timer"
937 depends on X86 && PCI
940 This is the driver for the hardware watchdog timer on VIA
941 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
943 To compile this driver as a module, choose M here; the module
944 will be called via_wdt.
946 Most people will say N.
949 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
953 This is the driver for the hardware watchdog on the following
955 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
965 This watchdog simply watches your kernel to make sure it doesn't
966 freeze, and if it does, it reboots your computer after a certain
969 To compile this driver as a module, choose M here: the
970 module will be called w83627hf_wdt.
972 Most people will say N.
975 tristate "W83877F (EMACS) Watchdog Timer"
978 This is the driver for the hardware watchdog on the W83877F chipset
979 as used in EMACS PC-104 motherboards (and likely others). This
980 watchdog simply watches your kernel to make sure it doesn't freeze,
981 and if it does, it reboots your computer after a certain amount of
984 To compile this driver as a module, choose M here: the
985 module will be called w83877f_wdt.
987 Most people will say N.
990 tristate "W83977F (PCM-5335) Watchdog Timer"
993 This is the driver for the hardware watchdog on the W83977F I/O chip
994 as used in AAEON's PCM-5335 SBC (and likely others). This
995 watchdog simply watches your kernel to make sure it doesn't freeze,
996 and if it does, it reboots your computer after a certain amount of
999 To compile this driver as a module, choose M here: the
1000 module will be called w83977f_wdt.
1003 tristate "ZF MachZ Watchdog"
1006 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1007 N. This is the driver for the watchdog timer built-in on that
1008 processor using ZF-Logic interface. This watchdog simply watches
1009 your kernel to make sure it doesn't freeze, and if it does, it
1010 reboots your computer after a certain amount of time.
1012 To compile this driver as a module, choose M here: the
1013 module will be called machzwd.
1015 config SBC_EPX_C3_WATCHDOG
1016 tristate "Winsystems SBC EPX-C3 watchdog"
1019 This is the driver for the built-in watchdog timer on the EPX-C3
1020 Single-board computer made by Winsystems, Inc.
1022 *Note*: This hardware watchdog is not probeable and thus there
1023 is no way to know if writing to its IO address will corrupt
1024 your system or have any real effect. The only way to be sure
1025 that this driver does what you want is to make sure you
1026 are running it on an EPX-C3 from Winsystems with the watchdog
1027 timer at IO address 0x1ee and 0x1ef. It will write to both those
1028 IO ports. Basically, the assumption is made that if you compile
1029 this driver into your kernel and/or load it as a module, that you
1030 know what you are doing and that you are in fact running on an
1033 To compile this driver as a module, choose M here: the
1034 module will be called sbc_epx_c3.
1040 config M54xx_WATCHDOG
1041 tristate "MCF54xx watchdog support"
1044 To compile this driver as a module, choose M here: the
1045 module will be called m54xx_wdt.
1047 # MicroBlaze Architecture
1052 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1055 Hardware driver for the built-in watchdog timer on the Atheros
1056 AR71XX/AR724X/AR913X SoCs.
1059 tristate "Broadcom BCM47xx Watchdog Timer"
1061 select WATCHDOG_CORE
1063 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1066 tristate "IDT RC32434 SoC Watchdog Timer"
1067 depends on MIKROTIK_RB532
1069 Hardware driver for the IDT RC32434 SoC built-in
1072 To compile this driver as a module, choose M here: the
1073 module will be called rc32434_wdt.
1076 tristate "Indy/I2 Hardware Watchdog"
1077 depends on SGI_HAS_INDYDOG
1079 Hardware driver for the Indy's/I2's watchdog. This is a
1080 watchdog timer that will reboot the machine after a 60 second
1081 timer expired and no process has written to /dev/watchdog during
1085 tristate "Ingenic jz4740 SoC hardware watchdog"
1086 depends on MACH_JZ4740
1087 select WATCHDOG_CORE
1089 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1092 tristate "MTX-1 Hardware Watchdog"
1093 depends on MIPS_MTX1
1095 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1096 will reboot the machine after a 100 seconds timer expired.
1099 tristate "PNX833x Hardware Watchdog"
1100 depends on SOC_PNX8335
1102 Hardware driver for the PNX833x's watchdog. This is a
1103 watchdog timer that will reboot the machine after a programmable
1104 timer has expired and no process has written to /dev/watchdog during
1108 tristate "Sibyte SoC hardware watchdog"
1111 Watchdog driver for the built in watchdog hardware in Sibyte
1112 SoC processors. There are apparently two watchdog timers
1113 on such processors; this driver supports only the first one,
1114 because currently Linux only supports exporting one watchdog
1117 To compile this driver as a loadable module, choose M here.
1118 The module will be called sb_wdog.
1121 tristate "TI AR7 Watchdog Timer"
1124 Hardware driver for the TI AR7 Watchdog Timer.
1127 tristate "Toshiba TXx9 Watchdog Timer"
1128 depends on CPU_TX39XX || CPU_TX49XX
1129 select WATCHDOG_CORE
1131 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1134 tristate "Cavium OCTEON SOC family Watchdog Timer"
1135 depends on CAVIUM_OCTEON_SOC
1137 select EXPORT_UASM if OCTEON_WDT = m
1139 Hardware driver for OCTEON's on chip watchdog timer.
1140 Enables the watchdog for all cores running Linux. It
1141 installs a NMI handler and pokes the watchdog based on an
1142 interrupt. On first expiration of the watchdog, the
1143 interrupt handler pokes it. The second expiration causes an
1144 NMI that prints a message. The third expiration causes a
1147 When userspace has /dev/watchdog open, no poking is done
1148 from the first interrupt, it is then only poked when the
1152 tristate "Broadcom BCM63xx hardware watchdog"
1155 Watchdog driver for the built in watchdog hardware in Broadcom
1158 To compile this driver as a loadable module, choose M here.
1159 The module will be called bcm63xx_wdt.
1162 tristate "Broadcom BCM2835 hardware watchdog"
1163 depends on ARCH_BCM2835
1164 select WATCHDOG_CORE
1166 Watchdog driver for the built in watchdog hardware in Broadcom
1169 To compile this driver as a loadable module, choose M here.
1170 The module will be called bcm2835_wdt.
1173 tristate "BCM Kona Watchdog"
1174 depends on ARCH_BCM_MOBILE
1175 select WATCHDOG_CORE
1177 Support for the watchdog timer on the following Broadcom BCM281xx
1178 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1181 Say 'Y' or 'M' here to enable the driver. The module will be called
1184 config BCM_KONA_WDT_DEBUG
1185 bool "DEBUGFS support for BCM Kona Watchdog"
1186 depends on BCM_KONA_WDT
1188 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1189 access to the driver's internal data structures as well as watchdog
1190 timer hardware registres.
1192 If in doubt, say 'N'.
1195 tristate "Lantiq SoC watchdog"
1198 Hardware driver for the Lantiq SoC Watchdog Timer.
1201 tristate "Ralink SoC watchdog"
1202 select WATCHDOG_CORE
1205 Hardware driver for the Ralink SoC Watchdog Timer.
1207 # PARISC Architecture
1209 # POWERPC Architecture
1212 tristate "GE Watchdog Timer"
1215 Watchdog timer found in a number of GE single board computers.
1218 bool "MPC52xx Watchdog Timer"
1219 depends on PPC_MPC52xx
1221 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1224 tristate "MPC8xxx Platform Watchdog Timer"
1225 depends on PPC_8xx || PPC_83xx || PPC_86xx
1226 select WATCHDOG_CORE
1228 This driver is for a SoC level watchdog that exists on some
1229 Freescale PowerPC processors. So far this driver supports:
1234 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1237 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1241 tristate "PIKA FPGA Watchdog"
1245 This enables the watchdog in the PIKA FPGA. Currently used on
1249 tristate "PowerPC Book-E Watchdog Timer"
1250 depends on BOOKE || 4xx
1251 select WATCHDOG_CORE
1253 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1254 MPC85xx SOCs and the IBM PowerPC 440.
1256 Please see Documentation/watchdog/watchdog-api.txt for
1259 config BOOKE_WDT_DEFAULT_TIMEOUT
1260 int "PowerPC Book-E Watchdog Timer Default Timeout"
1261 depends on BOOKE_WDT
1262 default 38 if PPC_FSL_BOOK3E
1263 range 0 63 if PPC_FSL_BOOK3E
1264 default 3 if !PPC_FSL_BOOK3E
1265 range 0 3 if !PPC_FSL_BOOK3E
1267 Select the default watchdog timer period to be used by the PowerPC
1268 Book-E watchdog driver. A watchdog "event" occurs when the bit
1269 position represented by this number transitions from zero to one.
1271 For Freescale Book-E processors, this is a number between 0 and 63.
1272 For other Book-E processors, this is a number between 0 and 3.
1274 The value can be overridden by the wdt_period command-line parameter.
1277 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1278 select WATCHDOG_CORE
1281 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1283 The driver can also be built as a module. If so, the module will be
1286 If unsure select N here.
1288 # PPC64 Architecture
1290 config WATCHDOG_RTAS
1291 tristate "RTAS watchdog"
1294 This driver adds watchdog support for the RTAS watchdog.
1296 To compile this driver as a module, choose M here. The module
1297 will be called wdrtas.
1301 config DIAG288_WATCHDOG
1302 tristate "System z diag288 Watchdog"
1304 select WATCHDOG_CORE
1306 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1307 provide a virtual watchdog timer to their guest that cause a
1308 user define Control Program command to be executed after a
1310 LPAR provides a very similar interface. This driver handles
1313 To compile this driver as a module, choose M here. The module
1314 will be called diag288_wdt.
1316 # SUPERH (sh + sh64) Architecture
1319 tristate "SuperH Watchdog"
1320 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1321 select WATCHDOG_CORE
1323 This driver adds watchdog support for the integrated watchdog in the
1324 SuperH processors. If you have one of these processors and wish
1325 to have watchdog support enabled, say Y, otherwise say N.
1327 As a side note, saying Y here will automatically boost HZ to 1000
1328 so that the timer has a chance to clear the overflow counter. On
1329 slower systems (such as the SH-2 and SH-3) this will likely yield
1330 some performance issues. As such, the WDT should be avoided here
1331 unless it is absolutely necessary.
1333 To compile this driver as a module, choose M here: the
1334 module will be called shwdt.
1336 # SPARC Architecture
1338 # SPARC64 Architecture
1340 config WATCHDOG_CP1XXX
1341 tristate "CP1XXX Hardware Watchdog support"
1342 depends on SPARC64 && PCI
1344 This is the driver for the hardware watchdog timers present on
1345 Sun Microsystems CompactPCI models CP1400 and CP1500.
1347 To compile this driver as a module, choose M here: the
1348 module will be called cpwatchdog.
1350 If you do not have a CompactPCI model CP1400 or CP1500, or
1351 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1352 you should say N to this option.
1355 tristate "RIO Hardware Watchdog support"
1356 depends on SPARC64 && PCI
1358 Say Y here to support the hardware watchdog capability on Sun RIO
1359 machines. The watchdog timeout period is normally one minute but
1360 can be changed with a boot-time parameter.
1362 # XTENSA Architecture
1367 tristate "Xen Watchdog support"
1370 Say Y here to support the hypervisor watchdog capability provided
1371 by Xen 4.0 and newer. The watchdog timeout period is normally one
1372 minute but can be changed with a boot-time parameter.
1375 tristate "UML watchdog"
1379 # ISA-based Watchdog Cards
1382 comment "ISA-based Watchdog Cards"
1386 tristate "Berkshire Products ISA-PC Watchdog"
1389 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1390 This card simply watches your kernel to make sure it doesn't freeze,
1391 and if it does, it reboots your computer after a certain amount of
1392 time. This driver is like the WDT501 driver but for different
1393 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1394 watchdog cards can be ordered from <http://www.berkprod.com/>.
1396 To compile this driver as a module, choose M here: the
1397 module will be called pcwd.
1399 Most people will say N.
1402 tristate "Mixcom Watchdog"
1405 This is a driver for the Mixcom hardware watchdog cards. This
1406 watchdog simply watches your kernel to make sure it doesn't freeze,
1407 and if it does, it reboots your computer after a certain amount of
1410 To compile this driver as a module, choose M here: the
1411 module will be called mixcomwd.
1413 Most people will say N.
1416 tristate "WDT Watchdog timer"
1419 If you have a WDT500P or WDT501P watchdog board, say Y here,
1420 otherwise N. It is not possible to probe for this board, which means
1421 that you have to inform the kernel about the IO port and IRQ that
1422 is needed (you can do this via the io and irq parameters)
1424 To compile this driver as a module, choose M here: the
1425 module will be called wdt.
1428 # PCI-based Watchdog Cards
1431 comment "PCI-based Watchdog Cards"
1434 config PCIPCWATCHDOG
1435 tristate "Berkshire Products PCI-PC Watchdog"
1438 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1439 This card simply watches your kernel to make sure it doesn't freeze,
1440 and if it does, it reboots your computer after a certain amount of
1441 time. The card can also monitor the internal temperature of the PC.
1442 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1444 To compile this driver as a module, choose M here: the
1445 module will be called pcwd_pci.
1447 Most people will say N.
1450 tristate "PCI-WDT500/501 Watchdog timer"
1453 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1455 If you have a PCI-WDT501 watchdog board then you can enable the
1456 temperature sensor by setting the type parameter to 501.
1458 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1459 can do this via the tachometer parameter. Only do this if you have a
1460 fan tachometer actually set up.
1462 To compile this driver as a module, choose M here: the
1463 module will be called wdt_pci.
1466 # USB-based Watchdog Cards
1469 comment "USB-based Watchdog Cards"
1472 config USBPCWATCHDOG
1473 tristate "Berkshire Products USB-PC Watchdog"
1476 This is the driver for the Berkshire Products USB-PC Watchdog card.
1477 This card simply watches your kernel to make sure it doesn't freeze,
1478 and if it does, it reboots your computer after a certain amount of
1479 time. The card can also monitor the internal temperature of the PC.
1480 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1482 To compile this driver as a module, choose M here: the
1483 module will be called pcwd_usb.
1485 Most people will say N.