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.
91 tristate "Watchdog device controlled through GPIO-line"
95 If you say yes here you get support for watchdog device
96 controlled through GPIO-line.
98 config WM831X_WATCHDOG
99 tristate "WM831x watchdog"
100 depends on MFD_WM831X
103 Support for the watchdog in the WM831x AudioPlus PMICs. When
104 the watchdog triggers the system will be reset.
106 config WM8350_WATCHDOG
107 tristate "WM8350 watchdog"
108 depends on MFD_WM8350
111 Support for the watchdog in the WM8350 AudioPlus PMIC. When
112 the watchdog triggers the system will be reset.
118 config ARM_SP805_WATCHDOG
119 tristate "ARM SP805 Watchdog"
120 depends on ARM && ARM_AMBA
123 ARM Primecell SP805 Watchdog timer. This will reboot your system when
124 the timeout is reached.
126 config AT91RM9200_WATCHDOG
127 tristate "AT91RM9200 watchdog"
128 depends on ARCH_AT91RM9200
130 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
131 system when the timeout is reached.
133 config AT91SAM9X_WATCHDOG
134 tristate "AT91SAM9X / AT91CAP9 watchdog"
135 depends on ARCH_AT91 && !ARCH_AT91RM9200
138 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
139 reboot your system when the timeout is reached.
141 config 21285_WATCHDOG
142 tristate "DC21285 watchdog"
143 depends on FOOTBRIDGE
145 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
146 here if you wish to use this. Alternatively say M to compile the
147 driver as a module, which will be called wdt285.
149 This driver does not work on all machines. In particular, early CATS
150 boards have hardware problems that will cause the machine to simply
151 lock up if the watchdog fires.
153 "If in doubt, leave it out" - say N.
156 tristate "NetWinder WB83C977 watchdog"
157 depends on FOOTBRIDGE && ARCH_NETWINDER
159 Say Y here to include support for the WB977 watchdog included in
160 NetWinder machines. Alternatively say M to compile the driver as
161 a module, which will be called wdt977.
163 Not sure? It's safe to say N.
165 config IXP4XX_WATCHDOG
166 tristate "IXP4xx Watchdog"
167 depends on ARCH_IXP4XX
169 Say Y here if to include support for the watchdog timer
170 in the Intel IXP4xx network processors. This driver can
171 be built as a module by choosing M. The module will
172 be called ixp4xx_wdt.
174 Note: The internal IXP4xx watchdog does a soft CPU reset
175 which doesn't reset any peripherals. There are circumstances
176 where the watchdog will fail to reset the board correctly
177 (e.g., if the boot ROM is in an unreadable state).
179 Say N if you are unsure.
181 config KS8695_WATCHDOG
182 tristate "KS8695 watchdog"
183 depends on ARCH_KS8695
185 Watchdog timer embedded into KS8695 processor. This will reboot your
186 system when the timeout is reached.
188 config HAVE_S3C2410_WATCHDOG
191 This will include watchdog timer support for Samsung SoCs. If
192 you want to include watchdog support for any machine, kindly
193 select this in the respective mach-XXXX/Kconfig file.
195 config S3C2410_WATCHDOG
196 tristate "S3C2410 Watchdog"
197 depends on HAVE_S3C2410_WATCHDOG
199 select MFD_SYSCON if ARCH_EXYNOS5
201 Watchdog timer block in the Samsung SoCs. This will reboot
202 the system when the timer expires with the watchdog enabled.
204 The driver is limited by the speed of the system's PCLK
205 signal, so with reasonably fast systems (PCLK around 50-66MHz)
206 then watchdog intervals of over approximately 20seconds are
209 The driver can be built as a module by choosing M, and will
210 be called s3c2410_wdt
212 config SA1100_WATCHDOG
213 tristate "SA1100/PXA2xx watchdog"
214 depends on ARCH_SA1100 || ARCH_PXA
216 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
217 reboot your system when timeout is reached.
219 NOTE: once enabled, this timer cannot be disabled.
221 To compile this driver as a module, choose M here: the
222 module will be called sa1100_wdt.
225 tristate "Synopsys DesignWare watchdog"
227 Say Y here if to include support for the Synopsys DesignWare
228 watchdog timer found in many chips.
229 To compile this driver as a module, choose M here: the
230 module will be called dw_wdt.
232 config EP93XX_WATCHDOG
233 tristate "EP93xx Watchdog"
234 depends on ARCH_EP93XX
237 Say Y here if to include support for the watchdog timer
238 embedded in the Cirrus Logic EP93xx family of devices.
240 To compile this driver as a module, choose M here: the
241 module will be called ep93xx_wdt.
244 tristate "OMAP Watchdog"
245 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
248 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
249 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
251 config PNX4008_WATCHDOG
252 tristate "LPC32XX Watchdog"
253 depends on ARCH_LPC32XX
256 Say Y here if to include support for the watchdog timer
257 in the LPC32XX processor.
258 This driver can be built as a module by choosing M. The module
259 will be called pnx4008_wdt.
261 Say N if you are unsure.
264 tristate "IOP Watchdog"
266 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
268 Say Y here if to include support for the watchdog timer
269 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
270 be built as a module by choosing M. The module will
273 Note: The IOP13XX watchdog does an Internal Bus Reset which will
274 affect both cores and the peripherals of the IOP. The ATU-X
275 and/or ATUe configuration registers will remain intact, but if
276 operating as an Root Complex and/or Central Resource, the PCI-X
277 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
279 config DAVINCI_WATCHDOG
280 tristate "DaVinci watchdog"
281 depends on ARCH_DAVINCI || ARCH_KEYSTONE
284 Say Y here if to include support for the watchdog timer
285 in the DaVinci DM644x/DM646x or Keystone processors.
286 To compile this driver as a module, choose M here: the
287 module will be called davinci_wdt.
289 NOTE: once enabled, this timer cannot be disabled.
290 Say N if you are unsure.
292 config ORION_WATCHDOG
293 tristate "Orion watchdog"
294 depends on ARCH_ORION5X || ARCH_KIRKWOOD || ARCH_DOVE
297 Say Y here if to include support for the watchdog timer
298 in the Marvell Orion5x and Kirkwood ARM SoCs.
299 To compile this driver as a module, choose M here: the
300 module will be called orion_wdt.
302 config SUNXI_WATCHDOG
303 tristate "Allwinner SoCs watchdog support"
304 depends on ARCH_SUNXI
307 Say Y here to include support for the watchdog timer
309 To compile this driver as a module, choose M here: the
310 module will be called sunxi_wdt.
312 config COH901327_WATCHDOG
313 bool "ST-Ericsson COH 901 327 watchdog"
315 default y if MACH_U300
318 Say Y here to include Watchdog timer support for the
319 watchdog embedded into the ST-Ericsson U300 series platforms.
320 This watchdog is used to reset the system and thus cannot be
321 compiled as a module.
323 config TWL4030_WATCHDOG
324 tristate "TWL4030 Watchdog"
325 depends on TWL4030_CORE
328 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
329 watchdog timer support for TWL4030 chips.
331 config STMP3XXX_RTC_WATCHDOG
332 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
333 depends on RTC_DRV_STMP
336 Say Y here to include support for the watchdog timer inside
337 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
338 To compile this driver as a module, choose M here: the
339 module will be called stmp3xxx_rtc_wdt.
341 config NUC900_WATCHDOG
342 tristate "Nuvoton NUC900 watchdog"
343 depends on ARCH_W90X900
345 Say Y here if to include support for the watchdog timer
346 for the Nuvoton NUC900 series SoCs.
347 To compile this driver as a module, choose M here: the
348 module will be called nuc900_wdt.
350 config TS72XX_WATCHDOG
351 tristate "TS-72XX SBC Watchdog"
352 depends on MACH_TS72XX
354 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
355 watchdog timer implemented in a external CPLD chip. Say Y here
356 if you want to support for the watchdog timer on TS-72XX boards.
358 To compile this driver as a module, choose M here: the
359 module will be called ts72xx_wdt.
361 config MAX63XX_WATCHDOG
362 tristate "Max63xx watchdog"
363 depends on ARM && HAS_IOMEM
366 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
369 tristate "IMX2+ Watchdog"
372 This is the driver for the hardware watchdog
373 on the Freescale IMX2 and later processors.
374 If you have one of these processors and wish to have
375 watchdog support enabled, say Y, otherwise say N.
377 To compile this driver as a module, choose M here: the
378 module will be called imx2_wdt.
380 config UX500_WATCHDOG
381 tristate "ST-Ericsson Ux500 watchdog"
382 depends on MFD_DB8500_PRCMU
386 Say Y here to include Watchdog timer support for the watchdog
387 existing in the prcmu of ST-Ericsson Ux500 series platforms.
389 To compile this driver as a module, choose M here: the
390 module will be called ux500_wdt.
393 tristate "Retu watchdog"
397 Retu watchdog driver for Nokia Internet Tablets (770, N800,
398 N810). At least on N800 the watchdog cannot be disabled, so
399 this driver is essential and you should enable it.
401 To compile this driver as a module, choose M here: the
402 module will be called retu_wdt.
405 tristate "MOXART watchdog"
406 depends on ARCH_MOXART
408 Say Y here to include Watchdog timer support for the watchdog
409 existing on the MOXA ART SoC series platforms.
411 To compile this driver as a module, choose M here: the
412 module will be called moxart_wdt.
414 config SIRFSOC_WATCHDOG
415 tristate "SiRFSOC watchdog"
420 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
421 the watchdog triggers the system will be reset.
425 config AT32AP700X_WDT
426 tristate "AT32AP700x watchdog"
427 depends on CPU_AT32AP700X
429 Watchdog timer embedded into AT32AP700x devices. This will reboot
430 your system when the timeout is reached.
432 # BLACKFIN Architecture
435 tristate "Blackfin On-Chip Watchdog Timer"
438 If you say yes here you will get support for the Blackfin On-Chip
439 Watchdog Timer. If you have one of these processors and wish to
440 have watchdog support enabled, say Y, otherwise say N.
442 To compile this driver as a module, choose M here: the
443 module will be called bfin_wdt.
449 # X86 (i386 + ia64 + x86_64) Architecture
452 tristate "Acquire SBC Watchdog Timer"
455 This is the driver for the hardware watchdog on Single Board
456 Computers produced by Acquire Inc (and others). This watchdog
457 simply watches your kernel to make sure it doesn't freeze, and if
458 it does, it reboots your computer after a certain amount of time.
460 To compile this driver as a module, choose M here: the
461 module will be called acquirewdt.
463 Most people will say N.
466 tristate "Advantech SBC Watchdog Timer"
469 If you are configuring a Linux kernel for the Advantech single-board
470 computer, say `Y' here to support its built-in watchdog timer
471 feature. More information can be found at
472 <http://www.advantech.com.tw/products/>
475 tristate "ALi M1535 PMU Watchdog Timer"
476 depends on X86 && PCI
478 This is the driver for the hardware watchdog on the ALi M1535 PMU.
480 To compile this driver as a module, choose M here: the
481 module will be called alim1535_wdt.
483 Most people will say N.
486 tristate "ALi M7101 PMU Computer Watchdog"
489 This is the driver for the hardware watchdog on the ALi M7101 PMU
490 as used in the x86 Cobalt servers and also found in some
491 SPARC Netra servers too.
493 To compile this driver as a module, choose M here: the
494 module will be called alim7101_wdt.
496 Most people will say N.
499 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
502 This is the driver for the hardware watchdog on the Fintek
503 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
505 You can compile this driver directly into the kernel, or use
506 it as a module. The module will be called f71808e_wdt.
509 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
510 depends on X86 && PCI
512 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
513 (Total Cost of Ownership) timer is a watchdog timer that will reboot
514 the machine after its expiration. The expiration time can be
515 configured with the "heartbeat" parameter.
517 To compile this driver as a module, choose M here: the
518 module will be called sp5100_tco.
521 tristate "AMD Geode CS5535/CS5536 Watchdog"
522 depends on CS5535_MFGPT
524 This driver enables a watchdog capability built into the
525 CS5535/CS5536 companion chips for the AMD Geode GX and LX
526 processors. This watchdog watches your kernel to make sure
527 it doesn't freeze, and if it does, it reboots your computer after
528 a certain amount of time.
530 You can compile this driver directly into the kernel, or use
531 it as a module. The module will be called geodewdt.
534 tristate "AMD Elan SC520 processor Watchdog"
537 This is the driver for the hardware watchdog built in to the
538 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
539 This watchdog simply watches your kernel to make sure it doesn't
540 freeze, and if it does, it reboots your computer after a certain
543 You can compile this driver directly into the kernel, or use
544 it as a module. The module will be called sc520_wdt.
546 config SBC_FITPC2_WATCHDOG
547 tristate "Compulab SBC-FITPC2 watchdog"
550 This is the driver for the built-in watchdog timer on the fit-PC2,
551 fit-PC2i, CM-iAM single-board computers made by Compulab.
553 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
554 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
556 Entering BIOS setup temporary disables watchdog operation regardless to current state,
557 so system will not be restarted while user in BIOS setup.
559 Once watchdog was enabled the system will be restarted every
560 "Watchdog Timer Value" period, so to prevent it user can restart or
561 disable the watchdog.
563 To compile this driver as a module, choose M here: the
564 module will be called sbc_fitpc2_wdt.
566 Most people will say N.
569 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
572 Enable support for the watchdog timer on the Eurotech CPU-1220 and
573 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
574 information are at <http://www.eurotech.it/>.
577 tristate "IB700 SBC Watchdog Timer"
580 This is the driver for the hardware watchdog on the IB700 Single
581 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
582 simply watches your kernel to make sure it doesn't freeze, and if
583 it does, it reboots your computer after a certain amount of time.
585 This driver is like the WDT501 driver but for slightly different hardware.
587 To compile this driver as a module, choose M here: the
588 module will be called ib700wdt.
590 Most people will say N.
593 tristate "IBM Automatic Server Restart"
596 This is the driver for the IBM Automatic Server Restart watchdog
597 timer built-in into some eServer xSeries machines.
599 To compile this driver as a module, choose M here: the
600 module will be called ibmasr.
603 tristate "ICP Single Board Computer Watchdog Timer"
606 This is a driver for the hardware watchdog on the ICP Single
607 Board Computer. This driver is working on (at least) the following
608 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
610 To compile this driver as a module, choose M here: the
611 module will be called wafer5823wdt.
614 tristate "Intel 6300ESB Timer/Watchdog"
617 Hardware driver for the watchdog timer built into the Intel
618 6300ESB controller hub.
620 To compile this driver as a module, choose M here: the
621 module will be called i6300esb.
624 tristate "Intel Atom E6xx Watchdog"
625 depends on X86 && PCI
630 Hardware driver for the watchdog timer built into the Intel
631 Atom E6XX (TunnelCreek) processor.
633 To compile this driver as a module, choose M here: the
634 module will be called ie6xx_wdt.
636 config INTEL_SCU_WATCHDOG
637 bool "Intel SCU Watchdog for Mobile Platforms"
638 depends on X86_INTEL_MID
640 Hardware driver for the watchdog time built into the Intel SCU
641 for Intel Mobile Platforms.
643 To compile this driver as a module, choose M here.
646 tristate "Intel TCO Timer/Watchdog"
647 depends on (X86 || IA64) && PCI
651 Hardware driver for the intel TCO timer based watchdog devices.
652 These drivers are included in the Intel 82801 I/O Controller
653 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
656 The TCO (Total Cost of Ownership) timer is a watchdog timer
657 that will reboot the machine after its second expiration. The
658 expiration time can be configured with the "heartbeat" parameter.
660 On some motherboards the driver may fail to reset the chipset's
661 NO_REBOOT flag which prevents the watchdog from rebooting the
662 machine. If this is the case you will get a kernel message like
663 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
665 To compile this driver as a module, choose M here: the
666 module will be called iTCO_wdt.
668 config ITCO_VENDOR_SUPPORT
669 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
672 Add vendor specific support to the intel TCO timer based watchdog
673 devices. At this moment we only have additional support for some
674 SuperMicro Inc. motherboards.
677 tristate "IT8712F (Smart Guardian) Watchdog Timer"
680 This is the driver for the built-in watchdog timer on the IT8712F
681 Super I/0 chipset used on many motherboards.
683 If the driver does not work, then make sure that the game port in
686 To compile this driver as a module, choose M here: the
687 module will be called it8712f_wdt.
690 tristate "IT87 Watchdog Timer"
693 This is the driver for the hardware watchdog on the ITE IT8702,
694 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
697 If the driver does not work, then make sure that the game port in
700 This watchdog simply watches your kernel to make sure it doesn't
701 freeze, and if it does, it reboots your computer after a certain
704 To compile this driver as a module, choose M here: the module will
708 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
709 depends on X86 && PCI
711 A software monitoring watchdog and NMI sourcing driver. This driver
712 will detect lockups and provide a stack trace. This is a driver that
713 will only load on an HP ProLiant system with a minimum of iLO2 support.
714 To compile this driver as a module, choose M here: the module will be
718 tristate "Kontron COM Watchdog Timer"
719 depends on MFD_KEMPLD
722 Support for the PLD watchdog on some Kontron ETX and COMexpress
725 This driver can also be built as a module. If so, the module will be
728 config HPWDT_NMI_DECODING
729 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
730 depends on HP_WATCHDOG
733 When an NMI occurs this feature will make the necessary BIOS calls to
734 log the cause of the NMI.
737 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
740 This is a driver for National Semiconductor PC87307/PC97307 hardware
741 watchdog cards as found on the SC1200. This watchdog is mainly used
742 for power management purposes and can be used to power down the device
743 during inactivity periods (includes interrupt activity monitoring).
745 To compile this driver as a module, choose M here: the
746 module will be called sc1200wdt.
748 Most people will say N.
751 tristate "National Semiconductor SCx200 Watchdog"
752 depends on SCx200 && PCI
754 Enable the built-in watchdog timer support on the National
755 Semiconductor SCx200 processors.
757 If compiled as a module, it will be called scx200_wdt.
760 tristate "NS PC87413 watchdog"
763 This is the driver for the hardware watchdog on the PC87413 chipset
764 This watchdog simply watches your kernel to make sure it doesn't
765 freeze, and if it does, it reboots your computer after a certain
768 To compile this driver as a module, choose M here: the
769 module will be called pc87413_wdt.
771 Most people will say N.
774 tristate "nVidia TCO Timer/Watchdog"
775 depends on X86 && PCI
777 Hardware driver for the TCO timer built into the nVidia Hub family
778 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
779 watchdog timer that will reboot the machine after its second
780 expiration. The expiration time can be configured with the
781 "heartbeat" parameter.
783 On some motherboards the driver may fail to reset the chipset's
784 NO_REBOOT flag which prevents the watchdog from rebooting the
785 machine. If this is the case you will get a kernel message like
786 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
788 To compile this driver as a module, choose M here: the
789 module will be called nv_tco.
792 tristate "RDC R-321x SoC watchdog"
793 depends on X86_RDC321X
795 This is the driver for the built in hardware watchdog
796 in the RDC R-321x SoC.
798 To compile this driver as a module, choose M here: the
799 module will be called rdc321x_wdt.
802 tristate "SBC-60XX Watchdog Timer"
805 This driver can be used with the watchdog timer found on some
806 single board computers, namely the 6010 PII based computer.
807 It may well work with other cards. It reads port 0x443 to enable
808 and re-set the watchdog timer, and reads port 0x45 to disable
809 the watchdog. If you have a card that behave in similar ways,
810 you can probably make this driver work with your card as well.
812 You can compile this driver directly into the kernel, or use
813 it as a module. The module will be called sbc60xxwdt.
816 tristate "SBC8360 Watchdog Timer"
820 This is the driver for the hardware watchdog on the SBC8360 Single
821 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
823 To compile this driver as a module, choose M here: the
824 module will be called sbc8360.
826 Most people will say N.
829 tristate "SBC Nano 7240 Watchdog Timer"
830 depends on X86_32 && !UML
832 This is the driver for the hardware watchdog found on the IEI
833 single board computers EPIC Nano 7240 (and likely others). This
834 watchdog simply watches your kernel to make sure it doesn't freeze,
835 and if it does, it reboots your computer after a certain amount of
838 To compile this driver as a module, choose M here: the
839 module will be called sbc7240_wdt.
842 tristate "SMA CPU5 Watchdog"
846 To compile this driver as a module, choose M here: the
847 module will be called cpu5wdt.
849 config SMSC_SCH311X_WDT
850 tristate "SMSC SCH311X Watchdog Timer"
853 This is the driver for the hardware watchdog timer on the
854 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
855 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
858 To compile this driver as a module, choose M here: the
859 module will be called sch311x_wdt.
861 config SMSC37B787_WDT
862 tristate "Winbond SMsC37B787 Watchdog Timer"
865 This is the driver for the hardware watchdog component on the
866 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
867 from Vision Systems and maybe others.
869 This watchdog simply watches your kernel to make sure it doesn't
870 freeze, and if it does, it reboots your computer after a certain
873 Usually a userspace daemon will notify the kernel WDT driver that
874 userspace is still alive, at regular intervals.
876 To compile this driver as a module, choose M here: the
877 module will be called smsc37b787_wdt.
879 Most people will say N.
882 tristate "VIA Watchdog Timer"
883 depends on X86 && PCI
886 This is the driver for the hardware watchdog timer on VIA
887 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
889 To compile this driver as a module, choose M here; the module
890 will be called via_wdt.
892 Most people will say N.
895 tristate "W83627HF/W83627DHG Watchdog Timer"
899 This is the driver for the hardware watchdog on the W83627HF chipset
900 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
901 (and likely others). The driver also supports the W83627DHG chip.
902 This watchdog simply watches your kernel to make sure it doesn't
903 freeze, and if it does, it reboots your computer after a certain
906 To compile this driver as a module, choose M here: the
907 module will be called w83627hf_wdt.
909 Most people will say N.
912 tristate "W83697HF/W83697HG Watchdog Timer"
915 This is the driver for the hardware watchdog on the W83697HF/HG
916 chipset as used in Dedibox/VIA motherboards (and likely others).
917 This watchdog simply watches your kernel to make sure it doesn't
918 freeze, and if it does, it reboots your computer after a certain
921 To compile this driver as a module, choose M here: the
922 module will be called w83697hf_wdt.
924 Most people will say N.
927 tristate "W83697UG/W83697UF Watchdog Timer"
930 This is the driver for the hardware watchdog on the W83697UG/UF
931 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
932 This watchdog simply watches your kernel to make sure it doesn't
933 freeze, and if it does, it reboots your computer after a certain
936 To compile this driver as a module, choose M here: the
937 module will be called w83697ug_wdt.
939 Most people will say N.
942 tristate "W83877F (EMACS) Watchdog Timer"
945 This is the driver for the hardware watchdog on the W83877F chipset
946 as used in EMACS PC-104 motherboards (and likely others). This
947 watchdog simply watches your kernel to make sure it doesn't freeze,
948 and if it does, it reboots your computer after a certain amount of
951 To compile this driver as a module, choose M here: the
952 module will be called w83877f_wdt.
954 Most people will say N.
957 tristate "W83977F (PCM-5335) Watchdog Timer"
960 This is the driver for the hardware watchdog on the W83977F I/O chip
961 as used in AAEON's PCM-5335 SBC (and likely others). This
962 watchdog simply watches your kernel to make sure it doesn't freeze,
963 and if it does, it reboots your computer after a certain amount of
966 To compile this driver as a module, choose M here: the
967 module will be called w83977f_wdt.
970 tristate "ZF MachZ Watchdog"
973 If you are using a ZF Micro MachZ processor, say Y here, otherwise
974 N. This is the driver for the watchdog timer built-in on that
975 processor using ZF-Logic interface. This watchdog simply watches
976 your kernel to make sure it doesn't freeze, and if it does, it
977 reboots your computer after a certain amount of time.
979 To compile this driver as a module, choose M here: the
980 module will be called machzwd.
982 config SBC_EPX_C3_WATCHDOG
983 tristate "Winsystems SBC EPX-C3 watchdog"
986 This is the driver for the built-in watchdog timer on the EPX-C3
987 Single-board computer made by Winsystems, Inc.
989 *Note*: This hardware watchdog is not probeable and thus there
990 is no way to know if writing to its IO address will corrupt
991 your system or have any real effect. The only way to be sure
992 that this driver does what you want is to make sure you
993 are running it on an EPX-C3 from Winsystems with the watchdog
994 timer at IO address 0x1ee and 0x1ef. It will write to both those
995 IO ports. Basically, the assumption is made that if you compile
996 this driver into your kernel and/or load it as a module, that you
997 know what you are doing and that you are in fact running on an
1000 To compile this driver as a module, choose M here: the
1001 module will be called sbc_epx_c3.
1007 config M54xx_WATCHDOG
1008 tristate "MCF54xx watchdog support"
1011 To compile this driver as a module, choose M here: the
1012 module will be called m54xx_wdt.
1014 # MicroBlaze Architecture
1016 config XILINX_WATCHDOG
1017 tristate "Xilinx Watchdog timer"
1018 depends on MICROBLAZE
1020 Watchdog driver for the xps_timebase_wdt ip core.
1022 IMPORTANT: The xps_timebase_wdt parent must have the property
1023 "clock-frequency" at device tree.
1025 To compile this driver as a module, choose M here: the
1026 module will be called of_xilinx_wdt.
1031 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1034 Hardware driver for the built-in watchdog timer on the Atheros
1035 AR71XX/AR724X/AR913X SoCs.
1038 tristate "Broadcom BCM47xx Watchdog Timer"
1040 select WATCHDOG_CORE
1042 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1045 tristate "IDT RC32434 SoC Watchdog Timer"
1046 depends on MIKROTIK_RB532
1048 Hardware driver for the IDT RC32434 SoC built-in
1051 To compile this driver as a module, choose M here: the
1052 module will be called rc32434_wdt.
1055 tristate "Indy/I2 Hardware Watchdog"
1056 depends on SGI_HAS_INDYDOG
1058 Hardware driver for the Indy's/I2's watchdog. This is a
1059 watchdog timer that will reboot the machine after a 60 second
1060 timer expired and no process has written to /dev/watchdog during
1064 tristate "Ingenic jz4740 SoC hardware watchdog"
1065 depends on MACH_JZ4740
1066 select WATCHDOG_CORE
1068 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1071 tristate "MTX-1 Hardware Watchdog"
1072 depends on MIPS_MTX1
1074 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1075 will reboot the machine after a 100 seconds timer expired.
1078 tristate "PNX833x Hardware Watchdog"
1079 depends on SOC_PNX8335
1081 Hardware driver for the PNX833x's watchdog. This is a
1082 watchdog timer that will reboot the machine after a programmable
1083 timer has expired and no process has written to /dev/watchdog during
1087 tristate "Sibyte SoC hardware watchdog"
1090 Watchdog driver for the built in watchdog hardware in Sibyte
1091 SoC processors. There are apparently two watchdog timers
1092 on such processors; this driver supports only the first one,
1093 because currently Linux only supports exporting one watchdog
1096 To compile this driver as a loadable module, choose M here.
1097 The module will be called sb_wdog.
1100 tristate "TI AR7 Watchdog Timer"
1103 Hardware driver for the TI AR7 Watchdog Timer.
1106 tristate "Toshiba TXx9 Watchdog Timer"
1107 depends on CPU_TX39XX || CPU_TX49XX
1108 select WATCHDOG_CORE
1110 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1113 tristate "Cavium OCTEON SOC family Watchdog Timer"
1114 depends on CAVIUM_OCTEON_SOC
1116 select EXPORT_UASM if OCTEON_WDT = m
1118 Hardware driver for OCTEON's on chip watchdog timer.
1119 Enables the watchdog for all cores running Linux. It
1120 installs a NMI handler and pokes the watchdog based on an
1121 interrupt. On first expiration of the watchdog, the
1122 interrupt handler pokes it. The second expiration causes an
1123 NMI that prints a message. The third expiration causes a
1126 When userspace has /dev/watchdog open, no poking is done
1127 from the first interrupt, it is then only poked when the
1131 tristate "Broadcom BCM63xx hardware watchdog"
1134 Watchdog driver for the built in watchdog hardware in Broadcom
1137 To compile this driver as a loadable module, choose M here.
1138 The module will be called bcm63xx_wdt.
1141 tristate "Broadcom BCM2835 hardware watchdog"
1142 depends on ARCH_BCM2835
1143 select WATCHDOG_CORE
1145 Watchdog driver for the built in watchdog hardware in Broadcom
1148 To compile this driver as a loadable module, choose M here.
1149 The module will be called bcm2835_wdt.
1152 tristate "BCM Kona Watchdog"
1154 select WATCHDOG_CORE
1156 Support for the watchdog timer on the following Broadcom BCM281xx
1157 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1160 Say 'Y' or 'M' here to enable the driver. The module will be called
1163 config BCM_KONA_WDT_DEBUG
1164 bool "DEBUGFS support for BCM Kona Watchdog"
1165 depends on BCM_KONA_WDT
1167 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1168 access to the driver's internal data structures as well as watchdog
1169 timer hardware registres.
1171 If in doubt, say 'N'.
1174 tristate "Lantiq SoC watchdog"
1177 Hardware driver for the Lantiq SoC Watchdog Timer.
1180 tristate "Ralink SoC watchdog"
1181 select WATCHDOG_CORE
1184 Hardware driver for the Ralink SoC Watchdog Timer.
1186 # PARISC Architecture
1188 # POWERPC Architecture
1191 tristate "GE Watchdog Timer"
1194 Watchdog timer found in a number of GE single board computers.
1197 bool "MPC52xx Watchdog Timer"
1198 depends on PPC_MPC52xx
1200 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1203 tristate "MPC8xxx Platform Watchdog Timer"
1204 depends on PPC_8xx || PPC_83xx || PPC_86xx
1205 select WATCHDOG_CORE
1207 This driver is for a SoC level watchdog that exists on some
1208 Freescale PowerPC processors. So far this driver supports:
1213 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1216 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1220 tristate "PIKA FPGA Watchdog"
1224 This enables the watchdog in the PIKA FPGA. Currently used on
1228 tristate "PowerPC Book-E Watchdog Timer"
1229 depends on BOOKE || 4xx
1230 select WATCHDOG_CORE
1232 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1233 MPC85xx SOCs and the IBM PowerPC 440.
1235 Please see Documentation/watchdog/watchdog-api.txt for
1238 config BOOKE_WDT_DEFAULT_TIMEOUT
1239 int "PowerPC Book-E Watchdog Timer Default Timeout"
1240 depends on BOOKE_WDT
1241 default 38 if PPC_FSL_BOOK3E
1242 range 0 63 if PPC_FSL_BOOK3E
1243 default 3 if !PPC_FSL_BOOK3E
1244 range 0 3 if !PPC_FSL_BOOK3E
1246 Select the default watchdog timer period to be used by the PowerPC
1247 Book-E watchdog driver. A watchdog "event" occurs when the bit
1248 position represented by this number transitions from zero to one.
1250 For Freescale Book-E processors, this is a number between 0 and 63.
1251 For other Book-E processors, this is a number between 0 and 3.
1253 The value can be overridden by the wdt_period command-line parameter.
1256 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1257 select WATCHDOG_CORE
1260 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1262 The driver can also be built as a module. If so, the module will be
1265 If unsure select N here.
1267 # PPC64 Architecture
1269 config WATCHDOG_RTAS
1270 tristate "RTAS watchdog"
1273 This driver adds watchdog support for the RTAS watchdog.
1275 To compile this driver as a module, choose M here. The module
1276 will be called wdrtas.
1281 tristate "z/VM Watchdog Timer"
1284 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1285 provide a virtual watchdog timer to their guest that cause a
1286 user define Control Program command to be executed after a
1289 To compile this driver as a module, choose M here. The module
1290 will be called vmwatchdog.
1292 # SUPERH (sh + sh64) Architecture
1295 tristate "SuperH Watchdog"
1296 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1297 select WATCHDOG_CORE
1299 This driver adds watchdog support for the integrated watchdog in the
1300 SuperH processors. If you have one of these processors and wish
1301 to have watchdog support enabled, say Y, otherwise say N.
1303 As a side note, saying Y here will automatically boost HZ to 1000
1304 so that the timer has a chance to clear the overflow counter. On
1305 slower systems (such as the SH-2 and SH-3) this will likely yield
1306 some performance issues. As such, the WDT should be avoided here
1307 unless it is absolutely necessary.
1309 To compile this driver as a module, choose M here: the
1310 module will be called shwdt.
1312 # SPARC Architecture
1314 # SPARC64 Architecture
1316 config WATCHDOG_CP1XXX
1317 tristate "CP1XXX Hardware Watchdog support"
1318 depends on SPARC64 && PCI
1320 This is the driver for the hardware watchdog timers present on
1321 Sun Microsystems CompactPCI models CP1400 and CP1500.
1323 To compile this driver as a module, choose M here: the
1324 module will be called cpwatchdog.
1326 If you do not have a CompactPCI model CP1400 or CP1500, or
1327 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1328 you should say N to this option.
1331 tristate "RIO Hardware Watchdog support"
1332 depends on SPARC64 && PCI
1334 Say Y here to support the hardware watchdog capability on Sun RIO
1335 machines. The watchdog timeout period is normally one minute but
1336 can be changed with a boot-time parameter.
1338 # XTENSA Architecture
1343 tristate "Xen Watchdog support"
1346 Say Y here to support the hypervisor watchdog capability provided
1347 by Xen 4.0 and newer. The watchdog timeout period is normally one
1348 minute but can be changed with a boot-time parameter.
1351 tristate "UML watchdog"
1355 # ISA-based Watchdog Cards
1358 comment "ISA-based Watchdog Cards"
1362 tristate "Berkshire Products ISA-PC Watchdog"
1365 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1366 This card simply watches your kernel to make sure it doesn't freeze,
1367 and if it does, it reboots your computer after a certain amount of
1368 time. This driver is like the WDT501 driver but for different
1369 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1370 watchdog cards can be ordered from <http://www.berkprod.com/>.
1372 To compile this driver as a module, choose M here: the
1373 module will be called pcwd.
1375 Most people will say N.
1378 tristate "Mixcom Watchdog"
1381 This is a driver for the Mixcom hardware watchdog cards. This
1382 watchdog simply watches your kernel to make sure it doesn't freeze,
1383 and if it does, it reboots your computer after a certain amount of
1386 To compile this driver as a module, choose M here: the
1387 module will be called mixcomwd.
1389 Most people will say N.
1392 tristate "WDT Watchdog timer"
1395 If you have a WDT500P or WDT501P watchdog board, say Y here,
1396 otherwise N. It is not possible to probe for this board, which means
1397 that you have to inform the kernel about the IO port and IRQ that
1398 is needed (you can do this via the io and irq parameters)
1400 To compile this driver as a module, choose M here: the
1401 module will be called wdt.
1404 # PCI-based Watchdog Cards
1407 comment "PCI-based Watchdog Cards"
1410 config PCIPCWATCHDOG
1411 tristate "Berkshire Products PCI-PC Watchdog"
1414 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1415 This card simply watches your kernel to make sure it doesn't freeze,
1416 and if it does, it reboots your computer after a certain amount of
1417 time. The card can also monitor the internal temperature of the PC.
1418 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1420 To compile this driver as a module, choose M here: the
1421 module will be called pcwd_pci.
1423 Most people will say N.
1426 tristate "PCI-WDT500/501 Watchdog timer"
1429 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1431 If you have a PCI-WDT501 watchdog board then you can enable the
1432 temperature sensor by setting the type parameter to 501.
1434 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1435 can do this via the tachometer parameter. Only do this if you have a
1436 fan tachometer actually set up.
1438 To compile this driver as a module, choose M here: the
1439 module will be called wdt_pci.
1442 # USB-based Watchdog Cards
1445 comment "USB-based Watchdog Cards"
1448 config USBPCWATCHDOG
1449 tristate "Berkshire Products USB-PC Watchdog"
1452 This is the driver for the Berkshire Products USB-PC Watchdog card.
1453 This card simply watches your kernel to make sure it doesn't freeze,
1454 and if it does, it reboots your computer after a certain amount of
1455 time. The card can also monitor the internal temperature of the PC.
1456 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1458 To compile this driver as a module, choose M here: the
1459 module will be called pcwd_usb.
1461 Most people will say N.