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"
112 depends on ARM && ARM_AMBA
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
130 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
131 reboot your system when the timeout is reached.
133 config 21285_WATCHDOG
134 tristate "DC21285 watchdog"
135 depends on FOOTBRIDGE
137 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
138 here if you wish to use this. Alternatively say M to compile the
139 driver as a module, which will be called wdt285.
141 This driver does not work on all machines. In particular, early CATS
142 boards have hardware problems that will cause the machine to simply
143 lock up if the watchdog fires.
145 "If in doubt, leave it out" - say N.
148 tristate "NetWinder WB83C977 watchdog"
149 depends on FOOTBRIDGE && ARCH_NETWINDER
151 Say Y here to include support for the WB977 watchdog included in
152 NetWinder machines. Alternatively say M to compile the driver as
153 a module, which will be called wdt977.
155 Not sure? It's safe to say N.
157 config IXP4XX_WATCHDOG
158 tristate "IXP4xx Watchdog"
159 depends on ARCH_IXP4XX
161 Say Y here if to include support for the watchdog timer
162 in the Intel IXP4xx network processors. This driver can
163 be built as a module by choosing M. The module will
164 be called ixp4xx_wdt.
166 Note: The internal IXP4xx watchdog does a soft CPU reset
167 which doesn't reset any peripherals. There are circumstances
168 where the watchdog will fail to reset the board correctly
169 (e.g., if the boot ROM is in an unreadable state).
171 Say N if you are unsure.
173 config KS8695_WATCHDOG
174 tristate "KS8695 watchdog"
175 depends on ARCH_KS8695
177 Watchdog timer embedded into KS8695 processor. This will reboot your
178 system when the timeout is reached.
180 config HAVE_S3C2410_WATCHDOG
183 This will include watchdog timer support for Samsung SoCs. If
184 you want to include watchdog support for any machine, kindly
185 select this in the respective mach-XXXX/Kconfig file.
187 config S3C2410_WATCHDOG
188 tristate "S3C2410 Watchdog"
189 depends on HAVE_S3C2410_WATCHDOG
192 Watchdog timer block in the Samsung SoCs. This will reboot
193 the system when the timer expires with the watchdog enabled.
195 The driver is limited by the speed of the system's PCLK
196 signal, so with reasonably fast systems (PCLK around 50-66MHz)
197 then watchdog intervals of over approximately 20seconds are
200 The driver can be built as a module by choosing M, and will
201 be called s3c2410_wdt
203 config SA1100_WATCHDOG
204 tristate "SA1100/PXA2xx watchdog"
205 depends on ARCH_SA1100 || ARCH_PXA
207 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
208 reboot your system when timeout is reached.
210 NOTE: once enabled, this timer cannot be disabled.
212 To compile this driver as a module, choose M here: the
213 module will be called sa1100_wdt.
216 tristate "Synopsys DesignWare watchdog"
217 depends on ARM && HAVE_CLK
219 Say Y here if to include support for the Synopsys DesignWare
220 watchdog timer found in many ARM chips.
221 To compile this driver as a module, choose M here: the
222 module will be called dw_wdt.
224 config EP93XX_WATCHDOG
225 tristate "EP93xx Watchdog"
226 depends on ARCH_EP93XX
229 Say Y here if to include support for the watchdog timer
230 embedded in the Cirrus Logic EP93xx family of devices.
232 To compile this driver as a module, choose M here: the
233 module will be called ep93xx_wdt.
236 tristate "OMAP Watchdog"
237 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
240 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
241 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
243 config PNX4008_WATCHDOG
244 tristate "LPC32XX Watchdog"
245 depends on ARCH_LPC32XX
248 Say Y here if to include support for the watchdog timer
249 in the LPC32XX processor.
250 This driver can be built as a module by choosing M. The module
251 will be called pnx4008_wdt.
253 Say N if you are unsure.
256 tristate "IOP Watchdog"
258 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
260 Say Y here if to include support for the watchdog timer
261 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
262 be built as a module by choosing M. The module will
265 Note: The IOP13XX watchdog does an Internal Bus Reset which will
266 affect both cores and the peripherals of the IOP. The ATU-X
267 and/or ATUe configuration registers will remain intact, but if
268 operating as an Root Complex and/or Central Resource, the PCI-X
269 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
271 config DAVINCI_WATCHDOG
272 tristate "DaVinci watchdog"
273 depends on ARCH_DAVINCI
275 Say Y here if to include support for the watchdog timer
276 in the DaVinci DM644x/DM646x processors.
277 To compile this driver as a module, choose M here: the
278 module will be called davinci_wdt.
280 NOTE: once enabled, this timer cannot be disabled.
281 Say N if you are unsure.
283 config ORION_WATCHDOG
284 tristate "Orion watchdog"
285 depends on ARCH_ORION5X || ARCH_KIRKWOOD || ARCH_DOVE
288 Say Y here if to include support for the watchdog timer
289 in the Marvell Orion5x and Kirkwood ARM SoCs.
290 To compile this driver as a module, choose M here: the
291 module will be called orion_wdt.
293 config SUNXI_WATCHDOG
294 tristate "Allwinner SoCs watchdog support"
295 depends on ARCH_SUNXI
298 Say Y here to include support for the watchdog timer
300 To compile this driver as a module, choose M here: the
301 module will be called sunxi_wdt.
303 config COH901327_WATCHDOG
304 bool "ST-Ericsson COH 901 327 watchdog"
306 default y if MACH_U300
309 Say Y here to include Watchdog timer support for the
310 watchdog embedded into the ST-Ericsson U300 series platforms.
311 This watchdog is used to reset the system and thus cannot be
312 compiled as a module.
314 config TWL4030_WATCHDOG
315 tristate "TWL4030 Watchdog"
316 depends on TWL4030_CORE
319 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
320 watchdog timer support for TWL4030 chips.
322 config STMP3XXX_RTC_WATCHDOG
323 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
324 depends on RTC_DRV_STMP
327 Say Y here to include support for the watchdog timer inside
328 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
329 To compile this driver as a module, choose M here: the
330 module will be called stmp3xxx_rtc_wdt.
332 config NUC900_WATCHDOG
333 tristate "Nuvoton NUC900 watchdog"
334 depends on ARCH_W90X900
336 Say Y here if to include support for the watchdog timer
337 for the Nuvoton NUC900 series SoCs.
338 To compile this driver as a module, choose M here: the
339 module will be called nuc900_wdt.
341 config TS72XX_WATCHDOG
342 tristate "TS-72XX SBC Watchdog"
343 depends on MACH_TS72XX
345 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
346 watchdog timer implemented in a external CPLD chip. Say Y here
347 if you want to support for the watchdog timer on TS-72XX boards.
349 To compile this driver as a module, choose M here: the
350 module will be called ts72xx_wdt.
352 config MAX63XX_WATCHDOG
353 tristate "Max63xx watchdog"
354 depends on ARM && HAS_IOMEM
357 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
360 tristate "IMX2+ Watchdog"
363 This is the driver for the hardware watchdog
364 on the Freescale IMX2 and later processors.
365 If you have one of these processors and wish to have
366 watchdog support enabled, say Y, otherwise say N.
368 To compile this driver as a module, choose M here: the
369 module will be called imx2_wdt.
371 config UX500_WATCHDOG
372 tristate "ST-Ericsson Ux500 watchdog"
373 depends on MFD_DB8500_PRCMU
377 Say Y here to include Watchdog timer support for the watchdog
378 existing in the prcmu of ST-Ericsson Ux500 series platforms.
380 To compile this driver as a module, choose M here: the
381 module will be called ux500_wdt.
384 tristate "Retu watchdog"
388 Retu watchdog driver for Nokia Internet Tablets (770, N800,
389 N810). At least on N800 the watchdog cannot be disabled, so
390 this driver is essential and you should enable it.
392 To compile this driver as a module, choose M here: the
393 module will be called retu_wdt.
397 config AT32AP700X_WDT
398 tristate "AT32AP700x watchdog"
399 depends on CPU_AT32AP700X
401 Watchdog timer embedded into AT32AP700x devices. This will reboot
402 your system when the timeout is reached.
404 # BLACKFIN Architecture
407 tristate "Blackfin On-Chip Watchdog Timer"
410 If you say yes here you will get support for the Blackfin On-Chip
411 Watchdog Timer. If you have one of these processors and wish to
412 have watchdog support enabled, say Y, otherwise say N.
414 To compile this driver as a module, choose M here: the
415 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
690 tristate "Kontron COM Watchdog Timer"
691 depends on MFD_KEMPLD
694 Support for the PLD watchdog on some Kontron ETX and COMexpress
697 This driver can also be built as a module. If so, the module will be
700 config HPWDT_NMI_DECODING
701 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
702 depends on HP_WATCHDOG
705 When an NMI occurs this feature will make the necessary BIOS calls to
706 log the cause of the NMI.
709 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
712 This is a driver for National Semiconductor PC87307/PC97307 hardware
713 watchdog cards as found on the SC1200. This watchdog is mainly used
714 for power management purposes and can be used to power down the device
715 during inactivity periods (includes interrupt activity monitoring).
717 To compile this driver as a module, choose M here: the
718 module will be called sc1200wdt.
720 Most people will say N.
723 tristate "National Semiconductor SCx200 Watchdog"
724 depends on SCx200 && PCI
726 Enable the built-in watchdog timer support on the National
727 Semiconductor SCx200 processors.
729 If compiled as a module, it will be called scx200_wdt.
732 tristate "NS PC87413 watchdog"
735 This is the driver for the hardware watchdog on the PC87413 chipset
736 This watchdog simply watches your kernel to make sure it doesn't
737 freeze, and if it does, it reboots your computer after a certain
740 To compile this driver as a module, choose M here: the
741 module will be called pc87413_wdt.
743 Most people will say N.
746 tristate "nVidia TCO Timer/Watchdog"
747 depends on X86 && PCI
749 Hardware driver for the TCO timer built into the nVidia Hub family
750 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
751 watchdog timer that will reboot the machine after its second
752 expiration. The expiration time can be configured with the
753 "heartbeat" parameter.
755 On some motherboards the driver may fail to reset the chipset's
756 NO_REBOOT flag which prevents the watchdog from rebooting the
757 machine. If this is the case you will get a kernel message like
758 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
760 To compile this driver as a module, choose M here: the
761 module will be called nv_tco.
764 tristate "RDC R-321x SoC watchdog"
765 depends on X86_RDC321X
767 This is the driver for the built in hardware watchdog
768 in the RDC R-321x SoC.
770 To compile this driver as a module, choose M here: the
771 module will be called rdc321x_wdt.
774 tristate "SBC-60XX Watchdog Timer"
777 This driver can be used with the watchdog timer found on some
778 single board computers, namely the 6010 PII based computer.
779 It may well work with other cards. It reads port 0x443 to enable
780 and re-set the watchdog timer, and reads port 0x45 to disable
781 the watchdog. If you have a card that behave in similar ways,
782 you can probably make this driver work with your card as well.
784 You can compile this driver directly into the kernel, or use
785 it as a module. The module will be called sbc60xxwdt.
788 tristate "SBC8360 Watchdog Timer"
792 This is the driver for the hardware watchdog on the SBC8360 Single
793 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
795 To compile this driver as a module, choose M here: the
796 module will be called sbc8360.
798 Most people will say N.
801 tristate "SBC Nano 7240 Watchdog Timer"
802 depends on X86_32 && !UML
804 This is the driver for the hardware watchdog found on the IEI
805 single board computers EPIC Nano 7240 (and likely others). This
806 watchdog simply watches your kernel to make sure it doesn't freeze,
807 and if it does, it reboots your computer after a certain amount of
810 To compile this driver as a module, choose M here: the
811 module will be called sbc7240_wdt.
814 tristate "SMA CPU5 Watchdog"
818 To compile this driver as a module, choose M here: the
819 module will be called cpu5wdt.
821 config SMSC_SCH311X_WDT
822 tristate "SMSC SCH311X Watchdog Timer"
825 This is the driver for the hardware watchdog timer on the
826 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
827 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
830 To compile this driver as a module, choose M here: the
831 module will be called sch311x_wdt.
833 config SMSC37B787_WDT
834 tristate "Winbond SMsC37B787 Watchdog Timer"
837 This is the driver for the hardware watchdog component on the
838 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
839 from Vision Systems and maybe others.
841 This watchdog simply watches your kernel to make sure it doesn't
842 freeze, and if it does, it reboots your computer after a certain
845 Usually a userspace daemon will notify the kernel WDT driver that
846 userspace is still alive, at regular intervals.
848 To compile this driver as a module, choose M here: the
849 module will be called smsc37b787_wdt.
851 Most people will say N.
854 tristate "VIA Watchdog Timer"
855 depends on X86 && PCI
858 This is the driver for the hardware watchdog timer on VIA
859 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
861 To compile this driver as a module, choose M here; the module
862 will be called via_wdt.
864 Most people will say N.
867 tristate "W83627HF/W83627DHG Watchdog Timer"
870 This is the driver for the hardware watchdog on the W83627HF chipset
871 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
872 (and likely others). The driver also supports the W83627DHG chip.
873 This watchdog simply watches your kernel to make sure it doesn't
874 freeze, and if it does, it reboots your computer after a certain
877 To compile this driver as a module, choose M here: the
878 module will be called w83627hf_wdt.
880 Most people will say N.
883 tristate "W83697HF/W83697HG Watchdog Timer"
886 This is the driver for the hardware watchdog on the W83697HF/HG
887 chipset as used in Dedibox/VIA motherboards (and likely others).
888 This watchdog simply watches your kernel to make sure it doesn't
889 freeze, and if it does, it reboots your computer after a certain
892 To compile this driver as a module, choose M here: the
893 module will be called w83697hf_wdt.
895 Most people will say N.
898 tristate "W83697UG/W83697UF Watchdog Timer"
901 This is the driver for the hardware watchdog on the W83697UG/UF
902 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
903 This watchdog simply watches your kernel to make sure it doesn't
904 freeze, and if it does, it reboots your computer after a certain
907 To compile this driver as a module, choose M here: the
908 module will be called w83697ug_wdt.
910 Most people will say N.
913 tristate "W83877F (EMACS) Watchdog Timer"
916 This is the driver for the hardware watchdog on the W83877F chipset
917 as used in EMACS PC-104 motherboards (and likely others). This
918 watchdog simply watches your kernel to make sure it doesn't freeze,
919 and if it does, it reboots your computer after a certain amount of
922 To compile this driver as a module, choose M here: the
923 module will be called w83877f_wdt.
925 Most people will say N.
928 tristate "W83977F (PCM-5335) Watchdog Timer"
931 This is the driver for the hardware watchdog on the W83977F I/O chip
932 as used in AAEON's PCM-5335 SBC (and likely others). This
933 watchdog simply watches your kernel to make sure it doesn't freeze,
934 and if it does, it reboots your computer after a certain amount of
937 To compile this driver as a module, choose M here: the
938 module will be called w83977f_wdt.
941 tristate "ZF MachZ Watchdog"
944 If you are using a ZF Micro MachZ processor, say Y here, otherwise
945 N. This is the driver for the watchdog timer built-in on that
946 processor using ZF-Logic interface. This watchdog simply watches
947 your kernel to make sure it doesn't freeze, and if it does, it
948 reboots your computer after a certain amount of time.
950 To compile this driver as a module, choose M here: the
951 module will be called machzwd.
953 config SBC_EPX_C3_WATCHDOG
954 tristate "Winsystems SBC EPX-C3 watchdog"
957 This is the driver for the built-in watchdog timer on the EPX-C3
958 Single-board computer made by Winsystems, Inc.
960 *Note*: This hardware watchdog is not probeable and thus there
961 is no way to know if writing to its IO address will corrupt
962 your system or have any real effect. The only way to be sure
963 that this driver does what you want is to make sure you
964 are running it on an EPX-C3 from Winsystems with the watchdog
965 timer at IO address 0x1ee and 0x1ef. It will write to both those
966 IO ports. Basically, the assumption is made that if you compile
967 this driver into your kernel and/or load it as a module, that you
968 know what you are doing and that you are in fact running on an
971 To compile this driver as a module, choose M here: the
972 module will be called sbc_epx_c3.
978 config M54xx_WATCHDOG
979 tristate "MCF54xx watchdog support"
982 To compile this driver as a module, choose M here: the
983 module will be called m54xx_wdt.
985 # MicroBlaze Architecture
987 config XILINX_WATCHDOG
988 tristate "Xilinx Watchdog timer"
989 depends on MICROBLAZE
991 Watchdog driver for the xps_timebase_wdt ip core.
993 IMPORTANT: The xps_timebase_wdt parent must have the property
994 "clock-frequency" at device tree.
996 To compile this driver as a module, choose M here: the
997 module will be called of_xilinx_wdt.
1002 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1005 Hardware driver for the built-in watchdog timer on the Atheros
1006 AR71XX/AR724X/AR913X SoCs.
1009 tristate "Broadcom BCM47xx Watchdog Timer"
1011 select WATCHDOG_CORE
1013 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1016 tristate "IDT RC32434 SoC Watchdog Timer"
1017 depends on MIKROTIK_RB532
1019 Hardware driver for the IDT RC32434 SoC built-in
1022 To compile this driver as a module, choose M here: the
1023 module will be called rc32434_wdt.
1026 tristate "Indy/I2 Hardware Watchdog"
1027 depends on SGI_HAS_INDYDOG
1029 Hardware driver for the Indy's/I2's watchdog. This is a
1030 watchdog timer that will reboot the machine after a 60 second
1031 timer expired and no process has written to /dev/watchdog during
1035 tristate "Ingenic jz4740 SoC hardware watchdog"
1036 depends on MACH_JZ4740
1037 select WATCHDOG_CORE
1039 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1042 tristate "MTX-1 Hardware Watchdog"
1043 depends on MIPS_MTX1
1045 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1046 will reboot the machine after a 100 seconds timer expired.
1049 tristate "PNX833x Hardware Watchdog"
1050 depends on SOC_PNX8335
1052 Hardware driver for the PNX833x's watchdog. This is a
1053 watchdog timer that will reboot the machine after a programmable
1054 timer has expired and no process has written to /dev/watchdog during
1058 tristate "Sibyte SoC hardware watchdog"
1061 Watchdog driver for the built in watchdog hardware in Sibyte
1062 SoC processors. There are apparently two watchdog timers
1063 on such processors; this driver supports only the first one,
1064 because currently Linux only supports exporting one watchdog
1067 To compile this driver as a loadable module, choose M here.
1068 The module will be called sb_wdog.
1071 tristate "TI AR7 Watchdog Timer"
1074 Hardware driver for the TI AR7 Watchdog Timer.
1077 tristate "Toshiba TXx9 Watchdog Timer"
1078 depends on CPU_TX39XX || CPU_TX49XX
1079 select WATCHDOG_CORE
1081 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1084 tristate "Cavium OCTEON SOC family Watchdog Timer"
1085 depends on CAVIUM_OCTEON_SOC
1087 select EXPORT_UASM if OCTEON_WDT = m
1089 Hardware driver for OCTEON's on chip watchdog timer.
1090 Enables the watchdog for all cores running Linux. It
1091 installs a NMI handler and pokes the watchdog based on an
1092 interrupt. On first expiration of the watchdog, the
1093 interrupt handler pokes it. The second expiration causes an
1094 NMI that prints a message. The third expiration causes a
1097 When userspace has /dev/watchdog open, no poking is done
1098 from the first interrupt, it is then only poked when the
1102 tristate "Broadcom BCM63xx hardware watchdog"
1105 Watchdog driver for the built in watchdog hardware in Broadcom
1108 To compile this driver as a loadable module, choose M here.
1109 The module will be called bcm63xx_wdt.
1112 tristate "Broadcom BCM2835 hardware watchdog"
1113 depends on ARCH_BCM2835
1114 select WATCHDOG_CORE
1116 Watchdog driver for the built in watchdog hardware in Broadcom
1119 To compile this driver as a loadable module, choose M here.
1120 The module will be called bcm2835_wdt.
1123 tristate "Lantiq SoC watchdog"
1126 Hardware driver for the Lantiq SoC Watchdog Timer.
1128 # PARISC Architecture
1130 # POWERPC Architecture
1133 tristate "GE Watchdog Timer"
1136 Watchdog timer found in a number of GE single board computers.
1139 bool "MPC52xx Watchdog Timer"
1140 depends on PPC_MPC52xx
1142 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1145 tristate "MPC8xxx Platform Watchdog Timer"
1146 depends on PPC_8xx || PPC_83xx || PPC_86xx
1148 This driver is for a SoC level watchdog that exists on some
1149 Freescale PowerPC processors. So far this driver supports:
1154 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1157 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1161 tristate "PIKA FPGA Watchdog"
1165 This enables the watchdog in the PIKA FPGA. Currently used on
1169 tristate "PowerPC Book-E Watchdog Timer"
1170 depends on BOOKE || 4xx
1171 select WATCHDOG_CORE
1173 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1174 MPC85xx SOCs and the IBM PowerPC 440.
1176 Please see Documentation/watchdog/watchdog-api.txt for
1179 config BOOKE_WDT_DEFAULT_TIMEOUT
1180 int "PowerPC Book-E Watchdog Timer Default Timeout"
1181 depends on BOOKE_WDT
1182 default 38 if PPC_FSL_BOOK3E
1183 range 0 63 if PPC_FSL_BOOK3E
1184 default 3 if !PPC_FSL_BOOK3E
1185 range 0 3 if !PPC_FSL_BOOK3E
1187 Select the default watchdog timer period to be used by the PowerPC
1188 Book-E watchdog driver. A watchdog "event" occurs when the bit
1189 position represented by this number transitions from zero to one.
1191 For Freescale Book-E processors, this is a number between 0 and 63.
1192 For other Book-E processors, this is a number between 0 and 3.
1194 The value can be overridden by the wdt_period command-line parameter.
1197 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1198 select WATCHDOG_CORE
1201 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1203 The driver can also be built as a module. If so, the module will be
1206 If unsure select N here.
1208 # PPC64 Architecture
1210 config WATCHDOG_RTAS
1211 tristate "RTAS watchdog"
1214 This driver adds watchdog support for the RTAS watchdog.
1216 To compile this driver as a module, choose M here. The module
1217 will be called wdrtas.
1222 tristate "z/VM Watchdog Timer"
1225 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1226 provide a virtual watchdog timer to their guest that cause a
1227 user define Control Program command to be executed after a
1230 To compile this driver as a module, choose M here. The module
1231 will be called vmwatchdog.
1233 # SUPERH (sh + sh64) Architecture
1236 tristate "SuperH Watchdog"
1237 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1238 select WATCHDOG_CORE
1240 This driver adds watchdog support for the integrated watchdog in the
1241 SuperH processors. If you have one of these processors and wish
1242 to have watchdog support enabled, say Y, otherwise say N.
1244 As a side note, saying Y here will automatically boost HZ to 1000
1245 so that the timer has a chance to clear the overflow counter. On
1246 slower systems (such as the SH-2 and SH-3) this will likely yield
1247 some performance issues. As such, the WDT should be avoided here
1248 unless it is absolutely necessary.
1250 To compile this driver as a module, choose M here: the
1251 module will be called shwdt.
1253 # SPARC Architecture
1255 # SPARC64 Architecture
1257 config WATCHDOG_CP1XXX
1258 tristate "CP1XXX Hardware Watchdog support"
1259 depends on SPARC64 && PCI
1261 This is the driver for the hardware watchdog timers present on
1262 Sun Microsystems CompactPCI models CP1400 and CP1500.
1264 To compile this driver as a module, choose M here: the
1265 module will be called cpwatchdog.
1267 If you do not have a CompactPCI model CP1400 or CP1500, or
1268 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1269 you should say N to this option.
1272 tristate "RIO Hardware Watchdog support"
1273 depends on SPARC64 && PCI
1275 Say Y here to support the hardware watchdog capability on Sun RIO
1276 machines. The watchdog timeout period is normally one minute but
1277 can be changed with a boot-time parameter.
1279 # XTENSA Architecture
1284 tristate "Xen Watchdog support"
1287 Say Y here to support the hypervisor watchdog capability provided
1288 by Xen 4.0 and newer. The watchdog timeout period is normally one
1289 minute but can be changed with a boot-time parameter.
1292 tristate "UML watchdog"
1296 # ISA-based Watchdog Cards
1299 comment "ISA-based Watchdog Cards"
1303 tristate "Berkshire Products ISA-PC Watchdog"
1306 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1307 This card simply watches your kernel to make sure it doesn't freeze,
1308 and if it does, it reboots your computer after a certain amount of
1309 time. This driver is like the WDT501 driver but for different
1310 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1311 watchdog cards can be ordered from <http://www.berkprod.com/>.
1313 To compile this driver as a module, choose M here: the
1314 module will be called pcwd.
1316 Most people will say N.
1319 tristate "Mixcom Watchdog"
1322 This is a driver for the Mixcom hardware watchdog cards. This
1323 watchdog simply watches your kernel to make sure it doesn't freeze,
1324 and if it does, it reboots your computer after a certain amount of
1327 To compile this driver as a module, choose M here: the
1328 module will be called mixcomwd.
1330 Most people will say N.
1333 tristate "WDT Watchdog timer"
1336 If you have a WDT500P or WDT501P watchdog board, say Y here,
1337 otherwise N. It is not possible to probe for this board, which means
1338 that you have to inform the kernel about the IO port and IRQ that
1339 is needed (you can do this via the io and irq parameters)
1341 To compile this driver as a module, choose M here: the
1342 module will be called wdt.
1345 # PCI-based Watchdog Cards
1348 comment "PCI-based Watchdog Cards"
1351 config PCIPCWATCHDOG
1352 tristate "Berkshire Products PCI-PC Watchdog"
1355 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1356 This card simply watches your kernel to make sure it doesn't freeze,
1357 and if it does, it reboots your computer after a certain amount of
1358 time. The card can also monitor the internal temperature of the PC.
1359 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1361 To compile this driver as a module, choose M here: the
1362 module will be called pcwd_pci.
1364 Most people will say N.
1367 tristate "PCI-WDT500/501 Watchdog timer"
1370 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1372 If you have a PCI-WDT501 watchdog board then you can enable the
1373 temperature sensor by setting the type parameter to 501.
1375 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1376 can do this via the tachometer parameter. Only do this if you have a
1377 fan tachometer actually set up.
1379 To compile this driver as a module, choose M here: the
1380 module will be called wdt_pci.
1383 # USB-based Watchdog Cards
1386 comment "USB-based Watchdog Cards"
1389 config USBPCWATCHDOG
1390 tristate "Berkshire Products USB-PC Watchdog"
1393 This is the driver for the Berkshire Products USB-PC Watchdog card.
1394 This card simply watches your kernel to make sure it doesn't freeze,
1395 and if it does, it reboots your computer after a certain amount of
1396 time. The card can also monitor the internal temperature of the PC.
1397 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1399 To compile this driver as a module, choose M here: the
1400 module will be called pcwd_usb.
1402 Most people will say N.