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"
275 depends on ARCH_IOP13XX
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"
384 This is the driver for the hardware watchdog
385 on the Freescale IMX2 and later processors.
386 If you have one of these processors and wish to have
387 watchdog support enabled, say Y, otherwise say N.
389 To compile this driver as a module, choose M here: the
390 module will be called imx2_wdt.
392 config UX500_WATCHDOG
393 tristate "ST-Ericsson Ux500 watchdog"
394 depends on MFD_DB8500_PRCMU
398 Say Y here to include Watchdog timer support for the watchdog
399 existing in the prcmu of ST-Ericsson Ux500 series platforms.
401 To compile this driver as a module, choose M here: the
402 module will be called ux500_wdt.
405 tristate "Retu watchdog"
409 Retu watchdog driver for Nokia Internet Tablets (770, N800,
410 N810). At least on N800 the watchdog cannot be disabled, so
411 this driver is essential and you should enable it.
413 To compile this driver as a module, choose M here: the
414 module will be called retu_wdt.
417 tristate "MOXART watchdog"
418 depends on ARCH_MOXART
420 Say Y here to include Watchdog timer support for the watchdog
421 existing on the MOXA ART SoC series platforms.
423 To compile this driver as a module, choose M here: the
424 module will be called moxart_wdt.
426 config SIRFSOC_WATCHDOG
427 tristate "SiRFSOC watchdog"
432 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
433 the watchdog triggers the system will be reset.
435 config TEGRA_WATCHDOG
436 tristate "Tegra watchdog"
437 depends on ARCH_TEGRA || COMPILE_TEST
440 Say Y here to include support for the watchdog timer
441 embedded in NVIDIA Tegra SoCs.
443 To compile this driver as a module, choose M here: the
444 module will be called tegra_wdt.
448 config AT32AP700X_WDT
449 tristate "AT32AP700x watchdog"
450 depends on CPU_AT32AP700X
452 Watchdog timer embedded into AT32AP700x devices. This will reboot
453 your system when the timeout is reached.
455 # BLACKFIN Architecture
458 tristate "Blackfin On-Chip Watchdog Timer"
461 If you say yes here you will get support for the Blackfin On-Chip
462 Watchdog Timer. If you have one of these processors and wish to
463 have watchdog support enabled, say Y, otherwise say N.
465 To compile this driver as a module, choose M here: the
466 module will be called bfin_wdt.
472 # X86 (i386 + ia64 + x86_64) Architecture
475 tristate "Acquire SBC Watchdog Timer"
478 This is the driver for the hardware watchdog on Single Board
479 Computers produced by Acquire Inc (and others). This watchdog
480 simply watches your kernel to make sure it doesn't freeze, and if
481 it does, it reboots your computer after a certain amount of time.
483 To compile this driver as a module, choose M here: the
484 module will be called acquirewdt.
486 Most people will say N.
489 tristate "Advantech SBC Watchdog Timer"
492 If you are configuring a Linux kernel for the Advantech single-board
493 computer, say `Y' here to support its built-in watchdog timer
494 feature. More information can be found at
495 <http://www.advantech.com.tw/products/>
498 tristate "ALi M1535 PMU Watchdog Timer"
499 depends on X86 && PCI
501 This is the driver for the hardware watchdog on the ALi M1535 PMU.
503 To compile this driver as a module, choose M here: the
504 module will be called alim1535_wdt.
506 Most people will say N.
509 tristate "ALi M7101 PMU Computer Watchdog"
512 This is the driver for the hardware watchdog on the ALi M7101 PMU
513 as used in the x86 Cobalt servers and also found in some
514 SPARC Netra servers too.
516 To compile this driver as a module, choose M here: the
517 module will be called alim7101_wdt.
519 Most people will say N.
522 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
525 This is the driver for the hardware watchdog on the Fintek
526 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
528 You can compile this driver directly into the kernel, or use
529 it as a module. The module will be called f71808e_wdt.
532 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
533 depends on X86 && PCI
535 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
536 (Total Cost of Ownership) timer is a watchdog timer that will reboot
537 the machine after its expiration. The expiration time can be
538 configured with the "heartbeat" parameter.
540 To compile this driver as a module, choose M here: the
541 module will be called sp5100_tco.
544 tristate "AMD Geode CS5535/CS5536 Watchdog"
545 depends on CS5535_MFGPT
547 This driver enables a watchdog capability built into the
548 CS5535/CS5536 companion chips for the AMD Geode GX and LX
549 processors. This watchdog watches your kernel to make sure
550 it doesn't freeze, and if it does, it reboots your computer after
551 a certain amount of time.
553 You can compile this driver directly into the kernel, or use
554 it as a module. The module will be called geodewdt.
557 tristate "AMD Elan SC520 processor Watchdog"
560 This is the driver for the hardware watchdog built in to the
561 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
562 This watchdog simply watches your kernel to make sure it doesn't
563 freeze, and if it does, it reboots your computer after a certain
566 You can compile this driver directly into the kernel, or use
567 it as a module. The module will be called sc520_wdt.
569 config SBC_FITPC2_WATCHDOG
570 tristate "Compulab SBC-FITPC2 watchdog"
573 This is the driver for the built-in watchdog timer on the fit-PC2,
574 fit-PC2i, CM-iAM single-board computers made by Compulab.
576 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
577 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
579 Entering BIOS setup temporary disables watchdog operation regardless to current state,
580 so system will not be restarted while user in BIOS setup.
582 Once watchdog was enabled the system will be restarted every
583 "Watchdog Timer Value" period, so to prevent it user can restart or
584 disable the watchdog.
586 To compile this driver as a module, choose M here: the
587 module will be called sbc_fitpc2_wdt.
589 Most people will say N.
592 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
595 Enable support for the watchdog timer on the Eurotech CPU-1220 and
596 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
597 information are at <http://www.eurotech.it/>.
600 tristate "IB700 SBC Watchdog Timer"
603 This is the driver for the hardware watchdog on the IB700 Single
604 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
605 simply watches your kernel to make sure it doesn't freeze, and if
606 it does, it reboots your computer after a certain amount of time.
608 This driver is like the WDT501 driver but for slightly different hardware.
610 To compile this driver as a module, choose M here: the
611 module will be called ib700wdt.
613 Most people will say N.
616 tristate "IBM Automatic Server Restart"
619 This is the driver for the IBM Automatic Server Restart watchdog
620 timer built-in into some eServer xSeries machines.
622 To compile this driver as a module, choose M here: the
623 module will be called ibmasr.
626 tristate "ICP Single Board Computer Watchdog Timer"
629 This is a driver for the hardware watchdog on the ICP Single
630 Board Computer. This driver is working on (at least) the following
631 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
633 To compile this driver as a module, choose M here: the
634 module will be called wafer5823wdt.
637 tristate "Intel 6300ESB Timer/Watchdog"
640 Hardware driver for the watchdog timer built into the Intel
641 6300ESB controller hub.
643 To compile this driver as a module, choose M here: the
644 module will be called i6300esb.
647 tristate "Intel Atom E6xx Watchdog"
648 depends on X86 && PCI
653 Hardware driver for the watchdog timer built into the Intel
654 Atom E6XX (TunnelCreek) processor.
656 To compile this driver as a module, choose M here: the
657 module will be called ie6xx_wdt.
659 config INTEL_SCU_WATCHDOG
660 bool "Intel SCU Watchdog for Mobile Platforms"
661 depends on X86_INTEL_MID
663 Hardware driver for the watchdog time built into the Intel SCU
664 for Intel Mobile Platforms.
666 To compile this driver as a module, choose M here.
669 tristate "Intel TCO Timer/Watchdog"
670 depends on (X86 || IA64) && PCI
674 Hardware driver for the intel TCO timer based watchdog devices.
675 These drivers are included in the Intel 82801 I/O Controller
676 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
679 The TCO (Total Cost of Ownership) timer is a watchdog timer
680 that will reboot the machine after its second expiration. The
681 expiration time can be configured with the "heartbeat" parameter.
683 On some motherboards the driver may fail to reset the chipset's
684 NO_REBOOT flag which prevents the watchdog from rebooting the
685 machine. If this is the case you will get a kernel message like
686 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
688 To compile this driver as a module, choose M here: the
689 module will be called iTCO_wdt.
691 config ITCO_VENDOR_SUPPORT
692 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
695 Add vendor specific support to the intel TCO timer based watchdog
696 devices. At this moment we only have additional support for some
697 SuperMicro Inc. motherboards.
700 tristate "IT8712F (Smart Guardian) Watchdog Timer"
703 This is the driver for the built-in watchdog timer on the IT8712F
704 Super I/0 chipset used on many motherboards.
706 If the driver does not work, then make sure that the game port in
709 To compile this driver as a module, choose M here: the
710 module will be called it8712f_wdt.
713 tristate "IT87 Watchdog Timer"
716 This is the driver for the hardware watchdog on the ITE IT8702,
717 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
720 If the driver does not work, then make sure that the game port in
723 This watchdog simply watches your kernel to make sure it doesn't
724 freeze, and if it does, it reboots your computer after a certain
727 To compile this driver as a module, choose M here: the module will
731 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
732 depends on X86 && PCI
734 A software monitoring watchdog and NMI sourcing driver. This driver
735 will detect lockups and provide a stack trace. This is a driver that
736 will only load on an HP ProLiant system with a minimum of iLO2 support.
737 To compile this driver as a module, choose M here: the module will be
741 tristate "Kontron COM Watchdog Timer"
742 depends on MFD_KEMPLD
745 Support for the PLD watchdog on some Kontron ETX and COMexpress
748 This driver can also be built as a module. If so, the module will be
751 config HPWDT_NMI_DECODING
752 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
753 depends on HP_WATCHDOG
756 When an NMI occurs this feature will make the necessary BIOS calls to
757 log the cause of the NMI.
760 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
763 This is a driver for National Semiconductor PC87307/PC97307 hardware
764 watchdog cards as found on the SC1200. This watchdog is mainly used
765 for power management purposes and can be used to power down the device
766 during inactivity periods (includes interrupt activity monitoring).
768 To compile this driver as a module, choose M here: the
769 module will be called sc1200wdt.
771 Most people will say N.
774 tristate "National Semiconductor SCx200 Watchdog"
775 depends on SCx200 && PCI
777 Enable the built-in watchdog timer support on the National
778 Semiconductor SCx200 processors.
780 If compiled as a module, it will be called scx200_wdt.
783 tristate "NS PC87413 watchdog"
786 This is the driver for the hardware watchdog on the PC87413 chipset
787 This watchdog simply watches your kernel to make sure it doesn't
788 freeze, and if it does, it reboots your computer after a certain
791 To compile this driver as a module, choose M here: the
792 module will be called pc87413_wdt.
794 Most people will say N.
797 tristate "nVidia TCO Timer/Watchdog"
798 depends on X86 && PCI
800 Hardware driver for the TCO timer built into the nVidia Hub family
801 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
802 watchdog timer that will reboot the machine after its second
803 expiration. The expiration time can be configured with the
804 "heartbeat" parameter.
806 On some motherboards the driver may fail to reset the chipset's
807 NO_REBOOT flag which prevents the watchdog from rebooting the
808 machine. If this is the case you will get a kernel message like
809 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
811 To compile this driver as a module, choose M here: the
812 module will be called nv_tco.
815 tristate "RDC R-321x SoC watchdog"
816 depends on X86_RDC321X
818 This is the driver for the built in hardware watchdog
819 in the RDC R-321x SoC.
821 To compile this driver as a module, choose M here: the
822 module will be called rdc321x_wdt.
825 tristate "SBC-60XX Watchdog Timer"
828 This driver can be used with the watchdog timer found on some
829 single board computers, namely the 6010 PII based computer.
830 It may well work with other cards. It reads port 0x443 to enable
831 and re-set the watchdog timer, and reads port 0x45 to disable
832 the watchdog. If you have a card that behave in similar ways,
833 you can probably make this driver work with your card as well.
835 You can compile this driver directly into the kernel, or use
836 it as a module. The module will be called sbc60xxwdt.
839 tristate "SBC8360 Watchdog Timer"
843 This is the driver for the hardware watchdog on the SBC8360 Single
844 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
846 To compile this driver as a module, choose M here: the
847 module will be called sbc8360.
849 Most people will say N.
852 tristate "SBC Nano 7240 Watchdog Timer"
853 depends on X86_32 && !UML
855 This is the driver for the hardware watchdog found on the IEI
856 single board computers EPIC Nano 7240 (and likely others). This
857 watchdog simply watches your kernel to make sure it doesn't freeze,
858 and if it does, it reboots your computer after a certain amount of
861 To compile this driver as a module, choose M here: the
862 module will be called sbc7240_wdt.
865 tristate "SMA CPU5 Watchdog"
869 To compile this driver as a module, choose M here: the
870 module will be called cpu5wdt.
872 config SMSC_SCH311X_WDT
873 tristate "SMSC SCH311X Watchdog Timer"
876 This is the driver for the hardware watchdog timer on the
877 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
878 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
881 To compile this driver as a module, choose M here: the
882 module will be called sch311x_wdt.
884 config SMSC37B787_WDT
885 tristate "Winbond SMsC37B787 Watchdog Timer"
888 This is the driver for the hardware watchdog component on the
889 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
890 from Vision Systems and maybe others.
892 This watchdog simply watches your kernel to make sure it doesn't
893 freeze, and if it does, it reboots your computer after a certain
896 Usually a userspace daemon will notify the kernel WDT driver that
897 userspace is still alive, at regular intervals.
899 To compile this driver as a module, choose M here: the
900 module will be called smsc37b787_wdt.
902 Most people will say N.
905 tristate "VIA Watchdog Timer"
906 depends on X86 && PCI
909 This is the driver for the hardware watchdog timer on VIA
910 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
912 To compile this driver as a module, choose M here; the module
913 will be called via_wdt.
915 Most people will say N.
918 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
922 This is the driver for the hardware watchdog on the following
924 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
934 This watchdog simply watches your kernel to make sure it doesn't
935 freeze, and if it does, it reboots your computer after a certain
938 To compile this driver as a module, choose M here: the
939 module will be called w83627hf_wdt.
941 Most people will say N.
944 tristate "W83877F (EMACS) Watchdog Timer"
947 This is the driver for the hardware watchdog on the W83877F chipset
948 as used in EMACS PC-104 motherboards (and likely others). This
949 watchdog simply watches your kernel to make sure it doesn't freeze,
950 and if it does, it reboots your computer after a certain amount of
953 To compile this driver as a module, choose M here: the
954 module will be called w83877f_wdt.
956 Most people will say N.
959 tristate "W83977F (PCM-5335) Watchdog Timer"
962 This is the driver for the hardware watchdog on the W83977F I/O chip
963 as used in AAEON's PCM-5335 SBC (and likely others). This
964 watchdog simply watches your kernel to make sure it doesn't freeze,
965 and if it does, it reboots your computer after a certain amount of
968 To compile this driver as a module, choose M here: the
969 module will be called w83977f_wdt.
972 tristate "ZF MachZ Watchdog"
975 If you are using a ZF Micro MachZ processor, say Y here, otherwise
976 N. This is the driver for the watchdog timer built-in on that
977 processor using ZF-Logic interface. This watchdog simply watches
978 your kernel to make sure it doesn't freeze, and if it does, it
979 reboots your computer after a certain amount of time.
981 To compile this driver as a module, choose M here: the
982 module will be called machzwd.
984 config SBC_EPX_C3_WATCHDOG
985 tristate "Winsystems SBC EPX-C3 watchdog"
988 This is the driver for the built-in watchdog timer on the EPX-C3
989 Single-board computer made by Winsystems, Inc.
991 *Note*: This hardware watchdog is not probeable and thus there
992 is no way to know if writing to its IO address will corrupt
993 your system or have any real effect. The only way to be sure
994 that this driver does what you want is to make sure you
995 are running it on an EPX-C3 from Winsystems with the watchdog
996 timer at IO address 0x1ee and 0x1ef. It will write to both those
997 IO ports. Basically, the assumption is made that if you compile
998 this driver into your kernel and/or load it as a module, that you
999 know what you are doing and that you are in fact running on an
1002 To compile this driver as a module, choose M here: the
1003 module will be called sbc_epx_c3.
1009 config M54xx_WATCHDOG
1010 tristate "MCF54xx watchdog support"
1013 To compile this driver as a module, choose M here: the
1014 module will be called m54xx_wdt.
1016 # MicroBlaze Architecture
1021 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1024 Hardware driver for the built-in watchdog timer on the Atheros
1025 AR71XX/AR724X/AR913X SoCs.
1028 tristate "Broadcom BCM47xx Watchdog Timer"
1030 select WATCHDOG_CORE
1032 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1035 tristate "IDT RC32434 SoC Watchdog Timer"
1036 depends on MIKROTIK_RB532
1038 Hardware driver for the IDT RC32434 SoC built-in
1041 To compile this driver as a module, choose M here: the
1042 module will be called rc32434_wdt.
1045 tristate "Indy/I2 Hardware Watchdog"
1046 depends on SGI_HAS_INDYDOG
1048 Hardware driver for the Indy's/I2's watchdog. This is a
1049 watchdog timer that will reboot the machine after a 60 second
1050 timer expired and no process has written to /dev/watchdog during
1054 tristate "Ingenic jz4740 SoC hardware watchdog"
1055 depends on MACH_JZ4740
1056 select WATCHDOG_CORE
1058 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1061 tristate "MTX-1 Hardware Watchdog"
1062 depends on MIPS_MTX1
1064 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1065 will reboot the machine after a 100 seconds timer expired.
1068 tristate "PNX833x Hardware Watchdog"
1069 depends on SOC_PNX8335
1071 Hardware driver for the PNX833x's watchdog. This is a
1072 watchdog timer that will reboot the machine after a programmable
1073 timer has expired and no process has written to /dev/watchdog during
1077 tristate "Sibyte SoC hardware watchdog"
1080 Watchdog driver for the built in watchdog hardware in Sibyte
1081 SoC processors. There are apparently two watchdog timers
1082 on such processors; this driver supports only the first one,
1083 because currently Linux only supports exporting one watchdog
1086 To compile this driver as a loadable module, choose M here.
1087 The module will be called sb_wdog.
1090 tristate "TI AR7 Watchdog Timer"
1093 Hardware driver for the TI AR7 Watchdog Timer.
1096 tristate "Toshiba TXx9 Watchdog Timer"
1097 depends on CPU_TX39XX || CPU_TX49XX
1098 select WATCHDOG_CORE
1100 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1103 tristate "Cavium OCTEON SOC family Watchdog Timer"
1104 depends on CAVIUM_OCTEON_SOC
1106 select EXPORT_UASM if OCTEON_WDT = m
1108 Hardware driver for OCTEON's on chip watchdog timer.
1109 Enables the watchdog for all cores running Linux. It
1110 installs a NMI handler and pokes the watchdog based on an
1111 interrupt. On first expiration of the watchdog, the
1112 interrupt handler pokes it. The second expiration causes an
1113 NMI that prints a message. The third expiration causes a
1116 When userspace has /dev/watchdog open, no poking is done
1117 from the first interrupt, it is then only poked when the
1121 tristate "Broadcom BCM63xx hardware watchdog"
1124 Watchdog driver for the built in watchdog hardware in Broadcom
1127 To compile this driver as a loadable module, choose M here.
1128 The module will be called bcm63xx_wdt.
1131 tristate "Broadcom BCM2835 hardware watchdog"
1132 depends on ARCH_BCM2835
1133 select WATCHDOG_CORE
1135 Watchdog driver for the built in watchdog hardware in Broadcom
1138 To compile this driver as a loadable module, choose M here.
1139 The module will be called bcm2835_wdt.
1142 tristate "BCM Kona Watchdog"
1143 depends on ARCH_BCM_MOBILE
1144 select WATCHDOG_CORE
1146 Support for the watchdog timer on the following Broadcom BCM281xx
1147 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1150 Say 'Y' or 'M' here to enable the driver. The module will be called
1153 config BCM_KONA_WDT_DEBUG
1154 bool "DEBUGFS support for BCM Kona Watchdog"
1155 depends on BCM_KONA_WDT
1157 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1158 access to the driver's internal data structures as well as watchdog
1159 timer hardware registres.
1161 If in doubt, say 'N'.
1164 tristate "Lantiq SoC watchdog"
1167 Hardware driver for the Lantiq SoC Watchdog Timer.
1170 tristate "Ralink SoC watchdog"
1171 select WATCHDOG_CORE
1174 Hardware driver for the Ralink SoC Watchdog Timer.
1176 # PARISC Architecture
1178 # POWERPC Architecture
1181 tristate "GE Watchdog Timer"
1184 Watchdog timer found in a number of GE single board computers.
1187 bool "MPC52xx Watchdog Timer"
1188 depends on PPC_MPC52xx
1190 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1193 tristate "MPC8xxx Platform Watchdog Timer"
1194 depends on PPC_8xx || PPC_83xx || PPC_86xx
1195 select WATCHDOG_CORE
1197 This driver is for a SoC level watchdog that exists on some
1198 Freescale PowerPC processors. So far this driver supports:
1203 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1206 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1210 tristate "PIKA FPGA Watchdog"
1214 This enables the watchdog in the PIKA FPGA. Currently used on
1218 tristate "PowerPC Book-E Watchdog Timer"
1219 depends on BOOKE || 4xx
1220 select WATCHDOG_CORE
1222 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1223 MPC85xx SOCs and the IBM PowerPC 440.
1225 Please see Documentation/watchdog/watchdog-api.txt for
1228 config BOOKE_WDT_DEFAULT_TIMEOUT
1229 int "PowerPC Book-E Watchdog Timer Default Timeout"
1230 depends on BOOKE_WDT
1231 default 38 if PPC_FSL_BOOK3E
1232 range 0 63 if PPC_FSL_BOOK3E
1233 default 3 if !PPC_FSL_BOOK3E
1234 range 0 3 if !PPC_FSL_BOOK3E
1236 Select the default watchdog timer period to be used by the PowerPC
1237 Book-E watchdog driver. A watchdog "event" occurs when the bit
1238 position represented by this number transitions from zero to one.
1240 For Freescale Book-E processors, this is a number between 0 and 63.
1241 For other Book-E processors, this is a number between 0 and 3.
1243 The value can be overridden by the wdt_period command-line parameter.
1246 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1247 select WATCHDOG_CORE
1250 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1252 The driver can also be built as a module. If so, the module will be
1255 If unsure select N here.
1257 # PPC64 Architecture
1259 config WATCHDOG_RTAS
1260 tristate "RTAS watchdog"
1263 This driver adds watchdog support for the RTAS watchdog.
1265 To compile this driver as a module, choose M here. The module
1266 will be called wdrtas.
1271 tristate "z/VM Watchdog Timer"
1274 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1275 provide a virtual watchdog timer to their guest that cause a
1276 user define Control Program command to be executed after a
1279 To compile this driver as a module, choose M here. The module
1280 will be called vmwatchdog.
1282 # SUPERH (sh + sh64) Architecture
1285 tristate "SuperH Watchdog"
1286 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1287 select WATCHDOG_CORE
1289 This driver adds watchdog support for the integrated watchdog in the
1290 SuperH processors. If you have one of these processors and wish
1291 to have watchdog support enabled, say Y, otherwise say N.
1293 As a side note, saying Y here will automatically boost HZ to 1000
1294 so that the timer has a chance to clear the overflow counter. On
1295 slower systems (such as the SH-2 and SH-3) this will likely yield
1296 some performance issues. As such, the WDT should be avoided here
1297 unless it is absolutely necessary.
1299 To compile this driver as a module, choose M here: the
1300 module will be called shwdt.
1302 # SPARC Architecture
1304 # SPARC64 Architecture
1306 config WATCHDOG_CP1XXX
1307 tristate "CP1XXX Hardware Watchdog support"
1308 depends on SPARC64 && PCI
1310 This is the driver for the hardware watchdog timers present on
1311 Sun Microsystems CompactPCI models CP1400 and CP1500.
1313 To compile this driver as a module, choose M here: the
1314 module will be called cpwatchdog.
1316 If you do not have a CompactPCI model CP1400 or CP1500, or
1317 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1318 you should say N to this option.
1321 tristate "RIO Hardware Watchdog support"
1322 depends on SPARC64 && PCI
1324 Say Y here to support the hardware watchdog capability on Sun RIO
1325 machines. The watchdog timeout period is normally one minute but
1326 can be changed with a boot-time parameter.
1328 # XTENSA Architecture
1333 tristate "Xen Watchdog support"
1336 Say Y here to support the hypervisor watchdog capability provided
1337 by Xen 4.0 and newer. The watchdog timeout period is normally one
1338 minute but can be changed with a boot-time parameter.
1341 tristate "UML watchdog"
1345 # ISA-based Watchdog Cards
1348 comment "ISA-based Watchdog Cards"
1352 tristate "Berkshire Products ISA-PC Watchdog"
1355 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1356 This card simply watches your kernel to make sure it doesn't freeze,
1357 and if it does, it reboots your computer after a certain amount of
1358 time. This driver is like the WDT501 driver but for different
1359 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1360 watchdog cards can be ordered from <http://www.berkprod.com/>.
1362 To compile this driver as a module, choose M here: the
1363 module will be called pcwd.
1365 Most people will say N.
1368 tristate "Mixcom Watchdog"
1371 This is a driver for the Mixcom hardware watchdog cards. This
1372 watchdog simply watches your kernel to make sure it doesn't freeze,
1373 and if it does, it reboots your computer after a certain amount of
1376 To compile this driver as a module, choose M here: the
1377 module will be called mixcomwd.
1379 Most people will say N.
1382 tristate "WDT Watchdog timer"
1385 If you have a WDT500P or WDT501P watchdog board, say Y here,
1386 otherwise N. It is not possible to probe for this board, which means
1387 that you have to inform the kernel about the IO port and IRQ that
1388 is needed (you can do this via the io and irq parameters)
1390 To compile this driver as a module, choose M here: the
1391 module will be called wdt.
1394 # PCI-based Watchdog Cards
1397 comment "PCI-based Watchdog Cards"
1400 config PCIPCWATCHDOG
1401 tristate "Berkshire Products PCI-PC Watchdog"
1404 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1405 This card simply watches your kernel to make sure it doesn't freeze,
1406 and if it does, it reboots your computer after a certain amount of
1407 time. The card can also monitor the internal temperature of the PC.
1408 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1410 To compile this driver as a module, choose M here: the
1411 module will be called pcwd_pci.
1413 Most people will say N.
1416 tristate "PCI-WDT500/501 Watchdog timer"
1419 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1421 If you have a PCI-WDT501 watchdog board then you can enable the
1422 temperature sensor by setting the type parameter to 501.
1424 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1425 can do this via the tachometer parameter. Only do this if you have a
1426 fan tachometer actually set up.
1428 To compile this driver as a module, choose M here: the
1429 module will be called wdt_pci.
1432 # USB-based Watchdog Cards
1435 comment "USB-based Watchdog Cards"
1438 config USBPCWATCHDOG
1439 tristate "Berkshire Products USB-PC Watchdog"
1442 This is the driver for the Berkshire Products USB-PC Watchdog card.
1443 This card simply watches your kernel to make sure it doesn't freeze,
1444 and if it does, it reboots your computer after a certain amount of
1445 time. The card can also monitor the internal temperature of the PC.
1446 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1448 To compile this driver as a module, choose M here: the
1449 module will be called pcwd_usb.
1451 Most people will say N.