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 IXP2000_WATCHDOG
133 tristate "IXP2000 Watchdog"
134 depends on ARCH_IXP2000
136 Say Y here if to include support for the watchdog timer
137 in the Intel IXP2000(2400, 2800, 2850) network processors.
138 This driver can be built as a module by choosing M. The module
139 will be called ixp2000_wdt.
141 Say N if you are unsure.
143 config IXP4XX_WATCHDOG
144 tristate "IXP4xx Watchdog"
145 depends on ARCH_IXP4XX
147 Say Y here if to include support for the watchdog timer
148 in the Intel IXP4xx network processors. This driver can
149 be built as a module by choosing M. The module will
150 be called ixp4xx_wdt.
152 Note: The internal IXP4xx watchdog does a soft CPU reset
153 which doesn't reset any peripherals. There are circumstances
154 where the watchdog will fail to reset the board correctly
155 (e.g., if the boot ROM is in an unreadable state).
157 Say N if you are unsure.
159 config KS8695_WATCHDOG
160 tristate "KS8695 watchdog"
161 depends on ARCH_KS8695
163 Watchdog timer embedded into KS8695 processor. This will reboot your
164 system when the timeout is reached.
166 config HAVE_S3C2410_WATCHDOG
169 This will include watchdog timer support for Samsung SoCs. If
170 you want to include watchdog support for any machine, kindly
171 select this in the respective mach-XXXX/Kconfig file.
173 config S3C2410_WATCHDOG
174 tristate "S3C2410 Watchdog"
175 depends on HAVE_S3C2410_WATCHDOG
178 Watchdog timer block in the Samsung SoCs. This will reboot
179 the system when the timer expires with the watchdog enabled.
181 The driver is limited by the speed of the system's PCLK
182 signal, so with reasonably fast systems (PCLK around 50-66MHz)
183 then watchdog intervals of over approximately 20seconds are
186 The driver can be built as a module by choosing M, and will
187 be called s3c2410_wdt
189 config SA1100_WATCHDOG
190 tristate "SA1100/PXA2xx watchdog"
191 depends on ARCH_SA1100 || ARCH_PXA
193 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
194 reboot your system when timeout is reached.
196 NOTE: once enabled, this timer cannot be disabled.
198 To compile this driver as a module, choose M here: the
199 module will be called sa1100_wdt.
202 tristate "Synopsys DesignWare watchdog"
203 depends on ARM && HAVE_CLK
205 Say Y here if to include support for the Synopsys DesignWare
206 watchdog timer found in many ARM chips.
207 To compile this driver as a module, choose M here: the
208 module will be called dw_wdt.
210 config MPCORE_WATCHDOG
211 tristate "MPcore watchdog"
212 depends on HAVE_ARM_TWD
214 Watchdog timer embedded into the MPcore system.
216 To compile this driver as a module, choose M here: the
217 module will be called mpcore_wdt.
219 config EP93XX_WATCHDOG
220 tristate "EP93xx Watchdog"
221 depends on ARCH_EP93XX
224 Say Y here if to include support for the watchdog timer
225 embedded in the Cirrus Logic EP93xx family of devices.
227 To compile this driver as a module, choose M here: the
228 module will be called ep93xx_wdt.
231 tristate "OMAP Watchdog"
232 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
234 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
235 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
237 config PNX4008_WATCHDOG
238 tristate "PNX4008 and LPC32XX Watchdog"
239 depends on ARCH_PNX4008 || ARCH_LPC32XX
242 Say Y here if to include support for the watchdog timer
243 in the PNX4008 or LPC32XX processor.
244 This driver can be built as a module by choosing M. The module
245 will be called pnx4008_wdt.
247 Say N if you are unsure.
250 tristate "IOP Watchdog"
252 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
254 Say Y here if to include support for the watchdog timer
255 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
256 be built as a module by choosing M. The module will
259 Note: The IOP13XX watchdog does an Internal Bus Reset which will
260 affect both cores and the peripherals of the IOP. The ATU-X
261 and/or ATUe configuration registers will remain intact, but if
262 operating as an Root Complex and/or Central Resource, the PCI-X
263 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
265 config DAVINCI_WATCHDOG
266 tristate "DaVinci watchdog"
267 depends on ARCH_DAVINCI
269 Say Y here if to include support for the watchdog timer
270 in the DaVinci DM644x/DM646x processors.
271 To compile this driver as a module, choose M here: the
272 module will be called davinci_wdt.
274 NOTE: once enabled, this timer cannot be disabled.
275 Say N if you are unsure.
277 config ORION_WATCHDOG
278 tristate "Orion watchdog"
279 depends on ARCH_ORION5X || ARCH_KIRKWOOD
281 Say Y here if to include support for the watchdog timer
282 in the Marvell Orion5x and Kirkwood ARM SoCs.
283 To compile this driver as a module, choose M here: the
284 module will be called orion_wdt.
286 config COH901327_WATCHDOG
287 bool "ST-Ericsson COH 901 327 watchdog"
289 default y if MACH_U300
292 Say Y here to include Watchdog timer support for the
293 watchdog embedded into the ST-Ericsson U300 series platforms.
294 This watchdog is used to reset the system and thus cannot be
295 compiled as a module.
297 config TWL4030_WATCHDOG
298 tristate "TWL4030 Watchdog"
299 depends on TWL4030_CORE
301 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
302 watchdog timer support for TWL4030 chips.
304 config STMP3XXX_WATCHDOG
305 tristate "Freescale STMP3XXX watchdog"
306 depends on ARCH_STMP3XXX
308 Say Y here if to include support for the watchdog timer
309 for the Sigmatel STMP37XX/378X SoC.
310 To compile this driver as a module, choose M here: the
311 module will be called stmp3xxx_wdt.
313 config NUC900_WATCHDOG
314 tristate "Nuvoton NUC900 watchdog"
315 depends on ARCH_W90X900
317 Say Y here if to include support for the watchdog timer
318 for the Nuvoton NUC900 series SoCs.
319 To compile this driver as a module, choose M here: the
320 module will be called nuc900_wdt.
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
338 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
341 tristate "IMX2+ Watchdog"
342 depends on IMX_HAVE_PLATFORM_IMX2_WDT
344 This is the driver for the hardware watchdog
345 on the Freescale IMX2 and later processors.
346 If you have one of these processors and wish to have
347 watchdog support enabled, say Y, otherwise say N.
349 To compile this driver as a module, choose M here: the
350 module will be called imx2_wdt.
354 config AT32AP700X_WDT
355 tristate "AT32AP700x watchdog"
356 depends on CPU_AT32AP700X
358 Watchdog timer embedded into AT32AP700x devices. This will reboot
359 your system when the timeout is reached.
361 # BLACKFIN Architecture
364 tristate "Blackfin On-Chip Watchdog Timer"
367 If you say yes here you will get support for the Blackfin On-Chip
368 Watchdog Timer. If you have one of these processors and wish to
369 have watchdog support enabled, say Y, otherwise say N.
371 To compile this driver as a module, choose M here: the
372 module will be called bfin_wdt.
380 # X86 (i386 + ia64 + x86_64) Architecture
383 tristate "Acquire SBC Watchdog Timer"
386 This is the driver for the hardware watchdog on Single Board
387 Computers produced by Acquire Inc (and others). This watchdog
388 simply watches your kernel to make sure it doesn't freeze, and if
389 it does, it reboots your computer after a certain amount of time.
391 To compile this driver as a module, choose M here: the
392 module will be called acquirewdt.
394 Most people will say N.
397 tristate "Advantech SBC Watchdog Timer"
400 If you are configuring a Linux kernel for the Advantech single-board
401 computer, say `Y' here to support its built-in watchdog timer
402 feature. More information can be found at
403 <http://www.advantech.com.tw/products/>
406 tristate "ALi M1535 PMU Watchdog Timer"
407 depends on X86 && PCI
409 This is the driver for the hardware watchdog on the ALi M1535 PMU.
411 To compile this driver as a module, choose M here: the
412 module will be called alim1535_wdt.
414 Most people will say N.
417 tristate "ALi M7101 PMU Computer Watchdog"
420 This is the driver for the hardware watchdog on the ALi M7101 PMU
421 as used in the x86 Cobalt servers and also found in some
422 SPARC Netra servers too.
424 To compile this driver as a module, choose M here: the
425 module will be called alim7101_wdt.
427 Most people will say N.
430 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
431 depends on X86 && EXPERIMENTAL
433 This is the driver for the hardware watchdog on the Fintek
434 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
436 You can compile this driver directly into the kernel, or use
437 it as a module. The module will be called f71808e_wdt.
440 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
441 depends on X86 && PCI
443 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
444 (Total Cost of Ownership) timer is a watchdog timer that will reboot
445 the machine after its expiration. The expiration time can be
446 configured with the "heartbeat" parameter.
448 To compile this driver as a module, choose M here: the
449 module will be called sp5100_tco.
452 tristate "AMD Geode CS5535/CS5536 Watchdog"
453 depends on CS5535_MFGPT
455 This driver enables a watchdog capability built into the
456 CS5535/CS5536 companion chips for the AMD Geode GX and LX
457 processors. This watchdog watches your kernel to make sure
458 it doesn't freeze, and if it does, it reboots your computer after
459 a certain amount of time.
461 You can compile this driver directly into the kernel, or use
462 it as a module. The module will be called geodewdt.
465 tristate "AMD Elan SC520 processor Watchdog"
468 This is the driver for the hardware watchdog built in to the
469 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
470 This watchdog simply watches your kernel to make sure it doesn't
471 freeze, and if it does, it reboots your computer after a certain
474 You can compile this driver directly into the kernel, or use
475 it as a module. The module will be called sc520_wdt.
477 config SBC_FITPC2_WATCHDOG
478 tristate "Compulab SBC-FITPC2 watchdog"
481 This is the driver for the built-in watchdog timer on the fit-PC2,
482 fit-PC2i, CM-iAM single-board computers made by Compulab.
484 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
485 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
487 Entering BIOS setup temporary disables watchdog operation regardless to current state,
488 so system will not be restarted while user in BIOS setup.
490 Once watchdog was enabled the system will be restarted every
491 "Watchdog Timer Value" period, so to prevent it user can restart or
492 disable the watchdog.
494 To compile this driver as a module, choose M here: the
495 module will be called sbc_fitpc2_wdt.
497 Most people will say N.
500 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
503 Enable support for the watchdog timer on the Eurotech CPU-1220 and
504 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
505 information are at <http://www.eurotech.it/>.
508 tristate "IB700 SBC Watchdog Timer"
511 This is the driver for the hardware watchdog on the IB700 Single
512 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
513 simply watches your kernel to make sure it doesn't freeze, and if
514 it does, it reboots your computer after a certain amount of time.
516 This driver is like the WDT501 driver but for slightly different hardware.
518 To compile this driver as a module, choose M here: the
519 module will be called ib700wdt.
521 Most people will say N.
524 tristate "IBM Automatic Server Restart"
527 This is the driver for the IBM Automatic Server Restart watchdog
528 timer built-in into some eServer xSeries machines.
530 To compile this driver as a module, choose M here: the
531 module will be called ibmasr.
534 tristate "ICP Single Board Computer Watchdog Timer"
537 This is a driver for the hardware watchdog on the ICP Single
538 Board Computer. This driver is working on (at least) the following
539 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
541 To compile this driver as a module, choose M here: the
542 module will be called wafer5823wdt.
545 tristate "Intel 6300ESB Timer/Watchdog"
546 depends on X86 && PCI
548 Hardware driver for the watchdog timer built into the Intel
549 6300ESB controller hub.
551 To compile this driver as a module, choose M here: the
552 module will be called i6300esb.
554 config INTEL_SCU_WATCHDOG
555 bool "Intel SCU Watchdog for Mobile Platforms"
558 Hardware driver for the watchdog time built into the Intel SCU
559 for Intel Mobile Platforms.
561 To compile this driver as a module, choose M here.
564 tristate "Intel TCO Timer/Watchdog"
565 depends on (X86 || IA64) && PCI
567 Hardware driver for the intel TCO timer based watchdog devices.
568 These drivers are included in the Intel 82801 I/O Controller
569 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
572 The TCO (Total Cost of Ownership) timer is a watchdog timer
573 that will reboot the machine after its second expiration. The
574 expiration time can be configured with the "heartbeat" parameter.
576 On some motherboards the driver may fail to reset the chipset's
577 NO_REBOOT flag which prevents the watchdog from rebooting the
578 machine. If this is the case you will get a kernel message like
579 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
581 To compile this driver as a module, choose M here: the
582 module will be called iTCO_wdt.
584 config ITCO_VENDOR_SUPPORT
585 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
588 Add vendor specific support to the intel TCO timer based watchdog
589 devices. At this moment we only have additional support for some
590 SuperMicro Inc. motherboards.
593 tristate "IT8712F (Smart Guardian) Watchdog Timer"
596 This is the driver for the built-in watchdog timer on the IT8712F
597 Super I/0 chipset used on many motherboards.
599 If the driver does not work, then make sure that the game port in
602 To compile this driver as a module, choose M here: the
603 module will be called it8712f_wdt.
606 tristate "IT87 Watchdog Timer"
607 depends on X86 && EXPERIMENTAL
609 This is the driver for the hardware watchdog on the ITE IT8702,
610 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
611 This watchdog simply watches your kernel to make sure it doesn't
612 freeze, and if it does, it reboots your computer after a certain
615 To compile this driver as a module, choose M here: the module will
619 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
620 depends on X86 && PCI
622 A software monitoring watchdog and NMI sourcing driver. This driver
623 will detect lockups and provide a stack trace. This is a driver that
624 will only load on an HP ProLiant system with a minimum of iLO2 support.
625 To compile this driver as a module, choose M here: the module will be
628 config HPWDT_NMI_DECODING
629 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
630 depends on HP_WATCHDOG
633 When an NMI occurs this feature will make the necessary BIOS calls to
634 log the cause of the NMI.
637 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
640 This is a driver for National Semiconductor PC87307/PC97307 hardware
641 watchdog cards as found on the SC1200. This watchdog is mainly used
642 for power management purposes and can be used to power down the device
643 during inactivity periods (includes interrupt activity monitoring).
645 To compile this driver as a module, choose M here: the
646 module will be called sc1200wdt.
648 Most people will say N.
651 tristate "National Semiconductor SCx200 Watchdog"
652 depends on SCx200 && PCI
654 Enable the built-in watchdog timer support on the National
655 Semiconductor SCx200 processors.
657 If compiled as a module, it will be called scx200_wdt.
660 tristate "NS PC87413 watchdog"
663 This is the driver for the hardware watchdog on the PC87413 chipset
664 This watchdog simply watches your kernel to make sure it doesn't
665 freeze, and if it does, it reboots your computer after a certain
668 To compile this driver as a module, choose M here: the
669 module will be called pc87413_wdt.
671 Most people will say N.
674 tristate "nVidia TCO Timer/Watchdog"
675 depends on X86 && PCI
677 Hardware driver for the TCO timer built into the nVidia Hub family
678 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
679 watchdog timer that will reboot the machine after its second
680 expiration. The expiration time can be configured with the
681 "heartbeat" parameter.
683 On some motherboards the driver may fail to reset the chipset's
684 NO_REBOOT flag which prevents the watchdog from rebooting the
685 machine. If this is the case you will get a kernel message like
686 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
688 To compile this driver as a module, choose M here: the
689 module will be called nv_tco.
692 tristate "RDC R-321x SoC watchdog"
693 depends on X86_RDC321X
695 This is the driver for the built in hardware watchdog
696 in the RDC R-321x SoC.
698 To compile this driver as a module, choose M here: the
699 module will be called rdc321x_wdt.
702 tristate "SBC-60XX Watchdog Timer"
705 This driver can be used with the watchdog timer found on some
706 single board computers, namely the 6010 PII based computer.
707 It may well work with other cards. It reads port 0x443 to enable
708 and re-set the watchdog timer, and reads port 0x45 to disable
709 the watchdog. If you have a card that behave in similar ways,
710 you can probably make this driver work with your card as well.
712 You can compile this driver directly into the kernel, or use
713 it as a module. The module will be called sbc60xxwdt.
716 tristate "SBC8360 Watchdog Timer"
720 This is the driver for the hardware watchdog on the SBC8360 Single
721 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
723 To compile this driver as a module, choose M here: the
724 module will be called sbc8360.
726 Most people will say N.
729 tristate "SBC Nano 7240 Watchdog Timer"
730 depends on X86_32 && !UML
732 This is the driver for the hardware watchdog found on the IEI
733 single board computers EPIC Nano 7240 (and likely others). This
734 watchdog simply watches your kernel to make sure it doesn't freeze,
735 and if it does, it reboots your computer after a certain amount of
738 To compile this driver as a module, choose M here: the
739 module will be called sbc7240_wdt.
742 tristate "SMA CPU5 Watchdog"
746 To compile this driver as a module, choose M here: the
747 module will be called cpu5wdt.
749 config SMSC_SCH311X_WDT
750 tristate "SMSC SCH311X Watchdog Timer"
753 This is the driver for the hardware watchdog timer on the
754 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
755 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
758 To compile this driver as a module, choose M here: the
759 module will be called sch311x_wdt.
761 config SMSC37B787_WDT
762 tristate "Winbond SMsC37B787 Watchdog Timer"
765 This is the driver for the hardware watchdog component on the
766 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
767 from Vision Systems and maybe others.
769 This watchdog simply watches your kernel to make sure it doesn't
770 freeze, and if it does, it reboots your computer after a certain
773 Usually a userspace daemon will notify the kernel WDT driver that
774 userspace is still alive, at regular intervals.
776 To compile this driver as a module, choose M here: the
777 module will be called smsc37b787_wdt.
779 Most people will say N.
782 tristate "VIA Watchdog Timer"
786 This is the driver for the hardware watchdog timer on VIA
787 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
789 To compile this driver as a module, choose M here; the module
790 will be called via_wdt.
792 Most people will say N.
795 tristate "W83627HF/W83627DHG Watchdog Timer"
798 This is the driver for the hardware watchdog on the W83627HF chipset
799 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
800 (and likely others). The driver also supports the W83627DHG chip.
801 This watchdog simply watches your kernel to make sure it doesn't
802 freeze, and if it does, it reboots your computer after a certain
805 To compile this driver as a module, choose M here: the
806 module will be called w83627hf_wdt.
808 Most people will say N.
811 tristate "W83697HF/W83697HG Watchdog Timer"
814 This is the driver for the hardware watchdog on the W83697HF/HG
815 chipset as used in Dedibox/VIA motherboards (and likely others).
816 This watchdog simply watches your kernel to make sure it doesn't
817 freeze, and if it does, it reboots your computer after a certain
820 To compile this driver as a module, choose M here: the
821 module will be called w83697hf_wdt.
823 Most people will say N.
826 tristate "W83697UG/W83697UF Watchdog Timer"
829 This is the driver for the hardware watchdog on the W83697UG/UF
830 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
831 This watchdog simply watches your kernel to make sure it doesn't
832 freeze, and if it does, it reboots your computer after a certain
835 To compile this driver as a module, choose M here: the
836 module will be called w83697ug_wdt.
838 Most people will say N.
841 tristate "W83877F (EMACS) Watchdog Timer"
844 This is the driver for the hardware watchdog on the W83877F chipset
845 as used in EMACS PC-104 motherboards (and likely others). This
846 watchdog simply watches your kernel to make sure it doesn't freeze,
847 and if it does, it reboots your computer after a certain amount of
850 To compile this driver as a module, choose M here: the
851 module will be called w83877f_wdt.
853 Most people will say N.
856 tristate "W83977F (PCM-5335) Watchdog Timer"
859 This is the driver for the hardware watchdog on the W83977F I/O chip
860 as used in AAEON's PCM-5335 SBC (and likely others). This
861 watchdog simply watches your kernel to make sure it doesn't freeze,
862 and if it does, it reboots your computer after a certain amount of
865 To compile this driver as a module, choose M here: the
866 module will be called w83977f_wdt.
869 tristate "ZF MachZ Watchdog"
872 If you are using a ZF Micro MachZ processor, say Y here, otherwise
873 N. This is the driver for the watchdog timer built-in on that
874 processor using ZF-Logic interface. This watchdog simply watches
875 your kernel to make sure it doesn't freeze, and if it does, it
876 reboots your computer after a certain amount of time.
878 To compile this driver as a module, choose M here: the
879 module will be called machzwd.
881 config SBC_EPX_C3_WATCHDOG
882 tristate "Winsystems SBC EPX-C3 watchdog"
885 This is the driver for the built-in watchdog timer on the EPX-C3
886 Single-board computer made by Winsystems, Inc.
888 *Note*: This hardware watchdog is not probeable and thus there
889 is no way to know if writing to its IO address will corrupt
890 your system or have any real effect. The only way to be sure
891 that this driver does what you want is to make sure you
892 are running it on an EPX-C3 from Winsystems with the watchdog
893 timer at IO address 0x1ee and 0x1ef. It will write to both those
894 IO ports. Basically, the assumption is made that if you compile
895 this driver into your kernel and/or load it as a module, that you
896 know what you are doing and that you are in fact running on an
899 To compile this driver as a module, choose M here: the
900 module will be called sbc_epx_c3.
906 config M54xx_WATCHDOG
907 tristate "MCF54xx watchdog support"
910 To compile this driver as a module, choose M here: the
911 module will be called m54xx_wdt.
913 # MicroBlaze Architecture
915 config XILINX_WATCHDOG
916 tristate "Xilinx Watchdog timer"
917 depends on MICROBLAZE
919 Watchdog driver for the xps_timebase_wdt ip core.
921 IMPORTANT: The xps_timebase_wdt parent must have the property
922 "clock-frequency" at device tree.
924 To compile this driver as a module, choose M here: the
925 module will be called of_xilinx_wdt.
930 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
933 Hardware driver for the built-in watchdog timer on the Atheros
934 AR71XX/AR724X/AR913X SoCs.
937 tristate "Broadcom BCM47xx Watchdog Timer"
940 Hardware driver for the Broadcom BCM47xx Watchog Timer.
943 tristate "IDT RC32434 SoC Watchdog Timer"
944 depends on MIKROTIK_RB532
946 Hardware driver for the IDT RC32434 SoC built-in
949 To compile this driver as a module, choose M here: the
950 module will be called rc32434_wdt.
953 tristate "Indy/I2 Hardware Watchdog"
954 depends on SGI_HAS_INDYDOG
956 Hardware driver for the Indy's/I2's watchdog. This is a
957 watchdog timer that will reboot the machine after a 60 second
958 timer expired and no process has written to /dev/watchdog during
962 tristate "Ingenic jz4740 SoC hardware watchdog"
963 depends on MACH_JZ4740
966 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
969 tristate "MTX-1 Hardware Watchdog"
972 Hardware driver for the MTX-1 boards. This is a watchdog timer that
973 will reboot the machine after a 100 seconds timer expired.
976 tristate "PNX833x Hardware Watchdog"
977 depends on SOC_PNX8335
979 Hardware driver for the PNX833x's watchdog. This is a
980 watchdog timer that will reboot the machine after a programmable
981 timer has expired and no process has written to /dev/watchdog during
985 tristate "Sibyte SoC hardware watchdog"
988 Watchdog driver for the built in watchdog hardware in Sibyte
989 SoC processors. There are apparently two watchdog timers
990 on such processors; this driver supports only the first one,
991 because currently Linux only supports exporting one watchdog
994 To compile this driver as a loadable module, choose M here.
995 The module will be called sb_wdog.
998 tristate "TI AR7 Watchdog Timer"
1001 Hardware driver for the TI AR7 Watchdog Timer.
1004 tristate "Toshiba TXx9 Watchdog Timer"
1005 depends on CPU_TX39XX || CPU_TX49XX
1006 select WATCHDOG_CORE
1008 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1011 tristate "Cavium OCTEON SOC family Watchdog Timer"
1012 depends on CPU_CAVIUM_OCTEON
1014 select EXPORT_UASM if OCTEON_WDT = m
1016 Hardware driver for OCTEON's on chip watchdog timer.
1017 Enables the watchdog for all cores running Linux. It
1018 installs a NMI handler and pokes the watchdog based on an
1019 interrupt. On first expiration of the watchdog, the
1020 interrupt handler pokes it. The second expiration causes an
1021 NMI that prints a message. The third expiration causes a
1024 When userspace has /dev/watchdog open, no poking is done
1025 from the first interrupt, it is then only poked when the
1029 tristate "Broadcom BCM63xx hardware watchdog"
1032 Watchdog driver for the built in watchdog hardware in Broadcom
1035 To compile this driver as a loadable module, choose M here.
1036 The module will be called bcm63xx_wdt.
1039 tristate "Lantiq SoC watchdog"
1042 Hardware driver for the Lantiq SoC Watchdog Timer.
1044 # PARISC Architecture
1046 # POWERPC Architecture
1049 tristate "GE Watchdog Timer"
1052 Watchdog timer found in a number of GE single board computers.
1055 bool "MPC52xx Watchdog Timer"
1056 depends on PPC_MPC52xx
1058 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1061 tristate "MPC8xxx Platform Watchdog Timer"
1062 depends on PPC_8xx || PPC_83xx || PPC_86xx
1064 This driver is for a SoC level watchdog that exists on some
1065 Freescale PowerPC processors. So far this driver supports:
1070 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1073 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1077 tristate "PIKA FPGA Watchdog"
1081 This enables the watchdog in the PIKA FPGA. Currently used on
1085 tristate "PowerPC Book-E Watchdog Timer"
1086 depends on BOOKE || 4xx
1088 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1089 MPC85xx SOCs and the IBM PowerPC 440.
1091 Please see Documentation/watchdog/watchdog-api.txt for
1094 config BOOKE_WDT_DEFAULT_TIMEOUT
1095 int "PowerPC Book-E Watchdog Timer Default Timeout"
1096 depends on BOOKE_WDT
1097 default 38 if FSL_BOOKE
1098 range 0 63 if FSL_BOOKE
1099 default 3 if !FSL_BOOKE
1100 range 0 3 if !FSL_BOOKE
1102 Select the default watchdog timer period to be used by the PowerPC
1103 Book-E watchdog driver. A watchdog "event" occurs when the bit
1104 position represented by this number transitions from zero to one.
1106 For Freescale Book-E processors, this is a number between 0 and 63.
1107 For other Book-E processors, this is a number between 0 and 3.
1109 The value can be overridden by the wdt_period command-line parameter.
1111 # PPC64 Architecture
1113 config WATCHDOG_RTAS
1114 tristate "RTAS watchdog"
1117 This driver adds watchdog support for the RTAS watchdog.
1119 To compile this driver as a module, choose M here. The module
1120 will be called wdrtas.
1125 tristate "z/VM Watchdog Timer"
1128 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1129 provide a virtual watchdog timer to their guest that cause a
1130 user define Control Program command to be executed after a
1133 To compile this driver as a module, choose M here. The module
1134 will be called vmwatchdog.
1136 # SUPERH (sh + sh64) Architecture
1139 tristate "SuperH Watchdog"
1140 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1142 This driver adds watchdog support for the integrated watchdog in the
1143 SuperH processors. If you have one of these processors and wish
1144 to have watchdog support enabled, say Y, otherwise say N.
1146 As a side note, saying Y here will automatically boost HZ to 1000
1147 so that the timer has a chance to clear the overflow counter. On
1148 slower systems (such as the SH-2 and SH-3) this will likely yield
1149 some performance issues. As such, the WDT should be avoided here
1150 unless it is absolutely necessary.
1152 To compile this driver as a module, choose M here: the
1153 module will be called shwdt.
1155 # SPARC Architecture
1157 # SPARC64 Architecture
1159 config WATCHDOG_CP1XXX
1160 tristate "CP1XXX Hardware Watchdog support"
1161 depends on SPARC64 && PCI
1163 This is the driver for the hardware watchdog timers present on
1164 Sun Microsystems CompactPCI models CP1400 and CP1500.
1166 To compile this driver as a module, choose M here: the
1167 module will be called cpwatchdog.
1169 If you do not have a CompactPCI model CP1400 or CP1500, or
1170 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1171 you should say N to this option.
1174 tristate "RIO Hardware Watchdog support"
1175 depends on SPARC64 && PCI
1177 Say Y here to support the hardware watchdog capability on Sun RIO
1178 machines. The watchdog timeout period is normally one minute but
1179 can be changed with a boot-time parameter.
1181 # XTENSA Architecture
1186 tristate "Xen Watchdog support"
1189 Say Y here to support the hypervisor watchdog capability provided
1190 by Xen 4.0 and newer. The watchdog timeout period is normally one
1191 minute but can be changed with a boot-time parameter.
1194 tristate "UML watchdog"
1198 # ISA-based Watchdog Cards
1201 comment "ISA-based Watchdog Cards"
1205 tristate "Berkshire Products ISA-PC Watchdog"
1208 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1209 This card simply watches your kernel to make sure it doesn't freeze,
1210 and if it does, it reboots your computer after a certain amount of
1211 time. This driver is like the WDT501 driver but for different
1212 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1213 watchdog cards can be ordered from <http://www.berkprod.com/>.
1215 To compile this driver as a module, choose M here: the
1216 module will be called pcwd.
1218 Most people will say N.
1221 tristate "Mixcom Watchdog"
1224 This is a driver for the Mixcom hardware watchdog cards. This
1225 watchdog simply watches your kernel to make sure it doesn't freeze,
1226 and if it does, it reboots your computer after a certain amount of
1229 To compile this driver as a module, choose M here: the
1230 module will be called mixcomwd.
1232 Most people will say N.
1235 tristate "WDT Watchdog timer"
1238 If you have a WDT500P or WDT501P watchdog board, say Y here,
1239 otherwise N. It is not possible to probe for this board, which means
1240 that you have to inform the kernel about the IO port and IRQ that
1241 is needed (you can do this via the io and irq parameters)
1243 To compile this driver as a module, choose M here: the
1244 module will be called wdt.
1247 # PCI-based Watchdog Cards
1250 comment "PCI-based Watchdog Cards"
1253 config PCIPCWATCHDOG
1254 tristate "Berkshire Products PCI-PC Watchdog"
1257 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1258 This card simply watches your kernel to make sure it doesn't freeze,
1259 and if it does, it reboots your computer after a certain amount of
1260 time. The card can also monitor the internal temperature of the PC.
1261 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1263 To compile this driver as a module, choose M here: the
1264 module will be called pcwd_pci.
1266 Most people will say N.
1269 tristate "PCI-WDT500/501 Watchdog timer"
1272 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1274 If you have a PCI-WDT501 watchdog board then you can enable the
1275 temperature sensor by setting the type parameter to 501.
1277 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1278 can do this via the tachometer parameter. Only do this if you have a
1279 fan tachometer actually set up.
1281 To compile this driver as a module, choose M here: the
1282 module will be called wdt_pci.
1285 # USB-based Watchdog Cards
1288 comment "USB-based Watchdog Cards"
1291 config USBPCWATCHDOG
1292 tristate "Berkshire Products USB-PC Watchdog"
1295 This is the driver for the Berkshire Products USB-PC Watchdog card.
1296 This card simply watches your kernel to make sure it doesn't freeze,
1297 and if it does, it reboots your computer after a certain amount of
1298 time. The card can also monitor the internal temperature of the PC.
1299 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1301 To compile this driver as a module, choose M here: the
1302 module will be called pcwd_usb.
1304 Most people will say N.