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"
70 Support for the watchdog in the WM831x AudioPlus PMICs. When
71 the watchdog triggers the system will be reset.
73 config WM8350_WATCHDOG
74 tristate "WM8350 watchdog"
77 Support for the watchdog in the WM8350 AudioPlus PMIC. When
78 the watchdog triggers the system will be reset.
84 config ARM_SP805_WATCHDOG
85 tristate "ARM SP805 Watchdog"
88 ARM Primecell SP805 Watchdog timer. This will reboot your system when
89 the timeout is reached.
91 config AT91RM9200_WATCHDOG
92 tristate "AT91RM9200 watchdog"
93 depends on ARCH_AT91RM9200
95 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
96 system when the timeout is reached.
98 config AT91SAM9X_WATCHDOG
99 tristate "AT91SAM9X / AT91CAP9 watchdog"
100 depends on ARCH_AT91 && !ARCH_AT91RM9200
102 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
103 reboot your system when the timeout is reached.
105 config 21285_WATCHDOG
106 tristate "DC21285 watchdog"
107 depends on FOOTBRIDGE
109 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
110 here if you wish to use this. Alternatively say M to compile the
111 driver as a module, which will be called wdt285.
113 This driver does not work on all machines. In particular, early CATS
114 boards have hardware problems that will cause the machine to simply
115 lock up if the watchdog fires.
117 "If in doubt, leave it out" - say N.
120 tristate "NetWinder WB83C977 watchdog"
121 depends on FOOTBRIDGE && ARCH_NETWINDER
123 Say Y here to include support for the WB977 watchdog included in
124 NetWinder machines. Alternatively say M to compile the driver as
125 a module, which will be called wdt977.
127 Not sure? It's safe to say N.
129 config IXP2000_WATCHDOG
130 tristate "IXP2000 Watchdog"
131 depends on ARCH_IXP2000
133 Say Y here if to include support for the watchdog timer
134 in the Intel IXP2000(2400, 2800, 2850) network processors.
135 This driver can be built as a module by choosing M. The module
136 will be called ixp2000_wdt.
138 Say N if you are unsure.
140 config IXP4XX_WATCHDOG
141 tristate "IXP4xx Watchdog"
142 depends on ARCH_IXP4XX
144 Say Y here if to include support for the watchdog timer
145 in the Intel IXP4xx network processors. This driver can
146 be built as a module by choosing M. The module will
147 be called ixp4xx_wdt.
149 Note: The internal IXP4xx watchdog does a soft CPU reset
150 which doesn't reset any peripherals. There are circumstances
151 where the watchdog will fail to reset the board correctly
152 (e.g., if the boot ROM is in an unreadable state).
154 Say N if you are unsure.
156 config KS8695_WATCHDOG
157 tristate "KS8695 watchdog"
158 depends on ARCH_KS8695
160 Watchdog timer embedded into KS8695 processor. This will reboot your
161 system when the timeout is reached.
163 config HAVE_S3C2410_WATCHDOG
166 This will include watchdog timer support for Samsung SoCs. If
167 you want to include watchdog support for any machine, kindly
168 select this in the respective mach-XXXX/Kconfig file.
170 config S3C2410_WATCHDOG
171 tristate "S3C2410 Watchdog"
172 depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
174 Watchdog timer block in the Samsung SoCs. This will reboot
175 the system when the timer expires with the watchdog enabled.
177 The driver is limited by the speed of the system's PCLK
178 signal, so with reasonably fast systems (PCLK around 50-66MHz)
179 then watchdog intervals of over approximately 20seconds are
182 The driver can be built as a module by choosing M, and will
183 be called s3c2410_wdt
185 config SA1100_WATCHDOG
186 tristate "SA1100/PXA2xx watchdog"
187 depends on ARCH_SA1100 || ARCH_PXA
189 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
190 reboot your system when timeout is reached.
192 NOTE: once enabled, this timer cannot be disabled.
194 To compile this driver as a module, choose M here: the
195 module will be called sa1100_wdt.
198 tristate "Synopsys DesignWare watchdog"
199 depends on ARM && HAVE_CLK
201 Say Y here if to include support for the Synopsys DesignWare
202 watchdog timer found in many ARM chips.
203 To compile this driver as a module, choose M here: the
204 module will be called dw_wdt.
206 config MPCORE_WATCHDOG
207 tristate "MPcore watchdog"
208 depends on HAVE_ARM_TWD
210 Watchdog timer embedded into the MPcore system.
212 To compile this driver as a module, choose M here: the
213 module will be called mpcore_wdt.
215 config EP93XX_WATCHDOG
216 tristate "EP93xx Watchdog"
217 depends on ARCH_EP93XX
219 Say Y here if to include support for the watchdog timer
220 embedded in the Cirrus Logic EP93xx family of devices.
222 To compile this driver as a module, choose M here: the
223 module will be called ep93xx_wdt.
226 tristate "OMAP Watchdog"
227 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
229 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
230 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
232 config PNX4008_WATCHDOG
233 tristate "PNX4008 and LPC32XX Watchdog"
234 depends on ARCH_PNX4008 || ARCH_LPC32XX
236 Say Y here if to include support for the watchdog timer
237 in the PNX4008 or LPC32XX processor.
238 This driver can be built as a module by choosing M. The module
239 will be called pnx4008_wdt.
241 Say N if you are unsure.
244 tristate "IOP Watchdog"
246 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
248 Say Y here if to include support for the watchdog timer
249 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
250 be built as a module by choosing M. The module will
253 Note: The IOP13XX watchdog does an Internal Bus Reset which will
254 affect both cores and the peripherals of the IOP. The ATU-X
255 and/or ATUe configuration registers will remain intact, but if
256 operating as an Root Complex and/or Central Resource, the PCI-X
257 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
259 config DAVINCI_WATCHDOG
260 tristate "DaVinci watchdog"
261 depends on ARCH_DAVINCI
263 Say Y here if to include support for the watchdog timer
264 in the DaVinci DM644x/DM646x processors.
265 To compile this driver as a module, choose M here: the
266 module will be called davinci_wdt.
268 NOTE: once enabled, this timer cannot be disabled.
269 Say N if you are unsure.
271 config ORION_WATCHDOG
272 tristate "Orion watchdog"
273 depends on ARCH_ORION5X || ARCH_KIRKWOOD
275 Say Y here if to include support for the watchdog timer
276 in the Marvell Orion5x and Kirkwood ARM SoCs.
277 To compile this driver as a module, choose M here: the
278 module will be called orion_wdt.
280 config COH901327_WATCHDOG
281 bool "ST-Ericsson COH 901 327 watchdog"
283 default y if MACH_U300
285 Say Y here to include Watchdog timer support for the
286 watchdog embedded into the ST-Ericsson U300 series platforms.
287 This watchdog is used to reset the system and thus cannot be
288 compiled as a module.
290 config TWL4030_WATCHDOG
291 tristate "TWL4030 Watchdog"
292 depends on TWL4030_CORE
294 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
295 watchdog timer support for TWL4030 chips.
297 config STMP3XXX_WATCHDOG
298 tristate "Freescale STMP3XXX watchdog"
299 depends on ARCH_STMP3XXX
301 Say Y here if to include support for the watchdog timer
302 for the Sigmatel STMP37XX/378X SoC.
303 To compile this driver as a module, choose M here: the
304 module will be called stmp3xxx_wdt.
306 config NUC900_WATCHDOG
307 tristate "Nuvoton NUC900 watchdog"
308 depends on ARCH_W90X900
310 Say Y here if to include support for the watchdog timer
311 for the Nuvoton NUC900 series SoCs.
312 To compile this driver as a module, choose M here: the
313 module will be called nuc900_wdt.
316 tristate "Avionic Design Xanthos watchdog"
317 depends on ARCH_PXA_ADX
319 Say Y here if you want support for the watchdog timer on Avionic
320 Design Xanthos boards.
322 config TS72XX_WATCHDOG
323 tristate "TS-72XX SBC Watchdog"
324 depends on MACH_TS72XX
326 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
327 watchdog timer implemented in a external CPLD chip. Say Y here
328 if you want to support for the watchdog timer on TS-72XX boards.
330 To compile this driver as a module, choose M here: the
331 module will be called ts72xx_wdt.
333 config MAX63XX_WATCHDOG
334 tristate "Max63xx watchdog"
335 depends on ARM && HAS_IOMEM
337 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
340 tristate "IMX2+ Watchdog"
341 depends on IMX_HAVE_PLATFORM_IMX2_WDT
343 This is the driver for the hardware watchdog
344 on the Freescale IMX2 and later processors.
345 If you have one of these processors and wish to have
346 watchdog support enabled, say Y, otherwise say N.
348 To compile this driver as a module, choose M here: the
349 module will be called imx2_wdt.
353 config AT32AP700X_WDT
354 tristate "AT32AP700x watchdog"
355 depends on CPU_AT32AP700X
357 Watchdog timer embedded into AT32AP700x devices. This will reboot
358 your system when the timeout is reached.
360 # BLACKFIN Architecture
363 tristate "Blackfin On-Chip Watchdog Timer"
366 If you say yes here you will get support for the Blackfin On-Chip
367 Watchdog Timer. If you have one of these processors and wish to
368 have watchdog support enabled, say Y, otherwise say N.
370 To compile this driver as a module, choose M here: the
371 module will be called bfin_wdt.
379 # X86 (i386 + ia64 + x86_64) Architecture
382 tristate "Acquire SBC Watchdog Timer"
385 This is the driver for the hardware watchdog on Single Board
386 Computers produced by Acquire Inc (and others). This watchdog
387 simply watches your kernel to make sure it doesn't freeze, and if
388 it does, it reboots your computer after a certain amount of time.
390 To compile this driver as a module, choose M here: the
391 module will be called acquirewdt.
393 Most people will say N.
396 tristate "Advantech SBC Watchdog Timer"
399 If you are configuring a Linux kernel for the Advantech single-board
400 computer, say `Y' here to support its built-in watchdog timer
401 feature. More information can be found at
402 <http://www.advantech.com.tw/products/>
405 tristate "ALi M1535 PMU Watchdog Timer"
406 depends on X86 && PCI
408 This is the driver for the hardware watchdog on the ALi M1535 PMU.
410 To compile this driver as a module, choose M here: the
411 module will be called alim1535_wdt.
413 Most people will say N.
416 tristate "ALi M7101 PMU Computer Watchdog"
419 This is the driver for the hardware watchdog on the ALi M7101 PMU
420 as used in the x86 Cobalt servers and also found in some
421 SPARC Netra servers too.
423 To compile this driver as a module, choose M here: the
424 module will be called alim7101_wdt.
426 Most people will say N.
429 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
430 depends on X86 && EXPERIMENTAL
432 This is the driver for the hardware watchdog on the Fintek
433 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
435 You can compile this driver directly into the kernel, or use
436 it as a module. The module will be called f71808e_wdt.
439 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
440 depends on X86 && PCI
442 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
443 (Total Cost of Ownership) timer is a watchdog timer that will reboot
444 the machine after its expiration. The expiration time can be
445 configured with the "heartbeat" parameter.
447 To compile this driver as a module, choose M here: the
448 module will be called sp5100_tco.
451 tristate "AMD Geode CS5535/CS5536 Watchdog"
452 depends on CS5535_MFGPT
454 This driver enables a watchdog capability built into the
455 CS5535/CS5536 companion chips for the AMD Geode GX and LX
456 processors. This watchdog watches your kernel to make sure
457 it doesn't freeze, and if it does, it reboots your computer after
458 a certain amount of time.
460 You can compile this driver directly into the kernel, or use
461 it as a module. The module will be called geodewdt.
464 tristate "AMD Elan SC520 processor Watchdog"
467 This is the driver for the hardware watchdog built in to the
468 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
469 This watchdog simply watches your kernel to make sure it doesn't
470 freeze, and if it does, it reboots your computer after a certain
473 You can compile this driver directly into the kernel, or use
474 it as a module. The module will be called sc520_wdt.
476 config SBC_FITPC2_WATCHDOG
477 tristate "Compulab SBC-FITPC2 watchdog"
480 This is the driver for the built-in watchdog timer on the fit-PC2,
481 fit-PC2i, CM-iAM single-board computers made by Compulab.
483 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
484 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
486 Entering BIOS setup temporary disables watchdog operation regardless to current state,
487 so system will not be restarted while user in BIOS setup.
489 Once watchdog was enabled the system will be restarted every
490 "Watchdog Timer Value" period, so to prevent it user can restart or
491 disable the watchdog.
493 To compile this driver as a module, choose M here: the
494 module will be called sbc_fitpc2_wdt.
496 Most people will say N.
499 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
502 Enable support for the watchdog timer on the Eurotech CPU-1220 and
503 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
504 information are at <http://www.eurotech.it/>.
507 tristate "IB700 SBC Watchdog Timer"
510 This is the driver for the hardware watchdog on the IB700 Single
511 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
512 simply watches your kernel to make sure it doesn't freeze, and if
513 it does, it reboots your computer after a certain amount of time.
515 This driver is like the WDT501 driver but for slightly different hardware.
517 To compile this driver as a module, choose M here: the
518 module will be called ib700wdt.
520 Most people will say N.
523 tristate "IBM Automatic Server Restart"
526 This is the driver for the IBM Automatic Server Restart watchdog
527 timer built-in into some eServer xSeries machines.
529 To compile this driver as a module, choose M here: the
530 module will be called ibmasr.
533 tristate "ICP Single Board Computer Watchdog Timer"
536 This is a driver for the hardware watchdog on the ICP Single
537 Board Computer. This driver is working on (at least) the following
538 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
540 To compile this driver as a module, choose M here: the
541 module will be called wafer5823wdt.
544 tristate "Intel 6300ESB Timer/Watchdog"
545 depends on X86 && PCI
547 Hardware driver for the watchdog timer built into the Intel
548 6300ESB controller hub.
550 To compile this driver as a module, choose M here: the
551 module will be called i6300esb.
553 config INTEL_SCU_WATCHDOG
554 bool "Intel SCU Watchdog for Mobile Platforms"
557 Hardware driver for the watchdog time built into the Intel SCU
558 for Intel Mobile Platforms.
560 To compile this driver as a module, choose M here.
563 tristate "Intel TCO Timer/Watchdog"
564 depends on (X86 || IA64) && PCI
566 Hardware driver for the intel TCO timer based watchdog devices.
567 These drivers are included in the Intel 82801 I/O Controller
568 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
571 The TCO (Total Cost of Ownership) timer is a watchdog timer
572 that will reboot the machine after its second expiration. The
573 expiration time can be configured with the "heartbeat" parameter.
575 On some motherboards the driver may fail to reset the chipset's
576 NO_REBOOT flag which prevents the watchdog from rebooting the
577 machine. If this is the case you will get a kernel message like
578 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
580 To compile this driver as a module, choose M here: the
581 module will be called iTCO_wdt.
583 config ITCO_VENDOR_SUPPORT
584 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
587 Add vendor specific support to the intel TCO timer based watchdog
588 devices. At this moment we only have additional support for some
589 SuperMicro Inc. motherboards.
592 tristate "IT8712F (Smart Guardian) Watchdog Timer"
595 This is the driver for the built-in watchdog timer on the IT8712F
596 Super I/0 chipset used on many motherboards.
598 If the driver does not work, then make sure that the game port in
601 To compile this driver as a module, choose M here: the
602 module will be called it8712f_wdt.
605 tristate "IT87 Watchdog Timer"
606 depends on X86 && EXPERIMENTAL
608 This is the driver for the hardware watchdog on the ITE IT8702,
609 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
610 This watchdog simply watches your kernel to make sure it doesn't
611 freeze, and if it does, it reboots your computer after a certain
614 To compile this driver as a module, choose M here: the module will
618 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
619 depends on X86 && PCI
621 A software monitoring watchdog and NMI sourcing driver. This driver
622 will detect lockups and provide a stack trace. This is a driver that
623 will only load on an HP ProLiant system with a minimum of iLO2 support.
624 To compile this driver as a module, choose M here: the module will be
627 config HPWDT_NMI_DECODING
628 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
629 depends on HP_WATCHDOG
632 When an NMI occurs this feature will make the necessary BIOS calls to
633 log the cause of the NMI.
636 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
639 This is a driver for National Semiconductor PC87307/PC97307 hardware
640 watchdog cards as found on the SC1200. This watchdog is mainly used
641 for power management purposes and can be used to power down the device
642 during inactivity periods (includes interrupt activity monitoring).
644 To compile this driver as a module, choose M here: the
645 module will be called sc1200wdt.
647 Most people will say N.
650 tristate "National Semiconductor SCx200 Watchdog"
651 depends on SCx200 && PCI
653 Enable the built-in watchdog timer support on the National
654 Semiconductor SCx200 processors.
656 If compiled as a module, it will be called scx200_wdt.
659 tristate "NS PC87413 watchdog"
662 This is the driver for the hardware watchdog on the PC87413 chipset
663 This watchdog simply watches your kernel to make sure it doesn't
664 freeze, and if it does, it reboots your computer after a certain
667 To compile this driver as a module, choose M here: the
668 module will be called pc87413_wdt.
670 Most people will say N.
673 tristate "nVidia TCO Timer/Watchdog"
674 depends on X86 && PCI
676 Hardware driver for the TCO timer built into the nVidia Hub family
677 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
678 watchdog timer that will reboot the machine after its second
679 expiration. The expiration time can be configured with the
680 "heartbeat" parameter.
682 On some motherboards the driver may fail to reset the chipset's
683 NO_REBOOT flag which prevents the watchdog from rebooting the
684 machine. If this is the case you will get a kernel message like
685 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
687 To compile this driver as a module, choose M here: the
688 module will be called nv_tco.
691 tristate "RDC R-321x SoC watchdog"
692 depends on X86_RDC321X
694 This is the driver for the built in hardware watchdog
695 in the RDC R-321x SoC.
697 To compile this driver as a module, choose M here: the
698 module will be called rdc321x_wdt.
701 tristate "SBC-60XX Watchdog Timer"
704 This driver can be used with the watchdog timer found on some
705 single board computers, namely the 6010 PII based computer.
706 It may well work with other cards. It reads port 0x443 to enable
707 and re-set the watchdog timer, and reads port 0x45 to disable
708 the watchdog. If you have a card that behave in similar ways,
709 you can probably make this driver work with your card as well.
711 You can compile this driver directly into the kernel, or use
712 it as a module. The module will be called sbc60xxwdt.
715 tristate "SBC8360 Watchdog Timer"
719 This is the driver for the hardware watchdog on the SBC8360 Single
720 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
722 To compile this driver as a module, choose M here: the
723 module will be called sbc8360.
725 Most people will say N.
728 tristate "SBC Nano 7240 Watchdog Timer"
731 This is the driver for the hardware watchdog found on the IEI
732 single board computers EPIC Nano 7240 (and likely others). This
733 watchdog simply watches your kernel to make sure it doesn't freeze,
734 and if it does, it reboots your computer after a certain amount of
737 To compile this driver as a module, choose M here: the
738 module will be called sbc7240_wdt.
741 tristate "SMA CPU5 Watchdog"
745 To compile this driver as a module, choose M here: the
746 module will be called cpu5wdt.
748 config SMSC_SCH311X_WDT
749 tristate "SMSC SCH311X Watchdog Timer"
752 This is the driver for the hardware watchdog timer on the
753 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
754 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
757 To compile this driver as a module, choose M here: the
758 module will be called sch311x_wdt.
760 config SMSC37B787_WDT
761 tristate "Winbond SMsC37B787 Watchdog Timer"
764 This is the driver for the hardware watchdog component on the
765 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
766 from Vision Systems and maybe others.
768 This watchdog simply watches your kernel to make sure it doesn't
769 freeze, and if it does, it reboots your computer after a certain
772 Usually a userspace daemon will notify the kernel WDT driver that
773 userspace is still alive, at regular intervals.
775 To compile this driver as a module, choose M here: the
776 module will be called smsc37b787_wdt.
778 Most people will say N.
781 tristate "W83627HF/W83627DHG Watchdog Timer"
784 This is the driver for the hardware watchdog on the W83627HF chipset
785 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
786 (and likely others). The driver also supports the W83627DHG chip.
787 This watchdog simply watches your kernel to make sure it doesn't
788 freeze, and if it does, it reboots your computer after a certain
791 To compile this driver as a module, choose M here: the
792 module will be called w83627hf_wdt.
794 Most people will say N.
797 tristate "W83697HF/W83697HG Watchdog Timer"
800 This is the driver for the hardware watchdog on the W83697HF/HG
801 chipset as used in Dedibox/VIA motherboards (and likely others).
802 This watchdog simply watches your kernel to make sure it doesn't
803 freeze, and if it does, it reboots your computer after a certain
806 To compile this driver as a module, choose M here: the
807 module will be called w83697hf_wdt.
809 Most people will say N.
812 tristate "W83697UG/W83697UF Watchdog Timer"
815 This is the driver for the hardware watchdog on the W83697UG/UF
816 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
817 This watchdog simply watches your kernel to make sure it doesn't
818 freeze, and if it does, it reboots your computer after a certain
821 To compile this driver as a module, choose M here: the
822 module will be called w83697ug_wdt.
824 Most people will say N.
827 tristate "W83877F (EMACS) Watchdog Timer"
830 This is the driver for the hardware watchdog on the W83877F chipset
831 as used in EMACS PC-104 motherboards (and likely others). This
832 watchdog simply watches your kernel to make sure it doesn't freeze,
833 and if it does, it reboots your computer after a certain amount of
836 To compile this driver as a module, choose M here: the
837 module will be called w83877f_wdt.
839 Most people will say N.
842 tristate "W83977F (PCM-5335) Watchdog Timer"
845 This is the driver for the hardware watchdog on the W83977F I/O chip
846 as used in AAEON's PCM-5335 SBC (and likely others). This
847 watchdog simply watches your kernel to make sure it doesn't freeze,
848 and if it does, it reboots your computer after a certain amount of
851 To compile this driver as a module, choose M here: the
852 module will be called w83977f_wdt.
855 tristate "ZF MachZ Watchdog"
858 If you are using a ZF Micro MachZ processor, say Y here, otherwise
859 N. This is the driver for the watchdog timer built-in on that
860 processor using ZF-Logic interface. This watchdog simply watches
861 your kernel to make sure it doesn't freeze, and if it does, it
862 reboots your computer after a certain amount of time.
864 To compile this driver as a module, choose M here: the
865 module will be called machzwd.
867 config SBC_EPX_C3_WATCHDOG
868 tristate "Winsystems SBC EPX-C3 watchdog"
871 This is the driver for the built-in watchdog timer on the EPX-C3
872 Single-board computer made by Winsystems, Inc.
874 *Note*: This hardware watchdog is not probeable and thus there
875 is no way to know if writing to its IO address will corrupt
876 your system or have any real effect. The only way to be sure
877 that this driver does what you want is to make sure you
878 are running it on an EPX-C3 from Winsystems with the watchdog
879 timer at IO address 0x1ee and 0x1ef. It will write to both those
880 IO ports. Basically, the assumption is made that if you compile
881 this driver into your kernel and/or load it as a module, that you
882 know what you are doing and that you are in fact running on an
885 To compile this driver as a module, choose M here: the
886 module will be called sbc_epx_c3.
892 config M54xx_WATCHDOG
893 tristate "MCF54xx watchdog support"
896 To compile this driver as a module, choose M here: the
897 module will be called m54xx_wdt.
899 # MicroBlaze Architecture
901 config XILINX_WATCHDOG
902 tristate "Xilinx Watchdog timer"
903 depends on MICROBLAZE
905 Watchdog driver for the xps_timebase_wdt ip core.
907 IMPORTANT: The xps_timebase_wdt parent must have the property
908 "clock-frequency" at device tree.
910 To compile this driver as a module, choose M here: the
911 module will be called of_xilinx_wdt.
916 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
919 Hardware driver for the built-in watchdog timer on the Atheros
920 AR71XX/AR724X/AR913X SoCs.
923 tristate "Broadcom BCM47xx Watchdog Timer"
926 Hardware driver for the Broadcom BCM47xx Watchog Timer.
929 tristate "IDT RC32434 SoC Watchdog Timer"
930 depends on MIKROTIK_RB532
932 Hardware driver for the IDT RC32434 SoC built-in
935 To compile this driver as a module, choose M here: the
936 module will be called rc32434_wdt.
939 tristate "Indy/I2 Hardware Watchdog"
940 depends on SGI_HAS_INDYDOG
942 Hardware driver for the Indy's/I2's watchdog. This is a
943 watchdog timer that will reboot the machine after a 60 second
944 timer expired and no process has written to /dev/watchdog during
948 tristate "Ingenic jz4740 SoC hardware watchdog"
949 depends on MACH_JZ4740
951 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
954 tristate "MTX-1 Hardware Watchdog"
957 Hardware driver for the MTX-1 boards. This is a watchdog timer that
958 will reboot the machine after a 100 seconds timer expired.
961 tristate "PNX833x Hardware Watchdog"
962 depends on SOC_PNX8335
964 Hardware driver for the PNX833x's watchdog. This is a
965 watchdog timer that will reboot the machine after a programmable
966 timer has expired and no process has written to /dev/watchdog during
970 tristate "Sibyte SoC hardware watchdog"
973 Watchdog driver for the built in watchdog hardware in Sibyte
974 SoC processors. There are apparently two watchdog timers
975 on such processors; this driver supports only the first one,
976 because currently Linux only supports exporting one watchdog
979 To compile this driver as a loadable module, choose M here.
980 The module will be called sb_wdog.
983 tristate "TI AR7 Watchdog Timer"
986 Hardware driver for the TI AR7 Watchdog Timer.
989 tristate "Toshiba TXx9 Watchdog Timer"
990 depends on CPU_TX39XX || CPU_TX49XX
992 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
995 tristate "Cavium OCTEON SOC family Watchdog Timer"
996 depends on CPU_CAVIUM_OCTEON
998 select EXPORT_UASM if OCTEON_WDT = m
1000 Hardware driver for OCTEON's on chip watchdog timer.
1001 Enables the watchdog for all cores running Linux. It
1002 installs a NMI handler and pokes the watchdog based on an
1003 interrupt. On first expiration of the watchdog, the
1004 interrupt handler pokes it. The second expiration causes an
1005 NMI that prints a message. The third expiration causes a
1008 When userspace has /dev/watchdog open, no poking is done
1009 from the first interrupt, it is then only poked when the
1013 tristate "Broadcom BCM63xx hardware watchdog"
1016 Watchdog driver for the built in watchdog hardware in Broadcom
1019 To compile this driver as a loadable module, choose M here.
1020 The module will be called bcm63xx_wdt.
1023 tristate "Lantiq SoC watchdog"
1026 Hardware driver for the Lantiq SoC Watchdog Timer.
1028 # PARISC Architecture
1030 # POWERPC Architecture
1033 tristate "GE Watchdog Timer"
1034 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
1036 Watchdog timer found in a number of GE single board computers.
1039 bool "MPC52xx Watchdog Timer"
1040 depends on PPC_MPC52xx
1042 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1045 tristate "MPC8xxx Platform Watchdog Timer"
1046 depends on PPC_8xx || PPC_83xx || PPC_86xx
1048 This driver is for a SoC level watchdog that exists on some
1049 Freescale PowerPC processors. So far this driver supports:
1054 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1057 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1061 tristate "PIKA FPGA Watchdog"
1065 This enables the watchdog in the PIKA FPGA. Currently used on
1069 tristate "PowerPC Book-E Watchdog Timer"
1070 depends on BOOKE || 4xx
1072 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1073 MPC85xx SOCs and the IBM PowerPC 440.
1075 Please see Documentation/watchdog/watchdog-api.txt for
1078 config BOOKE_WDT_DEFAULT_TIMEOUT
1079 int "PowerPC Book-E Watchdog Timer Default Timeout"
1080 depends on BOOKE_WDT
1081 default 38 if FSL_BOOKE
1082 range 0 63 if FSL_BOOKE
1083 default 3 if !FSL_BOOKE
1084 range 0 3 if !FSL_BOOKE
1086 Select the default watchdog timer period to be used by the PowerPC
1087 Book-E watchdog driver. A watchdog "event" occurs when the bit
1088 position represented by this number transitions from zero to one.
1090 For Freescale Book-E processors, this is a number between 0 and 63.
1091 For other Book-E processors, this is a number between 0 and 3.
1093 The value can be overidden by the wdt_period command-line parameter.
1095 # PPC64 Architecture
1097 config WATCHDOG_RTAS
1098 tristate "RTAS watchdog"
1101 This driver adds watchdog support for the RTAS watchdog.
1103 To compile this driver as a module, choose M here. The module
1104 will be called wdrtas.
1109 tristate "z/VM Watchdog Timer"
1112 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1113 provide a virtual watchdog timer to their guest that cause a
1114 user define Control Program command to be executed after a
1117 To compile this driver as a module, choose M here. The module
1118 will be called vmwatchdog.
1120 # SUPERH (sh + sh64) Architecture
1123 tristate "SuperH Watchdog"
1124 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1126 This driver adds watchdog support for the integrated watchdog in the
1127 SuperH processors. If you have one of these processors and wish
1128 to have watchdog support enabled, say Y, otherwise say N.
1130 As a side note, saying Y here will automatically boost HZ to 1000
1131 so that the timer has a chance to clear the overflow counter. On
1132 slower systems (such as the SH-2 and SH-3) this will likely yield
1133 some performance issues. As such, the WDT should be avoided here
1134 unless it is absolutely necessary.
1136 To compile this driver as a module, choose M here: the
1137 module will be called shwdt.
1139 # SPARC Architecture
1141 # SPARC64 Architecture
1143 config WATCHDOG_CP1XXX
1144 tristate "CP1XXX Hardware Watchdog support"
1145 depends on SPARC64 && PCI
1147 This is the driver for the hardware watchdog timers present on
1148 Sun Microsystems CompactPCI models CP1400 and CP1500.
1150 To compile this driver as a module, choose M here: the
1151 module will be called cpwatchdog.
1153 If you do not have a CompactPCI model CP1400 or CP1500, or
1154 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1155 you should say N to this option.
1158 tristate "RIO Hardware Watchdog support"
1159 depends on SPARC64 && PCI
1161 Say Y here to support the hardware watchdog capability on Sun RIO
1162 machines. The watchdog timeout period is normally one minute but
1163 can be changed with a boot-time parameter.
1165 # XTENSA Architecture
1170 tristate "Xen Watchdog support"
1173 Say Y here to support the hypervisor watchdog capability provided
1174 by Xen 4.0 and newer. The watchdog timeout period is normally one
1175 minute but can be changed with a boot-time parameter.
1178 # ISA-based Watchdog Cards
1181 comment "ISA-based Watchdog Cards"
1185 tristate "Berkshire Products ISA-PC Watchdog"
1188 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1189 This card simply watches your kernel to make sure it doesn't freeze,
1190 and if it does, it reboots your computer after a certain amount of
1191 time. This driver is like the WDT501 driver but for different
1192 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1193 watchdog cards can be ordered from <http://www.berkprod.com/>.
1195 To compile this driver as a module, choose M here: the
1196 module will be called pcwd.
1198 Most people will say N.
1201 tristate "Mixcom Watchdog"
1204 This is a driver for the Mixcom hardware watchdog cards. This
1205 watchdog 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
1209 To compile this driver as a module, choose M here: the
1210 module will be called mixcomwd.
1212 Most people will say N.
1215 tristate "WDT Watchdog timer"
1218 If you have a WDT500P or WDT501P watchdog board, say Y here,
1219 otherwise N. It is not possible to probe for this board, which means
1220 that you have to inform the kernel about the IO port and IRQ that
1221 is needed (you can do this via the io and irq parameters)
1223 To compile this driver as a module, choose M here: the
1224 module will be called wdt.
1227 # PCI-based Watchdog Cards
1230 comment "PCI-based Watchdog Cards"
1233 config PCIPCWATCHDOG
1234 tristate "Berkshire Products PCI-PC Watchdog"
1237 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1238 This card simply watches your kernel to make sure it doesn't freeze,
1239 and if it does, it reboots your computer after a certain amount of
1240 time. The card can also monitor the internal temperature of the PC.
1241 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1243 To compile this driver as a module, choose M here: the
1244 module will be called pcwd_pci.
1246 Most people will say N.
1249 tristate "PCI-WDT500/501 Watchdog timer"
1252 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1254 If you have a PCI-WDT501 watchdog board then you can enable the
1255 temperature sensor by setting the type parameter to 501.
1257 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1258 can do this via the tachometer parameter. Only do this if you have a
1259 fan tachometer actually set up.
1261 To compile this driver as a module, choose M here: the
1262 module will be called wdt_pci.
1265 # USB-based Watchdog Cards
1268 comment "USB-based Watchdog Cards"
1271 config USBPCWATCHDOG
1272 tristate "Berkshire Products USB-PC Watchdog"
1275 This is the driver for the Berkshire Products USB-PC Watchdog card.
1276 This card simply watches your kernel to make sure it doesn't freeze,
1277 and if it does, it reboots your computer after a certain amount of
1278 time. The card can also monitor the internal temperature of the PC.
1279 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1281 To compile this driver as a module, choose M here: the
1282 module will be called pcwd_usb.
1284 Most people will say N.