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"
83 If you say yes here you get support for watchdog on the Dialog
84 Semiconductor DA9055 PMIC.
86 This driver can also be built as a module. If so, the module
87 will be called da9055_wdt.
89 config WM831X_WATCHDOG
90 tristate "WM831x watchdog"
94 Support for the watchdog in the WM831x AudioPlus PMICs. When
95 the watchdog triggers the system will be reset.
97 config WM8350_WATCHDOG
98 tristate "WM8350 watchdog"
102 Support for the watchdog in the WM8350 AudioPlus PMIC. When
103 the watchdog triggers the system will be reset.
109 config ARM_SP805_WATCHDOG
110 tristate "ARM SP805 Watchdog"
114 ARM Primecell SP805 Watchdog timer. This will reboot your system when
115 the timeout is reached.
117 config AT91RM9200_WATCHDOG
118 tristate "AT91RM9200 watchdog"
119 depends on ARCH_AT91RM9200
121 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
122 system when the timeout is reached.
124 config AT91SAM9X_WATCHDOG
125 tristate "AT91SAM9X / AT91CAP9 watchdog"
126 depends on ARCH_AT91 && !ARCH_AT91RM9200
128 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
129 reboot your system when the timeout is reached.
131 config 21285_WATCHDOG
132 tristate "DC21285 watchdog"
133 depends on FOOTBRIDGE
135 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
136 here if you wish to use this. Alternatively say M to compile the
137 driver as a module, which will be called wdt285.
139 This driver does not work on all machines. In particular, early CATS
140 boards have hardware problems that will cause the machine to simply
141 lock up if the watchdog fires.
143 "If in doubt, leave it out" - say N.
146 tristate "NetWinder WB83C977 watchdog"
147 depends on FOOTBRIDGE && ARCH_NETWINDER
149 Say Y here to include support for the WB977 watchdog included in
150 NetWinder machines. Alternatively say M to compile the driver as
151 a module, which will be called wdt977.
153 Not sure? It's safe to say N.
155 config IXP4XX_WATCHDOG
156 tristate "IXP4xx Watchdog"
157 depends on ARCH_IXP4XX
159 Say Y here if to include support for the watchdog timer
160 in the Intel IXP4xx network processors. This driver can
161 be built as a module by choosing M. The module will
162 be called ixp4xx_wdt.
164 Note: The internal IXP4xx watchdog does a soft CPU reset
165 which doesn't reset any peripherals. There are circumstances
166 where the watchdog will fail to reset the board correctly
167 (e.g., if the boot ROM is in an unreadable state).
169 Say N if you are unsure.
171 config KS8695_WATCHDOG
172 tristate "KS8695 watchdog"
173 depends on ARCH_KS8695
175 Watchdog timer embedded into KS8695 processor. This will reboot your
176 system when the timeout is reached.
178 config HAVE_S3C2410_WATCHDOG
181 This will include watchdog timer support for Samsung SoCs. If
182 you want to include watchdog support for any machine, kindly
183 select this in the respective mach-XXXX/Kconfig file.
185 config S3C2410_WATCHDOG
186 tristate "S3C2410 Watchdog"
187 depends on HAVE_S3C2410_WATCHDOG
190 Watchdog timer block in the Samsung SoCs. This will reboot
191 the system when the timer expires with the watchdog enabled.
193 The driver is limited by the speed of the system's PCLK
194 signal, so with reasonably fast systems (PCLK around 50-66MHz)
195 then watchdog intervals of over approximately 20seconds are
198 The driver can be built as a module by choosing M, and will
199 be called s3c2410_wdt
201 config SA1100_WATCHDOG
202 tristate "SA1100/PXA2xx watchdog"
203 depends on ARCH_SA1100 || ARCH_PXA
205 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
206 reboot your system when timeout is reached.
208 NOTE: once enabled, this timer cannot be disabled.
210 To compile this driver as a module, choose M here: the
211 module will be called sa1100_wdt.
214 tristate "Synopsys DesignWare watchdog"
215 depends on ARM && HAVE_CLK
217 Say Y here if to include support for the Synopsys DesignWare
218 watchdog timer found in many ARM chips.
219 To compile this driver as a module, choose M here: the
220 module will be called dw_wdt.
222 config MPCORE_WATCHDOG
223 tristate "MPcore watchdog"
224 depends on HAVE_ARM_TWD
226 Watchdog timer embedded into the MPcore system.
228 To compile this driver as a module, choose M here: the
229 module will be called mpcore_wdt.
231 config EP93XX_WATCHDOG
232 tristate "EP93xx Watchdog"
233 depends on ARCH_EP93XX
236 Say Y here if to include support for the watchdog timer
237 embedded in the Cirrus Logic EP93xx family of devices.
239 To compile this driver as a module, choose M here: the
240 module will be called ep93xx_wdt.
243 tristate "OMAP Watchdog"
244 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
247 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
248 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
250 config PNX4008_WATCHDOG
251 tristate "LPC32XX Watchdog"
252 depends on ARCH_LPC32XX
255 Say Y here if to include support for the watchdog timer
256 in the LPC32XX processor.
257 This driver can be built as a module by choosing M. The module
258 will be called pnx4008_wdt.
260 Say N if you are unsure.
263 tristate "IOP Watchdog"
265 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
267 Say Y here if to include support for the watchdog timer
268 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
269 be built as a module by choosing M. The module will
272 Note: The IOP13XX watchdog does an Internal Bus Reset which will
273 affect both cores and the peripherals of the IOP. The ATU-X
274 and/or ATUe configuration registers will remain intact, but if
275 operating as an Root Complex and/or Central Resource, the PCI-X
276 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
278 config DAVINCI_WATCHDOG
279 tristate "DaVinci watchdog"
280 depends on ARCH_DAVINCI
282 Say Y here if to include support for the watchdog timer
283 in the DaVinci DM644x/DM646x processors.
284 To compile this driver as a module, choose M here: the
285 module will be called davinci_wdt.
287 NOTE: once enabled, this timer cannot be disabled.
288 Say N if you are unsure.
290 config ORION_WATCHDOG
291 tristate "Orion watchdog"
292 depends on ARCH_ORION5X || ARCH_KIRKWOOD
295 Say Y here if to include support for the watchdog timer
296 in the Marvell Orion5x and Kirkwood ARM SoCs.
297 To compile this driver as a module, choose M here: the
298 module will be called orion_wdt.
300 config COH901327_WATCHDOG
301 bool "ST-Ericsson COH 901 327 watchdog"
303 default y if MACH_U300
306 Say Y here to include Watchdog timer support for the
307 watchdog embedded into the ST-Ericsson U300 series platforms.
308 This watchdog is used to reset the system and thus cannot be
309 compiled as a module.
311 config TWL4030_WATCHDOG
312 tristate "TWL4030 Watchdog"
313 depends on TWL4030_CORE
316 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
317 watchdog timer support for TWL4030 chips.
319 config STMP3XXX_WATCHDOG
320 tristate "Freescale STMP3XXX watchdog"
321 depends on ARCH_STMP3XXX
323 Say Y here if to include support for the watchdog timer
324 for the Sigmatel STMP37XX/378X SoC.
325 To compile this driver as a module, choose M here: the
326 module will be called stmp3xxx_wdt.
328 config NUC900_WATCHDOG
329 tristate "Nuvoton NUC900 watchdog"
330 depends on ARCH_W90X900
332 Say Y here if to include support for the watchdog timer
333 for the Nuvoton NUC900 series SoCs.
334 To compile this driver as a module, choose M here: the
335 module will be called nuc900_wdt.
337 config TS72XX_WATCHDOG
338 tristate "TS-72XX SBC Watchdog"
339 depends on MACH_TS72XX
341 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
342 watchdog timer implemented in a external CPLD chip. Say Y here
343 if you want to support for the watchdog timer on TS-72XX boards.
345 To compile this driver as a module, choose M here: the
346 module will be called ts72xx_wdt.
348 config MAX63XX_WATCHDOG
349 tristate "Max63xx watchdog"
350 depends on ARM && HAS_IOMEM
353 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
356 tristate "IMX2+ Watchdog"
359 This is the driver for the hardware watchdog
360 on the Freescale IMX2 and later processors.
361 If you have one of these processors and wish to have
362 watchdog support enabled, say Y, otherwise say N.
364 To compile this driver as a module, choose M here: the
365 module will be called imx2_wdt.
369 config AT32AP700X_WDT
370 tristate "AT32AP700x watchdog"
371 depends on CPU_AT32AP700X
373 Watchdog timer embedded into AT32AP700x devices. This will reboot
374 your system when the timeout is reached.
376 # BLACKFIN Architecture
379 tristate "Blackfin On-Chip Watchdog Timer"
382 If you say yes here you will get support for the Blackfin On-Chip
383 Watchdog Timer. If you have one of these processors and wish to
384 have watchdog support enabled, say Y, otherwise say N.
386 To compile this driver as a module, choose M here: the
387 module will be called bfin_wdt.
395 # X86 (i386 + ia64 + x86_64) Architecture
398 tristate "Acquire SBC Watchdog Timer"
401 This is the driver for the hardware watchdog on Single Board
402 Computers produced by Acquire Inc (and others). This watchdog
403 simply watches your kernel to make sure it doesn't freeze, and if
404 it does, it reboots your computer after a certain amount of time.
406 To compile this driver as a module, choose M here: the
407 module will be called acquirewdt.
409 Most people will say N.
412 tristate "Advantech SBC Watchdog Timer"
415 If you are configuring a Linux kernel for the Advantech single-board
416 computer, say `Y' here to support its built-in watchdog timer
417 feature. More information can be found at
418 <http://www.advantech.com.tw/products/>
421 tristate "ALi M1535 PMU Watchdog Timer"
422 depends on X86 && PCI
424 This is the driver for the hardware watchdog on the ALi M1535 PMU.
426 To compile this driver as a module, choose M here: the
427 module will be called alim1535_wdt.
429 Most people will say N.
432 tristate "ALi M7101 PMU Computer Watchdog"
435 This is the driver for the hardware watchdog on the ALi M7101 PMU
436 as used in the x86 Cobalt servers and also found in some
437 SPARC Netra servers too.
439 To compile this driver as a module, choose M here: the
440 module will be called alim7101_wdt.
442 Most people will say N.
445 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
446 depends on X86 && EXPERIMENTAL
448 This is the driver for the hardware watchdog on the Fintek
449 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
451 You can compile this driver directly into the kernel, or use
452 it as a module. The module will be called f71808e_wdt.
455 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
456 depends on X86 && PCI
458 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
459 (Total Cost of Ownership) timer is a watchdog timer that will reboot
460 the machine after its expiration. The expiration time can be
461 configured with the "heartbeat" parameter.
463 To compile this driver as a module, choose M here: the
464 module will be called sp5100_tco.
467 tristate "AMD Geode CS5535/CS5536 Watchdog"
468 depends on CS5535_MFGPT
470 This driver enables a watchdog capability built into the
471 CS5535/CS5536 companion chips for the AMD Geode GX and LX
472 processors. This watchdog watches your kernel to make sure
473 it doesn't freeze, and if it does, it reboots your computer after
474 a certain amount of time.
476 You can compile this driver directly into the kernel, or use
477 it as a module. The module will be called geodewdt.
480 tristate "AMD Elan SC520 processor Watchdog"
483 This is the driver for the hardware watchdog built in to the
484 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
485 This watchdog simply watches your kernel to make sure it doesn't
486 freeze, and if it does, it reboots your computer after a certain
489 You can compile this driver directly into the kernel, or use
490 it as a module. The module will be called sc520_wdt.
492 config SBC_FITPC2_WATCHDOG
493 tristate "Compulab SBC-FITPC2 watchdog"
496 This is the driver for the built-in watchdog timer on the fit-PC2,
497 fit-PC2i, CM-iAM single-board computers made by Compulab.
499 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
500 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
502 Entering BIOS setup temporary disables watchdog operation regardless to current state,
503 so system will not be restarted while user in BIOS setup.
505 Once watchdog was enabled the system will be restarted every
506 "Watchdog Timer Value" period, so to prevent it user can restart or
507 disable the watchdog.
509 To compile this driver as a module, choose M here: the
510 module will be called sbc_fitpc2_wdt.
512 Most people will say N.
515 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
518 Enable support for the watchdog timer on the Eurotech CPU-1220 and
519 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
520 information are at <http://www.eurotech.it/>.
523 tristate "IB700 SBC Watchdog Timer"
526 This is the driver for the hardware watchdog on the IB700 Single
527 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
528 simply watches your kernel to make sure it doesn't freeze, and if
529 it does, it reboots your computer after a certain amount of time.
531 This driver is like the WDT501 driver but for slightly different hardware.
533 To compile this driver as a module, choose M here: the
534 module will be called ib700wdt.
536 Most people will say N.
539 tristate "IBM Automatic Server Restart"
542 This is the driver for the IBM Automatic Server Restart watchdog
543 timer built-in into some eServer xSeries machines.
545 To compile this driver as a module, choose M here: the
546 module will be called ibmasr.
549 tristate "ICP Single Board Computer Watchdog Timer"
552 This is a driver for the hardware watchdog on the ICP Single
553 Board Computer. This driver is working on (at least) the following
554 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
556 To compile this driver as a module, choose M here: the
557 module will be called wafer5823wdt.
560 tristate "Intel 6300ESB Timer/Watchdog"
563 Hardware driver for the watchdog timer built into the Intel
564 6300ESB controller hub.
566 To compile this driver as a module, choose M here: the
567 module will be called i6300esb.
570 tristate "Intel Atom E6xx Watchdog"
571 depends on X86 && PCI
576 Hardware driver for the watchdog timer built into the Intel
577 Atom E6XX (TunnelCreek) processor.
579 To compile this driver as a module, choose M here: the
580 module will be called ie6xx_wdt.
582 config INTEL_SCU_WATCHDOG
583 bool "Intel SCU Watchdog for Mobile Platforms"
586 Hardware driver for the watchdog time built into the Intel SCU
587 for Intel Mobile Platforms.
589 To compile this driver as a module, choose M here.
592 tristate "Intel TCO Timer/Watchdog"
593 depends on (X86 || IA64) && PCI
597 Hardware driver for the intel TCO timer based watchdog devices.
598 These drivers are included in the Intel 82801 I/O Controller
599 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
602 The TCO (Total Cost of Ownership) timer is a watchdog timer
603 that will reboot the machine after its second expiration. The
604 expiration time can be configured with the "heartbeat" parameter.
606 On some motherboards the driver may fail to reset the chipset's
607 NO_REBOOT flag which prevents the watchdog from rebooting the
608 machine. If this is the case you will get a kernel message like
609 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
611 To compile this driver as a module, choose M here: the
612 module will be called iTCO_wdt.
614 config ITCO_VENDOR_SUPPORT
615 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
618 Add vendor specific support to the intel TCO timer based watchdog
619 devices. At this moment we only have additional support for some
620 SuperMicro Inc. motherboards.
623 tristate "IT8712F (Smart Guardian) Watchdog Timer"
626 This is the driver for the built-in watchdog timer on the IT8712F
627 Super I/0 chipset used on many motherboards.
629 If the driver does not work, then make sure that the game port in
632 To compile this driver as a module, choose M here: the
633 module will be called it8712f_wdt.
636 tristate "IT87 Watchdog Timer"
637 depends on X86 && EXPERIMENTAL
639 This is the driver for the hardware watchdog on the ITE IT8702,
640 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
643 If the driver does not work, then make sure that the game port in
646 This watchdog simply watches your kernel to make sure it doesn't
647 freeze, and if it does, it reboots your computer after a certain
650 To compile this driver as a module, choose M here: the module will
654 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
655 depends on X86 && PCI
657 A software monitoring watchdog and NMI sourcing driver. This driver
658 will detect lockups and provide a stack trace. This is a driver that
659 will only load on an HP ProLiant system with a minimum of iLO2 support.
660 To compile this driver as a module, choose M here: the module will be
663 config HPWDT_NMI_DECODING
664 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
665 depends on HP_WATCHDOG
668 When an NMI occurs this feature will make the necessary BIOS calls to
669 log the cause of the NMI.
672 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
675 This is a driver for National Semiconductor PC87307/PC97307 hardware
676 watchdog cards as found on the SC1200. This watchdog is mainly used
677 for power management purposes and can be used to power down the device
678 during inactivity periods (includes interrupt activity monitoring).
680 To compile this driver as a module, choose M here: the
681 module will be called sc1200wdt.
683 Most people will say N.
686 tristate "National Semiconductor SCx200 Watchdog"
687 depends on SCx200 && PCI
689 Enable the built-in watchdog timer support on the National
690 Semiconductor SCx200 processors.
692 If compiled as a module, it will be called scx200_wdt.
695 tristate "NS PC87413 watchdog"
698 This is the driver for the hardware watchdog on the PC87413 chipset
699 This watchdog simply watches your kernel to make sure it doesn't
700 freeze, and if it does, it reboots your computer after a certain
703 To compile this driver as a module, choose M here: the
704 module will be called pc87413_wdt.
706 Most people will say N.
709 tristate "nVidia TCO Timer/Watchdog"
710 depends on X86 && PCI
712 Hardware driver for the TCO timer built into the nVidia Hub family
713 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
714 watchdog timer that will reboot the machine after its second
715 expiration. The expiration time can be configured with the
716 "heartbeat" parameter.
718 On some motherboards the driver may fail to reset the chipset's
719 NO_REBOOT flag which prevents the watchdog from rebooting the
720 machine. If this is the case you will get a kernel message like
721 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
723 To compile this driver as a module, choose M here: the
724 module will be called nv_tco.
727 tristate "RDC R-321x SoC watchdog"
728 depends on X86_RDC321X
730 This is the driver for the built in hardware watchdog
731 in the RDC R-321x SoC.
733 To compile this driver as a module, choose M here: the
734 module will be called rdc321x_wdt.
737 tristate "SBC-60XX Watchdog Timer"
740 This driver can be used with the watchdog timer found on some
741 single board computers, namely the 6010 PII based computer.
742 It may well work with other cards. It reads port 0x443 to enable
743 and re-set the watchdog timer, and reads port 0x45 to disable
744 the watchdog. If you have a card that behave in similar ways,
745 you can probably make this driver work with your card as well.
747 You can compile this driver directly into the kernel, or use
748 it as a module. The module will be called sbc60xxwdt.
751 tristate "SBC8360 Watchdog Timer"
755 This is the driver for the hardware watchdog on the SBC8360 Single
756 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
758 To compile this driver as a module, choose M here: the
759 module will be called sbc8360.
761 Most people will say N.
764 tristate "SBC Nano 7240 Watchdog Timer"
765 depends on X86_32 && !UML
767 This is the driver for the hardware watchdog found on the IEI
768 single board computers EPIC Nano 7240 (and likely others). This
769 watchdog simply watches your kernel to make sure it doesn't freeze,
770 and if it does, it reboots your computer after a certain amount of
773 To compile this driver as a module, choose M here: the
774 module will be called sbc7240_wdt.
777 tristate "SMA CPU5 Watchdog"
781 To compile this driver as a module, choose M here: the
782 module will be called cpu5wdt.
784 config SMSC_SCH311X_WDT
785 tristate "SMSC SCH311X Watchdog Timer"
788 This is the driver for the hardware watchdog timer on the
789 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
790 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
793 To compile this driver as a module, choose M here: the
794 module will be called sch311x_wdt.
796 config SMSC37B787_WDT
797 tristate "Winbond SMsC37B787 Watchdog Timer"
800 This is the driver for the hardware watchdog component on the
801 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
802 from Vision Systems and maybe others.
804 This watchdog simply watches your kernel to make sure it doesn't
805 freeze, and if it does, it reboots your computer after a certain
808 Usually a userspace daemon will notify the kernel WDT driver that
809 userspace is still alive, at regular intervals.
811 To compile this driver as a module, choose M here: the
812 module will be called smsc37b787_wdt.
814 Most people will say N.
817 tristate "VIA Watchdog Timer"
818 depends on X86 && PCI
821 This is the driver for the hardware watchdog timer on VIA
822 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
824 To compile this driver as a module, choose M here; the module
825 will be called via_wdt.
827 Most people will say N.
830 tristate "W83627HF/W83627DHG Watchdog Timer"
833 This is the driver for the hardware watchdog on the W83627HF chipset
834 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
835 (and likely others). The driver also supports the W83627DHG chip.
836 This watchdog simply watches your kernel to make sure it doesn't
837 freeze, and if it does, it reboots your computer after a certain
840 To compile this driver as a module, choose M here: the
841 module will be called w83627hf_wdt.
843 Most people will say N.
846 tristate "W83697HF/W83697HG Watchdog Timer"
849 This is the driver for the hardware watchdog on the W83697HF/HG
850 chipset as used in Dedibox/VIA motherboards (and likely others).
851 This watchdog simply watches your kernel to make sure it doesn't
852 freeze, and if it does, it reboots your computer after a certain
855 To compile this driver as a module, choose M here: the
856 module will be called w83697hf_wdt.
858 Most people will say N.
861 tristate "W83697UG/W83697UF Watchdog Timer"
864 This is the driver for the hardware watchdog on the W83697UG/UF
865 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
866 This watchdog simply watches your kernel to make sure it doesn't
867 freeze, and if it does, it reboots your computer after a certain
870 To compile this driver as a module, choose M here: the
871 module will be called w83697ug_wdt.
873 Most people will say N.
876 tristate "W83877F (EMACS) Watchdog Timer"
879 This is the driver for the hardware watchdog on the W83877F chipset
880 as used in EMACS PC-104 motherboards (and likely others). This
881 watchdog simply watches your kernel to make sure it doesn't freeze,
882 and if it does, it reboots your computer after a certain amount of
885 To compile this driver as a module, choose M here: the
886 module will be called w83877f_wdt.
888 Most people will say N.
891 tristate "W83977F (PCM-5335) Watchdog Timer"
894 This is the driver for the hardware watchdog on the W83977F I/O chip
895 as used in AAEON's PCM-5335 SBC (and likely others). This
896 watchdog simply watches your kernel to make sure it doesn't freeze,
897 and if it does, it reboots your computer after a certain amount of
900 To compile this driver as a module, choose M here: the
901 module will be called w83977f_wdt.
904 tristate "ZF MachZ Watchdog"
907 If you are using a ZF Micro MachZ processor, say Y here, otherwise
908 N. This is the driver for the watchdog timer built-in on that
909 processor using ZF-Logic interface. This watchdog simply watches
910 your kernel to make sure it doesn't freeze, and if it does, it
911 reboots your computer after a certain amount of time.
913 To compile this driver as a module, choose M here: the
914 module will be called machzwd.
916 config SBC_EPX_C3_WATCHDOG
917 tristate "Winsystems SBC EPX-C3 watchdog"
920 This is the driver for the built-in watchdog timer on the EPX-C3
921 Single-board computer made by Winsystems, Inc.
923 *Note*: This hardware watchdog is not probeable and thus there
924 is no way to know if writing to its IO address will corrupt
925 your system or have any real effect. The only way to be sure
926 that this driver does what you want is to make sure you
927 are running it on an EPX-C3 from Winsystems with the watchdog
928 timer at IO address 0x1ee and 0x1ef. It will write to both those
929 IO ports. Basically, the assumption is made that if you compile
930 this driver into your kernel and/or load it as a module, that you
931 know what you are doing and that you are in fact running on an
934 To compile this driver as a module, choose M here: the
935 module will be called sbc_epx_c3.
941 config M54xx_WATCHDOG
942 tristate "MCF54xx watchdog support"
945 To compile this driver as a module, choose M here: the
946 module will be called m54xx_wdt.
948 # MicroBlaze Architecture
950 config XILINX_WATCHDOG
951 tristate "Xilinx Watchdog timer"
952 depends on MICROBLAZE
954 Watchdog driver for the xps_timebase_wdt ip core.
956 IMPORTANT: The xps_timebase_wdt parent must have the property
957 "clock-frequency" at device tree.
959 To compile this driver as a module, choose M here: the
960 module will be called of_xilinx_wdt.
965 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
968 Hardware driver for the built-in watchdog timer on the Atheros
969 AR71XX/AR724X/AR913X SoCs.
972 tristate "Broadcom BCM47xx Watchdog Timer"
975 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
978 tristate "IDT RC32434 SoC Watchdog Timer"
979 depends on MIKROTIK_RB532
981 Hardware driver for the IDT RC32434 SoC built-in
984 To compile this driver as a module, choose M here: the
985 module will be called rc32434_wdt.
988 tristate "Indy/I2 Hardware Watchdog"
989 depends on SGI_HAS_INDYDOG
991 Hardware driver for the Indy's/I2's watchdog. This is a
992 watchdog timer that will reboot the machine after a 60 second
993 timer expired and no process has written to /dev/watchdog during
997 tristate "Ingenic jz4740 SoC hardware watchdog"
998 depends on MACH_JZ4740
1001 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1004 tristate "MTX-1 Hardware Watchdog"
1005 depends on MIPS_MTX1
1007 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1008 will reboot the machine after a 100 seconds timer expired.
1011 tristate "PNX833x Hardware Watchdog"
1012 depends on SOC_PNX8335
1014 Hardware driver for the PNX833x's watchdog. This is a
1015 watchdog timer that will reboot the machine after a programmable
1016 timer has expired and no process has written to /dev/watchdog during
1020 tristate "Sibyte SoC hardware watchdog"
1023 Watchdog driver for the built in watchdog hardware in Sibyte
1024 SoC processors. There are apparently two watchdog timers
1025 on such processors; this driver supports only the first one,
1026 because currently Linux only supports exporting one watchdog
1029 To compile this driver as a loadable module, choose M here.
1030 The module will be called sb_wdog.
1033 tristate "TI AR7 Watchdog Timer"
1036 Hardware driver for the TI AR7 Watchdog Timer.
1039 tristate "Toshiba TXx9 Watchdog Timer"
1040 depends on CPU_TX39XX || CPU_TX49XX
1041 select WATCHDOG_CORE
1043 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1046 tristate "Cavium OCTEON SOC family Watchdog Timer"
1047 depends on CPU_CAVIUM_OCTEON
1049 select EXPORT_UASM if OCTEON_WDT = m
1051 Hardware driver for OCTEON's on chip watchdog timer.
1052 Enables the watchdog for all cores running Linux. It
1053 installs a NMI handler and pokes the watchdog based on an
1054 interrupt. On first expiration of the watchdog, the
1055 interrupt handler pokes it. The second expiration causes an
1056 NMI that prints a message. The third expiration causes a
1059 When userspace has /dev/watchdog open, no poking is done
1060 from the first interrupt, it is then only poked when the
1064 tristate "Broadcom BCM63xx hardware watchdog"
1067 Watchdog driver for the built in watchdog hardware in Broadcom
1070 To compile this driver as a loadable module, choose M here.
1071 The module will be called bcm63xx_wdt.
1074 tristate "Lantiq SoC watchdog"
1077 Hardware driver for the Lantiq SoC Watchdog Timer.
1079 # PARISC Architecture
1081 # POWERPC Architecture
1084 tristate "GE Watchdog Timer"
1087 Watchdog timer found in a number of GE single board computers.
1090 bool "MPC52xx Watchdog Timer"
1091 depends on PPC_MPC52xx
1093 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1096 tristate "MPC8xxx Platform Watchdog Timer"
1097 depends on PPC_8xx || PPC_83xx || PPC_86xx
1099 This driver is for a SoC level watchdog that exists on some
1100 Freescale PowerPC processors. So far this driver supports:
1105 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1108 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1112 tristate "PIKA FPGA Watchdog"
1116 This enables the watchdog in the PIKA FPGA. Currently used on
1120 tristate "PowerPC Book-E Watchdog Timer"
1121 depends on BOOKE || 4xx
1123 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1124 MPC85xx SOCs and the IBM PowerPC 440.
1126 Please see Documentation/watchdog/watchdog-api.txt for
1129 config BOOKE_WDT_DEFAULT_TIMEOUT
1130 int "PowerPC Book-E Watchdog Timer Default Timeout"
1131 depends on BOOKE_WDT
1132 default 38 if PPC_FSL_BOOK3E
1133 range 0 63 if PPC_FSL_BOOK3E
1134 default 3 if !PPC_FSL_BOOK3E
1135 range 0 3 if !PPC_FSL_BOOK3E
1137 Select the default watchdog timer period to be used by the PowerPC
1138 Book-E watchdog driver. A watchdog "event" occurs when the bit
1139 position represented by this number transitions from zero to one.
1141 For Freescale Book-E processors, this is a number between 0 and 63.
1142 For other Book-E processors, this is a number between 0 and 3.
1144 The value can be overridden by the wdt_period command-line parameter.
1146 # PPC64 Architecture
1148 config WATCHDOG_RTAS
1149 tristate "RTAS watchdog"
1152 This driver adds watchdog support for the RTAS watchdog.
1154 To compile this driver as a module, choose M here. The module
1155 will be called wdrtas.
1160 tristate "z/VM Watchdog Timer"
1163 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1164 provide a virtual watchdog timer to their guest that cause a
1165 user define Control Program command to be executed after a
1168 To compile this driver as a module, choose M here. The module
1169 will be called vmwatchdog.
1171 # SUPERH (sh + sh64) Architecture
1174 tristate "SuperH Watchdog"
1175 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1176 select WATCHDOG_CORE
1178 This driver adds watchdog support for the integrated watchdog in the
1179 SuperH processors. If you have one of these processors and wish
1180 to have watchdog support enabled, say Y, otherwise say N.
1182 As a side note, saying Y here will automatically boost HZ to 1000
1183 so that the timer has a chance to clear the overflow counter. On
1184 slower systems (such as the SH-2 and SH-3) this will likely yield
1185 some performance issues. As such, the WDT should be avoided here
1186 unless it is absolutely necessary.
1188 To compile this driver as a module, choose M here: the
1189 module will be called shwdt.
1191 # SPARC Architecture
1193 # SPARC64 Architecture
1195 config WATCHDOG_CP1XXX
1196 tristate "CP1XXX Hardware Watchdog support"
1197 depends on SPARC64 && PCI
1199 This is the driver for the hardware watchdog timers present on
1200 Sun Microsystems CompactPCI models CP1400 and CP1500.
1202 To compile this driver as a module, choose M here: the
1203 module will be called cpwatchdog.
1205 If you do not have a CompactPCI model CP1400 or CP1500, or
1206 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1207 you should say N to this option.
1210 tristate "RIO Hardware Watchdog support"
1211 depends on SPARC64 && PCI
1213 Say Y here to support the hardware watchdog capability on Sun RIO
1214 machines. The watchdog timeout period is normally one minute but
1215 can be changed with a boot-time parameter.
1217 # XTENSA Architecture
1222 tristate "Xen Watchdog support"
1225 Say Y here to support the hypervisor watchdog capability provided
1226 by Xen 4.0 and newer. The watchdog timeout period is normally one
1227 minute but can be changed with a boot-time parameter.
1230 tristate "UML watchdog"
1234 # ISA-based Watchdog Cards
1237 comment "ISA-based Watchdog Cards"
1241 tristate "Berkshire Products ISA-PC Watchdog"
1244 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1245 This card simply watches your kernel to make sure it doesn't freeze,
1246 and if it does, it reboots your computer after a certain amount of
1247 time. This driver is like the WDT501 driver but for different
1248 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1249 watchdog cards can be ordered from <http://www.berkprod.com/>.
1251 To compile this driver as a module, choose M here: the
1252 module will be called pcwd.
1254 Most people will say N.
1257 tristate "Mixcom Watchdog"
1260 This is a driver for the Mixcom hardware watchdog cards. This
1261 watchdog simply watches your kernel to make sure it doesn't freeze,
1262 and if it does, it reboots your computer after a certain amount of
1265 To compile this driver as a module, choose M here: the
1266 module will be called mixcomwd.
1268 Most people will say N.
1271 tristate "WDT Watchdog timer"
1274 If you have a WDT500P or WDT501P watchdog board, say Y here,
1275 otherwise N. It is not possible to probe for this board, which means
1276 that you have to inform the kernel about the IO port and IRQ that
1277 is needed (you can do this via the io and irq parameters)
1279 To compile this driver as a module, choose M here: the
1280 module will be called wdt.
1283 # PCI-based Watchdog Cards
1286 comment "PCI-based Watchdog Cards"
1289 config PCIPCWATCHDOG
1290 tristate "Berkshire Products PCI-PC Watchdog"
1293 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1294 This card simply watches your kernel to make sure it doesn't freeze,
1295 and if it does, it reboots your computer after a certain amount of
1296 time. The card can also monitor the internal temperature of the PC.
1297 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1299 To compile this driver as a module, choose M here: the
1300 module will be called pcwd_pci.
1302 Most people will say N.
1305 tristate "PCI-WDT500/501 Watchdog timer"
1308 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1310 If you have a PCI-WDT501 watchdog board then you can enable the
1311 temperature sensor by setting the type parameter to 501.
1313 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1314 can do this via the tachometer parameter. Only do this if you have a
1315 fan tachometer actually set up.
1317 To compile this driver as a module, choose M here: the
1318 module will be called wdt_pci.
1321 # USB-based Watchdog Cards
1324 comment "USB-based Watchdog Cards"
1327 config USBPCWATCHDOG
1328 tristate "Berkshire Products USB-PC Watchdog"
1331 This is the driver for the Berkshire Products USB-PC Watchdog card.
1332 This card simply watches your kernel to make sure it doesn't freeze,
1333 and if it does, it reboots your computer after a certain amount of
1334 time. The card can also monitor the internal temperature of the PC.
1335 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1337 To compile this driver as a module, choose M here: the
1338 module will be called pcwd_usb.
1340 Most people will say N.