2 # Watchdog device configuration
6 bool "Watchdog Timer Support"
8 If you say Y here (and to one of the following options) and create a
9 character special file /dev/watchdog with major number 10 and minor
10 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
11 subsequently opening the file and then failing to write to it for
12 longer than 1 minute will result in rebooting the machine. This
13 could be useful for a networked machine that needs to come back
14 on-line as fast as possible after a lock-up. There's both a watchdog
15 implementation entirely in software (which can sometimes fail to
16 reboot the machine) and a driver for hardware watchdog boards, which
17 are more robust and can also keep track of the temperature inside
18 your computer. For details, read
19 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
21 The watchdog is usually used together with the watchdog daemon
22 which is available from
23 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
24 also monitor NFS connections and can reboot the machine when the process
32 bool "WatchDog Timer Driver Core"
34 Say Y here if you want to use the new watchdog timer driver core.
35 This driver provides a framework for all watchdog timer drivers
36 and gives them the /dev/watchdog interface (and later also the
39 config WATCHDOG_NOWAYOUT
40 bool "Disable watchdog shutdown on close"
42 The default watchdog behaviour (which you get if you say N here) is
43 to stop the timer if the process managing it closes the file
44 /dev/watchdog. It's always remotely possible that this process might
45 get killed. If you say Y here, the watchdog cannot be stopped once
49 # General Watchdog drivers
52 comment "Watchdog Device Drivers"
54 # Architecture Independent
57 tristate "Software watchdog"
60 A software monitoring watchdog. This will fail to reboot your system
61 from some situations that the hardware watchdog will recover
62 from. Equally it's a lot cheaper to install.
64 To compile this driver as a module, choose M here: the
65 module will be called softdog.
67 config WM831X_WATCHDOG
68 tristate "WM831x watchdog"
72 Support for the watchdog in the WM831x AudioPlus PMICs. When
73 the watchdog triggers the system will be reset.
75 config WM8350_WATCHDOG
76 tristate "WM8350 watchdog"
80 Support for the watchdog in the WM8350 AudioPlus PMIC. When
81 the watchdog triggers the system will be reset.
87 config ARM_SP805_WATCHDOG
88 tristate "ARM SP805 Watchdog"
91 ARM Primecell SP805 Watchdog timer. This will reboot your system when
92 the timeout is reached.
94 config AT91RM9200_WATCHDOG
95 tristate "AT91RM9200 watchdog"
96 depends on ARCH_AT91RM9200
98 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
99 system when the timeout is reached.
101 config AT91SAM9X_WATCHDOG
102 tristate "AT91SAM9X / AT91CAP9 watchdog"
103 depends on ARCH_AT91 && !ARCH_AT91RM9200
105 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
106 reboot your system when the timeout is reached.
108 config 21285_WATCHDOG
109 tristate "DC21285 watchdog"
110 depends on FOOTBRIDGE
112 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
113 here if you wish to use this. Alternatively say M to compile the
114 driver as a module, which will be called wdt285.
116 This driver does not work on all machines. In particular, early CATS
117 boards have hardware problems that will cause the machine to simply
118 lock up if the watchdog fires.
120 "If in doubt, leave it out" - say N.
123 tristate "NetWinder WB83C977 watchdog"
124 depends on FOOTBRIDGE && ARCH_NETWINDER
126 Say Y here to include support for the WB977 watchdog included in
127 NetWinder machines. Alternatively say M to compile the driver as
128 a module, which will be called wdt977.
130 Not sure? It's safe to say N.
132 config IXP4XX_WATCHDOG
133 tristate "IXP4xx Watchdog"
134 depends on ARCH_IXP4XX
136 Say Y here if to include support for the watchdog timer
137 in the Intel IXP4xx network processors. This driver can
138 be built as a module by choosing M. The module will
139 be called ixp4xx_wdt.
141 Note: The internal IXP4xx watchdog does a soft CPU reset
142 which doesn't reset any peripherals. There are circumstances
143 where the watchdog will fail to reset the board correctly
144 (e.g., if the boot ROM is in an unreadable state).
146 Say N if you are unsure.
148 config KS8695_WATCHDOG
149 tristate "KS8695 watchdog"
150 depends on ARCH_KS8695
152 Watchdog timer embedded into KS8695 processor. This will reboot your
153 system when the timeout is reached.
155 config HAVE_S3C2410_WATCHDOG
158 This will include watchdog timer support for Samsung SoCs. If
159 you want to include watchdog support for any machine, kindly
160 select this in the respective mach-XXXX/Kconfig file.
162 config S3C2410_WATCHDOG
163 tristate "S3C2410 Watchdog"
164 depends on HAVE_S3C2410_WATCHDOG
167 Watchdog timer block in the Samsung SoCs. This will reboot
168 the system when the timer expires with the watchdog enabled.
170 The driver is limited by the speed of the system's PCLK
171 signal, so with reasonably fast systems (PCLK around 50-66MHz)
172 then watchdog intervals of over approximately 20seconds are
175 The driver can be built as a module by choosing M, and will
176 be called s3c2410_wdt
178 config SA1100_WATCHDOG
179 tristate "SA1100/PXA2xx watchdog"
180 depends on ARCH_SA1100 || ARCH_PXA
182 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
183 reboot your system when timeout is reached.
185 NOTE: once enabled, this timer cannot be disabled.
187 To compile this driver as a module, choose M here: the
188 module will be called sa1100_wdt.
191 tristate "Synopsys DesignWare watchdog"
192 depends on ARM && HAVE_CLK
194 Say Y here if to include support for the Synopsys DesignWare
195 watchdog timer found in many ARM chips.
196 To compile this driver as a module, choose M here: the
197 module will be called dw_wdt.
199 config MPCORE_WATCHDOG
200 tristate "MPcore watchdog"
201 depends on HAVE_ARM_TWD
203 Watchdog timer embedded into the MPcore system.
205 To compile this driver as a module, choose M here: the
206 module will be called mpcore_wdt.
208 config EP93XX_WATCHDOG
209 tristate "EP93xx Watchdog"
210 depends on ARCH_EP93XX
213 Say Y here if to include support for the watchdog timer
214 embedded in the Cirrus Logic EP93xx family of devices.
216 To compile this driver as a module, choose M here: the
217 module will be called ep93xx_wdt.
220 tristate "OMAP Watchdog"
221 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
223 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
224 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
226 config PNX4008_WATCHDOG
227 tristate "PNX4008 and LPC32XX Watchdog"
228 depends on ARCH_PNX4008 || ARCH_LPC32XX
231 Say Y here if to include support for the watchdog timer
232 in the PNX4008 or LPC32XX processor.
233 This driver can be built as a module by choosing M. The module
234 will be called pnx4008_wdt.
236 Say N if you are unsure.
239 tristate "IOP Watchdog"
241 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
243 Say Y here if to include support for the watchdog timer
244 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
245 be built as a module by choosing M. The module will
248 Note: The IOP13XX watchdog does an Internal Bus Reset which will
249 affect both cores and the peripherals of the IOP. The ATU-X
250 and/or ATUe configuration registers will remain intact, but if
251 operating as an Root Complex and/or Central Resource, the PCI-X
252 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
254 config DAVINCI_WATCHDOG
255 tristate "DaVinci watchdog"
256 depends on ARCH_DAVINCI
258 Say Y here if to include support for the watchdog timer
259 in the DaVinci DM644x/DM646x processors.
260 To compile this driver as a module, choose M here: the
261 module will be called davinci_wdt.
263 NOTE: once enabled, this timer cannot be disabled.
264 Say N if you are unsure.
266 config ORION_WATCHDOG
267 tristate "Orion watchdog"
268 depends on ARCH_ORION5X || ARCH_KIRKWOOD
270 Say Y here if to include support for the watchdog timer
271 in the Marvell Orion5x and Kirkwood ARM SoCs.
272 To compile this driver as a module, choose M here: the
273 module will be called orion_wdt.
275 config COH901327_WATCHDOG
276 bool "ST-Ericsson COH 901 327 watchdog"
278 default y if MACH_U300
281 Say Y here to include Watchdog timer support for the
282 watchdog embedded into the ST-Ericsson U300 series platforms.
283 This watchdog is used to reset the system and thus cannot be
284 compiled as a module.
286 config TWL4030_WATCHDOG
287 tristate "TWL4030 Watchdog"
288 depends on TWL4030_CORE
290 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
291 watchdog timer support for TWL4030 chips.
293 config STMP3XXX_WATCHDOG
294 tristate "Freescale STMP3XXX watchdog"
295 depends on ARCH_STMP3XXX
297 Say Y here if to include support for the watchdog timer
298 for the Sigmatel STMP37XX/378X SoC.
299 To compile this driver as a module, choose M here: the
300 module will be called stmp3xxx_wdt.
302 config NUC900_WATCHDOG
303 tristate "Nuvoton NUC900 watchdog"
304 depends on ARCH_W90X900
306 Say Y here if to include support for the watchdog timer
307 for the Nuvoton NUC900 series SoCs.
308 To compile this driver as a module, choose M here: the
309 module will be called nuc900_wdt.
311 config TS72XX_WATCHDOG
312 tristate "TS-72XX SBC Watchdog"
313 depends on MACH_TS72XX
315 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
316 watchdog timer implemented in a external CPLD chip. Say Y here
317 if you want to support for the watchdog timer on TS-72XX boards.
319 To compile this driver as a module, choose M here: the
320 module will be called ts72xx_wdt.
322 config MAX63XX_WATCHDOG
323 tristate "Max63xx watchdog"
324 depends on ARM && HAS_IOMEM
327 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
330 tristate "IMX2+ Watchdog"
331 depends on IMX_HAVE_PLATFORM_IMX2_WDT
333 This is the driver for the hardware watchdog
334 on the Freescale IMX2 and later processors.
335 If you have one of these processors and wish to have
336 watchdog support enabled, say Y, otherwise say N.
338 To compile this driver as a module, choose M here: the
339 module will be called imx2_wdt.
343 config AT32AP700X_WDT
344 tristate "AT32AP700x watchdog"
345 depends on CPU_AT32AP700X
347 Watchdog timer embedded into AT32AP700x devices. This will reboot
348 your system when the timeout is reached.
350 # BLACKFIN Architecture
353 tristate "Blackfin On-Chip Watchdog Timer"
356 If you say yes here you will get support for the Blackfin On-Chip
357 Watchdog Timer. If you have one of these processors and wish to
358 have watchdog support enabled, say Y, otherwise say N.
360 To compile this driver as a module, choose M here: the
361 module will be called bfin_wdt.
369 # X86 (i386 + ia64 + x86_64) Architecture
372 tristate "Acquire SBC Watchdog Timer"
375 This is the driver for the hardware watchdog on Single Board
376 Computers produced by Acquire Inc (and others). This watchdog
377 simply watches your kernel to make sure it doesn't freeze, and if
378 it does, it reboots your computer after a certain amount of time.
380 To compile this driver as a module, choose M here: the
381 module will be called acquirewdt.
383 Most people will say N.
386 tristate "Advantech SBC Watchdog Timer"
389 If you are configuring a Linux kernel for the Advantech single-board
390 computer, say `Y' here to support its built-in watchdog timer
391 feature. More information can be found at
392 <http://www.advantech.com.tw/products/>
395 tristate "ALi M1535 PMU Watchdog Timer"
396 depends on X86 && PCI
398 This is the driver for the hardware watchdog on the ALi M1535 PMU.
400 To compile this driver as a module, choose M here: the
401 module will be called alim1535_wdt.
403 Most people will say N.
406 tristate "ALi M7101 PMU Computer Watchdog"
409 This is the driver for the hardware watchdog on the ALi M7101 PMU
410 as used in the x86 Cobalt servers and also found in some
411 SPARC Netra servers too.
413 To compile this driver as a module, choose M here: the
414 module will be called alim7101_wdt.
416 Most people will say N.
419 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
420 depends on X86 && EXPERIMENTAL
422 This is the driver for the hardware watchdog on the Fintek
423 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
425 You can compile this driver directly into the kernel, or use
426 it as a module. The module will be called f71808e_wdt.
429 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
430 depends on X86 && PCI
432 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
433 (Total Cost of Ownership) timer is a watchdog timer that will reboot
434 the machine after its expiration. The expiration time can be
435 configured with the "heartbeat" parameter.
437 To compile this driver as a module, choose M here: the
438 module will be called sp5100_tco.
441 tristate "AMD Geode CS5535/CS5536 Watchdog"
442 depends on CS5535_MFGPT
444 This driver enables a watchdog capability built into the
445 CS5535/CS5536 companion chips for the AMD Geode GX and LX
446 processors. This watchdog watches your kernel to make sure
447 it doesn't freeze, and if it does, it reboots your computer after
448 a certain amount of time.
450 You can compile this driver directly into the kernel, or use
451 it as a module. The module will be called geodewdt.
454 tristate "AMD Elan SC520 processor Watchdog"
457 This is the driver for the hardware watchdog built in to the
458 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
459 This watchdog simply watches your kernel to make sure it doesn't
460 freeze, and if it does, it reboots your computer after a certain
463 You can compile this driver directly into the kernel, or use
464 it as a module. The module will be called sc520_wdt.
466 config SBC_FITPC2_WATCHDOG
467 tristate "Compulab SBC-FITPC2 watchdog"
470 This is the driver for the built-in watchdog timer on the fit-PC2,
471 fit-PC2i, CM-iAM single-board computers made by Compulab.
473 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
474 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
476 Entering BIOS setup temporary disables watchdog operation regardless to current state,
477 so system will not be restarted while user in BIOS setup.
479 Once watchdog was enabled the system will be restarted every
480 "Watchdog Timer Value" period, so to prevent it user can restart or
481 disable the watchdog.
483 To compile this driver as a module, choose M here: the
484 module will be called sbc_fitpc2_wdt.
486 Most people will say N.
489 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
492 Enable support for the watchdog timer on the Eurotech CPU-1220 and
493 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
494 information are at <http://www.eurotech.it/>.
497 tristate "IB700 SBC Watchdog Timer"
500 This is the driver for the hardware watchdog on the IB700 Single
501 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
502 simply watches your kernel to make sure it doesn't freeze, and if
503 it does, it reboots your computer after a certain amount of time.
505 This driver is like the WDT501 driver but for slightly different hardware.
507 To compile this driver as a module, choose M here: the
508 module will be called ib700wdt.
510 Most people will say N.
513 tristate "IBM Automatic Server Restart"
516 This is the driver for the IBM Automatic Server Restart watchdog
517 timer built-in into some eServer xSeries machines.
519 To compile this driver as a module, choose M here: the
520 module will be called ibmasr.
523 tristate "ICP Single Board Computer Watchdog Timer"
526 This is a driver for the hardware watchdog on the ICP Single
527 Board Computer. This driver is working on (at least) the following
528 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
530 To compile this driver as a module, choose M here: the
531 module will be called wafer5823wdt.
534 tristate "Intel 6300ESB Timer/Watchdog"
537 Hardware driver for the watchdog timer built into the Intel
538 6300ESB controller hub.
540 To compile this driver as a module, choose M here: the
541 module will be called i6300esb.
544 tristate "Intel Atom E6xx Watchdog"
545 depends on X86 && PCI
550 Hardware driver for the watchdog timer built into the Intel
551 Atom E6XX (TunnelCreek) processor.
553 To compile this driver as a module, choose M here: the
554 module will be called ie6xx_wdt.
556 config INTEL_SCU_WATCHDOG
557 bool "Intel SCU Watchdog for Mobile Platforms"
560 Hardware driver for the watchdog time built into the Intel SCU
561 for Intel Mobile Platforms.
563 To compile this driver as a module, choose M here.
566 tristate "Intel TCO Timer/Watchdog"
567 depends on (X86 || IA64) && PCI
569 Hardware driver for the intel TCO timer based watchdog devices.
570 These drivers are included in the Intel 82801 I/O Controller
571 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
574 The TCO (Total Cost of Ownership) timer is a watchdog timer
575 that will reboot the machine after its second expiration. The
576 expiration time can be configured with the "heartbeat" parameter.
578 On some motherboards the driver may fail to reset the chipset's
579 NO_REBOOT flag which prevents the watchdog from rebooting the
580 machine. If this is the case you will get a kernel message like
581 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
583 To compile this driver as a module, choose M here: the
584 module will be called iTCO_wdt.
586 config ITCO_VENDOR_SUPPORT
587 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
590 Add vendor specific support to the intel TCO timer based watchdog
591 devices. At this moment we only have additional support for some
592 SuperMicro Inc. motherboards.
595 tristate "IT8712F (Smart Guardian) Watchdog Timer"
598 This is the driver for the built-in watchdog timer on the IT8712F
599 Super I/0 chipset used on many motherboards.
601 If the driver does not work, then make sure that the game port in
604 To compile this driver as a module, choose M here: the
605 module will be called it8712f_wdt.
608 tristate "IT87 Watchdog Timer"
609 depends on X86 && EXPERIMENTAL
611 This is the driver for the hardware watchdog on the ITE IT8702,
612 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
615 If the driver does not work, then make sure that the game port in
618 This watchdog simply watches your kernel to make sure it doesn't
619 freeze, and if it does, it reboots your computer after a certain
622 To compile this driver as a module, choose M here: the module will
626 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
627 depends on X86 && PCI
629 A software monitoring watchdog and NMI sourcing driver. This driver
630 will detect lockups and provide a stack trace. This is a driver that
631 will only load on an HP ProLiant system with a minimum of iLO2 support.
632 To compile this driver as a module, choose M here: the module will be
635 config HPWDT_NMI_DECODING
636 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
637 depends on HP_WATCHDOG
640 When an NMI occurs this feature will make the necessary BIOS calls to
641 log the cause of the NMI.
644 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
647 This is a driver for National Semiconductor PC87307/PC97307 hardware
648 watchdog cards as found on the SC1200. This watchdog is mainly used
649 for power management purposes and can be used to power down the device
650 during inactivity periods (includes interrupt activity monitoring).
652 To compile this driver as a module, choose M here: the
653 module will be called sc1200wdt.
655 Most people will say N.
658 tristate "National Semiconductor SCx200 Watchdog"
659 depends on SCx200 && PCI
661 Enable the built-in watchdog timer support on the National
662 Semiconductor SCx200 processors.
664 If compiled as a module, it will be called scx200_wdt.
667 tristate "NS PC87413 watchdog"
670 This is the driver for the hardware watchdog on the PC87413 chipset
671 This watchdog simply watches your kernel to make sure it doesn't
672 freeze, and if it does, it reboots your computer after a certain
675 To compile this driver as a module, choose M here: the
676 module will be called pc87413_wdt.
678 Most people will say N.
681 tristate "nVidia TCO Timer/Watchdog"
682 depends on X86 && PCI
684 Hardware driver for the TCO timer built into the nVidia Hub family
685 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
686 watchdog timer that will reboot the machine after its second
687 expiration. The expiration time can be configured with the
688 "heartbeat" parameter.
690 On some motherboards the driver may fail to reset the chipset's
691 NO_REBOOT flag which prevents the watchdog from rebooting the
692 machine. If this is the case you will get a kernel message like
693 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
695 To compile this driver as a module, choose M here: the
696 module will be called nv_tco.
699 tristate "RDC R-321x SoC watchdog"
700 depends on X86_RDC321X
702 This is the driver for the built in hardware watchdog
703 in the RDC R-321x SoC.
705 To compile this driver as a module, choose M here: the
706 module will be called rdc321x_wdt.
709 tristate "SBC-60XX Watchdog Timer"
712 This driver can be used with the watchdog timer found on some
713 single board computers, namely the 6010 PII based computer.
714 It may well work with other cards. It reads port 0x443 to enable
715 and re-set the watchdog timer, and reads port 0x45 to disable
716 the watchdog. If you have a card that behave in similar ways,
717 you can probably make this driver work with your card as well.
719 You can compile this driver directly into the kernel, or use
720 it as a module. The module will be called sbc60xxwdt.
723 tristate "SBC8360 Watchdog Timer"
727 This is the driver for the hardware watchdog on the SBC8360 Single
728 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
730 To compile this driver as a module, choose M here: the
731 module will be called sbc8360.
733 Most people will say N.
736 tristate "SBC Nano 7240 Watchdog Timer"
737 depends on X86_32 && !UML
739 This is the driver for the hardware watchdog found on the IEI
740 single board computers EPIC Nano 7240 (and likely others). This
741 watchdog simply watches your kernel to make sure it doesn't freeze,
742 and if it does, it reboots your computer after a certain amount of
745 To compile this driver as a module, choose M here: the
746 module will be called sbc7240_wdt.
749 tristate "SMA CPU5 Watchdog"
753 To compile this driver as a module, choose M here: the
754 module will be called cpu5wdt.
756 config SMSC_SCH311X_WDT
757 tristate "SMSC SCH311X Watchdog Timer"
760 This is the driver for the hardware watchdog timer on the
761 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
762 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
765 To compile this driver as a module, choose M here: the
766 module will be called sch311x_wdt.
768 config SMSC37B787_WDT
769 tristate "Winbond SMsC37B787 Watchdog Timer"
772 This is the driver for the hardware watchdog component on the
773 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
774 from Vision Systems and maybe others.
776 This watchdog simply watches your kernel to make sure it doesn't
777 freeze, and if it does, it reboots your computer after a certain
780 Usually a userspace daemon will notify the kernel WDT driver that
781 userspace is still alive, at regular intervals.
783 To compile this driver as a module, choose M here: the
784 module will be called smsc37b787_wdt.
786 Most people will say N.
789 tristate "VIA Watchdog Timer"
793 This is the driver for the hardware watchdog timer on VIA
794 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
796 To compile this driver as a module, choose M here; the module
797 will be called via_wdt.
799 Most people will say N.
802 tristate "W83627HF/W83627DHG Watchdog Timer"
805 This is the driver for the hardware watchdog on the W83627HF chipset
806 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
807 (and likely others). The driver also supports the W83627DHG chip.
808 This watchdog simply watches your kernel to make sure it doesn't
809 freeze, and if it does, it reboots your computer after a certain
812 To compile this driver as a module, choose M here: the
813 module will be called w83627hf_wdt.
815 Most people will say N.
818 tristate "W83697HF/W83697HG Watchdog Timer"
821 This is the driver for the hardware watchdog on the W83697HF/HG
822 chipset as used in Dedibox/VIA motherboards (and likely others).
823 This watchdog simply watches your kernel to make sure it doesn't
824 freeze, and if it does, it reboots your computer after a certain
827 To compile this driver as a module, choose M here: the
828 module will be called w83697hf_wdt.
830 Most people will say N.
833 tristate "W83697UG/W83697UF Watchdog Timer"
836 This is the driver for the hardware watchdog on the W83697UG/UF
837 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
838 This watchdog simply watches your kernel to make sure it doesn't
839 freeze, and if it does, it reboots your computer after a certain
842 To compile this driver as a module, choose M here: the
843 module will be called w83697ug_wdt.
845 Most people will say N.
848 tristate "W83877F (EMACS) Watchdog Timer"
851 This is the driver for the hardware watchdog on the W83877F chipset
852 as used in EMACS PC-104 motherboards (and likely others). This
853 watchdog simply watches your kernel to make sure it doesn't freeze,
854 and if it does, it reboots your computer after a certain amount of
857 To compile this driver as a module, choose M here: the
858 module will be called w83877f_wdt.
860 Most people will say N.
863 tristate "W83977F (PCM-5335) Watchdog Timer"
866 This is the driver for the hardware watchdog on the W83977F I/O chip
867 as used in AAEON's PCM-5335 SBC (and likely others). This
868 watchdog simply watches your kernel to make sure it doesn't freeze,
869 and if it does, it reboots your computer after a certain amount of
872 To compile this driver as a module, choose M here: the
873 module will be called w83977f_wdt.
876 tristate "ZF MachZ Watchdog"
879 If you are using a ZF Micro MachZ processor, say Y here, otherwise
880 N. This is the driver for the watchdog timer built-in on that
881 processor using ZF-Logic interface. This watchdog simply watches
882 your kernel to make sure it doesn't freeze, and if it does, it
883 reboots your computer after a certain amount of time.
885 To compile this driver as a module, choose M here: the
886 module will be called machzwd.
888 config SBC_EPX_C3_WATCHDOG
889 tristate "Winsystems SBC EPX-C3 watchdog"
892 This is the driver for the built-in watchdog timer on the EPX-C3
893 Single-board computer made by Winsystems, Inc.
895 *Note*: This hardware watchdog is not probeable and thus there
896 is no way to know if writing to its IO address will corrupt
897 your system or have any real effect. The only way to be sure
898 that this driver does what you want is to make sure you
899 are running it on an EPX-C3 from Winsystems with the watchdog
900 timer at IO address 0x1ee and 0x1ef. It will write to both those
901 IO ports. Basically, the assumption is made that if you compile
902 this driver into your kernel and/or load it as a module, that you
903 know what you are doing and that you are in fact running on an
906 To compile this driver as a module, choose M here: the
907 module will be called sbc_epx_c3.
913 config M54xx_WATCHDOG
914 tristate "MCF54xx watchdog support"
917 To compile this driver as a module, choose M here: the
918 module will be called m54xx_wdt.
920 # MicroBlaze Architecture
922 config XILINX_WATCHDOG
923 tristate "Xilinx Watchdog timer"
924 depends on MICROBLAZE
926 Watchdog driver for the xps_timebase_wdt ip core.
928 IMPORTANT: The xps_timebase_wdt parent must have the property
929 "clock-frequency" at device tree.
931 To compile this driver as a module, choose M here: the
932 module will be called of_xilinx_wdt.
937 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
940 Hardware driver for the built-in watchdog timer on the Atheros
941 AR71XX/AR724X/AR913X SoCs.
944 tristate "Broadcom BCM47xx Watchdog Timer"
947 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
950 tristate "IDT RC32434 SoC Watchdog Timer"
951 depends on MIKROTIK_RB532
953 Hardware driver for the IDT RC32434 SoC built-in
956 To compile this driver as a module, choose M here: the
957 module will be called rc32434_wdt.
960 tristate "Indy/I2 Hardware Watchdog"
961 depends on SGI_HAS_INDYDOG
963 Hardware driver for the Indy's/I2's watchdog. This is a
964 watchdog timer that will reboot the machine after a 60 second
965 timer expired and no process has written to /dev/watchdog during
969 tristate "Ingenic jz4740 SoC hardware watchdog"
970 depends on MACH_JZ4740
973 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
976 tristate "MTX-1 Hardware Watchdog"
979 Hardware driver for the MTX-1 boards. This is a watchdog timer that
980 will reboot the machine after a 100 seconds timer expired.
983 tristate "PNX833x Hardware Watchdog"
984 depends on SOC_PNX8335
986 Hardware driver for the PNX833x's watchdog. This is a
987 watchdog timer that will reboot the machine after a programmable
988 timer has expired and no process has written to /dev/watchdog during
992 tristate "Sibyte SoC hardware watchdog"
995 Watchdog driver for the built in watchdog hardware in Sibyte
996 SoC processors. There are apparently two watchdog timers
997 on such processors; this driver supports only the first one,
998 because currently Linux only supports exporting one watchdog
1001 To compile this driver as a loadable module, choose M here.
1002 The module will be called sb_wdog.
1005 tristate "TI AR7 Watchdog Timer"
1008 Hardware driver for the TI AR7 Watchdog Timer.
1011 tristate "Toshiba TXx9 Watchdog Timer"
1012 depends on CPU_TX39XX || CPU_TX49XX
1013 select WATCHDOG_CORE
1015 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1018 tristate "Cavium OCTEON SOC family Watchdog Timer"
1019 depends on CPU_CAVIUM_OCTEON
1021 select EXPORT_UASM if OCTEON_WDT = m
1023 Hardware driver for OCTEON's on chip watchdog timer.
1024 Enables the watchdog for all cores running Linux. It
1025 installs a NMI handler and pokes the watchdog based on an
1026 interrupt. On first expiration of the watchdog, the
1027 interrupt handler pokes it. The second expiration causes an
1028 NMI that prints a message. The third expiration causes a
1031 When userspace has /dev/watchdog open, no poking is done
1032 from the first interrupt, it is then only poked when the
1036 tristate "Broadcom BCM63xx hardware watchdog"
1039 Watchdog driver for the built in watchdog hardware in Broadcom
1042 To compile this driver as a loadable module, choose M here.
1043 The module will be called bcm63xx_wdt.
1046 tristate "Lantiq SoC watchdog"
1049 Hardware driver for the Lantiq SoC Watchdog Timer.
1051 # PARISC Architecture
1053 # POWERPC Architecture
1056 tristate "GE Watchdog Timer"
1059 Watchdog timer found in a number of GE single board computers.
1062 bool "MPC52xx Watchdog Timer"
1063 depends on PPC_MPC52xx
1065 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1068 tristate "MPC8xxx Platform Watchdog Timer"
1069 depends on PPC_8xx || PPC_83xx || PPC_86xx
1071 This driver is for a SoC level watchdog that exists on some
1072 Freescale PowerPC processors. So far this driver supports:
1077 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1080 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1084 tristate "PIKA FPGA Watchdog"
1088 This enables the watchdog in the PIKA FPGA. Currently used on
1092 tristate "PowerPC Book-E Watchdog Timer"
1093 depends on BOOKE || 4xx
1095 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1096 MPC85xx SOCs and the IBM PowerPC 440.
1098 Please see Documentation/watchdog/watchdog-api.txt for
1101 config BOOKE_WDT_DEFAULT_TIMEOUT
1102 int "PowerPC Book-E Watchdog Timer Default Timeout"
1103 depends on BOOKE_WDT
1104 default 38 if FSL_BOOKE
1105 range 0 63 if FSL_BOOKE
1106 default 3 if !FSL_BOOKE
1107 range 0 3 if !FSL_BOOKE
1109 Select the default watchdog timer period to be used by the PowerPC
1110 Book-E watchdog driver. A watchdog "event" occurs when the bit
1111 position represented by this number transitions from zero to one.
1113 For Freescale Book-E processors, this is a number between 0 and 63.
1114 For other Book-E processors, this is a number between 0 and 3.
1116 The value can be overridden by the wdt_period command-line parameter.
1118 # PPC64 Architecture
1120 config WATCHDOG_RTAS
1121 tristate "RTAS watchdog"
1124 This driver adds watchdog support for the RTAS watchdog.
1126 To compile this driver as a module, choose M here. The module
1127 will be called wdrtas.
1132 tristate "z/VM Watchdog Timer"
1135 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1136 provide a virtual watchdog timer to their guest that cause a
1137 user define Control Program command to be executed after a
1140 To compile this driver as a module, choose M here. The module
1141 will be called vmwatchdog.
1143 # SUPERH (sh + sh64) Architecture
1146 tristate "SuperH Watchdog"
1147 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1149 This driver adds watchdog support for the integrated watchdog in the
1150 SuperH processors. If you have one of these processors and wish
1151 to have watchdog support enabled, say Y, otherwise say N.
1153 As a side note, saying Y here will automatically boost HZ to 1000
1154 so that the timer has a chance to clear the overflow counter. On
1155 slower systems (such as the SH-2 and SH-3) this will likely yield
1156 some performance issues. As such, the WDT should be avoided here
1157 unless it is absolutely necessary.
1159 To compile this driver as a module, choose M here: the
1160 module will be called shwdt.
1162 # SPARC Architecture
1164 # SPARC64 Architecture
1166 config WATCHDOG_CP1XXX
1167 tristate "CP1XXX Hardware Watchdog support"
1168 depends on SPARC64 && PCI
1170 This is the driver for the hardware watchdog timers present on
1171 Sun Microsystems CompactPCI models CP1400 and CP1500.
1173 To compile this driver as a module, choose M here: the
1174 module will be called cpwatchdog.
1176 If you do not have a CompactPCI model CP1400 or CP1500, or
1177 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1178 you should say N to this option.
1181 tristate "RIO Hardware Watchdog support"
1182 depends on SPARC64 && PCI
1184 Say Y here to support the hardware watchdog capability on Sun RIO
1185 machines. The watchdog timeout period is normally one minute but
1186 can be changed with a boot-time parameter.
1188 # XTENSA Architecture
1193 tristate "Xen Watchdog support"
1196 Say Y here to support the hypervisor watchdog capability provided
1197 by Xen 4.0 and newer. The watchdog timeout period is normally one
1198 minute but can be changed with a boot-time parameter.
1201 tristate "UML watchdog"
1205 # ISA-based Watchdog Cards
1208 comment "ISA-based Watchdog Cards"
1212 tristate "Berkshire Products ISA-PC Watchdog"
1215 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1216 This card simply watches your kernel to make sure it doesn't freeze,
1217 and if it does, it reboots your computer after a certain amount of
1218 time. This driver is like the WDT501 driver but for different
1219 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1220 watchdog cards can be ordered from <http://www.berkprod.com/>.
1222 To compile this driver as a module, choose M here: the
1223 module will be called pcwd.
1225 Most people will say N.
1228 tristate "Mixcom Watchdog"
1231 This is a driver for the Mixcom hardware watchdog cards. This
1232 watchdog simply watches your kernel to make sure it doesn't freeze,
1233 and if it does, it reboots your computer after a certain amount of
1236 To compile this driver as a module, choose M here: the
1237 module will be called mixcomwd.
1239 Most people will say N.
1242 tristate "WDT Watchdog timer"
1245 If you have a WDT500P or WDT501P watchdog board, say Y here,
1246 otherwise N. It is not possible to probe for this board, which means
1247 that you have to inform the kernel about the IO port and IRQ that
1248 is needed (you can do this via the io and irq parameters)
1250 To compile this driver as a module, choose M here: the
1251 module will be called wdt.
1254 # PCI-based Watchdog Cards
1257 comment "PCI-based Watchdog Cards"
1260 config PCIPCWATCHDOG
1261 tristate "Berkshire Products PCI-PC Watchdog"
1264 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1265 This card simply watches your kernel to make sure it doesn't freeze,
1266 and if it does, it reboots your computer after a certain amount of
1267 time. The card can also monitor the internal temperature of the PC.
1268 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1270 To compile this driver as a module, choose M here: the
1271 module will be called pcwd_pci.
1273 Most people will say N.
1276 tristate "PCI-WDT500/501 Watchdog timer"
1279 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1281 If you have a PCI-WDT501 watchdog board then you can enable the
1282 temperature sensor by setting the type parameter to 501.
1284 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1285 can do this via the tachometer parameter. Only do this if you have a
1286 fan tachometer actually set up.
1288 To compile this driver as a module, choose M here: the
1289 module will be called wdt_pci.
1292 # USB-based Watchdog Cards
1295 comment "USB-based Watchdog Cards"
1298 config USBPCWATCHDOG
1299 tristate "Berkshire Products USB-PC Watchdog"
1302 This is the driver for the Berkshire Products USB-PC Watchdog card.
1303 This card simply watches your kernel to make sure it doesn't freeze,
1304 and if it does, it reboots your computer after a certain amount of
1305 time. The card can also monitor the internal temperature of the PC.
1306 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1308 To compile this driver as a module, choose M here: the
1309 module will be called pcwd_usb.
1311 Most people will say N.