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.
110 config ARM_SP805_WATCHDOG
111 tristate "ARM SP805 Watchdog"
115 ARM Primecell SP805 Watchdog timer. This will reboot your system when
116 the timeout is reached.
118 config AT91RM9200_WATCHDOG
119 tristate "AT91RM9200 watchdog"
120 depends on ARCH_AT91RM9200
122 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
123 system when the timeout is reached.
125 config AT91SAM9X_WATCHDOG
126 tristate "AT91SAM9X / AT91CAP9 watchdog"
127 depends on ARCH_AT91 && !ARCH_AT91RM9200
129 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
130 reboot your system when the timeout is reached.
132 config 21285_WATCHDOG
133 tristate "DC21285 watchdog"
134 depends on FOOTBRIDGE
136 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
137 here if you wish to use this. Alternatively say M to compile the
138 driver as a module, which will be called wdt285.
140 This driver does not work on all machines. In particular, early CATS
141 boards have hardware problems that will cause the machine to simply
142 lock up if the watchdog fires.
144 "If in doubt, leave it out" - say N.
147 tristate "NetWinder WB83C977 watchdog"
148 depends on FOOTBRIDGE && ARCH_NETWINDER
150 Say Y here to include support for the WB977 watchdog included in
151 NetWinder machines. Alternatively say M to compile the driver as
152 a module, which will be called wdt977.
154 Not sure? It's safe to say N.
156 config IXP4XX_WATCHDOG
157 tristate "IXP4xx Watchdog"
158 depends on ARCH_IXP4XX
160 Say Y here if to include support for the watchdog timer
161 in the Intel IXP4xx network processors. This driver can
162 be built as a module by choosing M. The module will
163 be called ixp4xx_wdt.
165 Note: The internal IXP4xx watchdog does a soft CPU reset
166 which doesn't reset any peripherals. There are circumstances
167 where the watchdog will fail to reset the board correctly
168 (e.g., if the boot ROM is in an unreadable state).
170 Say N if you are unsure.
172 config KS8695_WATCHDOG
173 tristate "KS8695 watchdog"
174 depends on ARCH_KS8695
176 Watchdog timer embedded into KS8695 processor. This will reboot your
177 system when the timeout is reached.
179 config HAVE_S3C2410_WATCHDOG
182 This will include watchdog timer support for Samsung SoCs. If
183 you want to include watchdog support for any machine, kindly
184 select this in the respective mach-XXXX/Kconfig file.
186 config S3C2410_WATCHDOG
187 tristate "S3C2410 Watchdog"
188 depends on HAVE_S3C2410_WATCHDOG
191 Watchdog timer block in the Samsung SoCs. This will reboot
192 the system when the timer expires with the watchdog enabled.
194 The driver is limited by the speed of the system's PCLK
195 signal, so with reasonably fast systems (PCLK around 50-66MHz)
196 then watchdog intervals of over approximately 20seconds are
199 The driver can be built as a module by choosing M, and will
200 be called s3c2410_wdt
202 config SA1100_WATCHDOG
203 tristate "SA1100/PXA2xx watchdog"
204 depends on ARCH_SA1100 || ARCH_PXA
206 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
207 reboot your system when timeout is reached.
209 NOTE: once enabled, this timer cannot be disabled.
211 To compile this driver as a module, choose M here: the
212 module will be called sa1100_wdt.
215 tristate "Synopsys DesignWare watchdog"
216 depends on ARM && HAVE_CLK
218 Say Y here if to include support for the Synopsys DesignWare
219 watchdog timer found in many ARM chips.
220 To compile this driver as a module, choose M here: the
221 module will be called dw_wdt.
223 config MPCORE_WATCHDOG
224 tristate "MPcore watchdog"
225 depends on HAVE_ARM_TWD
227 Watchdog timer embedded into the MPcore system.
229 To compile this driver as a module, choose M here: the
230 module will be called mpcore_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
283 Say Y here if to include support for the watchdog timer
284 in the DaVinci DM644x/DM646x processors.
285 To compile this driver as a module, choose M here: the
286 module will be called davinci_wdt.
288 NOTE: once enabled, this timer cannot be disabled.
289 Say N if you are unsure.
291 config ORION_WATCHDOG
292 tristate "Orion watchdog"
293 depends on ARCH_ORION5X || ARCH_KIRKWOOD
296 Say Y here if to include support for the watchdog timer
297 in the Marvell Orion5x and Kirkwood ARM SoCs.
298 To compile this driver as a module, choose M here: the
299 module will be called orion_wdt.
301 config COH901327_WATCHDOG
302 bool "ST-Ericsson COH 901 327 watchdog"
304 default y if MACH_U300
307 Say Y here to include Watchdog timer support for the
308 watchdog embedded into the ST-Ericsson U300 series platforms.
309 This watchdog is used to reset the system and thus cannot be
310 compiled as a module.
312 config TWL4030_WATCHDOG
313 tristate "TWL4030 Watchdog"
314 depends on TWL4030_CORE
317 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
318 watchdog timer support for TWL4030 chips.
320 config STMP3XXX_WATCHDOG
321 tristate "Freescale STMP3XXX watchdog"
322 depends on ARCH_STMP3XXX
324 Say Y here if to include support for the watchdog timer
325 for the Sigmatel STMP37XX/378X SoC.
326 To compile this driver as a module, choose M here: the
327 module will be called stmp3xxx_wdt.
329 config NUC900_WATCHDOG
330 tristate "Nuvoton NUC900 watchdog"
331 depends on ARCH_W90X900
333 Say Y here if to include support for the watchdog timer
334 for the Nuvoton NUC900 series SoCs.
335 To compile this driver as a module, choose M here: the
336 module will be called nuc900_wdt.
338 config TS72XX_WATCHDOG
339 tristate "TS-72XX SBC Watchdog"
340 depends on MACH_TS72XX
342 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
343 watchdog timer implemented in a external CPLD chip. Say Y here
344 if you want to support for the watchdog timer on TS-72XX boards.
346 To compile this driver as a module, choose M here: the
347 module will be called ts72xx_wdt.
349 config MAX63XX_WATCHDOG
350 tristate "Max63xx watchdog"
351 depends on ARM && HAS_IOMEM
354 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
357 tristate "IMX2+ Watchdog"
360 This is the driver for the hardware watchdog
361 on the Freescale IMX2 and later processors.
362 If you have one of these processors and wish to have
363 watchdog support enabled, say Y, otherwise say N.
365 To compile this driver as a module, choose M here: the
366 module will be called imx2_wdt.
368 config UX500_WATCHDOG
369 tristate "ST-Ericsson Ux500 watchdog"
370 depends on MFD_DB8500_PRCMU
374 Say Y here to include Watchdog timer support for the watchdog
375 existing in the prcmu of ST-Ericsson Ux500 series platforms.
377 To compile this driver as a module, choose M here: the
378 module will be called ux500_wdt.
381 tristate "Retu watchdog"
385 Retu watchdog driver for Nokia Internet Tablets (770, N800,
386 N810). At least on N800 the watchdog cannot be disabled, so
387 this driver is essential and you should enable it.
389 To compile this driver as a module, choose M here: the
390 module will be called retu_wdt.
394 config AT32AP700X_WDT
395 tristate "AT32AP700x watchdog"
396 depends on CPU_AT32AP700X
398 Watchdog timer embedded into AT32AP700x devices. This will reboot
399 your system when the timeout is reached.
401 # BLACKFIN Architecture
404 tristate "Blackfin On-Chip Watchdog Timer"
407 If you say yes here you will get support for the Blackfin On-Chip
408 Watchdog Timer. If you have one of these processors and wish to
409 have watchdog support enabled, say Y, otherwise say N.
411 To compile this driver as a module, choose M here: the
412 module will be called bfin_wdt.
420 # X86 (i386 + ia64 + x86_64) Architecture
423 tristate "Acquire SBC Watchdog Timer"
426 This is the driver for the hardware watchdog on Single Board
427 Computers produced by Acquire Inc (and others). This watchdog
428 simply watches your kernel to make sure it doesn't freeze, and if
429 it does, it reboots your computer after a certain amount of time.
431 To compile this driver as a module, choose M here: the
432 module will be called acquirewdt.
434 Most people will say N.
437 tristate "Advantech SBC Watchdog Timer"
440 If you are configuring a Linux kernel for the Advantech single-board
441 computer, say `Y' here to support its built-in watchdog timer
442 feature. More information can be found at
443 <http://www.advantech.com.tw/products/>
446 tristate "ALi M1535 PMU Watchdog Timer"
447 depends on X86 && PCI
449 This is the driver for the hardware watchdog on the ALi M1535 PMU.
451 To compile this driver as a module, choose M here: the
452 module will be called alim1535_wdt.
454 Most people will say N.
457 tristate "ALi M7101 PMU Computer Watchdog"
460 This is the driver for the hardware watchdog on the ALi M7101 PMU
461 as used in the x86 Cobalt servers and also found in some
462 SPARC Netra servers too.
464 To compile this driver as a module, choose M here: the
465 module will be called alim7101_wdt.
467 Most people will say N.
470 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
473 This is the driver for the hardware watchdog on the Fintek
474 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
476 You can compile this driver directly into the kernel, or use
477 it as a module. The module will be called f71808e_wdt.
480 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
481 depends on X86 && PCI
483 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
484 (Total Cost of Ownership) timer is a watchdog timer that will reboot
485 the machine after its expiration. The expiration time can be
486 configured with the "heartbeat" parameter.
488 To compile this driver as a module, choose M here: the
489 module will be called sp5100_tco.
492 tristate "AMD Geode CS5535/CS5536 Watchdog"
493 depends on CS5535_MFGPT
495 This driver enables a watchdog capability built into the
496 CS5535/CS5536 companion chips for the AMD Geode GX and LX
497 processors. This watchdog watches your kernel to make sure
498 it doesn't freeze, and if it does, it reboots your computer after
499 a certain amount of time.
501 You can compile this driver directly into the kernel, or use
502 it as a module. The module will be called geodewdt.
505 tristate "AMD Elan SC520 processor Watchdog"
508 This is the driver for the hardware watchdog built in to the
509 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
510 This watchdog simply watches your kernel to make sure it doesn't
511 freeze, and if it does, it reboots your computer after a certain
514 You can compile this driver directly into the kernel, or use
515 it as a module. The module will be called sc520_wdt.
517 config SBC_FITPC2_WATCHDOG
518 tristate "Compulab SBC-FITPC2 watchdog"
521 This is the driver for the built-in watchdog timer on the fit-PC2,
522 fit-PC2i, CM-iAM single-board computers made by Compulab.
524 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
525 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
527 Entering BIOS setup temporary disables watchdog operation regardless to current state,
528 so system will not be restarted while user in BIOS setup.
530 Once watchdog was enabled the system will be restarted every
531 "Watchdog Timer Value" period, so to prevent it user can restart or
532 disable the watchdog.
534 To compile this driver as a module, choose M here: the
535 module will be called sbc_fitpc2_wdt.
537 Most people will say N.
540 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
543 Enable support for the watchdog timer on the Eurotech CPU-1220 and
544 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
545 information are at <http://www.eurotech.it/>.
548 tristate "IB700 SBC Watchdog Timer"
551 This is the driver for the hardware watchdog on the IB700 Single
552 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
553 simply watches your kernel to make sure it doesn't freeze, and if
554 it does, it reboots your computer after a certain amount of time.
556 This driver is like the WDT501 driver but for slightly different hardware.
558 To compile this driver as a module, choose M here: the
559 module will be called ib700wdt.
561 Most people will say N.
564 tristate "IBM Automatic Server Restart"
567 This is the driver for the IBM Automatic Server Restart watchdog
568 timer built-in into some eServer xSeries machines.
570 To compile this driver as a module, choose M here: the
571 module will be called ibmasr.
574 tristate "ICP Single Board Computer Watchdog Timer"
577 This is a driver for the hardware watchdog on the ICP Single
578 Board Computer. This driver is working on (at least) the following
579 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
581 To compile this driver as a module, choose M here: the
582 module will be called wafer5823wdt.
585 tristate "Intel 6300ESB Timer/Watchdog"
588 Hardware driver for the watchdog timer built into the Intel
589 6300ESB controller hub.
591 To compile this driver as a module, choose M here: the
592 module will be called i6300esb.
595 tristate "Intel Atom E6xx Watchdog"
596 depends on X86 && PCI
601 Hardware driver for the watchdog timer built into the Intel
602 Atom E6XX (TunnelCreek) processor.
604 To compile this driver as a module, choose M here: the
605 module will be called ie6xx_wdt.
607 config INTEL_SCU_WATCHDOG
608 bool "Intel SCU Watchdog for Mobile Platforms"
609 depends on X86_INTEL_MID
611 Hardware driver for the watchdog time built into the Intel SCU
612 for Intel Mobile Platforms.
614 To compile this driver as a module, choose M here.
617 tristate "Intel TCO Timer/Watchdog"
618 depends on (X86 || IA64) && PCI
622 Hardware driver for the intel TCO timer based watchdog devices.
623 These drivers are included in the Intel 82801 I/O Controller
624 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
627 The TCO (Total Cost of Ownership) timer is a watchdog timer
628 that will reboot the machine after its second expiration. The
629 expiration time can be configured with the "heartbeat" parameter.
631 On some motherboards the driver may fail to reset the chipset's
632 NO_REBOOT flag which prevents the watchdog from rebooting the
633 machine. If this is the case you will get a kernel message like
634 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
636 To compile this driver as a module, choose M here: the
637 module will be called iTCO_wdt.
639 config ITCO_VENDOR_SUPPORT
640 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
643 Add vendor specific support to the intel TCO timer based watchdog
644 devices. At this moment we only have additional support for some
645 SuperMicro Inc. motherboards.
648 tristate "IT8712F (Smart Guardian) Watchdog Timer"
651 This is the driver for the built-in watchdog timer on the IT8712F
652 Super I/0 chipset used on many motherboards.
654 If the driver does not work, then make sure that the game port in
657 To compile this driver as a module, choose M here: the
658 module will be called it8712f_wdt.
661 tristate "IT87 Watchdog Timer"
664 This is the driver for the hardware watchdog on the ITE IT8702,
665 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
668 If the driver does not work, then make sure that the game port in
671 This watchdog simply watches your kernel to make sure it doesn't
672 freeze, and if it does, it reboots your computer after a certain
675 To compile this driver as a module, choose M here: the module will
679 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
680 depends on X86 && PCI
682 A software monitoring watchdog and NMI sourcing driver. This driver
683 will detect lockups and provide a stack trace. This is a driver that
684 will only load on an HP ProLiant system with a minimum of iLO2 support.
685 To compile this driver as a module, choose M here: the module will be
688 config HPWDT_NMI_DECODING
689 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
690 depends on HP_WATCHDOG
693 When an NMI occurs this feature will make the necessary BIOS calls to
694 log the cause of the NMI.
697 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
700 This is a driver for National Semiconductor PC87307/PC97307 hardware
701 watchdog cards as found on the SC1200. This watchdog is mainly used
702 for power management purposes and can be used to power down the device
703 during inactivity periods (includes interrupt activity monitoring).
705 To compile this driver as a module, choose M here: the
706 module will be called sc1200wdt.
708 Most people will say N.
711 tristate "National Semiconductor SCx200 Watchdog"
712 depends on SCx200 && PCI
714 Enable the built-in watchdog timer support on the National
715 Semiconductor SCx200 processors.
717 If compiled as a module, it will be called scx200_wdt.
720 tristate "NS PC87413 watchdog"
723 This is the driver for the hardware watchdog on the PC87413 chipset
724 This watchdog simply watches your kernel to make sure it doesn't
725 freeze, and if it does, it reboots your computer after a certain
728 To compile this driver as a module, choose M here: the
729 module will be called pc87413_wdt.
731 Most people will say N.
734 tristate "nVidia TCO Timer/Watchdog"
735 depends on X86 && PCI
737 Hardware driver for the TCO timer built into the nVidia Hub family
738 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
739 watchdog timer that will reboot the machine after its second
740 expiration. The expiration time can be configured with the
741 "heartbeat" parameter.
743 On some motherboards the driver may fail to reset the chipset's
744 NO_REBOOT flag which prevents the watchdog from rebooting the
745 machine. If this is the case you will get a kernel message like
746 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
748 To compile this driver as a module, choose M here: the
749 module will be called nv_tco.
752 tristate "RDC R-321x SoC watchdog"
753 depends on X86_RDC321X
755 This is the driver for the built in hardware watchdog
756 in the RDC R-321x SoC.
758 To compile this driver as a module, choose M here: the
759 module will be called rdc321x_wdt.
762 tristate "SBC-60XX Watchdog Timer"
765 This driver can be used with the watchdog timer found on some
766 single board computers, namely the 6010 PII based computer.
767 It may well work with other cards. It reads port 0x443 to enable
768 and re-set the watchdog timer, and reads port 0x45 to disable
769 the watchdog. If you have a card that behave in similar ways,
770 you can probably make this driver work with your card as well.
772 You can compile this driver directly into the kernel, or use
773 it as a module. The module will be called sbc60xxwdt.
776 tristate "SBC8360 Watchdog Timer"
780 This is the driver for the hardware watchdog on the SBC8360 Single
781 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
783 To compile this driver as a module, choose M here: the
784 module will be called sbc8360.
786 Most people will say N.
789 tristate "SBC Nano 7240 Watchdog Timer"
790 depends on X86_32 && !UML
792 This is the driver for the hardware watchdog found on the IEI
793 single board computers EPIC Nano 7240 (and likely others). This
794 watchdog simply watches your kernel to make sure it doesn't freeze,
795 and if it does, it reboots your computer after a certain amount of
798 To compile this driver as a module, choose M here: the
799 module will be called sbc7240_wdt.
802 tristate "SMA CPU5 Watchdog"
806 To compile this driver as a module, choose M here: the
807 module will be called cpu5wdt.
809 config SMSC_SCH311X_WDT
810 tristate "SMSC SCH311X Watchdog Timer"
813 This is the driver for the hardware watchdog timer on the
814 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
815 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
818 To compile this driver as a module, choose M here: the
819 module will be called sch311x_wdt.
821 config SMSC37B787_WDT
822 tristate "Winbond SMsC37B787 Watchdog Timer"
825 This is the driver for the hardware watchdog component on the
826 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
827 from Vision Systems and maybe others.
829 This watchdog simply watches your kernel to make sure it doesn't
830 freeze, and if it does, it reboots your computer after a certain
833 Usually a userspace daemon will notify the kernel WDT driver that
834 userspace is still alive, at regular intervals.
836 To compile this driver as a module, choose M here: the
837 module will be called smsc37b787_wdt.
839 Most people will say N.
842 tristate "VIA Watchdog Timer"
843 depends on X86 && PCI
846 This is the driver for the hardware watchdog timer on VIA
847 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
849 To compile this driver as a module, choose M here; the module
850 will be called via_wdt.
852 Most people will say N.
855 tristate "W83627HF/W83627DHG Watchdog Timer"
858 This is the driver for the hardware watchdog on the W83627HF chipset
859 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
860 (and likely others). The driver also supports the W83627DHG chip.
861 This watchdog simply watches your kernel to make sure it doesn't
862 freeze, and if it does, it reboots your computer after a certain
865 To compile this driver as a module, choose M here: the
866 module will be called w83627hf_wdt.
868 Most people will say N.
871 tristate "W83697HF/W83697HG Watchdog Timer"
874 This is the driver for the hardware watchdog on the W83697HF/HG
875 chipset as used in Dedibox/VIA motherboards (and likely others).
876 This watchdog simply watches your kernel to make sure it doesn't
877 freeze, and if it does, it reboots your computer after a certain
880 To compile this driver as a module, choose M here: the
881 module will be called w83697hf_wdt.
883 Most people will say N.
886 tristate "W83697UG/W83697UF Watchdog Timer"
889 This is the driver for the hardware watchdog on the W83697UG/UF
890 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
891 This watchdog simply watches your kernel to make sure it doesn't
892 freeze, and if it does, it reboots your computer after a certain
895 To compile this driver as a module, choose M here: the
896 module will be called w83697ug_wdt.
898 Most people will say N.
901 tristate "W83877F (EMACS) Watchdog Timer"
904 This is the driver for the hardware watchdog on the W83877F chipset
905 as used in EMACS PC-104 motherboards (and likely others). This
906 watchdog simply watches your kernel to make sure it doesn't freeze,
907 and if it does, it reboots your computer after a certain amount of
910 To compile this driver as a module, choose M here: the
911 module will be called w83877f_wdt.
913 Most people will say N.
916 tristate "W83977F (PCM-5335) Watchdog Timer"
919 This is the driver for the hardware watchdog on the W83977F I/O chip
920 as used in AAEON's PCM-5335 SBC (and likely others). This
921 watchdog simply watches your kernel to make sure it doesn't freeze,
922 and if it does, it reboots your computer after a certain amount of
925 To compile this driver as a module, choose M here: the
926 module will be called w83977f_wdt.
929 tristate "ZF MachZ Watchdog"
932 If you are using a ZF Micro MachZ processor, say Y here, otherwise
933 N. This is the driver for the watchdog timer built-in on that
934 processor using ZF-Logic interface. This watchdog simply watches
935 your kernel to make sure it doesn't freeze, and if it does, it
936 reboots your computer after a certain amount of time.
938 To compile this driver as a module, choose M here: the
939 module will be called machzwd.
941 config SBC_EPX_C3_WATCHDOG
942 tristate "Winsystems SBC EPX-C3 watchdog"
945 This is the driver for the built-in watchdog timer on the EPX-C3
946 Single-board computer made by Winsystems, Inc.
948 *Note*: This hardware watchdog is not probeable and thus there
949 is no way to know if writing to its IO address will corrupt
950 your system or have any real effect. The only way to be sure
951 that this driver does what you want is to make sure you
952 are running it on an EPX-C3 from Winsystems with the watchdog
953 timer at IO address 0x1ee and 0x1ef. It will write to both those
954 IO ports. Basically, the assumption is made that if you compile
955 this driver into your kernel and/or load it as a module, that you
956 know what you are doing and that you are in fact running on an
959 To compile this driver as a module, choose M here: the
960 module will be called sbc_epx_c3.
966 config M54xx_WATCHDOG
967 tristate "MCF54xx watchdog support"
970 To compile this driver as a module, choose M here: the
971 module will be called m54xx_wdt.
973 # MicroBlaze Architecture
975 config XILINX_WATCHDOG
976 tristate "Xilinx Watchdog timer"
977 depends on MICROBLAZE
979 Watchdog driver for the xps_timebase_wdt ip core.
981 IMPORTANT: The xps_timebase_wdt parent must have the property
982 "clock-frequency" at device tree.
984 To compile this driver as a module, choose M here: the
985 module will be called of_xilinx_wdt.
990 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
993 Hardware driver for the built-in watchdog timer on the Atheros
994 AR71XX/AR724X/AR913X SoCs.
997 tristate "Broadcom BCM47xx Watchdog Timer"
1000 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1003 tristate "IDT RC32434 SoC Watchdog Timer"
1004 depends on MIKROTIK_RB532
1006 Hardware driver for the IDT RC32434 SoC built-in
1009 To compile this driver as a module, choose M here: the
1010 module will be called rc32434_wdt.
1013 tristate "Indy/I2 Hardware Watchdog"
1014 depends on SGI_HAS_INDYDOG
1016 Hardware driver for the Indy's/I2's watchdog. This is a
1017 watchdog timer that will reboot the machine after a 60 second
1018 timer expired and no process has written to /dev/watchdog during
1022 tristate "Ingenic jz4740 SoC hardware watchdog"
1023 depends on MACH_JZ4740
1024 select WATCHDOG_CORE
1026 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1029 tristate "MTX-1 Hardware Watchdog"
1030 depends on MIPS_MTX1
1032 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1033 will reboot the machine after a 100 seconds timer expired.
1036 tristate "PNX833x Hardware Watchdog"
1037 depends on SOC_PNX8335
1039 Hardware driver for the PNX833x's watchdog. This is a
1040 watchdog timer that will reboot the machine after a programmable
1041 timer has expired and no process has written to /dev/watchdog during
1045 tristate "Sibyte SoC hardware watchdog"
1048 Watchdog driver for the built in watchdog hardware in Sibyte
1049 SoC processors. There are apparently two watchdog timers
1050 on such processors; this driver supports only the first one,
1051 because currently Linux only supports exporting one watchdog
1054 To compile this driver as a loadable module, choose M here.
1055 The module will be called sb_wdog.
1058 tristate "TI AR7 Watchdog Timer"
1061 Hardware driver for the TI AR7 Watchdog Timer.
1064 tristate "Toshiba TXx9 Watchdog Timer"
1065 depends on CPU_TX39XX || CPU_TX49XX
1066 select WATCHDOG_CORE
1068 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1071 tristate "Cavium OCTEON SOC family Watchdog Timer"
1072 depends on CPU_CAVIUM_OCTEON
1074 select EXPORT_UASM if OCTEON_WDT = m
1076 Hardware driver for OCTEON's on chip watchdog timer.
1077 Enables the watchdog for all cores running Linux. It
1078 installs a NMI handler and pokes the watchdog based on an
1079 interrupt. On first expiration of the watchdog, the
1080 interrupt handler pokes it. The second expiration causes an
1081 NMI that prints a message. The third expiration causes a
1084 When userspace has /dev/watchdog open, no poking is done
1085 from the first interrupt, it is then only poked when the
1089 tristate "Broadcom BCM63xx hardware watchdog"
1092 Watchdog driver for the built in watchdog hardware in Broadcom
1095 To compile this driver as a loadable module, choose M here.
1096 The module will be called bcm63xx_wdt.
1099 tristate "Lantiq SoC watchdog"
1102 Hardware driver for the Lantiq SoC Watchdog Timer.
1104 # PARISC Architecture
1106 # POWERPC Architecture
1109 tristate "GE Watchdog Timer"
1112 Watchdog timer found in a number of GE single board computers.
1115 bool "MPC52xx Watchdog Timer"
1116 depends on PPC_MPC52xx
1118 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1121 tristate "MPC8xxx Platform Watchdog Timer"
1122 depends on PPC_8xx || PPC_83xx || PPC_86xx
1124 This driver is for a SoC level watchdog that exists on some
1125 Freescale PowerPC processors. So far this driver supports:
1130 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1133 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1137 tristate "PIKA FPGA Watchdog"
1141 This enables the watchdog in the PIKA FPGA. Currently used on
1145 tristate "PowerPC Book-E Watchdog Timer"
1146 depends on BOOKE || 4xx
1148 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1149 MPC85xx SOCs and the IBM PowerPC 440.
1151 Please see Documentation/watchdog/watchdog-api.txt for
1154 config BOOKE_WDT_DEFAULT_TIMEOUT
1155 int "PowerPC Book-E Watchdog Timer Default Timeout"
1156 depends on BOOKE_WDT
1157 default 38 if PPC_FSL_BOOK3E
1158 range 0 63 if PPC_FSL_BOOK3E
1159 default 3 if !PPC_FSL_BOOK3E
1160 range 0 3 if !PPC_FSL_BOOK3E
1162 Select the default watchdog timer period to be used by the PowerPC
1163 Book-E watchdog driver. A watchdog "event" occurs when the bit
1164 position represented by this number transitions from zero to one.
1166 For Freescale Book-E processors, this is a number between 0 and 63.
1167 For other Book-E processors, this is a number between 0 and 3.
1169 The value can be overridden by the wdt_period command-line parameter.
1171 # PPC64 Architecture
1173 config WATCHDOG_RTAS
1174 tristate "RTAS watchdog"
1177 This driver adds watchdog support for the RTAS watchdog.
1179 To compile this driver as a module, choose M here. The module
1180 will be called wdrtas.
1185 tristate "z/VM Watchdog Timer"
1188 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1189 provide a virtual watchdog timer to their guest that cause a
1190 user define Control Program command to be executed after a
1193 To compile this driver as a module, choose M here. The module
1194 will be called vmwatchdog.
1196 # SUPERH (sh + sh64) Architecture
1199 tristate "SuperH Watchdog"
1200 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1201 select WATCHDOG_CORE
1203 This driver adds watchdog support for the integrated watchdog in the
1204 SuperH processors. If you have one of these processors and wish
1205 to have watchdog support enabled, say Y, otherwise say N.
1207 As a side note, saying Y here will automatically boost HZ to 1000
1208 so that the timer has a chance to clear the overflow counter. On
1209 slower systems (such as the SH-2 and SH-3) this will likely yield
1210 some performance issues. As such, the WDT should be avoided here
1211 unless it is absolutely necessary.
1213 To compile this driver as a module, choose M here: the
1214 module will be called shwdt.
1216 # SPARC Architecture
1218 # SPARC64 Architecture
1220 config WATCHDOG_CP1XXX
1221 tristate "CP1XXX Hardware Watchdog support"
1222 depends on SPARC64 && PCI
1224 This is the driver for the hardware watchdog timers present on
1225 Sun Microsystems CompactPCI models CP1400 and CP1500.
1227 To compile this driver as a module, choose M here: the
1228 module will be called cpwatchdog.
1230 If you do not have a CompactPCI model CP1400 or CP1500, or
1231 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1232 you should say N to this option.
1235 tristate "RIO Hardware Watchdog support"
1236 depends on SPARC64 && PCI
1238 Say Y here to support the hardware watchdog capability on Sun RIO
1239 machines. The watchdog timeout period is normally one minute but
1240 can be changed with a boot-time parameter.
1242 # XTENSA Architecture
1247 tristate "Xen Watchdog support"
1250 Say Y here to support the hypervisor watchdog capability provided
1251 by Xen 4.0 and newer. The watchdog timeout period is normally one
1252 minute but can be changed with a boot-time parameter.
1255 tristate "UML watchdog"
1259 # ISA-based Watchdog Cards
1262 comment "ISA-based Watchdog Cards"
1266 tristate "Berkshire Products ISA-PC Watchdog"
1269 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1270 This card simply watches your kernel to make sure it doesn't freeze,
1271 and if it does, it reboots your computer after a certain amount of
1272 time. This driver is like the WDT501 driver but for different
1273 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1274 watchdog cards can be ordered from <http://www.berkprod.com/>.
1276 To compile this driver as a module, choose M here: the
1277 module will be called pcwd.
1279 Most people will say N.
1282 tristate "Mixcom Watchdog"
1285 This is a driver for the Mixcom hardware watchdog cards. This
1286 watchdog simply watches your kernel to make sure it doesn't freeze,
1287 and if it does, it reboots your computer after a certain amount of
1290 To compile this driver as a module, choose M here: the
1291 module will be called mixcomwd.
1293 Most people will say N.
1296 tristate "WDT Watchdog timer"
1299 If you have a WDT500P or WDT501P watchdog board, say Y here,
1300 otherwise N. It is not possible to probe for this board, which means
1301 that you have to inform the kernel about the IO port and IRQ that
1302 is needed (you can do this via the io and irq parameters)
1304 To compile this driver as a module, choose M here: the
1305 module will be called wdt.
1308 # PCI-based Watchdog Cards
1311 comment "PCI-based Watchdog Cards"
1314 config PCIPCWATCHDOG
1315 tristate "Berkshire Products PCI-PC Watchdog"
1318 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1319 This card simply watches your kernel to make sure it doesn't freeze,
1320 and if it does, it reboots your computer after a certain amount of
1321 time. The card can also monitor the internal temperature of the PC.
1322 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1324 To compile this driver as a module, choose M here: the
1325 module will be called pcwd_pci.
1327 Most people will say N.
1330 tristate "PCI-WDT500/501 Watchdog timer"
1333 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1335 If you have a PCI-WDT501 watchdog board then you can enable the
1336 temperature sensor by setting the type parameter to 501.
1338 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1339 can do this via the tachometer parameter. Only do this if you have a
1340 fan tachometer actually set up.
1342 To compile this driver as a module, choose M here: the
1343 module will be called wdt_pci.
1346 # USB-based Watchdog Cards
1349 comment "USB-based Watchdog Cards"
1352 config USBPCWATCHDOG
1353 tristate "Berkshire Products USB-PC Watchdog"
1356 This is the driver for the Berkshire Products USB-PC Watchdog card.
1357 This card simply watches your kernel to make sure it doesn't freeze,
1358 and if it does, it reboots your computer after a certain amount of
1359 time. The card can also monitor the internal temperature of the PC.
1360 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1362 To compile this driver as a module, choose M here: the
1363 module will be called pcwd_usb.
1365 Most people will say N.