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_RTC_WATCHDOG
321 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
322 depends on RTC_DRV_STMP
325 Say Y here to include support for the watchdog timer inside
326 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
327 To compile this driver as a module, choose M here: the
328 module will be called stmp3xxx_rtc_wdt.
330 config NUC900_WATCHDOG
331 tristate "Nuvoton NUC900 watchdog"
332 depends on ARCH_W90X900
334 Say Y here if to include support for the watchdog timer
335 for the Nuvoton NUC900 series SoCs.
336 To compile this driver as a module, choose M here: the
337 module will be called nuc900_wdt.
339 config TS72XX_WATCHDOG
340 tristate "TS-72XX SBC Watchdog"
341 depends on MACH_TS72XX
343 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
344 watchdog timer implemented in a external CPLD chip. Say Y here
345 if you want to support for the watchdog timer on TS-72XX boards.
347 To compile this driver as a module, choose M here: the
348 module will be called ts72xx_wdt.
350 config MAX63XX_WATCHDOG
351 tristate "Max63xx watchdog"
352 depends on ARM && HAS_IOMEM
355 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
358 tristate "IMX2+ Watchdog"
361 This is the driver for the hardware watchdog
362 on the Freescale IMX2 and later processors.
363 If you have one of these processors and wish to have
364 watchdog support enabled, say Y, otherwise say N.
366 To compile this driver as a module, choose M here: the
367 module will be called imx2_wdt.
369 config UX500_WATCHDOG
370 tristate "ST-Ericsson Ux500 watchdog"
371 depends on MFD_DB8500_PRCMU
375 Say Y here to include Watchdog timer support for the watchdog
376 existing in the prcmu of ST-Ericsson Ux500 series platforms.
378 To compile this driver as a module, choose M here: the
379 module will be called ux500_wdt.
382 tristate "Retu watchdog"
386 Retu watchdog driver for Nokia Internet Tablets (770, N800,
387 N810). At least on N800 the watchdog cannot be disabled, so
388 this driver is essential and you should enable it.
390 To compile this driver as a module, choose M here: the
391 module will be called retu_wdt.
395 config AT32AP700X_WDT
396 tristate "AT32AP700x watchdog"
397 depends on CPU_AT32AP700X
399 Watchdog timer embedded into AT32AP700x devices. This will reboot
400 your system when the timeout is reached.
402 # BLACKFIN Architecture
405 tristate "Blackfin On-Chip Watchdog Timer"
408 If you say yes here you will get support for the Blackfin On-Chip
409 Watchdog Timer. If you have one of these processors and wish to
410 have watchdog support enabled, say Y, otherwise say N.
412 To compile this driver as a module, choose M here: the
413 module will be called bfin_wdt.
421 # X86 (i386 + ia64 + x86_64) Architecture
424 tristate "Acquire SBC Watchdog Timer"
427 This is the driver for the hardware watchdog on Single Board
428 Computers produced by Acquire Inc (and others). This watchdog
429 simply watches your kernel to make sure it doesn't freeze, and if
430 it does, it reboots your computer after a certain amount of time.
432 To compile this driver as a module, choose M here: the
433 module will be called acquirewdt.
435 Most people will say N.
438 tristate "Advantech SBC Watchdog Timer"
441 If you are configuring a Linux kernel for the Advantech single-board
442 computer, say `Y' here to support its built-in watchdog timer
443 feature. More information can be found at
444 <http://www.advantech.com.tw/products/>
447 tristate "ALi M1535 PMU Watchdog Timer"
448 depends on X86 && PCI
450 This is the driver for the hardware watchdog on the ALi M1535 PMU.
452 To compile this driver as a module, choose M here: the
453 module will be called alim1535_wdt.
455 Most people will say N.
458 tristate "ALi M7101 PMU Computer Watchdog"
461 This is the driver for the hardware watchdog on the ALi M7101 PMU
462 as used in the x86 Cobalt servers and also found in some
463 SPARC Netra servers too.
465 To compile this driver as a module, choose M here: the
466 module will be called alim7101_wdt.
468 Most people will say N.
471 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
474 This is the driver for the hardware watchdog on the Fintek
475 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
477 You can compile this driver directly into the kernel, or use
478 it as a module. The module will be called f71808e_wdt.
481 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
482 depends on X86 && PCI
484 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
485 (Total Cost of Ownership) timer is a watchdog timer that will reboot
486 the machine after its expiration. The expiration time can be
487 configured with the "heartbeat" parameter.
489 To compile this driver as a module, choose M here: the
490 module will be called sp5100_tco.
493 tristate "AMD Geode CS5535/CS5536 Watchdog"
494 depends on CS5535_MFGPT
496 This driver enables a watchdog capability built into the
497 CS5535/CS5536 companion chips for the AMD Geode GX and LX
498 processors. This watchdog watches your kernel to make sure
499 it doesn't freeze, and if it does, it reboots your computer after
500 a certain amount of time.
502 You can compile this driver directly into the kernel, or use
503 it as a module. The module will be called geodewdt.
506 tristate "AMD Elan SC520 processor Watchdog"
509 This is the driver for the hardware watchdog built in to the
510 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
511 This watchdog simply watches your kernel to make sure it doesn't
512 freeze, and if it does, it reboots your computer after a certain
515 You can compile this driver directly into the kernel, or use
516 it as a module. The module will be called sc520_wdt.
518 config SBC_FITPC2_WATCHDOG
519 tristate "Compulab SBC-FITPC2 watchdog"
522 This is the driver for the built-in watchdog timer on the fit-PC2,
523 fit-PC2i, CM-iAM single-board computers made by Compulab.
525 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
526 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
528 Entering BIOS setup temporary disables watchdog operation regardless to current state,
529 so system will not be restarted while user in BIOS setup.
531 Once watchdog was enabled the system will be restarted every
532 "Watchdog Timer Value" period, so to prevent it user can restart or
533 disable the watchdog.
535 To compile this driver as a module, choose M here: the
536 module will be called sbc_fitpc2_wdt.
538 Most people will say N.
541 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
544 Enable support for the watchdog timer on the Eurotech CPU-1220 and
545 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
546 information are at <http://www.eurotech.it/>.
549 tristate "IB700 SBC Watchdog Timer"
552 This is the driver for the hardware watchdog on the IB700 Single
553 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
554 simply watches your kernel to make sure it doesn't freeze, and if
555 it does, it reboots your computer after a certain amount of time.
557 This driver is like the WDT501 driver but for slightly different hardware.
559 To compile this driver as a module, choose M here: the
560 module will be called ib700wdt.
562 Most people will say N.
565 tristate "IBM Automatic Server Restart"
568 This is the driver for the IBM Automatic Server Restart watchdog
569 timer built-in into some eServer xSeries machines.
571 To compile this driver as a module, choose M here: the
572 module will be called ibmasr.
575 tristate "ICP Single Board Computer Watchdog Timer"
578 This is a driver for the hardware watchdog on the ICP Single
579 Board Computer. This driver is working on (at least) the following
580 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
582 To compile this driver as a module, choose M here: the
583 module will be called wafer5823wdt.
586 tristate "Intel 6300ESB Timer/Watchdog"
589 Hardware driver for the watchdog timer built into the Intel
590 6300ESB controller hub.
592 To compile this driver as a module, choose M here: the
593 module will be called i6300esb.
596 tristate "Intel Atom E6xx Watchdog"
597 depends on X86 && PCI
602 Hardware driver for the watchdog timer built into the Intel
603 Atom E6XX (TunnelCreek) processor.
605 To compile this driver as a module, choose M here: the
606 module will be called ie6xx_wdt.
608 config INTEL_SCU_WATCHDOG
609 bool "Intel SCU Watchdog for Mobile Platforms"
610 depends on X86_INTEL_MID
612 Hardware driver for the watchdog time built into the Intel SCU
613 for Intel Mobile Platforms.
615 To compile this driver as a module, choose M here.
618 tristate "Intel TCO Timer/Watchdog"
619 depends on (X86 || IA64) && PCI
623 Hardware driver for the intel TCO timer based watchdog devices.
624 These drivers are included in the Intel 82801 I/O Controller
625 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
628 The TCO (Total Cost of Ownership) timer is a watchdog timer
629 that will reboot the machine after its second expiration. The
630 expiration time can be configured with the "heartbeat" parameter.
632 On some motherboards the driver may fail to reset the chipset's
633 NO_REBOOT flag which prevents the watchdog from rebooting the
634 machine. If this is the case you will get a kernel message like
635 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
637 To compile this driver as a module, choose M here: the
638 module will be called iTCO_wdt.
640 config ITCO_VENDOR_SUPPORT
641 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
644 Add vendor specific support to the intel TCO timer based watchdog
645 devices. At this moment we only have additional support for some
646 SuperMicro Inc. motherboards.
649 tristate "IT8712F (Smart Guardian) Watchdog Timer"
652 This is the driver for the built-in watchdog timer on the IT8712F
653 Super I/0 chipset used on many motherboards.
655 If the driver does not work, then make sure that the game port in
658 To compile this driver as a module, choose M here: the
659 module will be called it8712f_wdt.
662 tristate "IT87 Watchdog Timer"
665 This is the driver for the hardware watchdog on the ITE IT8702,
666 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
669 If the driver does not work, then make sure that the game port in
672 This watchdog simply watches your kernel to make sure it doesn't
673 freeze, and if it does, it reboots your computer after a certain
676 To compile this driver as a module, choose M here: the module will
680 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
681 depends on X86 && PCI
683 A software monitoring watchdog and NMI sourcing driver. This driver
684 will detect lockups and provide a stack trace. This is a driver that
685 will only load on an HP ProLiant system with a minimum of iLO2 support.
686 To compile this driver as a module, choose M here: the module will be
689 config HPWDT_NMI_DECODING
690 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
691 depends on HP_WATCHDOG
694 When an NMI occurs this feature will make the necessary BIOS calls to
695 log the cause of the NMI.
698 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
701 This is a driver for National Semiconductor PC87307/PC97307 hardware
702 watchdog cards as found on the SC1200. This watchdog is mainly used
703 for power management purposes and can be used to power down the device
704 during inactivity periods (includes interrupt activity monitoring).
706 To compile this driver as a module, choose M here: the
707 module will be called sc1200wdt.
709 Most people will say N.
712 tristate "National Semiconductor SCx200 Watchdog"
713 depends on SCx200 && PCI
715 Enable the built-in watchdog timer support on the National
716 Semiconductor SCx200 processors.
718 If compiled as a module, it will be called scx200_wdt.
721 tristate "NS PC87413 watchdog"
724 This is the driver for the hardware watchdog on the PC87413 chipset
725 This watchdog simply watches your kernel to make sure it doesn't
726 freeze, and if it does, it reboots your computer after a certain
729 To compile this driver as a module, choose M here: the
730 module will be called pc87413_wdt.
732 Most people will say N.
735 tristate "nVidia TCO Timer/Watchdog"
736 depends on X86 && PCI
738 Hardware driver for the TCO timer built into the nVidia Hub family
739 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
740 watchdog timer that will reboot the machine after its second
741 expiration. The expiration time can be configured with the
742 "heartbeat" parameter.
744 On some motherboards the driver may fail to reset the chipset's
745 NO_REBOOT flag which prevents the watchdog from rebooting the
746 machine. If this is the case you will get a kernel message like
747 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
749 To compile this driver as a module, choose M here: the
750 module will be called nv_tco.
753 tristate "RDC R-321x SoC watchdog"
754 depends on X86_RDC321X
756 This is the driver for the built in hardware watchdog
757 in the RDC R-321x SoC.
759 To compile this driver as a module, choose M here: the
760 module will be called rdc321x_wdt.
763 tristate "SBC-60XX Watchdog Timer"
766 This driver can be used with the watchdog timer found on some
767 single board computers, namely the 6010 PII based computer.
768 It may well work with other cards. It reads port 0x443 to enable
769 and re-set the watchdog timer, and reads port 0x45 to disable
770 the watchdog. If you have a card that behave in similar ways,
771 you can probably make this driver work with your card as well.
773 You can compile this driver directly into the kernel, or use
774 it as a module. The module will be called sbc60xxwdt.
777 tristate "SBC8360 Watchdog Timer"
781 This is the driver for the hardware watchdog on the SBC8360 Single
782 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
784 To compile this driver as a module, choose M here: the
785 module will be called sbc8360.
787 Most people will say N.
790 tristate "SBC Nano 7240 Watchdog Timer"
791 depends on X86_32 && !UML
793 This is the driver for the hardware watchdog found on the IEI
794 single board computers EPIC Nano 7240 (and likely others). This
795 watchdog simply watches your kernel to make sure it doesn't freeze,
796 and if it does, it reboots your computer after a certain amount of
799 To compile this driver as a module, choose M here: the
800 module will be called sbc7240_wdt.
803 tristate "SMA CPU5 Watchdog"
807 To compile this driver as a module, choose M here: the
808 module will be called cpu5wdt.
810 config SMSC_SCH311X_WDT
811 tristate "SMSC SCH311X Watchdog Timer"
814 This is the driver for the hardware watchdog timer on the
815 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
816 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
819 To compile this driver as a module, choose M here: the
820 module will be called sch311x_wdt.
822 config SMSC37B787_WDT
823 tristate "Winbond SMsC37B787 Watchdog Timer"
826 This is the driver for the hardware watchdog component on the
827 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
828 from Vision Systems and maybe others.
830 This watchdog simply watches your kernel to make sure it doesn't
831 freeze, and if it does, it reboots your computer after a certain
834 Usually a userspace daemon will notify the kernel WDT driver that
835 userspace is still alive, at regular intervals.
837 To compile this driver as a module, choose M here: the
838 module will be called smsc37b787_wdt.
840 Most people will say N.
843 tristate "VIA Watchdog Timer"
844 depends on X86 && PCI
847 This is the driver for the hardware watchdog timer on VIA
848 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
850 To compile this driver as a module, choose M here; the module
851 will be called via_wdt.
853 Most people will say N.
856 tristate "W83627HF/W83627DHG Watchdog Timer"
859 This is the driver for the hardware watchdog on the W83627HF chipset
860 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
861 (and likely others). The driver also supports the W83627DHG chip.
862 This watchdog simply watches your kernel to make sure it doesn't
863 freeze, and if it does, it reboots your computer after a certain
866 To compile this driver as a module, choose M here: the
867 module will be called w83627hf_wdt.
869 Most people will say N.
872 tristate "W83697HF/W83697HG Watchdog Timer"
875 This is the driver for the hardware watchdog on the W83697HF/HG
876 chipset as used in Dedibox/VIA motherboards (and likely others).
877 This watchdog simply watches your kernel to make sure it doesn't
878 freeze, and if it does, it reboots your computer after a certain
881 To compile this driver as a module, choose M here: the
882 module will be called w83697hf_wdt.
884 Most people will say N.
887 tristate "W83697UG/W83697UF Watchdog Timer"
890 This is the driver for the hardware watchdog on the W83697UG/UF
891 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
892 This watchdog simply watches your kernel to make sure it doesn't
893 freeze, and if it does, it reboots your computer after a certain
896 To compile this driver as a module, choose M here: the
897 module will be called w83697ug_wdt.
899 Most people will say N.
902 tristate "W83877F (EMACS) Watchdog Timer"
905 This is the driver for the hardware watchdog on the W83877F chipset
906 as used in EMACS PC-104 motherboards (and likely others). This
907 watchdog simply watches your kernel to make sure it doesn't freeze,
908 and if it does, it reboots your computer after a certain amount of
911 To compile this driver as a module, choose M here: the
912 module will be called w83877f_wdt.
914 Most people will say N.
917 tristate "W83977F (PCM-5335) Watchdog Timer"
920 This is the driver for the hardware watchdog on the W83977F I/O chip
921 as used in AAEON's PCM-5335 SBC (and likely others). This
922 watchdog simply watches your kernel to make sure it doesn't freeze,
923 and if it does, it reboots your computer after a certain amount of
926 To compile this driver as a module, choose M here: the
927 module will be called w83977f_wdt.
930 tristate "ZF MachZ Watchdog"
933 If you are using a ZF Micro MachZ processor, say Y here, otherwise
934 N. This is the driver for the watchdog timer built-in on that
935 processor using ZF-Logic interface. This watchdog simply watches
936 your kernel to make sure it doesn't freeze, and if it does, it
937 reboots your computer after a certain amount of time.
939 To compile this driver as a module, choose M here: the
940 module will be called machzwd.
942 config SBC_EPX_C3_WATCHDOG
943 tristate "Winsystems SBC EPX-C3 watchdog"
946 This is the driver for the built-in watchdog timer on the EPX-C3
947 Single-board computer made by Winsystems, Inc.
949 *Note*: This hardware watchdog is not probeable and thus there
950 is no way to know if writing to its IO address will corrupt
951 your system or have any real effect. The only way to be sure
952 that this driver does what you want is to make sure you
953 are running it on an EPX-C3 from Winsystems with the watchdog
954 timer at IO address 0x1ee and 0x1ef. It will write to both those
955 IO ports. Basically, the assumption is made that if you compile
956 this driver into your kernel and/or load it as a module, that you
957 know what you are doing and that you are in fact running on an
960 To compile this driver as a module, choose M here: the
961 module will be called sbc_epx_c3.
967 config M54xx_WATCHDOG
968 tristate "MCF54xx watchdog support"
971 To compile this driver as a module, choose M here: the
972 module will be called m54xx_wdt.
974 # MicroBlaze Architecture
976 config XILINX_WATCHDOG
977 tristate "Xilinx Watchdog timer"
978 depends on MICROBLAZE
980 Watchdog driver for the xps_timebase_wdt ip core.
982 IMPORTANT: The xps_timebase_wdt parent must have the property
983 "clock-frequency" at device tree.
985 To compile this driver as a module, choose M here: the
986 module will be called of_xilinx_wdt.
991 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
994 Hardware driver for the built-in watchdog timer on the Atheros
995 AR71XX/AR724X/AR913X SoCs.
998 tristate "Broadcom BCM47xx Watchdog Timer"
1001 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1004 tristate "IDT RC32434 SoC Watchdog Timer"
1005 depends on MIKROTIK_RB532
1007 Hardware driver for the IDT RC32434 SoC built-in
1010 To compile this driver as a module, choose M here: the
1011 module will be called rc32434_wdt.
1014 tristate "Indy/I2 Hardware Watchdog"
1015 depends on SGI_HAS_INDYDOG
1017 Hardware driver for the Indy's/I2's watchdog. This is a
1018 watchdog timer that will reboot the machine after a 60 second
1019 timer expired and no process has written to /dev/watchdog during
1023 tristate "Ingenic jz4740 SoC hardware watchdog"
1024 depends on MACH_JZ4740
1025 select WATCHDOG_CORE
1027 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1030 tristate "MTX-1 Hardware Watchdog"
1031 depends on MIPS_MTX1
1033 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1034 will reboot the machine after a 100 seconds timer expired.
1037 tristate "PNX833x Hardware Watchdog"
1038 depends on SOC_PNX8335
1040 Hardware driver for the PNX833x's watchdog. This is a
1041 watchdog timer that will reboot the machine after a programmable
1042 timer has expired and no process has written to /dev/watchdog during
1046 tristate "Sibyte SoC hardware watchdog"
1049 Watchdog driver for the built in watchdog hardware in Sibyte
1050 SoC processors. There are apparently two watchdog timers
1051 on such processors; this driver supports only the first one,
1052 because currently Linux only supports exporting one watchdog
1055 To compile this driver as a loadable module, choose M here.
1056 The module will be called sb_wdog.
1059 tristate "TI AR7 Watchdog Timer"
1062 Hardware driver for the TI AR7 Watchdog Timer.
1065 tristate "Toshiba TXx9 Watchdog Timer"
1066 depends on CPU_TX39XX || CPU_TX49XX
1067 select WATCHDOG_CORE
1069 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1072 tristate "Cavium OCTEON SOC family Watchdog Timer"
1073 depends on CPU_CAVIUM_OCTEON
1075 select EXPORT_UASM if OCTEON_WDT = m
1077 Hardware driver for OCTEON's on chip watchdog timer.
1078 Enables the watchdog for all cores running Linux. It
1079 installs a NMI handler and pokes the watchdog based on an
1080 interrupt. On first expiration of the watchdog, the
1081 interrupt handler pokes it. The second expiration causes an
1082 NMI that prints a message. The third expiration causes a
1085 When userspace has /dev/watchdog open, no poking is done
1086 from the first interrupt, it is then only poked when the
1090 tristate "Broadcom BCM63xx hardware watchdog"
1093 Watchdog driver for the built in watchdog hardware in Broadcom
1096 To compile this driver as a loadable module, choose M here.
1097 The module will be called bcm63xx_wdt.
1100 tristate "Lantiq SoC watchdog"
1103 Hardware driver for the Lantiq SoC Watchdog Timer.
1105 # PARISC Architecture
1107 # POWERPC Architecture
1110 tristate "GE Watchdog Timer"
1113 Watchdog timer found in a number of GE single board computers.
1116 bool "MPC52xx Watchdog Timer"
1117 depends on PPC_MPC52xx
1119 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1122 tristate "MPC8xxx Platform Watchdog Timer"
1123 depends on PPC_8xx || PPC_83xx || PPC_86xx
1125 This driver is for a SoC level watchdog that exists on some
1126 Freescale PowerPC processors. So far this driver supports:
1131 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1134 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1138 tristate "PIKA FPGA Watchdog"
1142 This enables the watchdog in the PIKA FPGA. Currently used on
1146 tristate "PowerPC Book-E Watchdog Timer"
1147 depends on BOOKE || 4xx
1149 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1150 MPC85xx SOCs and the IBM PowerPC 440.
1152 Please see Documentation/watchdog/watchdog-api.txt for
1155 config BOOKE_WDT_DEFAULT_TIMEOUT
1156 int "PowerPC Book-E Watchdog Timer Default Timeout"
1157 depends on BOOKE_WDT
1158 default 38 if PPC_FSL_BOOK3E
1159 range 0 63 if PPC_FSL_BOOK3E
1160 default 3 if !PPC_FSL_BOOK3E
1161 range 0 3 if !PPC_FSL_BOOK3E
1163 Select the default watchdog timer period to be used by the PowerPC
1164 Book-E watchdog driver. A watchdog "event" occurs when the bit
1165 position represented by this number transitions from zero to one.
1167 For Freescale Book-E processors, this is a number between 0 and 63.
1168 For other Book-E processors, this is a number between 0 and 3.
1170 The value can be overridden by the wdt_period command-line parameter.
1172 # PPC64 Architecture
1174 config WATCHDOG_RTAS
1175 tristate "RTAS watchdog"
1178 This driver adds watchdog support for the RTAS watchdog.
1180 To compile this driver as a module, choose M here. The module
1181 will be called wdrtas.
1186 tristate "z/VM Watchdog Timer"
1189 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1190 provide a virtual watchdog timer to their guest that cause a
1191 user define Control Program command to be executed after a
1194 To compile this driver as a module, choose M here. The module
1195 will be called vmwatchdog.
1197 # SUPERH (sh + sh64) Architecture
1200 tristate "SuperH Watchdog"
1201 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1202 select WATCHDOG_CORE
1204 This driver adds watchdog support for the integrated watchdog in the
1205 SuperH processors. If you have one of these processors and wish
1206 to have watchdog support enabled, say Y, otherwise say N.
1208 As a side note, saying Y here will automatically boost HZ to 1000
1209 so that the timer has a chance to clear the overflow counter. On
1210 slower systems (such as the SH-2 and SH-3) this will likely yield
1211 some performance issues. As such, the WDT should be avoided here
1212 unless it is absolutely necessary.
1214 To compile this driver as a module, choose M here: the
1215 module will be called shwdt.
1217 # SPARC Architecture
1219 # SPARC64 Architecture
1221 config WATCHDOG_CP1XXX
1222 tristate "CP1XXX Hardware Watchdog support"
1223 depends on SPARC64 && PCI
1225 This is the driver for the hardware watchdog timers present on
1226 Sun Microsystems CompactPCI models CP1400 and CP1500.
1228 To compile this driver as a module, choose M here: the
1229 module will be called cpwatchdog.
1231 If you do not have a CompactPCI model CP1400 or CP1500, or
1232 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1233 you should say N to this option.
1236 tristate "RIO Hardware Watchdog support"
1237 depends on SPARC64 && PCI
1239 Say Y here to support the hardware watchdog capability on Sun RIO
1240 machines. The watchdog timeout period is normally one minute but
1241 can be changed with a boot-time parameter.
1243 # XTENSA Architecture
1248 tristate "Xen Watchdog support"
1251 Say Y here to support the hypervisor watchdog capability provided
1252 by Xen 4.0 and newer. The watchdog timeout period is normally one
1253 minute but can be changed with a boot-time parameter.
1256 tristate "UML watchdog"
1260 # ISA-based Watchdog Cards
1263 comment "ISA-based Watchdog Cards"
1267 tristate "Berkshire Products ISA-PC Watchdog"
1270 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1271 This card simply watches your kernel to make sure it doesn't freeze,
1272 and if it does, it reboots your computer after a certain amount of
1273 time. This driver is like the WDT501 driver but for different
1274 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1275 watchdog cards can be ordered from <http://www.berkprod.com/>.
1277 To compile this driver as a module, choose M here: the
1278 module will be called pcwd.
1280 Most people will say N.
1283 tristate "Mixcom Watchdog"
1286 This is a driver for the Mixcom hardware watchdog cards. This
1287 watchdog simply watches your kernel to make sure it doesn't freeze,
1288 and if it does, it reboots your computer after a certain amount of
1291 To compile this driver as a module, choose M here: the
1292 module will be called mixcomwd.
1294 Most people will say N.
1297 tristate "WDT Watchdog timer"
1300 If you have a WDT500P or WDT501P watchdog board, say Y here,
1301 otherwise N. It is not possible to probe for this board, which means
1302 that you have to inform the kernel about the IO port and IRQ that
1303 is needed (you can do this via the io and irq parameters)
1305 To compile this driver as a module, choose M here: the
1306 module will be called wdt.
1309 # PCI-based Watchdog Cards
1312 comment "PCI-based Watchdog Cards"
1315 config PCIPCWATCHDOG
1316 tristate "Berkshire Products PCI-PC Watchdog"
1319 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1320 This card simply watches your kernel to make sure it doesn't freeze,
1321 and if it does, it reboots your computer after a certain amount of
1322 time. The card can also monitor the internal temperature of the PC.
1323 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1325 To compile this driver as a module, choose M here: the
1326 module will be called pcwd_pci.
1328 Most people will say N.
1331 tristate "PCI-WDT500/501 Watchdog timer"
1334 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1336 If you have a PCI-WDT501 watchdog board then you can enable the
1337 temperature sensor by setting the type parameter to 501.
1339 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1340 can do this via the tachometer parameter. Only do this if you have a
1341 fan tachometer actually set up.
1343 To compile this driver as a module, choose M here: the
1344 module will be called wdt_pci.
1347 # USB-based Watchdog Cards
1350 comment "USB-based Watchdog Cards"
1353 config USBPCWATCHDOG
1354 tristate "Berkshire Products USB-PC Watchdog"
1357 This is the driver for the Berkshire Products USB-PC Watchdog card.
1358 This card simply watches your kernel to make sure it doesn't freeze,
1359 and if it does, it reboots your computer after a certain amount of
1360 time. The card can also monitor the internal temperature of the PC.
1361 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1363 To compile this driver as a module, choose M here: the
1364 module will be called pcwd_usb.
1366 Most people will say N.