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
334 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
337 tristate "IMX2+ Watchdog"
338 depends on IMX_HAVE_PLATFORM_IMX2_WDT
340 This is the driver for the hardware watchdog
341 on the Freescale IMX2 and later processors.
342 If you have one of these processors and wish to have
343 watchdog support enabled, say Y, otherwise say N.
345 To compile this driver as a module, choose M here: the
346 module will be called imx2_wdt.
350 config AT32AP700X_WDT
351 tristate "AT32AP700x watchdog"
352 depends on CPU_AT32AP700X
354 Watchdog timer embedded into AT32AP700x devices. This will reboot
355 your system when the timeout is reached.
357 # BLACKFIN Architecture
360 tristate "Blackfin On-Chip Watchdog Timer"
363 If you say yes here you will get support for the Blackfin On-Chip
364 Watchdog Timer. If you have one of these processors and wish to
365 have watchdog support enabled, say Y, otherwise say N.
367 To compile this driver as a module, choose M here: the
368 module will be called bfin_wdt.
376 # X86 (i386 + ia64 + x86_64) Architecture
379 tristate "Acquire SBC Watchdog Timer"
382 This is the driver for the hardware watchdog on Single Board
383 Computers produced by Acquire Inc (and others). This watchdog
384 simply watches your kernel to make sure it doesn't freeze, and if
385 it does, it reboots your computer after a certain amount of time.
387 To compile this driver as a module, choose M here: the
388 module will be called acquirewdt.
390 Most people will say N.
393 tristate "Advantech SBC Watchdog Timer"
396 If you are configuring a Linux kernel for the Advantech single-board
397 computer, say `Y' here to support its built-in watchdog timer
398 feature. More information can be found at
399 <http://www.advantech.com.tw/products/>
402 tristate "ALi M1535 PMU Watchdog Timer"
403 depends on X86 && PCI
405 This is the driver for the hardware watchdog on the ALi M1535 PMU.
407 To compile this driver as a module, choose M here: the
408 module will be called alim1535_wdt.
410 Most people will say N.
413 tristate "ALi M7101 PMU Computer Watchdog"
416 This is the driver for the hardware watchdog on the ALi M7101 PMU
417 as used in the x86 Cobalt servers and also found in some
418 SPARC Netra servers too.
420 To compile this driver as a module, choose M here: the
421 module will be called alim7101_wdt.
423 Most people will say N.
426 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
427 depends on X86 && EXPERIMENTAL
429 This is the driver for the hardware watchdog on the Fintek
430 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
432 You can compile this driver directly into the kernel, or use
433 it as a module. The module will be called f71808e_wdt.
436 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
437 depends on X86 && PCI
439 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
440 (Total Cost of Ownership) timer is a watchdog timer that will reboot
441 the machine after its expiration. The expiration time can be
442 configured with the "heartbeat" parameter.
444 To compile this driver as a module, choose M here: the
445 module will be called sp5100_tco.
448 tristate "AMD Geode CS5535/CS5536 Watchdog"
449 depends on CS5535_MFGPT
451 This driver enables a watchdog capability built into the
452 CS5535/CS5536 companion chips for the AMD Geode GX and LX
453 processors. This watchdog watches your kernel to make sure
454 it doesn't freeze, and if it does, it reboots your computer after
455 a certain amount of time.
457 You can compile this driver directly into the kernel, or use
458 it as a module. The module will be called geodewdt.
461 tristate "AMD Elan SC520 processor Watchdog"
464 This is the driver for the hardware watchdog built in to the
465 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
466 This watchdog simply watches your kernel to make sure it doesn't
467 freeze, and if it does, it reboots your computer after a certain
470 You can compile this driver directly into the kernel, or use
471 it as a module. The module will be called sc520_wdt.
473 config SBC_FITPC2_WATCHDOG
474 tristate "Compulab SBC-FITPC2 watchdog"
477 This is the driver for the built-in watchdog timer on the fit-PC2,
478 fit-PC2i, CM-iAM single-board computers made by Compulab.
480 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
481 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
483 Entering BIOS setup temporary disables watchdog operation regardless to current state,
484 so system will not be restarted while user in BIOS setup.
486 Once watchdog was enabled the system will be restarted every
487 "Watchdog Timer Value" period, so to prevent it user can restart or
488 disable the watchdog.
490 To compile this driver as a module, choose M here: the
491 module will be called sbc_fitpc2_wdt.
493 Most people will say N.
496 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
499 Enable support for the watchdog timer on the Eurotech CPU-1220 and
500 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
501 information are at <http://www.eurotech.it/>.
504 tristate "IB700 SBC Watchdog Timer"
507 This is the driver for the hardware watchdog on the IB700 Single
508 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
509 simply watches your kernel to make sure it doesn't freeze, and if
510 it does, it reboots your computer after a certain amount of time.
512 This driver is like the WDT501 driver but for slightly different hardware.
514 To compile this driver as a module, choose M here: the
515 module will be called ib700wdt.
517 Most people will say N.
520 tristate "IBM Automatic Server Restart"
523 This is the driver for the IBM Automatic Server Restart watchdog
524 timer built-in into some eServer xSeries machines.
526 To compile this driver as a module, choose M here: the
527 module will be called ibmasr.
530 tristate "ICP Single Board Computer Watchdog Timer"
533 This is a driver for the hardware watchdog on the ICP Single
534 Board Computer. This driver is working on (at least) the following
535 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
537 To compile this driver as a module, choose M here: the
538 module will be called wafer5823wdt.
541 tristate "Intel 6300ESB Timer/Watchdog"
542 depends on X86 && PCI
544 Hardware driver for the watchdog timer built into the Intel
545 6300ESB controller hub.
547 To compile this driver as a module, choose M here: the
548 module will be called i6300esb.
550 config INTEL_SCU_WATCHDOG
551 bool "Intel SCU Watchdog for Mobile Platforms"
554 Hardware driver for the watchdog time built into the Intel SCU
555 for Intel Mobile Platforms.
557 To compile this driver as a module, choose M here.
560 tristate "Intel TCO Timer/Watchdog"
561 depends on (X86 || IA64) && PCI
563 Hardware driver for the intel TCO timer based watchdog devices.
564 These drivers are included in the Intel 82801 I/O Controller
565 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
568 The TCO (Total Cost of Ownership) timer is a watchdog timer
569 that will reboot the machine after its second expiration. The
570 expiration time can be configured with the "heartbeat" parameter.
572 On some motherboards the driver may fail to reset the chipset's
573 NO_REBOOT flag which prevents the watchdog from rebooting the
574 machine. If this is the case you will get a kernel message like
575 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
577 To compile this driver as a module, choose M here: the
578 module will be called iTCO_wdt.
580 config ITCO_VENDOR_SUPPORT
581 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
584 Add vendor specific support to the intel TCO timer based watchdog
585 devices. At this moment we only have additional support for some
586 SuperMicro Inc. motherboards.
589 tristate "IT8712F (Smart Guardian) Watchdog Timer"
592 This is the driver for the built-in watchdog timer on the IT8712F
593 Super I/0 chipset used on many motherboards.
595 If the driver does not work, then make sure that the game port in
598 To compile this driver as a module, choose M here: the
599 module will be called it8712f_wdt.
602 tristate "IT87 Watchdog Timer"
603 depends on X86 && EXPERIMENTAL
605 This is the driver for the hardware watchdog on the ITE IT8702,
606 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
607 This watchdog simply watches your kernel to make sure it doesn't
608 freeze, and if it does, it reboots your computer after a certain
611 To compile this driver as a module, choose M here: the module will
615 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
616 depends on X86 && PCI
618 A software monitoring watchdog and NMI sourcing driver. This driver
619 will detect lockups and provide a stack trace. This is a driver that
620 will only load on an HP ProLiant system with a minimum of iLO2 support.
621 To compile this driver as a module, choose M here: the module will be
624 config HPWDT_NMI_DECODING
625 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
626 depends on HP_WATCHDOG
629 When an NMI occurs this feature will make the necessary BIOS calls to
630 log the cause of the NMI.
633 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
636 This is a driver for National Semiconductor PC87307/PC97307 hardware
637 watchdog cards as found on the SC1200. This watchdog is mainly used
638 for power management purposes and can be used to power down the device
639 during inactivity periods (includes interrupt activity monitoring).
641 To compile this driver as a module, choose M here: the
642 module will be called sc1200wdt.
644 Most people will say N.
647 tristate "National Semiconductor SCx200 Watchdog"
648 depends on SCx200 && PCI
650 Enable the built-in watchdog timer support on the National
651 Semiconductor SCx200 processors.
653 If compiled as a module, it will be called scx200_wdt.
656 tristate "NS PC87413 watchdog"
659 This is the driver for the hardware watchdog on the PC87413 chipset
660 This watchdog simply watches your kernel to make sure it doesn't
661 freeze, and if it does, it reboots your computer after a certain
664 To compile this driver as a module, choose M here: the
665 module will be called pc87413_wdt.
667 Most people will say N.
670 tristate "nVidia TCO Timer/Watchdog"
671 depends on X86 && PCI
673 Hardware driver for the TCO timer built into the nVidia Hub family
674 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
675 watchdog timer that will reboot the machine after its second
676 expiration. The expiration time can be configured with the
677 "heartbeat" parameter.
679 On some motherboards the driver may fail to reset the chipset's
680 NO_REBOOT flag which prevents the watchdog from rebooting the
681 machine. If this is the case you will get a kernel message like
682 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
684 To compile this driver as a module, choose M here: the
685 module will be called nv_tco.
688 tristate "RDC R-321x SoC watchdog"
689 depends on X86_RDC321X
691 This is the driver for the built in hardware watchdog
692 in the RDC R-321x SoC.
694 To compile this driver as a module, choose M here: the
695 module will be called rdc321x_wdt.
698 tristate "SBC-60XX Watchdog Timer"
701 This driver can be used with the watchdog timer found on some
702 single board computers, namely the 6010 PII based computer.
703 It may well work with other cards. It reads port 0x443 to enable
704 and re-set the watchdog timer, and reads port 0x45 to disable
705 the watchdog. If you have a card that behave in similar ways,
706 you can probably make this driver work with your card as well.
708 You can compile this driver directly into the kernel, or use
709 it as a module. The module will be called sbc60xxwdt.
712 tristate "SBC8360 Watchdog Timer"
716 This is the driver for the hardware watchdog on the SBC8360 Single
717 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
719 To compile this driver as a module, choose M here: the
720 module will be called sbc8360.
722 Most people will say N.
725 tristate "SBC Nano 7240 Watchdog Timer"
726 depends on X86_32 && !UML
728 This is the driver for the hardware watchdog found on the IEI
729 single board computers EPIC Nano 7240 (and likely others). This
730 watchdog simply watches your kernel to make sure it doesn't freeze,
731 and if it does, it reboots your computer after a certain amount of
734 To compile this driver as a module, choose M here: the
735 module will be called sbc7240_wdt.
738 tristate "SMA CPU5 Watchdog"
742 To compile this driver as a module, choose M here: the
743 module will be called cpu5wdt.
745 config SMSC_SCH311X_WDT
746 tristate "SMSC SCH311X Watchdog Timer"
749 This is the driver for the hardware watchdog timer on the
750 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
751 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
754 To compile this driver as a module, choose M here: the
755 module will be called sch311x_wdt.
757 config SMSC37B787_WDT
758 tristate "Winbond SMsC37B787 Watchdog Timer"
761 This is the driver for the hardware watchdog component on the
762 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
763 from Vision Systems and maybe others.
765 This watchdog simply watches your kernel to make sure it doesn't
766 freeze, and if it does, it reboots your computer after a certain
769 Usually a userspace daemon will notify the kernel WDT driver that
770 userspace is still alive, at regular intervals.
772 To compile this driver as a module, choose M here: the
773 module will be called smsc37b787_wdt.
775 Most people will say N.
778 tristate "VIA Watchdog Timer"
782 This is the driver for the hardware watchdog timer on VIA
783 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
785 To compile this driver as a module, choose M here; the module
786 will be called via_wdt.
788 Most people will say N.
791 tristate "W83627HF/W83627DHG Watchdog Timer"
794 This is the driver for the hardware watchdog on the W83627HF chipset
795 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
796 (and likely others). The driver also supports the W83627DHG chip.
797 This watchdog simply watches your kernel to make sure it doesn't
798 freeze, and if it does, it reboots your computer after a certain
801 To compile this driver as a module, choose M here: the
802 module will be called w83627hf_wdt.
804 Most people will say N.
807 tristate "W83697HF/W83697HG Watchdog Timer"
810 This is the driver for the hardware watchdog on the W83697HF/HG
811 chipset as used in Dedibox/VIA motherboards (and likely others).
812 This watchdog simply watches your kernel to make sure it doesn't
813 freeze, and if it does, it reboots your computer after a certain
816 To compile this driver as a module, choose M here: the
817 module will be called w83697hf_wdt.
819 Most people will say N.
822 tristate "W83697UG/W83697UF Watchdog Timer"
825 This is the driver for the hardware watchdog on the W83697UG/UF
826 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
827 This watchdog simply watches your kernel to make sure it doesn't
828 freeze, and if it does, it reboots your computer after a certain
831 To compile this driver as a module, choose M here: the
832 module will be called w83697ug_wdt.
834 Most people will say N.
837 tristate "W83877F (EMACS) Watchdog Timer"
840 This is the driver for the hardware watchdog on the W83877F chipset
841 as used in EMACS PC-104 motherboards (and likely others). This
842 watchdog simply watches your kernel to make sure it doesn't freeze,
843 and if it does, it reboots your computer after a certain amount of
846 To compile this driver as a module, choose M here: the
847 module will be called w83877f_wdt.
849 Most people will say N.
852 tristate "W83977F (PCM-5335) Watchdog Timer"
855 This is the driver for the hardware watchdog on the W83977F I/O chip
856 as used in AAEON's PCM-5335 SBC (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 w83977f_wdt.
865 tristate "ZF MachZ Watchdog"
868 If you are using a ZF Micro MachZ processor, say Y here, otherwise
869 N. This is the driver for the watchdog timer built-in on that
870 processor using ZF-Logic interface. This watchdog simply watches
871 your kernel to make sure it doesn't freeze, and if it does, it
872 reboots your computer after a certain amount of time.
874 To compile this driver as a module, choose M here: the
875 module will be called machzwd.
877 config SBC_EPX_C3_WATCHDOG
878 tristate "Winsystems SBC EPX-C3 watchdog"
881 This is the driver for the built-in watchdog timer on the EPX-C3
882 Single-board computer made by Winsystems, Inc.
884 *Note*: This hardware watchdog is not probeable and thus there
885 is no way to know if writing to its IO address will corrupt
886 your system or have any real effect. The only way to be sure
887 that this driver does what you want is to make sure you
888 are running it on an EPX-C3 from Winsystems with the watchdog
889 timer at IO address 0x1ee and 0x1ef. It will write to both those
890 IO ports. Basically, the assumption is made that if you compile
891 this driver into your kernel and/or load it as a module, that you
892 know what you are doing and that you are in fact running on an
895 To compile this driver as a module, choose M here: the
896 module will be called sbc_epx_c3.
902 config M54xx_WATCHDOG
903 tristate "MCF54xx watchdog support"
906 To compile this driver as a module, choose M here: the
907 module will be called m54xx_wdt.
909 # MicroBlaze Architecture
911 config XILINX_WATCHDOG
912 tristate "Xilinx Watchdog timer"
913 depends on MICROBLAZE
915 Watchdog driver for the xps_timebase_wdt ip core.
917 IMPORTANT: The xps_timebase_wdt parent must have the property
918 "clock-frequency" at device tree.
920 To compile this driver as a module, choose M here: the
921 module will be called of_xilinx_wdt.
926 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
929 Hardware driver for the built-in watchdog timer on the Atheros
930 AR71XX/AR724X/AR913X SoCs.
933 tristate "Broadcom BCM47xx Watchdog Timer"
936 Hardware driver for the Broadcom BCM47xx Watchog Timer.
939 tristate "IDT RC32434 SoC Watchdog Timer"
940 depends on MIKROTIK_RB532
942 Hardware driver for the IDT RC32434 SoC built-in
945 To compile this driver as a module, choose M here: the
946 module will be called rc32434_wdt.
949 tristate "Indy/I2 Hardware Watchdog"
950 depends on SGI_HAS_INDYDOG
952 Hardware driver for the Indy's/I2's watchdog. This is a
953 watchdog timer that will reboot the machine after a 60 second
954 timer expired and no process has written to /dev/watchdog during
958 tristate "Ingenic jz4740 SoC hardware watchdog"
959 depends on MACH_JZ4740
962 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
965 tristate "MTX-1 Hardware Watchdog"
968 Hardware driver for the MTX-1 boards. This is a watchdog timer that
969 will reboot the machine after a 100 seconds timer expired.
972 tristate "PNX833x Hardware Watchdog"
973 depends on SOC_PNX8335
975 Hardware driver for the PNX833x's watchdog. This is a
976 watchdog timer that will reboot the machine after a programmable
977 timer has expired and no process has written to /dev/watchdog during
981 tristate "Sibyte SoC hardware watchdog"
984 Watchdog driver for the built in watchdog hardware in Sibyte
985 SoC processors. There are apparently two watchdog timers
986 on such processors; this driver supports only the first one,
987 because currently Linux only supports exporting one watchdog
990 To compile this driver as a loadable module, choose M here.
991 The module will be called sb_wdog.
994 tristate "TI AR7 Watchdog Timer"
997 Hardware driver for the TI AR7 Watchdog Timer.
1000 tristate "Toshiba TXx9 Watchdog Timer"
1001 depends on CPU_TX39XX || CPU_TX49XX
1003 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1006 tristate "Cavium OCTEON SOC family Watchdog Timer"
1007 depends on CPU_CAVIUM_OCTEON
1009 select EXPORT_UASM if OCTEON_WDT = m
1011 Hardware driver for OCTEON's on chip watchdog timer.
1012 Enables the watchdog for all cores running Linux. It
1013 installs a NMI handler and pokes the watchdog based on an
1014 interrupt. On first expiration of the watchdog, the
1015 interrupt handler pokes it. The second expiration causes an
1016 NMI that prints a message. The third expiration causes a
1019 When userspace has /dev/watchdog open, no poking is done
1020 from the first interrupt, it is then only poked when the
1024 tristate "Broadcom BCM63xx hardware watchdog"
1027 Watchdog driver for the built in watchdog hardware in Broadcom
1030 To compile this driver as a loadable module, choose M here.
1031 The module will be called bcm63xx_wdt.
1034 tristate "Lantiq SoC watchdog"
1037 Hardware driver for the Lantiq SoC Watchdog Timer.
1039 # PARISC Architecture
1041 # POWERPC Architecture
1044 tristate "GE Watchdog Timer"
1047 Watchdog timer found in a number of GE single board computers.
1050 bool "MPC52xx Watchdog Timer"
1051 depends on PPC_MPC52xx
1053 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1056 tristate "MPC8xxx Platform Watchdog Timer"
1057 depends on PPC_8xx || PPC_83xx || PPC_86xx
1059 This driver is for a SoC level watchdog that exists on some
1060 Freescale PowerPC processors. So far this driver supports:
1065 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1068 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1072 tristate "PIKA FPGA Watchdog"
1076 This enables the watchdog in the PIKA FPGA. Currently used on
1080 tristate "PowerPC Book-E Watchdog Timer"
1081 depends on BOOKE || 4xx
1083 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1084 MPC85xx SOCs and the IBM PowerPC 440.
1086 Please see Documentation/watchdog/watchdog-api.txt for
1089 config BOOKE_WDT_DEFAULT_TIMEOUT
1090 int "PowerPC Book-E Watchdog Timer Default Timeout"
1091 depends on BOOKE_WDT
1092 default 38 if FSL_BOOKE
1093 range 0 63 if FSL_BOOKE
1094 default 3 if !FSL_BOOKE
1095 range 0 3 if !FSL_BOOKE
1097 Select the default watchdog timer period to be used by the PowerPC
1098 Book-E watchdog driver. A watchdog "event" occurs when the bit
1099 position represented by this number transitions from zero to one.
1101 For Freescale Book-E processors, this is a number between 0 and 63.
1102 For other Book-E processors, this is a number between 0 and 3.
1104 The value can be overridden by the wdt_period command-line parameter.
1106 # PPC64 Architecture
1108 config WATCHDOG_RTAS
1109 tristate "RTAS watchdog"
1112 This driver adds watchdog support for the RTAS watchdog.
1114 To compile this driver as a module, choose M here. The module
1115 will be called wdrtas.
1120 tristate "z/VM Watchdog Timer"
1123 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1124 provide a virtual watchdog timer to their guest that cause a
1125 user define Control Program command to be executed after a
1128 To compile this driver as a module, choose M here. The module
1129 will be called vmwatchdog.
1131 # SUPERH (sh + sh64) Architecture
1134 tristate "SuperH Watchdog"
1135 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1137 This driver adds watchdog support for the integrated watchdog in the
1138 SuperH processors. If you have one of these processors and wish
1139 to have watchdog support enabled, say Y, otherwise say N.
1141 As a side note, saying Y here will automatically boost HZ to 1000
1142 so that the timer has a chance to clear the overflow counter. On
1143 slower systems (such as the SH-2 and SH-3) this will likely yield
1144 some performance issues. As such, the WDT should be avoided here
1145 unless it is absolutely necessary.
1147 To compile this driver as a module, choose M here: the
1148 module will be called shwdt.
1150 # SPARC Architecture
1152 # SPARC64 Architecture
1154 config WATCHDOG_CP1XXX
1155 tristate "CP1XXX Hardware Watchdog support"
1156 depends on SPARC64 && PCI
1158 This is the driver for the hardware watchdog timers present on
1159 Sun Microsystems CompactPCI models CP1400 and CP1500.
1161 To compile this driver as a module, choose M here: the
1162 module will be called cpwatchdog.
1164 If you do not have a CompactPCI model CP1400 or CP1500, or
1165 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1166 you should say N to this option.
1169 tristate "RIO Hardware Watchdog support"
1170 depends on SPARC64 && PCI
1172 Say Y here to support the hardware watchdog capability on Sun RIO
1173 machines. The watchdog timeout period is normally one minute but
1174 can be changed with a boot-time parameter.
1176 # XTENSA Architecture
1181 tristate "Xen Watchdog support"
1184 Say Y here to support the hypervisor watchdog capability provided
1185 by Xen 4.0 and newer. The watchdog timeout period is normally one
1186 minute but can be changed with a boot-time parameter.
1189 tristate "UML watchdog"
1193 # ISA-based Watchdog Cards
1196 comment "ISA-based Watchdog Cards"
1200 tristate "Berkshire Products ISA-PC Watchdog"
1203 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1204 This card simply watches your kernel to make sure it doesn't freeze,
1205 and if it does, it reboots your computer after a certain amount of
1206 time. This driver is like the WDT501 driver but for different
1207 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1208 watchdog cards can be ordered from <http://www.berkprod.com/>.
1210 To compile this driver as a module, choose M here: the
1211 module will be called pcwd.
1213 Most people will say N.
1216 tristate "Mixcom Watchdog"
1219 This is a driver for the Mixcom hardware watchdog cards. This
1220 watchdog simply watches your kernel to make sure it doesn't freeze,
1221 and if it does, it reboots your computer after a certain amount of
1224 To compile this driver as a module, choose M here: the
1225 module will be called mixcomwd.
1227 Most people will say N.
1230 tristate "WDT Watchdog timer"
1233 If you have a WDT500P or WDT501P watchdog board, say Y here,
1234 otherwise N. It is not possible to probe for this board, which means
1235 that you have to inform the kernel about the IO port and IRQ that
1236 is needed (you can do this via the io and irq parameters)
1238 To compile this driver as a module, choose M here: the
1239 module will be called wdt.
1242 # PCI-based Watchdog Cards
1245 comment "PCI-based Watchdog Cards"
1248 config PCIPCWATCHDOG
1249 tristate "Berkshire Products PCI-PC Watchdog"
1252 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1253 This card simply watches your kernel to make sure it doesn't freeze,
1254 and if it does, it reboots your computer after a certain amount of
1255 time. The card can also monitor the internal temperature of the PC.
1256 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1258 To compile this driver as a module, choose M here: the
1259 module will be called pcwd_pci.
1261 Most people will say N.
1264 tristate "PCI-WDT500/501 Watchdog timer"
1267 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1269 If you have a PCI-WDT501 watchdog board then you can enable the
1270 temperature sensor by setting the type parameter to 501.
1272 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1273 can do this via the tachometer parameter. Only do this if you have a
1274 fan tachometer actually set up.
1276 To compile this driver as a module, choose M here: the
1277 module will be called wdt_pci.
1280 # USB-based Watchdog Cards
1283 comment "USB-based Watchdog Cards"
1286 config USBPCWATCHDOG
1287 tristate "Berkshire Products USB-PC Watchdog"
1290 This is the driver for the Berkshire Products USB-PC Watchdog card.
1291 This card simply watches your kernel to make sure it doesn't freeze,
1292 and if it does, it reboots your computer after a certain amount of
1293 time. The card can also monitor the internal temperature of the PC.
1294 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1296 To compile this driver as a module, choose M here: the
1297 module will be called pcwd_usb.
1299 Most people will say N.