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"
59 A software monitoring watchdog. This will fail to reboot your system
60 from some situations that the hardware watchdog will recover
61 from. Equally it's a lot cheaper to install.
63 To compile this driver as a module, choose M here: the
64 module will be called softdog.
66 config WM831X_WATCHDOG
67 tristate "WM831x watchdog"
71 Support for the watchdog in the WM831x AudioPlus PMICs. When
72 the watchdog triggers the system will be reset.
74 config WM8350_WATCHDOG
75 tristate "WM8350 watchdog"
79 Support for the watchdog in the WM8350 AudioPlus PMIC. When
80 the watchdog triggers the system will be reset.
86 config ARM_SP805_WATCHDOG
87 tristate "ARM SP805 Watchdog"
90 ARM Primecell SP805 Watchdog timer. This will reboot your system when
91 the timeout is reached.
93 config AT91RM9200_WATCHDOG
94 tristate "AT91RM9200 watchdog"
95 depends on ARCH_AT91RM9200
97 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
98 system when the timeout is reached.
100 config AT91SAM9X_WATCHDOG
101 tristate "AT91SAM9X / AT91CAP9 watchdog"
102 depends on ARCH_AT91 && !ARCH_AT91RM9200
104 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
105 reboot your system when the timeout is reached.
107 config 21285_WATCHDOG
108 tristate "DC21285 watchdog"
109 depends on FOOTBRIDGE
111 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
112 here if you wish to use this. Alternatively say M to compile the
113 driver as a module, which will be called wdt285.
115 This driver does not work on all machines. In particular, early CATS
116 boards have hardware problems that will cause the machine to simply
117 lock up if the watchdog fires.
119 "If in doubt, leave it out" - say N.
122 tristate "NetWinder WB83C977 watchdog"
123 depends on FOOTBRIDGE && ARCH_NETWINDER
125 Say Y here to include support for the WB977 watchdog included in
126 NetWinder machines. Alternatively say M to compile the driver as
127 a module, which will be called wdt977.
129 Not sure? It's safe to say N.
131 config IXP2000_WATCHDOG
132 tristate "IXP2000 Watchdog"
133 depends on ARCH_IXP2000
135 Say Y here if to include support for the watchdog timer
136 in the Intel IXP2000(2400, 2800, 2850) network processors.
137 This driver can be built as a module by choosing M. The module
138 will be called ixp2000_wdt.
140 Say N if you are unsure.
142 config IXP4XX_WATCHDOG
143 tristate "IXP4xx Watchdog"
144 depends on ARCH_IXP4XX
146 Say Y here if to include support for the watchdog timer
147 in the Intel IXP4xx network processors. This driver can
148 be built as a module by choosing M. The module will
149 be called ixp4xx_wdt.
151 Note: The internal IXP4xx watchdog does a soft CPU reset
152 which doesn't reset any peripherals. There are circumstances
153 where the watchdog will fail to reset the board correctly
154 (e.g., if the boot ROM is in an unreadable state).
156 Say N if you are unsure.
158 config KS8695_WATCHDOG
159 tristate "KS8695 watchdog"
160 depends on ARCH_KS8695
162 Watchdog timer embedded into KS8695 processor. This will reboot your
163 system when the timeout is reached.
165 config HAVE_S3C2410_WATCHDOG
168 This will include watchdog timer support for Samsung SoCs. If
169 you want to include watchdog support for any machine, kindly
170 select this in the respective mach-XXXX/Kconfig file.
172 config S3C2410_WATCHDOG
173 tristate "S3C2410 Watchdog"
174 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
177 Watchdog timer block in the Samsung SoCs. This will reboot
178 the system when the timer expires with the watchdog enabled.
180 The driver is limited by the speed of the system's PCLK
181 signal, so with reasonably fast systems (PCLK around 50-66MHz)
182 then watchdog intervals of over approximately 20seconds are
185 The driver can be built as a module by choosing M, and will
186 be called s3c2410_wdt
188 config SA1100_WATCHDOG
189 tristate "SA1100/PXA2xx watchdog"
190 depends on ARCH_SA1100 || ARCH_PXA
192 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
193 reboot your system when timeout is reached.
195 NOTE: once enabled, this timer cannot be disabled.
197 To compile this driver as a module, choose M here: the
198 module will be called sa1100_wdt.
201 tristate "Synopsys DesignWare watchdog"
202 depends on ARM && HAVE_CLK
204 Say Y here if to include support for the Synopsys DesignWare
205 watchdog timer found in many ARM chips.
206 To compile this driver as a module, choose M here: the
207 module will be called dw_wdt.
209 config MPCORE_WATCHDOG
210 tristate "MPcore watchdog"
211 depends on HAVE_ARM_TWD
213 Watchdog timer embedded into the MPcore system.
215 To compile this driver as a module, choose M here: the
216 module will be called mpcore_wdt.
218 config EP93XX_WATCHDOG
219 tristate "EP93xx Watchdog"
220 depends on ARCH_EP93XX
222 Say Y here if to include support for the watchdog timer
223 embedded in the Cirrus Logic EP93xx family of devices.
225 To compile this driver as a module, choose M here: the
226 module will be called ep93xx_wdt.
229 tristate "OMAP Watchdog"
230 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
232 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
233 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
235 config PNX4008_WATCHDOG
236 tristate "PNX4008 and LPC32XX Watchdog"
237 depends on ARCH_PNX4008 || ARCH_LPC32XX
240 Say Y here if to include support for the watchdog timer
241 in the PNX4008 or LPC32XX processor.
242 This driver can be built as a module by choosing M. The module
243 will be called pnx4008_wdt.
245 Say N if you are unsure.
248 tristate "IOP Watchdog"
250 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
252 Say Y here if to include support for the watchdog timer
253 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
254 be built as a module by choosing M. The module will
257 Note: The IOP13XX watchdog does an Internal Bus Reset which will
258 affect both cores and the peripherals of the IOP. The ATU-X
259 and/or ATUe configuration registers will remain intact, but if
260 operating as an Root Complex and/or Central Resource, the PCI-X
261 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
263 config DAVINCI_WATCHDOG
264 tristate "DaVinci watchdog"
265 depends on ARCH_DAVINCI
267 Say Y here if to include support for the watchdog timer
268 in the DaVinci DM644x/DM646x processors.
269 To compile this driver as a module, choose M here: the
270 module will be called davinci_wdt.
272 NOTE: once enabled, this timer cannot be disabled.
273 Say N if you are unsure.
275 config ORION_WATCHDOG
276 tristate "Orion watchdog"
277 depends on ARCH_ORION5X || ARCH_KIRKWOOD
279 Say Y here if to include support for the watchdog timer
280 in the Marvell Orion5x and Kirkwood ARM SoCs.
281 To compile this driver as a module, choose M here: the
282 module will be called orion_wdt.
284 config COH901327_WATCHDOG
285 bool "ST-Ericsson COH 901 327 watchdog"
287 default y if MACH_U300
289 Say Y here to include Watchdog timer support for the
290 watchdog embedded into the ST-Ericsson U300 series platforms.
291 This watchdog is used to reset the system and thus cannot be
292 compiled as a module.
294 config TWL4030_WATCHDOG
295 tristate "TWL4030 Watchdog"
296 depends on TWL4030_CORE
298 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
299 watchdog timer support for TWL4030 chips.
301 config STMP3XXX_WATCHDOG
302 tristate "Freescale STMP3XXX watchdog"
303 depends on ARCH_STMP3XXX
305 Say Y here if to include support for the watchdog timer
306 for the Sigmatel STMP37XX/378X SoC.
307 To compile this driver as a module, choose M here: the
308 module will be called stmp3xxx_wdt.
310 config NUC900_WATCHDOG
311 tristate "Nuvoton NUC900 watchdog"
312 depends on ARCH_W90X900
314 Say Y here if to include support for the watchdog timer
315 for the Nuvoton NUC900 series SoCs.
316 To compile this driver as a module, choose M here: the
317 module will be called nuc900_wdt.
319 config TS72XX_WATCHDOG
320 tristate "TS-72XX SBC Watchdog"
321 depends on MACH_TS72XX
323 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
324 watchdog timer implemented in a external CPLD chip. Say Y here
325 if you want to support for the watchdog timer on TS-72XX boards.
327 To compile this driver as a module, choose M here: the
328 module will be called ts72xx_wdt.
330 config MAX63XX_WATCHDOG
331 tristate "Max63xx watchdog"
332 depends on ARM && HAS_IOMEM
335 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
338 tristate "IMX2+ Watchdog"
339 depends on IMX_HAVE_PLATFORM_IMX2_WDT
341 This is the driver for the hardware watchdog
342 on the Freescale IMX2 and later processors.
343 If you have one of these processors and wish to have
344 watchdog support enabled, say Y, otherwise say N.
346 To compile this driver as a module, choose M here: the
347 module will be called imx2_wdt.
351 config AT32AP700X_WDT
352 tristate "AT32AP700x watchdog"
353 depends on CPU_AT32AP700X
355 Watchdog timer embedded into AT32AP700x devices. This will reboot
356 your system when the timeout is reached.
358 # BLACKFIN Architecture
361 tristate "Blackfin On-Chip Watchdog Timer"
364 If you say yes here you will get support for the Blackfin On-Chip
365 Watchdog Timer. If you have one of these processors and wish to
366 have watchdog support enabled, say Y, otherwise say N.
368 To compile this driver as a module, choose M here: the
369 module will be called bfin_wdt.
377 # X86 (i386 + ia64 + x86_64) Architecture
380 tristate "Acquire SBC Watchdog Timer"
383 This is the driver for the hardware watchdog on Single Board
384 Computers produced by Acquire Inc (and others). This watchdog
385 simply watches your kernel to make sure it doesn't freeze, and if
386 it does, it reboots your computer after a certain amount of time.
388 To compile this driver as a module, choose M here: the
389 module will be called acquirewdt.
391 Most people will say N.
394 tristate "Advantech SBC Watchdog Timer"
397 If you are configuring a Linux kernel for the Advantech single-board
398 computer, say `Y' here to support its built-in watchdog timer
399 feature. More information can be found at
400 <http://www.advantech.com.tw/products/>
403 tristate "ALi M1535 PMU Watchdog Timer"
404 depends on X86 && PCI
406 This is the driver for the hardware watchdog on the ALi M1535 PMU.
408 To compile this driver as a module, choose M here: the
409 module will be called alim1535_wdt.
411 Most people will say N.
414 tristate "ALi M7101 PMU Computer Watchdog"
417 This is the driver for the hardware watchdog on the ALi M7101 PMU
418 as used in the x86 Cobalt servers and also found in some
419 SPARC Netra servers too.
421 To compile this driver as a module, choose M here: the
422 module will be called alim7101_wdt.
424 Most people will say N.
427 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
428 depends on X86 && EXPERIMENTAL
430 This is the driver for the hardware watchdog on the Fintek
431 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
433 You can compile this driver directly into the kernel, or use
434 it as a module. The module will be called f71808e_wdt.
437 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
438 depends on X86 && PCI
440 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
441 (Total Cost of Ownership) timer is a watchdog timer that will reboot
442 the machine after its expiration. The expiration time can be
443 configured with the "heartbeat" parameter.
445 To compile this driver as a module, choose M here: the
446 module will be called sp5100_tco.
449 tristate "AMD Geode CS5535/CS5536 Watchdog"
450 depends on CS5535_MFGPT
452 This driver enables a watchdog capability built into the
453 CS5535/CS5536 companion chips for the AMD Geode GX and LX
454 processors. This watchdog watches your kernel to make sure
455 it doesn't freeze, and if it does, it reboots your computer after
456 a certain amount of time.
458 You can compile this driver directly into the kernel, or use
459 it as a module. The module will be called geodewdt.
462 tristate "AMD Elan SC520 processor Watchdog"
465 This is the driver for the hardware watchdog built in to the
466 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
467 This watchdog simply watches your kernel to make sure it doesn't
468 freeze, and if it does, it reboots your computer after a certain
471 You can compile this driver directly into the kernel, or use
472 it as a module. The module will be called sc520_wdt.
474 config SBC_FITPC2_WATCHDOG
475 tristate "Compulab SBC-FITPC2 watchdog"
478 This is the driver for the built-in watchdog timer on the fit-PC2,
479 fit-PC2i, CM-iAM single-board computers made by Compulab.
481 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
482 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
484 Entering BIOS setup temporary disables watchdog operation regardless to current state,
485 so system will not be restarted while user in BIOS setup.
487 Once watchdog was enabled the system will be restarted every
488 "Watchdog Timer Value" period, so to prevent it user can restart or
489 disable the watchdog.
491 To compile this driver as a module, choose M here: the
492 module will be called sbc_fitpc2_wdt.
494 Most people will say N.
497 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
500 Enable support for the watchdog timer on the Eurotech CPU-1220 and
501 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
502 information are at <http://www.eurotech.it/>.
505 tristate "IB700 SBC Watchdog Timer"
508 This is the driver for the hardware watchdog on the IB700 Single
509 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
510 simply watches your kernel to make sure it doesn't freeze, and if
511 it does, it reboots your computer after a certain amount of time.
513 This driver is like the WDT501 driver but for slightly different hardware.
515 To compile this driver as a module, choose M here: the
516 module will be called ib700wdt.
518 Most people will say N.
521 tristate "IBM Automatic Server Restart"
524 This is the driver for the IBM Automatic Server Restart watchdog
525 timer built-in into some eServer xSeries machines.
527 To compile this driver as a module, choose M here: the
528 module will be called ibmasr.
531 tristate "ICP Single Board Computer Watchdog Timer"
534 This is a driver for the hardware watchdog on the ICP Single
535 Board Computer. This driver is working on (at least) the following
536 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
538 To compile this driver as a module, choose M here: the
539 module will be called wafer5823wdt.
542 tristate "Intel 6300ESB Timer/Watchdog"
543 depends on X86 && PCI
545 Hardware driver for the watchdog timer built into the Intel
546 6300ESB controller hub.
548 To compile this driver as a module, choose M here: the
549 module will be called i6300esb.
551 config INTEL_SCU_WATCHDOG
552 bool "Intel SCU Watchdog for Mobile Platforms"
555 Hardware driver for the watchdog time built into the Intel SCU
556 for Intel Mobile Platforms.
558 To compile this driver as a module, choose M here.
561 tristate "Intel TCO Timer/Watchdog"
562 depends on (X86 || IA64) && PCI
564 Hardware driver for the intel TCO timer based watchdog devices.
565 These drivers are included in the Intel 82801 I/O Controller
566 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
569 The TCO (Total Cost of Ownership) timer is a watchdog timer
570 that will reboot the machine after its second expiration. The
571 expiration time can be configured with the "heartbeat" parameter.
573 On some motherboards the driver may fail to reset the chipset's
574 NO_REBOOT flag which prevents the watchdog from rebooting the
575 machine. If this is the case you will get a kernel message like
576 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
578 To compile this driver as a module, choose M here: the
579 module will be called iTCO_wdt.
581 config ITCO_VENDOR_SUPPORT
582 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
585 Add vendor specific support to the intel TCO timer based watchdog
586 devices. At this moment we only have additional support for some
587 SuperMicro Inc. motherboards.
590 tristate "IT8712F (Smart Guardian) Watchdog Timer"
593 This is the driver for the built-in watchdog timer on the IT8712F
594 Super I/0 chipset used on many motherboards.
596 If the driver does not work, then make sure that the game port in
599 To compile this driver as a module, choose M here: the
600 module will be called it8712f_wdt.
603 tristate "IT87 Watchdog Timer"
604 depends on X86 && EXPERIMENTAL
606 This is the driver for the hardware watchdog on the ITE IT8702,
607 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
608 This watchdog simply watches your kernel to make sure it doesn't
609 freeze, and if it does, it reboots your computer after a certain
612 To compile this driver as a module, choose M here: the module will
616 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
617 depends on X86 && PCI
619 A software monitoring watchdog and NMI sourcing driver. This driver
620 will detect lockups and provide a stack trace. This is a driver that
621 will only load on an HP ProLiant system with a minimum of iLO2 support.
622 To compile this driver as a module, choose M here: the module will be
625 config HPWDT_NMI_DECODING
626 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
627 depends on HP_WATCHDOG
630 When an NMI occurs this feature will make the necessary BIOS calls to
631 log the cause of the NMI.
634 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
637 This is a driver for National Semiconductor PC87307/PC97307 hardware
638 watchdog cards as found on the SC1200. This watchdog is mainly used
639 for power management purposes and can be used to power down the device
640 during inactivity periods (includes interrupt activity monitoring).
642 To compile this driver as a module, choose M here: the
643 module will be called sc1200wdt.
645 Most people will say N.
648 tristate "National Semiconductor SCx200 Watchdog"
649 depends on SCx200 && PCI
651 Enable the built-in watchdog timer support on the National
652 Semiconductor SCx200 processors.
654 If compiled as a module, it will be called scx200_wdt.
657 tristate "NS PC87413 watchdog"
660 This is the driver for the hardware watchdog on the PC87413 chipset
661 This watchdog simply watches your kernel to make sure it doesn't
662 freeze, and if it does, it reboots your computer after a certain
665 To compile this driver as a module, choose M here: the
666 module will be called pc87413_wdt.
668 Most people will say N.
671 tristate "nVidia TCO Timer/Watchdog"
672 depends on X86 && PCI
674 Hardware driver for the TCO timer built into the nVidia Hub family
675 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
676 watchdog timer that will reboot the machine after its second
677 expiration. The expiration time can be configured with the
678 "heartbeat" parameter.
680 On some motherboards the driver may fail to reset the chipset's
681 NO_REBOOT flag which prevents the watchdog from rebooting the
682 machine. If this is the case you will get a kernel message like
683 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
685 To compile this driver as a module, choose M here: the
686 module will be called nv_tco.
689 tristate "RDC R-321x SoC watchdog"
690 depends on X86_RDC321X
692 This is the driver for the built in hardware watchdog
693 in the RDC R-321x SoC.
695 To compile this driver as a module, choose M here: the
696 module will be called rdc321x_wdt.
699 tristate "SBC-60XX Watchdog Timer"
702 This driver can be used with the watchdog timer found on some
703 single board computers, namely the 6010 PII based computer.
704 It may well work with other cards. It reads port 0x443 to enable
705 and re-set the watchdog timer, and reads port 0x45 to disable
706 the watchdog. If you have a card that behave in similar ways,
707 you can probably make this driver work with your card as well.
709 You can compile this driver directly into the kernel, or use
710 it as a module. The module will be called sbc60xxwdt.
713 tristate "SBC8360 Watchdog Timer"
717 This is the driver for the hardware watchdog on the SBC8360 Single
718 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
720 To compile this driver as a module, choose M here: the
721 module will be called sbc8360.
723 Most people will say N.
726 tristate "SBC Nano 7240 Watchdog Timer"
727 depends on X86_32 && !UML
729 This is the driver for the hardware watchdog found on the IEI
730 single board computers EPIC Nano 7240 (and likely others). This
731 watchdog simply watches your kernel to make sure it doesn't freeze,
732 and if it does, it reboots your computer after a certain amount of
735 To compile this driver as a module, choose M here: the
736 module will be called sbc7240_wdt.
739 tristate "SMA CPU5 Watchdog"
743 To compile this driver as a module, choose M here: the
744 module will be called cpu5wdt.
746 config SMSC_SCH311X_WDT
747 tristate "SMSC SCH311X Watchdog Timer"
750 This is the driver for the hardware watchdog timer on the
751 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
752 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
755 To compile this driver as a module, choose M here: the
756 module will be called sch311x_wdt.
758 config SMSC37B787_WDT
759 tristate "Winbond SMsC37B787 Watchdog Timer"
762 This is the driver for the hardware watchdog component on the
763 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
764 from Vision Systems and maybe others.
766 This watchdog simply watches your kernel to make sure it doesn't
767 freeze, and if it does, it reboots your computer after a certain
770 Usually a userspace daemon will notify the kernel WDT driver that
771 userspace is still alive, at regular intervals.
773 To compile this driver as a module, choose M here: the
774 module will be called smsc37b787_wdt.
776 Most people will say N.
779 tristate "VIA Watchdog Timer"
783 This is the driver for the hardware watchdog timer on VIA
784 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
786 To compile this driver as a module, choose M here; the module
787 will be called via_wdt.
789 Most people will say N.
792 tristate "W83627HF/W83627DHG Watchdog Timer"
795 This is the driver for the hardware watchdog on the W83627HF chipset
796 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
797 (and likely others). The driver also supports the W83627DHG chip.
798 This watchdog simply watches your kernel to make sure it doesn't
799 freeze, and if it does, it reboots your computer after a certain
802 To compile this driver as a module, choose M here: the
803 module will be called w83627hf_wdt.
805 Most people will say N.
808 tristate "W83697HF/W83697HG Watchdog Timer"
811 This is the driver for the hardware watchdog on the W83697HF/HG
812 chipset as used in Dedibox/VIA motherboards (and likely others).
813 This watchdog simply watches your kernel to make sure it doesn't
814 freeze, and if it does, it reboots your computer after a certain
817 To compile this driver as a module, choose M here: the
818 module will be called w83697hf_wdt.
820 Most people will say N.
823 tristate "W83697UG/W83697UF Watchdog Timer"
826 This is the driver for the hardware watchdog on the W83697UG/UF
827 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
828 This watchdog simply watches your kernel to make sure it doesn't
829 freeze, and if it does, it reboots your computer after a certain
832 To compile this driver as a module, choose M here: the
833 module will be called w83697ug_wdt.
835 Most people will say N.
838 tristate "W83877F (EMACS) Watchdog Timer"
841 This is the driver for the hardware watchdog on the W83877F chipset
842 as used in EMACS PC-104 motherboards (and likely others). This
843 watchdog simply watches your kernel to make sure it doesn't freeze,
844 and if it does, it reboots your computer after a certain amount of
847 To compile this driver as a module, choose M here: the
848 module will be called w83877f_wdt.
850 Most people will say N.
853 tristate "W83977F (PCM-5335) Watchdog Timer"
856 This is the driver for the hardware watchdog on the W83977F I/O chip
857 as used in AAEON's PCM-5335 SBC (and likely others). This
858 watchdog simply watches your kernel to make sure it doesn't freeze,
859 and if it does, it reboots your computer after a certain amount of
862 To compile this driver as a module, choose M here: the
863 module will be called w83977f_wdt.
866 tristate "ZF MachZ Watchdog"
869 If you are using a ZF Micro MachZ processor, say Y here, otherwise
870 N. This is the driver for the watchdog timer built-in on that
871 processor using ZF-Logic interface. This watchdog simply watches
872 your kernel to make sure it doesn't freeze, and if it does, it
873 reboots your computer after a certain amount of time.
875 To compile this driver as a module, choose M here: the
876 module will be called machzwd.
878 config SBC_EPX_C3_WATCHDOG
879 tristate "Winsystems SBC EPX-C3 watchdog"
882 This is the driver for the built-in watchdog timer on the EPX-C3
883 Single-board computer made by Winsystems, Inc.
885 *Note*: This hardware watchdog is not probeable and thus there
886 is no way to know if writing to its IO address will corrupt
887 your system or have any real effect. The only way to be sure
888 that this driver does what you want is to make sure you
889 are running it on an EPX-C3 from Winsystems with the watchdog
890 timer at IO address 0x1ee and 0x1ef. It will write to both those
891 IO ports. Basically, the assumption is made that if you compile
892 this driver into your kernel and/or load it as a module, that you
893 know what you are doing and that you are in fact running on an
896 To compile this driver as a module, choose M here: the
897 module will be called sbc_epx_c3.
903 config M54xx_WATCHDOG
904 tristate "MCF54xx watchdog support"
907 To compile this driver as a module, choose M here: the
908 module will be called m54xx_wdt.
910 # MicroBlaze Architecture
912 config XILINX_WATCHDOG
913 tristate "Xilinx Watchdog timer"
914 depends on MICROBLAZE
916 Watchdog driver for the xps_timebase_wdt ip core.
918 IMPORTANT: The xps_timebase_wdt parent must have the property
919 "clock-frequency" at device tree.
921 To compile this driver as a module, choose M here: the
922 module will be called of_xilinx_wdt.
927 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
930 Hardware driver for the built-in watchdog timer on the Atheros
931 AR71XX/AR724X/AR913X SoCs.
934 tristate "Broadcom BCM47xx Watchdog Timer"
937 Hardware driver for the Broadcom BCM47xx Watchog Timer.
940 tristate "IDT RC32434 SoC Watchdog Timer"
941 depends on MIKROTIK_RB532
943 Hardware driver for the IDT RC32434 SoC built-in
946 To compile this driver as a module, choose M here: the
947 module will be called rc32434_wdt.
950 tristate "Indy/I2 Hardware Watchdog"
951 depends on SGI_HAS_INDYDOG
953 Hardware driver for the Indy's/I2's watchdog. This is a
954 watchdog timer that will reboot the machine after a 60 second
955 timer expired and no process has written to /dev/watchdog during
959 tristate "Ingenic jz4740 SoC hardware watchdog"
960 depends on MACH_JZ4740
963 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
966 tristate "MTX-1 Hardware Watchdog"
969 Hardware driver for the MTX-1 boards. This is a watchdog timer that
970 will reboot the machine after a 100 seconds timer expired.
973 tristate "PNX833x Hardware Watchdog"
974 depends on SOC_PNX8335
976 Hardware driver for the PNX833x's watchdog. This is a
977 watchdog timer that will reboot the machine after a programmable
978 timer has expired and no process has written to /dev/watchdog during
982 tristate "Sibyte SoC hardware watchdog"
985 Watchdog driver for the built in watchdog hardware in Sibyte
986 SoC processors. There are apparently two watchdog timers
987 on such processors; this driver supports only the first one,
988 because currently Linux only supports exporting one watchdog
991 To compile this driver as a loadable module, choose M here.
992 The module will be called sb_wdog.
995 tristate "TI AR7 Watchdog Timer"
998 Hardware driver for the TI AR7 Watchdog Timer.
1001 tristate "Toshiba TXx9 Watchdog Timer"
1002 depends on CPU_TX39XX || CPU_TX49XX
1004 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1007 tristate "Cavium OCTEON SOC family Watchdog Timer"
1008 depends on CPU_CAVIUM_OCTEON
1010 select EXPORT_UASM if OCTEON_WDT = m
1012 Hardware driver for OCTEON's on chip watchdog timer.
1013 Enables the watchdog for all cores running Linux. It
1014 installs a NMI handler and pokes the watchdog based on an
1015 interrupt. On first expiration of the watchdog, the
1016 interrupt handler pokes it. The second expiration causes an
1017 NMI that prints a message. The third expiration causes a
1020 When userspace has /dev/watchdog open, no poking is done
1021 from the first interrupt, it is then only poked when the
1025 tristate "Broadcom BCM63xx hardware watchdog"
1028 Watchdog driver for the built in watchdog hardware in Broadcom
1031 To compile this driver as a loadable module, choose M here.
1032 The module will be called bcm63xx_wdt.
1035 tristate "Lantiq SoC watchdog"
1038 Hardware driver for the Lantiq SoC Watchdog Timer.
1040 # PARISC Architecture
1042 # POWERPC Architecture
1045 tristate "GE Watchdog Timer"
1048 Watchdog timer found in a number of GE single board computers.
1051 bool "MPC52xx Watchdog Timer"
1052 depends on PPC_MPC52xx
1054 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1057 tristate "MPC8xxx Platform Watchdog Timer"
1058 depends on PPC_8xx || PPC_83xx || PPC_86xx
1060 This driver is for a SoC level watchdog that exists on some
1061 Freescale PowerPC processors. So far this driver supports:
1066 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1069 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1073 tristate "PIKA FPGA Watchdog"
1077 This enables the watchdog in the PIKA FPGA. Currently used on
1081 tristate "PowerPC Book-E Watchdog Timer"
1082 depends on BOOKE || 4xx
1084 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1085 MPC85xx SOCs and the IBM PowerPC 440.
1087 Please see Documentation/watchdog/watchdog-api.txt for
1090 config BOOKE_WDT_DEFAULT_TIMEOUT
1091 int "PowerPC Book-E Watchdog Timer Default Timeout"
1092 depends on BOOKE_WDT
1093 default 38 if FSL_BOOKE
1094 range 0 63 if FSL_BOOKE
1095 default 3 if !FSL_BOOKE
1096 range 0 3 if !FSL_BOOKE
1098 Select the default watchdog timer period to be used by the PowerPC
1099 Book-E watchdog driver. A watchdog "event" occurs when the bit
1100 position represented by this number transitions from zero to one.
1102 For Freescale Book-E processors, this is a number between 0 and 63.
1103 For other Book-E processors, this is a number between 0 and 3.
1105 The value can be overridden by the wdt_period command-line parameter.
1107 # PPC64 Architecture
1109 config WATCHDOG_RTAS
1110 tristate "RTAS watchdog"
1113 This driver adds watchdog support for the RTAS watchdog.
1115 To compile this driver as a module, choose M here. The module
1116 will be called wdrtas.
1121 tristate "z/VM Watchdog Timer"
1124 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1125 provide a virtual watchdog timer to their guest that cause a
1126 user define Control Program command to be executed after a
1129 To compile this driver as a module, choose M here. The module
1130 will be called vmwatchdog.
1132 # SUPERH (sh + sh64) Architecture
1135 tristate "SuperH Watchdog"
1136 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1138 This driver adds watchdog support for the integrated watchdog in the
1139 SuperH processors. If you have one of these processors and wish
1140 to have watchdog support enabled, say Y, otherwise say N.
1142 As a side note, saying Y here will automatically boost HZ to 1000
1143 so that the timer has a chance to clear the overflow counter. On
1144 slower systems (such as the SH-2 and SH-3) this will likely yield
1145 some performance issues. As such, the WDT should be avoided here
1146 unless it is absolutely necessary.
1148 To compile this driver as a module, choose M here: the
1149 module will be called shwdt.
1151 # SPARC Architecture
1153 # SPARC64 Architecture
1155 config WATCHDOG_CP1XXX
1156 tristate "CP1XXX Hardware Watchdog support"
1157 depends on SPARC64 && PCI
1159 This is the driver for the hardware watchdog timers present on
1160 Sun Microsystems CompactPCI models CP1400 and CP1500.
1162 To compile this driver as a module, choose M here: the
1163 module will be called cpwatchdog.
1165 If you do not have a CompactPCI model CP1400 or CP1500, or
1166 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1167 you should say N to this option.
1170 tristate "RIO Hardware Watchdog support"
1171 depends on SPARC64 && PCI
1173 Say Y here to support the hardware watchdog capability on Sun RIO
1174 machines. The watchdog timeout period is normally one minute but
1175 can be changed with a boot-time parameter.
1177 # XTENSA Architecture
1182 tristate "Xen Watchdog support"
1185 Say Y here to support the hypervisor watchdog capability provided
1186 by Xen 4.0 and newer. The watchdog timeout period is normally one
1187 minute but can be changed with a boot-time parameter.
1190 tristate "UML watchdog"
1194 # ISA-based Watchdog Cards
1197 comment "ISA-based Watchdog Cards"
1201 tristate "Berkshire Products ISA-PC Watchdog"
1204 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1205 This card simply watches your kernel to make sure it doesn't freeze,
1206 and if it does, it reboots your computer after a certain amount of
1207 time. This driver is like the WDT501 driver but for different
1208 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1209 watchdog cards can be ordered from <http://www.berkprod.com/>.
1211 To compile this driver as a module, choose M here: the
1212 module will be called pcwd.
1214 Most people will say N.
1217 tristate "Mixcom Watchdog"
1220 This is a driver for the Mixcom hardware watchdog cards. This
1221 watchdog simply watches your kernel to make sure it doesn't freeze,
1222 and if it does, it reboots your computer after a certain amount of
1225 To compile this driver as a module, choose M here: the
1226 module will be called mixcomwd.
1228 Most people will say N.
1231 tristate "WDT Watchdog timer"
1234 If you have a WDT500P or WDT501P watchdog board, say Y here,
1235 otherwise N. It is not possible to probe for this board, which means
1236 that you have to inform the kernel about the IO port and IRQ that
1237 is needed (you can do this via the io and irq parameters)
1239 To compile this driver as a module, choose M here: the
1240 module will be called wdt.
1243 # PCI-based Watchdog Cards
1246 comment "PCI-based Watchdog Cards"
1249 config PCIPCWATCHDOG
1250 tristate "Berkshire Products PCI-PC Watchdog"
1253 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1254 This card simply watches your kernel to make sure it doesn't freeze,
1255 and if it does, it reboots your computer after a certain amount of
1256 time. The card can also monitor the internal temperature of the PC.
1257 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1259 To compile this driver as a module, choose M here: the
1260 module will be called pcwd_pci.
1262 Most people will say N.
1265 tristate "PCI-WDT500/501 Watchdog timer"
1268 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1270 If you have a PCI-WDT501 watchdog board then you can enable the
1271 temperature sensor by setting the type parameter to 501.
1273 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1274 can do this via the tachometer parameter. Only do this if you have a
1275 fan tachometer actually set up.
1277 To compile this driver as a module, choose M here: the
1278 module will be called wdt_pci.
1281 # USB-based Watchdog Cards
1284 comment "USB-based Watchdog Cards"
1287 config USBPCWATCHDOG
1288 tristate "Berkshire Products USB-PC Watchdog"
1291 This is the driver for the Berkshire Products USB-PC Watchdog card.
1292 This card simply watches your kernel to make sure it doesn't freeze,
1293 and if it does, it reboots your computer after a certain amount of
1294 time. The card can also monitor the internal temperature of the PC.
1295 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1297 To compile this driver as a module, choose M here: the
1298 module will be called pcwd_usb.
1300 Most people will say N.