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 DA9052_WATCHDOG
68 tristate "Dialog DA9052 Watchdog"
69 depends on PMIC_DA9052
72 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
75 Say Y here to include support for the DA9052 watchdog.
76 Alternatively say M to compile the driver as a module,
77 which will be called da9052_wdt.
79 config DA9055_WATCHDOG
80 tristate "Dialog Semiconductor DA9055 Watchdog"
84 If you say yes here you get support for watchdog on the Dialog
85 Semiconductor DA9055 PMIC.
87 This driver can also be built as a module. If so, the module
88 will be called da9055_wdt.
90 config WM831X_WATCHDOG
91 tristate "WM831x watchdog"
95 Support for the watchdog in the WM831x AudioPlus PMICs. When
96 the watchdog triggers the system will be reset.
98 config WM8350_WATCHDOG
99 tristate "WM8350 watchdog"
100 depends on MFD_WM8350
103 Support for the watchdog in the WM8350 AudioPlus PMIC. When
104 the watchdog triggers the system will be reset.
111 tristate "RK29 watchdog"
113 Watchdog timer embedded into RK29xx chips. This will reboot your
114 system when the timeout is reached.
116 config RK29_FEED_DOG_BY_INTE
117 bool "feed watchdog by interrupt"
118 depends on RK29_WATCHDOG
120 config RK29_WATCHDOG_ATBOOT
121 bool "start watchdog at system boot"
122 depends on RK29_WATCHDOG
124 config RK29_WATCHDOG_DEFAULT_TIME
125 int "set watchdog time out value (unit second)"
127 depends on RK29_WATCHDOG
129 the real time out value is two times more than the setting value
131 config RK29_WATCHDOG_DEBUG
132 bool "enable watchdog debug"
133 depends on RK29_WATCHDOG
135 config ARM_SP805_WATCHDOG
136 tristate "ARM SP805 Watchdog"
137 depends on ARM && ARM_AMBA
140 ARM Primecell SP805 Watchdog timer. This will reboot your system when
141 the timeout is reached.
143 config AT91RM9200_WATCHDOG
144 tristate "AT91RM9200 watchdog"
145 depends on ARCH_AT91RM9200
147 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
148 system when the timeout is reached.
150 config AT91SAM9X_WATCHDOG
151 tristate "AT91SAM9X / AT91CAP9 watchdog"
152 depends on ARCH_AT91 && !ARCH_AT91RM9200
155 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
156 reboot your system when the timeout is reached.
158 config 21285_WATCHDOG
159 tristate "DC21285 watchdog"
160 depends on FOOTBRIDGE
162 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
163 here if you wish to use this. Alternatively say M to compile the
164 driver as a module, which will be called wdt285.
166 This driver does not work on all machines. In particular, early CATS
167 boards have hardware problems that will cause the machine to simply
168 lock up if the watchdog fires.
170 "If in doubt, leave it out" - say N.
173 tristate "NetWinder WB83C977 watchdog"
174 depends on FOOTBRIDGE && ARCH_NETWINDER
176 Say Y here to include support for the WB977 watchdog included in
177 NetWinder machines. Alternatively say M to compile the driver as
178 a module, which will be called wdt977.
180 Not sure? It's safe to say N.
182 config IXP4XX_WATCHDOG
183 tristate "IXP4xx Watchdog"
184 depends on ARCH_IXP4XX
186 Say Y here if to include support for the watchdog timer
187 in the Intel IXP4xx network processors. This driver can
188 be built as a module by choosing M. The module will
189 be called ixp4xx_wdt.
191 Note: The internal IXP4xx watchdog does a soft CPU reset
192 which doesn't reset any peripherals. There are circumstances
193 where the watchdog will fail to reset the board correctly
194 (e.g., if the boot ROM is in an unreadable state).
196 Say N if you are unsure.
198 config KS8695_WATCHDOG
199 tristate "KS8695 watchdog"
200 depends on ARCH_KS8695
202 Watchdog timer embedded into KS8695 processor. This will reboot your
203 system when the timeout is reached.
205 config HAVE_S3C2410_WATCHDOG
208 This will include watchdog timer support for Samsung SoCs. If
209 you want to include watchdog support for any machine, kindly
210 select this in the respective mach-XXXX/Kconfig file.
212 config S3C2410_WATCHDOG
213 tristate "S3C2410 Watchdog"
214 depends on HAVE_S3C2410_WATCHDOG
217 Watchdog timer block in the Samsung SoCs. This will reboot
218 the system when the timer expires with the watchdog enabled.
220 The driver is limited by the speed of the system's PCLK
221 signal, so with reasonably fast systems (PCLK around 50-66MHz)
222 then watchdog intervals of over approximately 20seconds are
225 The driver can be built as a module by choosing M, and will
226 be called s3c2410_wdt
228 config SA1100_WATCHDOG
229 tristate "SA1100/PXA2xx watchdog"
230 depends on ARCH_SA1100 || ARCH_PXA
232 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
233 reboot your system when timeout is reached.
235 NOTE: once enabled, this timer cannot be disabled.
237 To compile this driver as a module, choose M here: the
238 module will be called sa1100_wdt.
241 tristate "Synopsys DesignWare watchdog"
242 depends on ARM && HAVE_CLK
244 Say Y here if to include support for the Synopsys DesignWare
245 watchdog timer found in many ARM chips.
246 To compile this driver as a module, choose M here: the
247 module will be called dw_wdt.
249 config MPCORE_WATCHDOG
250 tristate "MPcore watchdog"
251 depends on HAVE_ARM_TWD
253 Watchdog timer embedded into the MPcore system.
255 To compile this driver as a module, choose M here: the
256 module will be called mpcore_wdt.
258 config EP93XX_WATCHDOG
259 tristate "EP93xx Watchdog"
260 depends on ARCH_EP93XX
263 Say Y here if to include support for the watchdog timer
264 embedded in the Cirrus Logic EP93xx family of devices.
266 To compile this driver as a module, choose M here: the
267 module will be called ep93xx_wdt.
270 tristate "OMAP Watchdog"
271 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
274 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
275 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
277 config PNX4008_WATCHDOG
278 tristate "LPC32XX Watchdog"
279 depends on ARCH_LPC32XX
282 Say Y here if to include support for the watchdog timer
283 in the LPC32XX processor.
284 This driver can be built as a module by choosing M. The module
285 will be called pnx4008_wdt.
287 Say N if you are unsure.
290 tristate "IOP Watchdog"
292 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
294 Say Y here if to include support for the watchdog timer
295 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
296 be built as a module by choosing M. The module will
299 Note: The IOP13XX watchdog does an Internal Bus Reset which will
300 affect both cores and the peripherals of the IOP. The ATU-X
301 and/or ATUe configuration registers will remain intact, but if
302 operating as an Root Complex and/or Central Resource, the PCI-X
303 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
305 config DAVINCI_WATCHDOG
306 tristate "DaVinci watchdog"
307 depends on ARCH_DAVINCI
309 Say Y here if to include support for the watchdog timer
310 in the DaVinci DM644x/DM646x processors.
311 To compile this driver as a module, choose M here: the
312 module will be called davinci_wdt.
314 NOTE: once enabled, this timer cannot be disabled.
315 Say N if you are unsure.
317 config ORION_WATCHDOG
318 tristate "Orion watchdog"
319 depends on ARCH_ORION5X || ARCH_KIRKWOOD
322 Say Y here if to include support for the watchdog timer
323 in the Marvell Orion5x and Kirkwood ARM SoCs.
324 To compile this driver as a module, choose M here: the
325 module will be called orion_wdt.
327 config COH901327_WATCHDOG
328 bool "ST-Ericsson COH 901 327 watchdog"
330 default y if MACH_U300
333 Say Y here to include Watchdog timer support for the
334 watchdog embedded into the ST-Ericsson U300 series platforms.
335 This watchdog is used to reset the system and thus cannot be
336 compiled as a module.
338 config TWL4030_WATCHDOG
339 tristate "TWL4030 Watchdog"
340 depends on TWL4030_CORE
343 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
344 watchdog timer support for TWL4030 chips.
346 config STMP3XXX_RTC_WATCHDOG
347 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
348 depends on RTC_DRV_STMP
351 Say Y here to include support for the watchdog timer inside
352 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
353 To compile this driver as a module, choose M here: the
354 module will be called stmp3xxx_rtc_wdt.
356 config NUC900_WATCHDOG
357 tristate "Nuvoton NUC900 watchdog"
358 depends on ARCH_W90X900
360 Say Y here if to include support for the watchdog timer
361 for the Nuvoton NUC900 series SoCs.
362 To compile this driver as a module, choose M here: the
363 module will be called nuc900_wdt.
365 config TS72XX_WATCHDOG
366 tristate "TS-72XX SBC Watchdog"
367 depends on MACH_TS72XX
369 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
370 watchdog timer implemented in a external CPLD chip. Say Y here
371 if you want to support for the watchdog timer on TS-72XX boards.
373 To compile this driver as a module, choose M here: the
374 module will be called ts72xx_wdt.
376 config MAX63XX_WATCHDOG
377 tristate "Max63xx watchdog"
378 depends on ARM && HAS_IOMEM
381 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
384 tristate "IMX2+ Watchdog"
387 This is the driver for the hardware watchdog
388 on the Freescale IMX2 and later processors.
389 If you have one of these processors and wish to have
390 watchdog support enabled, say Y, otherwise say N.
392 To compile this driver as a module, choose M here: the
393 module will be called imx2_wdt.
395 config UX500_WATCHDOG
396 tristate "ST-Ericsson Ux500 watchdog"
397 depends on MFD_DB8500_PRCMU
401 Say Y here to include Watchdog timer support for the watchdog
402 existing in the prcmu of ST-Ericsson Ux500 series platforms.
404 To compile this driver as a module, choose M here: the
405 module will be called ux500_wdt.
408 tristate "Retu watchdog"
412 Retu watchdog driver for Nokia Internet Tablets (770, N800,
413 N810). At least on N800 the watchdog cannot be disabled, so
414 this driver is essential and you should enable it.
416 To compile this driver as a module, choose M here: the
417 module will be called retu_wdt.
421 config AT32AP700X_WDT
422 tristate "AT32AP700x watchdog"
423 depends on CPU_AT32AP700X
425 Watchdog timer embedded into AT32AP700x devices. This will reboot
426 your system when the timeout is reached.
428 # BLACKFIN Architecture
431 tristate "Blackfin On-Chip Watchdog Timer"
434 If you say yes here you will get support for the Blackfin On-Chip
435 Watchdog Timer. If you have one of these processors and wish to
436 have watchdog support enabled, say Y, otherwise say N.
438 To compile this driver as a module, choose M here: the
439 module will be called bfin_wdt.
447 # X86 (i386 + ia64 + x86_64) Architecture
450 tristate "Acquire SBC Watchdog Timer"
453 This is the driver for the hardware watchdog on Single Board
454 Computers produced by Acquire Inc (and others). This watchdog
455 simply watches your kernel to make sure it doesn't freeze, and if
456 it does, it reboots your computer after a certain amount of time.
458 To compile this driver as a module, choose M here: the
459 module will be called acquirewdt.
461 Most people will say N.
464 tristate "Advantech SBC Watchdog Timer"
467 If you are configuring a Linux kernel for the Advantech single-board
468 computer, say `Y' here to support its built-in watchdog timer
469 feature. More information can be found at
470 <http://www.advantech.com.tw/products/>
473 tristate "ALi M1535 PMU Watchdog Timer"
474 depends on X86 && PCI
476 This is the driver for the hardware watchdog on the ALi M1535 PMU.
478 To compile this driver as a module, choose M here: the
479 module will be called alim1535_wdt.
481 Most people will say N.
484 tristate "ALi M7101 PMU Computer Watchdog"
487 This is the driver for the hardware watchdog on the ALi M7101 PMU
488 as used in the x86 Cobalt servers and also found in some
489 SPARC Netra servers too.
491 To compile this driver as a module, choose M here: the
492 module will be called alim7101_wdt.
494 Most people will say N.
497 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
500 This is the driver for the hardware watchdog on the Fintek
501 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
503 You can compile this driver directly into the kernel, or use
504 it as a module. The module will be called f71808e_wdt.
507 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
508 depends on X86 && PCI
510 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
511 (Total Cost of Ownership) timer is a watchdog timer that will reboot
512 the machine after its expiration. The expiration time can be
513 configured with the "heartbeat" parameter.
515 To compile this driver as a module, choose M here: the
516 module will be called sp5100_tco.
519 tristate "AMD Geode CS5535/CS5536 Watchdog"
520 depends on CS5535_MFGPT
522 This driver enables a watchdog capability built into the
523 CS5535/CS5536 companion chips for the AMD Geode GX and LX
524 processors. This watchdog watches your kernel to make sure
525 it doesn't freeze, and if it does, it reboots your computer after
526 a certain amount of time.
528 You can compile this driver directly into the kernel, or use
529 it as a module. The module will be called geodewdt.
532 tristate "AMD Elan SC520 processor Watchdog"
535 This is the driver for the hardware watchdog built in to the
536 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
537 This watchdog simply watches your kernel to make sure it doesn't
538 freeze, and if it does, it reboots your computer after a certain
541 You can compile this driver directly into the kernel, or use
542 it as a module. The module will be called sc520_wdt.
544 config SBC_FITPC2_WATCHDOG
545 tristate "Compulab SBC-FITPC2 watchdog"
548 This is the driver for the built-in watchdog timer on the fit-PC2,
549 fit-PC2i, CM-iAM single-board computers made by Compulab.
551 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
552 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
554 Entering BIOS setup temporary disables watchdog operation regardless to current state,
555 so system will not be restarted while user in BIOS setup.
557 Once watchdog was enabled the system will be restarted every
558 "Watchdog Timer Value" period, so to prevent it user can restart or
559 disable the watchdog.
561 To compile this driver as a module, choose M here: the
562 module will be called sbc_fitpc2_wdt.
564 Most people will say N.
567 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
570 Enable support for the watchdog timer on the Eurotech CPU-1220 and
571 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
572 information are at <http://www.eurotech.it/>.
575 tristate "IB700 SBC Watchdog Timer"
578 This is the driver for the hardware watchdog on the IB700 Single
579 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
580 simply watches your kernel to make sure it doesn't freeze, and if
581 it does, it reboots your computer after a certain amount of time.
583 This driver is like the WDT501 driver but for slightly different hardware.
585 To compile this driver as a module, choose M here: the
586 module will be called ib700wdt.
588 Most people will say N.
591 tristate "IBM Automatic Server Restart"
594 This is the driver for the IBM Automatic Server Restart watchdog
595 timer built-in into some eServer xSeries machines.
597 To compile this driver as a module, choose M here: the
598 module will be called ibmasr.
601 tristate "ICP Single Board Computer Watchdog Timer"
604 This is a driver for the hardware watchdog on the ICP Single
605 Board Computer. This driver is working on (at least) the following
606 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
608 To compile this driver as a module, choose M here: the
609 module will be called wafer5823wdt.
612 tristate "Intel 6300ESB Timer/Watchdog"
615 Hardware driver for the watchdog timer built into the Intel
616 6300ESB controller hub.
618 To compile this driver as a module, choose M here: the
619 module will be called i6300esb.
622 tristate "Intel Atom E6xx Watchdog"
623 depends on X86 && PCI
628 Hardware driver for the watchdog timer built into the Intel
629 Atom E6XX (TunnelCreek) processor.
631 To compile this driver as a module, choose M here: the
632 module will be called ie6xx_wdt.
634 config INTEL_SCU_WATCHDOG
635 bool "Intel SCU Watchdog for Mobile Platforms"
636 depends on X86_INTEL_MID
638 Hardware driver for the watchdog time built into the Intel SCU
639 for Intel Mobile Platforms.
641 To compile this driver as a module, choose M here.
644 tristate "Intel TCO Timer/Watchdog"
645 depends on (X86 || IA64) && PCI
649 Hardware driver for the intel TCO timer based watchdog devices.
650 These drivers are included in the Intel 82801 I/O Controller
651 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
654 The TCO (Total Cost of Ownership) timer is a watchdog timer
655 that will reboot the machine after its second expiration. The
656 expiration time can be configured with the "heartbeat" parameter.
658 On some motherboards the driver may fail to reset the chipset's
659 NO_REBOOT flag which prevents the watchdog from rebooting the
660 machine. If this is the case you will get a kernel message like
661 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
663 To compile this driver as a module, choose M here: the
664 module will be called iTCO_wdt.
666 config ITCO_VENDOR_SUPPORT
667 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
670 Add vendor specific support to the intel TCO timer based watchdog
671 devices. At this moment we only have additional support for some
672 SuperMicro Inc. motherboards.
675 tristate "IT8712F (Smart Guardian) Watchdog Timer"
678 This is the driver for the built-in watchdog timer on the IT8712F
679 Super I/0 chipset used on many motherboards.
681 If the driver does not work, then make sure that the game port in
684 To compile this driver as a module, choose M here: the
685 module will be called it8712f_wdt.
688 tristate "IT87 Watchdog Timer"
691 This is the driver for the hardware watchdog on the ITE IT8702,
692 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
695 If the driver does not work, then make sure that the game port in
698 This watchdog simply watches your kernel to make sure it doesn't
699 freeze, and if it does, it reboots your computer after a certain
702 To compile this driver as a module, choose M here: the module will
706 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
707 depends on X86 && PCI
709 A software monitoring watchdog and NMI sourcing driver. This driver
710 will detect lockups and provide a stack trace. This is a driver that
711 will only load on an HP ProLiant system with a minimum of iLO2 support.
712 To compile this driver as a module, choose M here: the module will be
715 config HPWDT_NMI_DECODING
716 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
717 depends on HP_WATCHDOG
720 When an NMI occurs this feature will make the necessary BIOS calls to
721 log the cause of the NMI.
724 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
727 This is a driver for National Semiconductor PC87307/PC97307 hardware
728 watchdog cards as found on the SC1200. This watchdog is mainly used
729 for power management purposes and can be used to power down the device
730 during inactivity periods (includes interrupt activity monitoring).
732 To compile this driver as a module, choose M here: the
733 module will be called sc1200wdt.
735 Most people will say N.
738 tristate "National Semiconductor SCx200 Watchdog"
739 depends on SCx200 && PCI
741 Enable the built-in watchdog timer support on the National
742 Semiconductor SCx200 processors.
744 If compiled as a module, it will be called scx200_wdt.
747 tristate "NS PC87413 watchdog"
750 This is the driver for the hardware watchdog on the PC87413 chipset
751 This watchdog simply watches your kernel to make sure it doesn't
752 freeze, and if it does, it reboots your computer after a certain
755 To compile this driver as a module, choose M here: the
756 module will be called pc87413_wdt.
758 Most people will say N.
761 tristate "nVidia TCO Timer/Watchdog"
762 depends on X86 && PCI
764 Hardware driver for the TCO timer built into the nVidia Hub family
765 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
766 watchdog timer that will reboot the machine after its second
767 expiration. The expiration time can be configured with the
768 "heartbeat" parameter.
770 On some motherboards the driver may fail to reset the chipset's
771 NO_REBOOT flag which prevents the watchdog from rebooting the
772 machine. If this is the case you will get a kernel message like
773 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
775 To compile this driver as a module, choose M here: the
776 module will be called nv_tco.
779 tristate "RDC R-321x SoC watchdog"
780 depends on X86_RDC321X
782 This is the driver for the built in hardware watchdog
783 in the RDC R-321x SoC.
785 To compile this driver as a module, choose M here: the
786 module will be called rdc321x_wdt.
789 tristate "SBC-60XX Watchdog Timer"
792 This driver can be used with the watchdog timer found on some
793 single board computers, namely the 6010 PII based computer.
794 It may well work with other cards. It reads port 0x443 to enable
795 and re-set the watchdog timer, and reads port 0x45 to disable
796 the watchdog. If you have a card that behave in similar ways,
797 you can probably make this driver work with your card as well.
799 You can compile this driver directly into the kernel, or use
800 it as a module. The module will be called sbc60xxwdt.
803 tristate "SBC8360 Watchdog Timer"
807 This is the driver for the hardware watchdog on the SBC8360 Single
808 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
810 To compile this driver as a module, choose M here: the
811 module will be called sbc8360.
813 Most people will say N.
816 tristate "SBC Nano 7240 Watchdog Timer"
817 depends on X86_32 && !UML
819 This is the driver for the hardware watchdog found on the IEI
820 single board computers EPIC Nano 7240 (and likely others). This
821 watchdog simply watches your kernel to make sure it doesn't freeze,
822 and if it does, it reboots your computer after a certain amount of
825 To compile this driver as a module, choose M here: the
826 module will be called sbc7240_wdt.
829 tristate "SMA CPU5 Watchdog"
833 To compile this driver as a module, choose M here: the
834 module will be called cpu5wdt.
836 config SMSC_SCH311X_WDT
837 tristate "SMSC SCH311X Watchdog Timer"
840 This is the driver for the hardware watchdog timer on the
841 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
842 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
845 To compile this driver as a module, choose M here: the
846 module will be called sch311x_wdt.
848 config SMSC37B787_WDT
849 tristate "Winbond SMsC37B787 Watchdog Timer"
852 This is the driver for the hardware watchdog component on the
853 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
854 from Vision Systems and maybe others.
856 This watchdog simply watches your kernel to make sure it doesn't
857 freeze, and if it does, it reboots your computer after a certain
860 Usually a userspace daemon will notify the kernel WDT driver that
861 userspace is still alive, at regular intervals.
863 To compile this driver as a module, choose M here: the
864 module will be called smsc37b787_wdt.
866 Most people will say N.
869 tristate "VIA Watchdog Timer"
870 depends on X86 && PCI
873 This is the driver for the hardware watchdog timer on VIA
874 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
876 To compile this driver as a module, choose M here; the module
877 will be called via_wdt.
879 Most people will say N.
882 tristate "W83627HF/W83627DHG Watchdog Timer"
885 This is the driver for the hardware watchdog on the W83627HF chipset
886 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
887 (and likely others). The driver also supports the W83627DHG chip.
888 This watchdog simply watches your kernel to make sure it doesn't
889 freeze, and if it does, it reboots your computer after a certain
892 To compile this driver as a module, choose M here: the
893 module will be called w83627hf_wdt.
895 Most people will say N.
898 tristate "W83697HF/W83697HG Watchdog Timer"
901 This is the driver for the hardware watchdog on the W83697HF/HG
902 chipset as used in Dedibox/VIA motherboards (and likely others).
903 This watchdog simply watches your kernel to make sure it doesn't
904 freeze, and if it does, it reboots your computer after a certain
907 To compile this driver as a module, choose M here: the
908 module will be called w83697hf_wdt.
910 Most people will say N.
913 tristate "W83697UG/W83697UF Watchdog Timer"
916 This is the driver for the hardware watchdog on the W83697UG/UF
917 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
918 This watchdog simply watches your kernel to make sure it doesn't
919 freeze, and if it does, it reboots your computer after a certain
922 To compile this driver as a module, choose M here: the
923 module will be called w83697ug_wdt.
925 Most people will say N.
928 tristate "W83877F (EMACS) Watchdog Timer"
931 This is the driver for the hardware watchdog on the W83877F chipset
932 as used in EMACS PC-104 motherboards (and likely others). This
933 watchdog simply watches your kernel to make sure it doesn't freeze,
934 and if it does, it reboots your computer after a certain amount of
937 To compile this driver as a module, choose M here: the
938 module will be called w83877f_wdt.
940 Most people will say N.
943 tristate "W83977F (PCM-5335) Watchdog Timer"
946 This is the driver for the hardware watchdog on the W83977F I/O chip
947 as used in AAEON's PCM-5335 SBC (and likely others). This
948 watchdog simply watches your kernel to make sure it doesn't freeze,
949 and if it does, it reboots your computer after a certain amount of
952 To compile this driver as a module, choose M here: the
953 module will be called w83977f_wdt.
956 tristate "ZF MachZ Watchdog"
959 If you are using a ZF Micro MachZ processor, say Y here, otherwise
960 N. This is the driver for the watchdog timer built-in on that
961 processor using ZF-Logic interface. This watchdog simply watches
962 your kernel to make sure it doesn't freeze, and if it does, it
963 reboots your computer after a certain amount of time.
965 To compile this driver as a module, choose M here: the
966 module will be called machzwd.
968 config SBC_EPX_C3_WATCHDOG
969 tristate "Winsystems SBC EPX-C3 watchdog"
972 This is the driver for the built-in watchdog timer on the EPX-C3
973 Single-board computer made by Winsystems, Inc.
975 *Note*: This hardware watchdog is not probeable and thus there
976 is no way to know if writing to its IO address will corrupt
977 your system or have any real effect. The only way to be sure
978 that this driver does what you want is to make sure you
979 are running it on an EPX-C3 from Winsystems with the watchdog
980 timer at IO address 0x1ee and 0x1ef. It will write to both those
981 IO ports. Basically, the assumption is made that if you compile
982 this driver into your kernel and/or load it as a module, that you
983 know what you are doing and that you are in fact running on an
986 To compile this driver as a module, choose M here: the
987 module will be called sbc_epx_c3.
993 config M54xx_WATCHDOG
994 tristate "MCF54xx watchdog support"
997 To compile this driver as a module, choose M here: the
998 module will be called m54xx_wdt.
1000 # MicroBlaze Architecture
1002 config XILINX_WATCHDOG
1003 tristate "Xilinx Watchdog timer"
1004 depends on MICROBLAZE
1006 Watchdog driver for the xps_timebase_wdt ip core.
1008 IMPORTANT: The xps_timebase_wdt parent must have the property
1009 "clock-frequency" at device tree.
1011 To compile this driver as a module, choose M here: the
1012 module will be called of_xilinx_wdt.
1017 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1020 Hardware driver for the built-in watchdog timer on the Atheros
1021 AR71XX/AR724X/AR913X SoCs.
1024 tristate "Broadcom BCM47xx Watchdog Timer"
1026 select WATCHDOG_CORE
1028 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1031 tristate "IDT RC32434 SoC Watchdog Timer"
1032 depends on MIKROTIK_RB532
1034 Hardware driver for the IDT RC32434 SoC built-in
1037 To compile this driver as a module, choose M here: the
1038 module will be called rc32434_wdt.
1041 tristate "Indy/I2 Hardware Watchdog"
1042 depends on SGI_HAS_INDYDOG
1044 Hardware driver for the Indy's/I2's watchdog. This is a
1045 watchdog timer that will reboot the machine after a 60 second
1046 timer expired and no process has written to /dev/watchdog during
1050 tristate "Ingenic jz4740 SoC hardware watchdog"
1051 depends on MACH_JZ4740
1052 select WATCHDOG_CORE
1054 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1057 tristate "MTX-1 Hardware Watchdog"
1058 depends on MIPS_MTX1
1060 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1061 will reboot the machine after a 100 seconds timer expired.
1064 tristate "PNX833x Hardware Watchdog"
1065 depends on SOC_PNX8335
1067 Hardware driver for the PNX833x's watchdog. This is a
1068 watchdog timer that will reboot the machine after a programmable
1069 timer has expired and no process has written to /dev/watchdog during
1073 tristate "Sibyte SoC hardware watchdog"
1076 Watchdog driver for the built in watchdog hardware in Sibyte
1077 SoC processors. There are apparently two watchdog timers
1078 on such processors; this driver supports only the first one,
1079 because currently Linux only supports exporting one watchdog
1082 To compile this driver as a loadable module, choose M here.
1083 The module will be called sb_wdog.
1086 tristate "TI AR7 Watchdog Timer"
1089 Hardware driver for the TI AR7 Watchdog Timer.
1092 tristate "Toshiba TXx9 Watchdog Timer"
1093 depends on CPU_TX39XX || CPU_TX49XX
1094 select WATCHDOG_CORE
1096 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1099 tristate "Cavium OCTEON SOC family Watchdog Timer"
1100 depends on CPU_CAVIUM_OCTEON
1102 select EXPORT_UASM if OCTEON_WDT = m
1104 Hardware driver for OCTEON's on chip watchdog timer.
1105 Enables the watchdog for all cores running Linux. It
1106 installs a NMI handler and pokes the watchdog based on an
1107 interrupt. On first expiration of the watchdog, the
1108 interrupt handler pokes it. The second expiration causes an
1109 NMI that prints a message. The third expiration causes a
1112 When userspace has /dev/watchdog open, no poking is done
1113 from the first interrupt, it is then only poked when the
1117 tristate "Broadcom BCM63xx hardware watchdog"
1120 Watchdog driver for the built in watchdog hardware in Broadcom
1123 To compile this driver as a loadable module, choose M here.
1124 The module will be called bcm63xx_wdt.
1127 tristate "Lantiq SoC watchdog"
1130 Hardware driver for the Lantiq SoC Watchdog Timer.
1132 # PARISC Architecture
1134 # POWERPC Architecture
1137 tristate "GE Watchdog Timer"
1140 Watchdog timer found in a number of GE single board computers.
1143 bool "MPC52xx Watchdog Timer"
1144 depends on PPC_MPC52xx
1146 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1149 tristate "MPC8xxx Platform Watchdog Timer"
1150 depends on PPC_8xx || PPC_83xx || PPC_86xx
1152 This driver is for a SoC level watchdog that exists on some
1153 Freescale PowerPC processors. So far this driver supports:
1158 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1161 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1165 tristate "PIKA FPGA Watchdog"
1169 This enables the watchdog in the PIKA FPGA. Currently used on
1173 tristate "PowerPC Book-E Watchdog Timer"
1174 depends on BOOKE || 4xx
1175 select WATCHDOG_CORE
1177 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1178 MPC85xx SOCs and the IBM PowerPC 440.
1180 Please see Documentation/watchdog/watchdog-api.txt for
1183 config BOOKE_WDT_DEFAULT_TIMEOUT
1184 int "PowerPC Book-E Watchdog Timer Default Timeout"
1185 depends on BOOKE_WDT
1186 default 38 if PPC_FSL_BOOK3E
1187 range 0 63 if PPC_FSL_BOOK3E
1188 default 3 if !PPC_FSL_BOOK3E
1189 range 0 3 if !PPC_FSL_BOOK3E
1191 Select the default watchdog timer period to be used by the PowerPC
1192 Book-E watchdog driver. A watchdog "event" occurs when the bit
1193 position represented by this number transitions from zero to one.
1195 For Freescale Book-E processors, this is a number between 0 and 63.
1196 For other Book-E processors, this is a number between 0 and 3.
1198 The value can be overridden by the wdt_period command-line parameter.
1200 # PPC64 Architecture
1202 config WATCHDOG_RTAS
1203 tristate "RTAS watchdog"
1206 This driver adds watchdog support for the RTAS watchdog.
1208 To compile this driver as a module, choose M here. The module
1209 will be called wdrtas.
1214 tristate "z/VM Watchdog Timer"
1217 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1218 provide a virtual watchdog timer to their guest that cause a
1219 user define Control Program command to be executed after a
1222 To compile this driver as a module, choose M here. The module
1223 will be called vmwatchdog.
1225 # SUPERH (sh + sh64) Architecture
1228 tristate "SuperH Watchdog"
1229 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1230 select WATCHDOG_CORE
1232 This driver adds watchdog support for the integrated watchdog in the
1233 SuperH processors. If you have one of these processors and wish
1234 to have watchdog support enabled, say Y, otherwise say N.
1236 As a side note, saying Y here will automatically boost HZ to 1000
1237 so that the timer has a chance to clear the overflow counter. On
1238 slower systems (such as the SH-2 and SH-3) this will likely yield
1239 some performance issues. As such, the WDT should be avoided here
1240 unless it is absolutely necessary.
1242 To compile this driver as a module, choose M here: the
1243 module will be called shwdt.
1245 # SPARC Architecture
1247 # SPARC64 Architecture
1249 config WATCHDOG_CP1XXX
1250 tristate "CP1XXX Hardware Watchdog support"
1251 depends on SPARC64 && PCI
1253 This is the driver for the hardware watchdog timers present on
1254 Sun Microsystems CompactPCI models CP1400 and CP1500.
1256 To compile this driver as a module, choose M here: the
1257 module will be called cpwatchdog.
1259 If you do not have a CompactPCI model CP1400 or CP1500, or
1260 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1261 you should say N to this option.
1264 tristate "RIO Hardware Watchdog support"
1265 depends on SPARC64 && PCI
1267 Say Y here to support the hardware watchdog capability on Sun RIO
1268 machines. The watchdog timeout period is normally one minute but
1269 can be changed with a boot-time parameter.
1271 # XTENSA Architecture
1276 tristate "Xen Watchdog support"
1279 Say Y here to support the hypervisor watchdog capability provided
1280 by Xen 4.0 and newer. The watchdog timeout period is normally one
1281 minute but can be changed with a boot-time parameter.
1284 tristate "UML watchdog"
1288 # ISA-based Watchdog Cards
1291 comment "ISA-based Watchdog Cards"
1295 tristate "Berkshire Products ISA-PC Watchdog"
1298 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1299 This card simply watches your kernel to make sure it doesn't freeze,
1300 and if it does, it reboots your computer after a certain amount of
1301 time. This driver is like the WDT501 driver but for different
1302 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1303 watchdog cards can be ordered from <http://www.berkprod.com/>.
1305 To compile this driver as a module, choose M here: the
1306 module will be called pcwd.
1308 Most people will say N.
1311 tristate "Mixcom Watchdog"
1314 This is a driver for the Mixcom hardware watchdog cards. This
1315 watchdog simply watches your kernel to make sure it doesn't freeze,
1316 and if it does, it reboots your computer after a certain amount of
1319 To compile this driver as a module, choose M here: the
1320 module will be called mixcomwd.
1322 Most people will say N.
1325 tristate "WDT Watchdog timer"
1328 If you have a WDT500P or WDT501P watchdog board, say Y here,
1329 otherwise N. It is not possible to probe for this board, which means
1330 that you have to inform the kernel about the IO port and IRQ that
1331 is needed (you can do this via the io and irq parameters)
1333 To compile this driver as a module, choose M here: the
1334 module will be called wdt.
1337 # PCI-based Watchdog Cards
1340 comment "PCI-based Watchdog Cards"
1343 config PCIPCWATCHDOG
1344 tristate "Berkshire Products PCI-PC Watchdog"
1347 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1348 This card simply watches your kernel to make sure it doesn't freeze,
1349 and if it does, it reboots your computer after a certain amount of
1350 time. The card can also monitor the internal temperature of the PC.
1351 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1353 To compile this driver as a module, choose M here: the
1354 module will be called pcwd_pci.
1356 Most people will say N.
1359 tristate "PCI-WDT500/501 Watchdog timer"
1362 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1364 If you have a PCI-WDT501 watchdog board then you can enable the
1365 temperature sensor by setting the type parameter to 501.
1367 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1368 can do this via the tachometer parameter. Only do this if you have a
1369 fan tachometer actually set up.
1371 To compile this driver as a module, choose M here: the
1372 module will be called wdt_pci.
1375 # USB-based Watchdog Cards
1378 comment "USB-based Watchdog Cards"
1381 config USBPCWATCHDOG
1382 tristate "Berkshire Products USB-PC Watchdog"
1385 This is the driver for the Berkshire Products USB-PC Watchdog card.
1386 This card simply watches your kernel to make sure it doesn't freeze,
1387 and if it does, it reboots your computer after a certain amount of
1388 time. The card can also monitor the internal temperature of the PC.
1389 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1391 To compile this driver as a module, choose M here: the
1392 module will be called pcwd_usb.
1394 Most people will say N.