3 # Watchdog device configuration
7 bool "Watchdog Timer Support"
9 If you say Y here (and to one of the following options) and create a
10 character special file /dev/watchdog with major number 10 and minor
11 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
12 subsequently opening the file and then failing to write to it for
13 longer than 1 minute will result in rebooting the machine. This
14 could be useful for a networked machine that needs to come back
15 on-line as fast as possible after a lock-up. There's both a watchdog
16 implementation entirely in software (which can sometimes fail to
17 reboot the machine) and a driver for hardware watchdog boards, which
18 are more robust and can also keep track of the temperature inside
19 your computer. For details, read
20 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
22 The watchdog is usually used together with the watchdog daemon
23 which is available from
24 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
25 also monitor NFS connections and can reboot the machine when the process
33 bool "WatchDog Timer Driver Core"
35 Say Y here if you want to use the new watchdog timer driver core.
36 This driver provides a framework for all watchdog timer drivers
37 and gives them the /dev/watchdog interface (and later also the
40 config WATCHDOG_NOWAYOUT
41 bool "Disable watchdog shutdown on close"
43 The default watchdog behaviour (which you get if you say N here) is
44 to stop the timer if the process managing it closes the file
45 /dev/watchdog. It's always remotely possible that this process might
46 get killed. If you say Y here, the watchdog cannot be stopped once
50 bool "Read different watchdog information through sysfs"
53 Say Y here if you want to enable watchdog device status read through
57 # General Watchdog drivers
60 comment "Watchdog Device Drivers"
62 # Architecture Independent
65 tristate "Software watchdog"
68 A software monitoring watchdog. This will fail to reboot your system
69 from some situations that the hardware watchdog will recover
70 from. Equally it's a lot cheaper to install.
72 To compile this driver as a module, choose M here: the
73 module will be called softdog.
75 config DA9052_WATCHDOG
76 tristate "Dialog DA9052 Watchdog"
77 depends on PMIC_DA9052
80 Support for the watchdog in the DA9052 PMIC. Watchdog trigger
83 Say Y here to include support for the DA9052 watchdog.
84 Alternatively say M to compile the driver as a module,
85 which will be called da9052_wdt.
87 config DA9055_WATCHDOG
88 tristate "Dialog Semiconductor DA9055 Watchdog"
92 If you say yes here you get support for watchdog on the Dialog
93 Semiconductor DA9055 PMIC.
95 This driver can also be built as a module. If so, the module
96 will be called da9055_wdt.
98 config DA9063_WATCHDOG
99 tristate "Dialog DA9063 Watchdog"
100 depends on MFD_DA9063
103 Support for the watchdog in the DA9063 PMIC.
105 This driver can be built as a module. The module name is da9063_wdt.
107 config DA9062_WATCHDOG
108 tristate "Dialog DA9062 Watchdog"
109 depends on MFD_DA9062
112 Support for the watchdog in the DA9062 PMIC.
114 This driver can be built as a module. The module name is da9062_wdt.
117 tristate "Watchdog device controlled through GPIO-line"
121 If you say yes here you get support for watchdog device
122 controlled through GPIO-line.
124 config GPIO_WATCHDOG_ARCH_INITCALL
125 bool "Register the watchdog as early as possible"
126 depends on GPIO_WATCHDOG=y
128 In some situations, the default initcall level (module_init)
129 in not early enough in the boot process to avoid the watchdog
131 If you say yes here, the initcall level would be raised to
135 config MENF21BMC_WATCHDOG
136 tristate "MEN 14F021P00 BMC Watchdog"
137 depends on MFD_MENF21BMC
140 Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
142 This driver can also be built as a module. If so the module
143 will be called menf21bmc_wdt.
145 config WM831X_WATCHDOG
146 tristate "WM831x watchdog"
147 depends on MFD_WM831X
150 Support for the watchdog in the WM831x AudioPlus PMICs. When
151 the watchdog triggers the system will be reset.
153 config WM8350_WATCHDOG
154 tristate "WM8350 watchdog"
155 depends on MFD_WM8350
158 Support for the watchdog in the WM8350 AudioPlus PMIC. When
159 the watchdog triggers the system will be reset.
161 config XILINX_WATCHDOG
162 tristate "Xilinx Watchdog timer"
166 Watchdog driver for the xps_timebase_wdt ip core.
168 To compile this driver as a module, choose M here: the
169 module will be called of_xilinx_wdt.
175 config ARM_SP805_WATCHDOG
176 tristate "ARM SP805 Watchdog"
177 depends on (ARM || ARM64) && ARM_AMBA
180 ARM Primecell SP805 Watchdog timer. This will reboot your system when
181 the timeout is reached.
183 config AT91RM9200_WATCHDOG
184 tristate "AT91RM9200 watchdog"
185 depends on SOC_AT91RM9200 && MFD_SYSCON
187 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
188 system when the timeout is reached.
190 config AT91SAM9X_WATCHDOG
191 tristate "AT91SAM9X / AT91CAP9 watchdog"
195 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
196 reboot your system when the timeout is reached.
198 config SAMA5D4_WATCHDOG
199 tristate "Atmel SAMA5D4 Watchdog Timer"
203 Atmel SAMA5D4 watchdog timer is embedded into SAMA5D4 chips.
204 Its Watchdog Timer Mode Register can be written more than once.
205 This will reboot your system when the timeout is reached.
207 config CADENCE_WATCHDOG
208 tristate "Cadence Watchdog Timer"
212 Say Y here if you want to include support for the watchdog
213 timer in the Xilinx Zynq.
215 config 21285_WATCHDOG
216 tristate "DC21285 watchdog"
217 depends on FOOTBRIDGE
219 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
220 here if you wish to use this. Alternatively say M to compile the
221 driver as a module, which will be called wdt285.
223 This driver does not work on all machines. In particular, early CATS
224 boards have hardware problems that will cause the machine to simply
225 lock up if the watchdog fires.
227 "If in doubt, leave it out" - say N.
230 tristate "NetWinder WB83C977 watchdog"
231 depends on FOOTBRIDGE && ARCH_NETWINDER
233 Say Y here to include support for the WB977 watchdog included in
234 NetWinder machines. Alternatively say M to compile the driver as
235 a module, which will be called wdt977.
237 Not sure? It's safe to say N.
239 config IXP4XX_WATCHDOG
240 tristate "IXP4xx Watchdog"
241 depends on ARCH_IXP4XX
243 Say Y here if to include support for the watchdog timer
244 in the Intel IXP4xx network processors. This driver can
245 be built as a module by choosing M. The module will
246 be called ixp4xx_wdt.
248 Note: The internal IXP4xx watchdog does a soft CPU reset
249 which doesn't reset any peripherals. There are circumstances
250 where the watchdog will fail to reset the board correctly
251 (e.g., if the boot ROM is in an unreadable state).
253 Say N if you are unsure.
255 config KS8695_WATCHDOG
256 tristate "KS8695 watchdog"
257 depends on ARCH_KS8695
259 Watchdog timer embedded into KS8695 processor. This will reboot your
260 system when the timeout is reached.
262 config HAVE_S3C2410_WATCHDOG
265 This will include watchdog timer support for Samsung SoCs. If
266 you want to include watchdog support for any machine, kindly
267 select this in the respective mach-XXXX/Kconfig file.
269 config S3C2410_WATCHDOG
270 tristate "S3C2410 Watchdog"
271 depends on HAVE_S3C2410_WATCHDOG
273 select MFD_SYSCON if ARCH_EXYNOS5
275 Watchdog timer block in the Samsung SoCs. This will reboot
276 the system when the timer expires with the watchdog enabled.
278 The driver is limited by the speed of the system's PCLK
279 signal, so with reasonably fast systems (PCLK around 50-66MHz)
280 then watchdog intervals of over approximately 20seconds are
283 The driver can be built as a module by choosing M, and will
284 be called s3c2410_wdt
286 config SA1100_WATCHDOG
287 tristate "SA1100/PXA2xx watchdog"
288 depends on ARCH_SA1100 || ARCH_PXA
290 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
291 reboot your system when timeout is reached.
293 NOTE: once enabled, this timer cannot be disabled.
295 To compile this driver as a module, choose M here: the
296 module will be called sa1100_wdt.
299 tristate "Synopsys DesignWare watchdog"
302 Say Y here if to include support for the Synopsys DesignWare
303 watchdog timer found in many chips.
304 To compile this driver as a module, choose M here: the
305 module will be called dw_wdt.
307 config EP93XX_WATCHDOG
308 tristate "EP93xx Watchdog"
309 depends on ARCH_EP93XX
312 Say Y here if to include support for the watchdog timer
313 embedded in the Cirrus Logic EP93xx family of devices.
315 To compile this driver as a module, choose M here: the
316 module will be called ep93xx_wdt.
319 tristate "OMAP Watchdog"
320 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
323 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
324 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
326 config PNX4008_WATCHDOG
327 tristate "LPC32XX Watchdog"
328 depends on ARCH_LPC32XX
331 Say Y here if to include support for the watchdog timer
332 in the LPC32XX processor.
333 This driver can be built as a module by choosing M. The module
334 will be called pnx4008_wdt.
336 Say N if you are unsure.
339 tristate "IOP Watchdog"
340 depends on ARCH_IOP13XX
341 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
343 Say Y here if to include support for the watchdog timer
344 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
345 be built as a module by choosing M. The module will
348 Note: The IOP13XX watchdog does an Internal Bus Reset which will
349 affect both cores and the peripherals of the IOP. The ATU-X
350 and/or ATUe configuration registers will remain intact, but if
351 operating as an Root Complex and/or Central Resource, the PCI-X
352 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
354 config DAVINCI_WATCHDOG
355 tristate "DaVinci watchdog"
356 depends on ARCH_DAVINCI || ARCH_KEYSTONE
359 Say Y here if to include support for the watchdog timer
360 in the DaVinci DM644x/DM646x or Keystone processors.
361 To compile this driver as a module, choose M here: the
362 module will be called davinci_wdt.
364 NOTE: once enabled, this timer cannot be disabled.
365 Say N if you are unsure.
367 config ORION_WATCHDOG
368 tristate "Orion watchdog"
369 depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU
372 Say Y here if to include support for the watchdog timer
373 in the Marvell Orion5x and Kirkwood ARM SoCs.
374 To compile this driver as a module, choose M here: the
375 module will be called orion_wdt.
377 config RN5T618_WATCHDOG
378 tristate "Ricoh RN5T618 watchdog"
379 depends on MFD_RN5T618
382 If you say yes here you get support for watchdog on the Ricoh
385 This driver can also be built as a module. If so, the module
386 will be called rn5t618_wdt.
388 config SUNXI_WATCHDOG
389 tristate "Allwinner SoCs watchdog support"
390 depends on ARCH_SUNXI
393 Say Y here to include support for the watchdog timer
395 To compile this driver as a module, choose M here: the
396 module will be called sunxi_wdt.
398 config COH901327_WATCHDOG
399 bool "ST-Ericsson COH 901 327 watchdog"
401 default y if MACH_U300
404 Say Y here to include Watchdog timer support for the
405 watchdog embedded into the ST-Ericsson U300 series platforms.
406 This watchdog is used to reset the system and thus cannot be
407 compiled as a module.
409 config TWL4030_WATCHDOG
410 tristate "TWL4030 Watchdog"
411 depends on TWL4030_CORE
414 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
415 watchdog timer support for TWL4030 chips.
417 config STMP3XXX_RTC_WATCHDOG
418 tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
419 depends on RTC_DRV_STMP
422 Say Y here to include support for the watchdog timer inside
423 the RTC for the STMP37XX/378X or i.MX23/28 SoC.
424 To compile this driver as a module, choose M here: the
425 module will be called stmp3xxx_rtc_wdt.
427 config NUC900_WATCHDOG
428 tristate "Nuvoton NUC900 watchdog"
429 depends on ARCH_W90X900
431 Say Y here if to include support for the watchdog timer
432 for the Nuvoton NUC900 series SoCs.
433 To compile this driver as a module, choose M here: the
434 module will be called nuc900_wdt.
436 config TS72XX_WATCHDOG
437 tristate "TS-72XX SBC Watchdog"
438 depends on MACH_TS72XX
440 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
441 watchdog timer implemented in a external CPLD chip. Say Y here
442 if you want to support for the watchdog timer on TS-72XX boards.
444 To compile this driver as a module, choose M here: the
445 module will be called ts72xx_wdt.
447 config MAX63XX_WATCHDOG
448 tristate "Max63xx watchdog"
452 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
455 tristate "IMX2+ Watchdog"
456 depends on ARCH_MXC || ARCH_LAYERSCAPE
460 This is the driver for the hardware watchdog
461 on the Freescale IMX2 and later processors.
462 If you have one of these processors and wish to have
463 watchdog support enabled, say Y, otherwise say N.
465 To compile this driver as a module, choose M here: the
466 module will be called imx2_wdt.
468 config UX500_WATCHDOG
469 tristate "ST-Ericsson Ux500 watchdog"
470 depends on MFD_DB8500_PRCMU
474 Say Y here to include Watchdog timer support for the watchdog
475 existing in the prcmu of ST-Ericsson Ux500 series platforms.
477 To compile this driver as a module, choose M here: the
478 module will be called ux500_wdt.
481 tristate "Retu watchdog"
485 Retu watchdog driver for Nokia Internet Tablets (770, N800,
486 N810). At least on N800 the watchdog cannot be disabled, so
487 this driver is essential and you should enable it.
489 To compile this driver as a module, choose M here: the
490 module will be called retu_wdt.
493 tristate "MOXART watchdog"
494 depends on ARCH_MOXART
496 Say Y here to include Watchdog timer support for the watchdog
497 existing on the MOXA ART SoC series platforms.
499 To compile this driver as a module, choose M here: the
500 module will be called moxart_wdt.
502 config SIRFSOC_WATCHDOG
503 tristate "SiRFSOC watchdog"
508 Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
509 the watchdog triggers the system will be reset.
511 config ST_LPC_WATCHDOG
512 tristate "STMicroelectronics LPC Watchdog"
517 Say Y here to include STMicroelectronics Low Power Controller
518 (LPC) based Watchdog timer support.
520 To compile this driver as a module, choose M here: the
521 module will be called st_lpc_wdt.
523 config TEGRA_WATCHDOG
524 tristate "Tegra watchdog"
525 depends on (ARCH_TEGRA || COMPILE_TEST) && HAS_IOMEM
528 Say Y here to include support for the watchdog timer
529 embedded in NVIDIA Tegra SoCs.
531 To compile this driver as a module, choose M here: the
532 module will be called tegra_wdt.
535 tristate "QCOM watchdog"
540 Say Y here to include Watchdog timer support for the watchdog found
541 on QCOM chipsets. Currently supported targets are the MSM8960,
542 APQ8064, and IPQ8064.
544 To compile this driver as a module, choose M here: the
545 module will be called qcom_wdt.
547 config MESON_WATCHDOG
548 tristate "Amlogic Meson SoCs watchdog support"
549 depends on ARCH_MESON
552 Say Y here to include support for the watchdog timer
553 in Amlogic Meson SoCs.
554 To compile this driver as a module, choose M here: the
555 module will be called meson_wdt.
557 config MEDIATEK_WATCHDOG
558 tristate "Mediatek SoCs watchdog support"
559 depends on ARCH_MEDIATEK
562 Say Y here to include support for the watchdog timer
564 To compile this driver as a module, choose M here: the
565 module will be called mtk_wdt.
567 config DIGICOLOR_WATCHDOG
568 tristate "Conexant Digicolor SoCs watchdog support"
569 depends on ARCH_DIGICOLOR
572 Say Y here to include support for the watchdog timer
573 in Conexant Digicolor SoCs.
574 To compile this driver as a module, choose M here: the
575 module will be called digicolor_wdt.
577 config LPC18XX_WATCHDOG
578 tristate "LPC18xx/43xx Watchdog"
579 depends on ARCH_LPC18XX || COMPILE_TEST
582 Say Y here if to include support for the watchdog timer
583 in NXP LPC SoCs family, which includes LPC18xx/LPC43xx
585 To compile this driver as a module, choose M here: the
586 module will be called lpc18xx_wdt.
590 config AT32AP700X_WDT
591 tristate "AT32AP700x watchdog"
592 depends on CPU_AT32AP700X
594 Watchdog timer embedded into AT32AP700x devices. This will reboot
595 your system when the timeout is reached.
597 # BLACKFIN Architecture
600 tristate "Blackfin On-Chip Watchdog Timer"
603 If you say yes here you will get support for the Blackfin On-Chip
604 Watchdog Timer. If you have one of these processors and wish to
605 have watchdog support enabled, say Y, otherwise say N.
607 To compile this driver as a module, choose M here: the
608 module will be called bfin_wdt.
614 # X86 (i386 + ia64 + x86_64) Architecture
617 tristate "Acquire SBC Watchdog Timer"
620 This is the driver for the hardware watchdog on Single Board
621 Computers produced by Acquire Inc (and others). This watchdog
622 simply watches your kernel to make sure it doesn't freeze, and if
623 it does, it reboots your computer after a certain amount of time.
625 To compile this driver as a module, choose M here: the
626 module will be called acquirewdt.
628 Most people will say N.
631 tristate "Advantech SBC Watchdog Timer"
634 If you are configuring a Linux kernel for the Advantech single-board
635 computer, say `Y' here to support its built-in watchdog timer
636 feature. More information can be found at
637 <http://www.advantech.com.tw/products/>
640 tristate "ALi M1535 PMU Watchdog Timer"
641 depends on X86 && PCI
643 This is the driver for the hardware watchdog on the ALi M1535 PMU.
645 To compile this driver as a module, choose M here: the
646 module will be called alim1535_wdt.
648 Most people will say N.
651 tristate "ALi M7101 PMU Computer Watchdog"
654 This is the driver for the hardware watchdog on the ALi M7101 PMU
655 as used in the x86 Cobalt servers and also found in some
656 SPARC Netra servers too.
658 To compile this driver as a module, choose M here: the
659 module will be called alim7101_wdt.
661 Most people will say N.
664 tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
667 This is the driver for the hardware watchdog on the Fintek
668 F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
670 You can compile this driver directly into the kernel, or use
671 it as a module. The module will be called f71808e_wdt.
674 tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
675 depends on X86 && PCI
677 Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
678 (Total Cost of Ownership) timer is a watchdog timer that will reboot
679 the machine after its expiration. The expiration time can be
680 configured with the "heartbeat" parameter.
682 To compile this driver as a module, choose M here: the
683 module will be called sp5100_tco.
686 tristate "AMD Geode CS5535/CS5536 Watchdog"
687 depends on CS5535_MFGPT
689 This driver enables a watchdog capability built into the
690 CS5535/CS5536 companion chips for the AMD Geode GX and LX
691 processors. This watchdog watches your kernel to make sure
692 it doesn't freeze, and if it does, it reboots your computer after
693 a certain amount of time.
695 You can compile this driver directly into the kernel, or use
696 it as a module. The module will be called geodewdt.
699 tristate "AMD Elan SC520 processor Watchdog"
702 This is the driver for the hardware watchdog built in to the
703 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
704 This watchdog simply watches your kernel to make sure it doesn't
705 freeze, and if it does, it reboots your computer after a certain
708 You can compile this driver directly into the kernel, or use
709 it as a module. The module will be called sc520_wdt.
711 config SBC_FITPC2_WATCHDOG
712 tristate "Compulab SBC-FITPC2 watchdog"
715 This is the driver for the built-in watchdog timer on the fit-PC2,
716 fit-PC2i, CM-iAM single-board computers made by Compulab.
718 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
719 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
721 Entering BIOS setup temporary disables watchdog operation regardless to current state,
722 so system will not be restarted while user in BIOS setup.
724 Once watchdog was enabled the system will be restarted every
725 "Watchdog Timer Value" period, so to prevent it user can restart or
726 disable the watchdog.
728 To compile this driver as a module, choose M here: the
729 module will be called sbc_fitpc2_wdt.
731 Most people will say N.
734 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
737 Enable support for the watchdog timer on the Eurotech CPU-1220 and
738 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
739 information are at <http://www.eurotech.it/>.
742 tristate "IB700 SBC Watchdog Timer"
745 This is the driver for the hardware watchdog on the IB700 Single
746 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
747 simply watches your kernel to make sure it doesn't freeze, and if
748 it does, it reboots your computer after a certain amount of time.
750 This driver is like the WDT501 driver but for slightly different hardware.
752 To compile this driver as a module, choose M here: the
753 module will be called ib700wdt.
755 Most people will say N.
758 tristate "IBM Automatic Server Restart"
761 This is the driver for the IBM Automatic Server Restart watchdog
762 timer built-in into some eServer xSeries machines.
764 To compile this driver as a module, choose M here: the
765 module will be called ibmasr.
768 tristate "ICP Single Board Computer Watchdog Timer"
771 This is a driver for the hardware watchdog on the ICP Single
772 Board Computer. This driver is working on (at least) the following
773 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
775 To compile this driver as a module, choose M here: the
776 module will be called wafer5823wdt.
779 tristate "Intel 6300ESB Timer/Watchdog"
782 Hardware driver for the watchdog timer built into the Intel
783 6300ESB controller hub.
785 To compile this driver as a module, choose M here: the
786 module will be called i6300esb.
789 tristate "Intel Atom E6xx Watchdog"
790 depends on X86 && PCI
795 Hardware driver for the watchdog timer built into the Intel
796 Atom E6XX (TunnelCreek) processor.
798 To compile this driver as a module, choose M here: the
799 module will be called ie6xx_wdt.
801 config INTEL_SCU_WATCHDOG
802 bool "Intel SCU Watchdog for Mobile Platforms"
803 depends on X86_INTEL_MID
805 Hardware driver for the watchdog time built into the Intel SCU
806 for Intel Mobile Platforms.
808 To compile this driver as a module, choose M here.
810 config INTEL_MID_WATCHDOG
811 tristate "Intel MID Watchdog Timer"
812 depends on X86_INTEL_MID
815 Watchdog timer driver built into the Intel SCU for Intel MID
818 This driver currently supports only the watchdog evolution
819 implementation in SCU, available for Merrifield generation.
821 To compile this driver as a module, choose M here.
824 tristate "Intel TCO Timer/Watchdog"
825 depends on (X86 || IA64) && PCI
827 depends on I2C || I2C=n
828 select LPC_ICH if !EXPERT
829 select I2C_I801 if !EXPERT && I2C
831 Hardware driver for the intel TCO timer based watchdog devices.
832 These drivers are included in the Intel 82801 I/O Controller
833 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
836 The TCO (Total Cost of Ownership) timer is a watchdog timer
837 that will reboot the machine after its second expiration. The
838 expiration time can be configured with the "heartbeat" parameter.
840 On some motherboards the driver may fail to reset the chipset's
841 NO_REBOOT flag which prevents the watchdog from rebooting the
842 machine. If this is the case you will get a kernel message like
843 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
845 To compile this driver as a module, choose M here: the
846 module will be called iTCO_wdt.
848 config ITCO_VENDOR_SUPPORT
849 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
852 Add vendor specific support to the intel TCO timer based watchdog
853 devices. At this moment we only have additional support for some
854 SuperMicro Inc. motherboards.
857 tristate "IT8712F (Smart Guardian) Watchdog Timer"
860 This is the driver for the built-in watchdog timer on the IT8712F
861 Super I/0 chipset used on many motherboards.
863 If the driver does not work, then make sure that the game port in
866 To compile this driver as a module, choose M here: the
867 module will be called it8712f_wdt.
870 tristate "IT87 Watchdog Timer"
873 This is the driver for the hardware watchdog on the ITE IT8702,
874 IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
877 If the driver does not work, then make sure that the game port in
880 This watchdog simply watches your kernel to make sure it doesn't
881 freeze, and if it does, it reboots your computer after a certain
884 To compile this driver as a module, choose M here: the module will
888 tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
889 depends on X86 && PCI
891 A software monitoring watchdog and NMI sourcing driver. This driver
892 will detect lockups and provide a stack trace. This is a driver that
893 will only load on an HP ProLiant system with a minimum of iLO2 support.
894 To compile this driver as a module, choose M here: the module will be
898 tristate "Kontron COM Watchdog Timer"
899 depends on MFD_KEMPLD
902 Support for the PLD watchdog on some Kontron ETX and COMexpress
905 This driver can also be built as a module. If so, the module will be
908 config HPWDT_NMI_DECODING
909 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
910 depends on HP_WATCHDOG
913 When an NMI occurs this feature will make the necessary BIOS calls to
914 log the cause of the NMI.
917 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
920 This is a driver for National Semiconductor PC87307/PC97307 hardware
921 watchdog cards as found on the SC1200. This watchdog is mainly used
922 for power management purposes and can be used to power down the device
923 during inactivity periods (includes interrupt activity monitoring).
925 To compile this driver as a module, choose M here: the
926 module will be called sc1200wdt.
928 Most people will say N.
931 tristate "National Semiconductor SCx200 Watchdog"
932 depends on SCx200 && PCI
934 Enable the built-in watchdog timer support on the National
935 Semiconductor SCx200 processors.
937 If compiled as a module, it will be called scx200_wdt.
940 tristate "NS PC87413 watchdog"
943 This is the driver for the hardware watchdog on the PC87413 chipset
944 This watchdog simply watches your kernel to make sure it doesn't
945 freeze, and if it does, it reboots your computer after a certain
948 To compile this driver as a module, choose M here: the
949 module will be called pc87413_wdt.
951 Most people will say N.
954 tristate "nVidia TCO Timer/Watchdog"
955 depends on X86 && PCI
957 Hardware driver for the TCO timer built into the nVidia Hub family
958 (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
959 watchdog timer that will reboot the machine after its second
960 expiration. The expiration time can be configured with the
961 "heartbeat" parameter.
963 On some motherboards the driver may fail to reset the chipset's
964 NO_REBOOT flag which prevents the watchdog from rebooting the
965 machine. If this is the case you will get a kernel message like
966 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
968 To compile this driver as a module, choose M here: the
969 module will be called nv_tco.
972 tristate "RDC R-321x SoC watchdog"
973 depends on X86_RDC321X
975 This is the driver for the built in hardware watchdog
976 in the RDC R-321x SoC.
978 To compile this driver as a module, choose M here: the
979 module will be called rdc321x_wdt.
982 tristate "SBC-60XX Watchdog Timer"
985 This driver can be used with the watchdog timer found on some
986 single board computers, namely the 6010 PII based computer.
987 It may well work with other cards. It reads port 0x443 to enable
988 and re-set the watchdog timer, and reads port 0x45 to disable
989 the watchdog. If you have a card that behave in similar ways,
990 you can probably make this driver work with your card as well.
992 You can compile this driver directly into the kernel, or use
993 it as a module. The module will be called sbc60xxwdt.
996 tristate "SBC8360 Watchdog Timer"
1000 This is the driver for the hardware watchdog on the SBC8360 Single
1001 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
1003 To compile this driver as a module, choose M here: the
1004 module will be called sbc8360.
1006 Most people will say N.
1009 tristate "SBC Nano 7240 Watchdog Timer"
1010 depends on X86_32 && !UML
1012 This is the driver for the hardware watchdog found on the IEI
1013 single board computers EPIC Nano 7240 (and likely others). This
1014 watchdog simply watches your kernel to make sure it doesn't freeze,
1015 and if it does, it reboots your computer after a certain amount of
1018 To compile this driver as a module, choose M here: the
1019 module will be called sbc7240_wdt.
1022 tristate "SMA CPU5 Watchdog"
1026 To compile this driver as a module, choose M here: the
1027 module will be called cpu5wdt.
1029 config SMSC_SCH311X_WDT
1030 tristate "SMSC SCH311X Watchdog Timer"
1033 This is the driver for the hardware watchdog timer on the
1034 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
1035 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
1038 To compile this driver as a module, choose M here: the
1039 module will be called sch311x_wdt.
1041 config SMSC37B787_WDT
1042 tristate "Winbond SMsC37B787 Watchdog Timer"
1045 This is the driver for the hardware watchdog component on the
1046 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
1047 from Vision Systems and maybe others.
1049 This watchdog simply watches your kernel to make sure it doesn't
1050 freeze, and if it does, it reboots your computer after a certain
1053 Usually a userspace daemon will notify the kernel WDT driver that
1054 userspace is still alive, at regular intervals.
1056 To compile this driver as a module, choose M here: the
1057 module will be called smsc37b787_wdt.
1059 Most people will say N.
1062 tristate "VIA Watchdog Timer"
1063 depends on X86 && PCI
1064 select WATCHDOG_CORE
1066 This is the driver for the hardware watchdog timer on VIA
1067 southbridge chipset CX700, VX800/VX820 or VX855/VX875.
1069 To compile this driver as a module, choose M here; the module
1070 will be called via_wdt.
1072 Most people will say N.
1075 tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
1077 select WATCHDOG_CORE
1079 This is the driver for the hardware watchdog on the following
1081 W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG
1093 This watchdog simply watches your kernel to make sure it doesn't
1094 freeze, and if it does, it reboots your computer after a certain
1097 To compile this driver as a module, choose M here: the
1098 module will be called w83627hf_wdt.
1100 Most people will say N.
1103 tristate "W83877F (EMACS) Watchdog Timer"
1106 This is the driver for the hardware watchdog on the W83877F chipset
1107 as used in EMACS PC-104 motherboards (and likely others). This
1108 watchdog simply watches your kernel to make sure it doesn't freeze,
1109 and if it does, it reboots your computer after a certain amount of
1112 To compile this driver as a module, choose M here: the
1113 module will be called w83877f_wdt.
1115 Most people will say N.
1118 tristate "W83977F (PCM-5335) Watchdog Timer"
1121 This is the driver for the hardware watchdog on the W83977F I/O chip
1122 as used in AAEON's PCM-5335 SBC (and likely others). This
1123 watchdog simply watches your kernel to make sure it doesn't freeze,
1124 and if it does, it reboots your computer after a certain amount of
1127 To compile this driver as a module, choose M here: the
1128 module will be called w83977f_wdt.
1131 tristate "ZF MachZ Watchdog"
1134 If you are using a ZF Micro MachZ processor, say Y here, otherwise
1135 N. This is the driver for the watchdog timer built-in on that
1136 processor using ZF-Logic interface. This watchdog simply watches
1137 your kernel to make sure it doesn't freeze, and if it does, it
1138 reboots your computer after a certain amount of time.
1140 To compile this driver as a module, choose M here: the
1141 module will be called machzwd.
1143 config SBC_EPX_C3_WATCHDOG
1144 tristate "Winsystems SBC EPX-C3 watchdog"
1147 This is the driver for the built-in watchdog timer on the EPX-C3
1148 Single-board computer made by Winsystems, Inc.
1150 *Note*: This hardware watchdog is not probeable and thus there
1151 is no way to know if writing to its IO address will corrupt
1152 your system or have any real effect. The only way to be sure
1153 that this driver does what you want is to make sure you
1154 are running it on an EPX-C3 from Winsystems with the watchdog
1155 timer at IO address 0x1ee and 0x1ef. It will write to both those
1156 IO ports. Basically, the assumption is made that if you compile
1157 this driver into your kernel and/or load it as a module, that you
1158 know what you are doing and that you are in fact running on an
1161 To compile this driver as a module, choose M here: the
1162 module will be called sbc_epx_c3.
1168 config M54xx_WATCHDOG
1169 tristate "MCF54xx watchdog support"
1172 To compile this driver as a module, choose M here: the
1173 module will be called m54xx_wdt.
1175 # MicroBlaze Architecture
1180 tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
1183 Hardware driver for the built-in watchdog timer on the Atheros
1184 AR71XX/AR724X/AR913X SoCs.
1187 tristate "Broadcom BCM47xx Watchdog Timer"
1188 depends on BCM47XX || ARCH_BCM_5301X
1189 select WATCHDOG_CORE
1191 Hardware driver for the Broadcom BCM47xx Watchdog Timer.
1194 tristate "IDT RC32434 SoC Watchdog Timer"
1195 depends on MIKROTIK_RB532
1197 Hardware driver for the IDT RC32434 SoC built-in
1200 To compile this driver as a module, choose M here: the
1201 module will be called rc32434_wdt.
1204 tristate "Indy/I2 Hardware Watchdog"
1205 depends on SGI_HAS_INDYDOG
1207 Hardware driver for the Indy's/I2's watchdog. This is a
1208 watchdog timer that will reboot the machine after a 60 second
1209 timer expired and no process has written to /dev/watchdog during
1213 tristate "Ingenic jz4740 SoC hardware watchdog"
1214 depends on MACH_JZ4740
1215 select WATCHDOG_CORE
1217 Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
1220 tristate "MTX-1 Hardware Watchdog"
1221 depends on MIPS_MTX1
1223 Hardware driver for the MTX-1 boards. This is a watchdog timer that
1224 will reboot the machine after a 100 seconds timer expired.
1227 tristate "PNX833x Hardware Watchdog"
1228 depends on SOC_PNX8335
1230 Hardware driver for the PNX833x's watchdog. This is a
1231 watchdog timer that will reboot the machine after a programmable
1232 timer has expired and no process has written to /dev/watchdog during
1236 tristate "Sibyte SoC hardware watchdog"
1239 Watchdog driver for the built in watchdog hardware in Sibyte
1240 SoC processors. There are apparently two watchdog timers
1241 on such processors; this driver supports only the first one,
1242 because currently Linux only supports exporting one watchdog
1245 To compile this driver as a loadable module, choose M here.
1246 The module will be called sb_wdog.
1249 tristate "TI AR7 Watchdog Timer"
1252 Hardware driver for the TI AR7 Watchdog Timer.
1255 tristate "Toshiba TXx9 Watchdog Timer"
1256 depends on CPU_TX39XX || CPU_TX49XX
1257 select WATCHDOG_CORE
1259 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
1262 tristate "Cavium OCTEON SOC family Watchdog Timer"
1263 depends on CAVIUM_OCTEON_SOC
1265 select WATCHDOG_CORE
1266 select EXPORT_UASM if OCTEON_WDT = m
1268 Hardware driver for OCTEON's on chip watchdog timer.
1269 Enables the watchdog for all cores running Linux. It
1270 installs a NMI handler and pokes the watchdog based on an
1271 interrupt. On first expiration of the watchdog, the
1272 interrupt handler pokes it. The second expiration causes an
1273 NMI that prints a message. The third expiration causes a
1276 When userspace has /dev/watchdog open, no poking is done
1277 from the first interrupt, it is then only poked when the
1281 tristate "Broadcom BCM63xx hardware watchdog"
1284 Watchdog driver for the built in watchdog hardware in Broadcom
1287 To compile this driver as a loadable module, choose M here.
1288 The module will be called bcm63xx_wdt.
1291 tristate "Broadcom BCM2835 hardware watchdog"
1292 depends on ARCH_BCM2835
1293 select WATCHDOG_CORE
1295 Watchdog driver for the built in watchdog hardware in Broadcom
1298 To compile this driver as a loadable module, choose M here.
1299 The module will be called bcm2835_wdt.
1302 tristate "BCM Kona Watchdog"
1303 depends on ARCH_BCM_MOBILE
1304 select WATCHDOG_CORE
1306 Support for the watchdog timer on the following Broadcom BCM281xx
1307 family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
1310 Say 'Y' or 'M' here to enable the driver. The module will be called
1313 config BCM_KONA_WDT_DEBUG
1314 bool "DEBUGFS support for BCM Kona Watchdog"
1315 depends on BCM_KONA_WDT
1317 If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
1318 access to the driver's internal data structures as well as watchdog
1319 timer hardware registres.
1321 If in doubt, say 'N'.
1324 tristate "BCM7038 Watchdog"
1325 select WATCHDOG_CORE
1327 Watchdog driver for the built-in hardware in Broadcom 7038 SoCs.
1329 Say 'Y or 'M' here to enable the driver.
1332 tristate "Imagination Technologies PDC Watchdog Timer"
1333 depends on HAS_IOMEM
1334 depends on METAG || MIPS || COMPILE_TEST
1336 Driver for Imagination Technologies PowerDown Controller
1339 To compile this driver as a loadable module, choose M here.
1340 The module will be called imgpdc_wdt.
1343 tristate "Lantiq SoC watchdog"
1346 Hardware driver for the Lantiq SoC Watchdog Timer.
1349 tristate "Ralink SoC watchdog"
1350 select WATCHDOG_CORE
1353 Hardware driver for the Ralink SoC Watchdog Timer.
1355 # PARISC Architecture
1357 # POWERPC Architecture
1360 tristate "GE Watchdog Timer"
1363 Watchdog timer found in a number of GE single board computers.
1366 bool "MPC52xx Watchdog Timer"
1367 depends on PPC_MPC52xx
1369 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
1372 tristate "MPC8xxx Platform Watchdog Timer"
1373 depends on PPC_8xx || PPC_83xx || PPC_86xx || PPC_MPC512x
1374 select WATCHDOG_CORE
1376 This driver is for a SoC level watchdog that exists on some
1377 Freescale PowerPC processors. So far this driver supports:
1382 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
1385 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
1389 tristate "PIKA FPGA Watchdog"
1393 This enables the watchdog in the PIKA FPGA. Currently used on
1397 tristate "PowerPC Book-E Watchdog Timer"
1398 depends on BOOKE || 4xx
1399 select WATCHDOG_CORE
1401 Watchdog driver for PowerPC Book-E chips, such as the Freescale
1402 MPC85xx SOCs and the IBM PowerPC 440.
1404 Please see Documentation/watchdog/watchdog-api.txt for
1407 config BOOKE_WDT_DEFAULT_TIMEOUT
1408 int "PowerPC Book-E Watchdog Timer Default Timeout"
1409 depends on BOOKE_WDT
1410 default 38 if PPC_FSL_BOOK3E
1411 range 0 63 if PPC_FSL_BOOK3E
1412 default 3 if !PPC_FSL_BOOK3E
1413 range 0 3 if !PPC_FSL_BOOK3E
1415 Select the default watchdog timer period to be used by the PowerPC
1416 Book-E watchdog driver. A watchdog "event" occurs when the bit
1417 position represented by this number transitions from zero to one.
1419 For Freescale Book-E processors, this is a number between 0 and 63.
1420 For other Book-E processors, this is a number between 0 and 3.
1422 The value can be overridden by the wdt_period command-line parameter.
1425 tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
1426 select WATCHDOG_CORE
1427 depends on GPIOLIB || COMPILE_TEST
1429 Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
1431 The driver can also be built as a module. If so, the module will be
1434 If unsure select N here.
1436 # PPC64 Architecture
1438 config WATCHDOG_RTAS
1439 tristate "RTAS watchdog"
1442 This driver adds watchdog support for the RTAS watchdog.
1444 To compile this driver as a module, choose M here. The module
1445 will be called wdrtas.
1449 config DIAG288_WATCHDOG
1450 tristate "System z diag288 Watchdog"
1452 select WATCHDOG_CORE
1454 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1455 provide a virtual watchdog timer to their guest that cause a
1456 user define Control Program command to be executed after a
1458 LPAR provides a very similar interface. This driver handles
1461 To compile this driver as a module, choose M here. The module
1462 will be called diag288_wdt.
1464 # SUPERH (sh + sh64) Architecture
1467 tristate "SuperH Watchdog"
1468 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1469 select WATCHDOG_CORE
1471 This driver adds watchdog support for the integrated watchdog in the
1472 SuperH processors. If you have one of these processors and wish
1473 to have watchdog support enabled, say Y, otherwise say N.
1475 As a side note, saying Y here will automatically boost HZ to 1000
1476 so that the timer has a chance to clear the overflow counter. On
1477 slower systems (such as the SH-2 and SH-3) this will likely yield
1478 some performance issues. As such, the WDT should be avoided here
1479 unless it is absolutely necessary.
1481 To compile this driver as a module, choose M here: the
1482 module will be called shwdt.
1484 # SPARC Architecture
1486 # SPARC64 Architecture
1488 config WATCHDOG_CP1XXX
1489 tristate "CP1XXX Hardware Watchdog support"
1490 depends on SPARC64 && PCI
1492 This is the driver for the hardware watchdog timers present on
1493 Sun Microsystems CompactPCI models CP1400 and CP1500.
1495 To compile this driver as a module, choose M here: the
1496 module will be called cpwatchdog.
1498 If you do not have a CompactPCI model CP1400 or CP1500, or
1499 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1500 you should say N to this option.
1503 tristate "RIO Hardware Watchdog support"
1504 depends on SPARC64 && PCI
1506 Say Y here to support the hardware watchdog capability on Sun RIO
1507 machines. The watchdog timeout period is normally one minute but
1508 can be changed with a boot-time parameter.
1510 # XTENSA Architecture
1515 tristate "Xen Watchdog support"
1518 Say Y here to support the hypervisor watchdog capability provided
1519 by Xen 4.0 and newer. The watchdog timeout period is normally one
1520 minute but can be changed with a boot-time parameter.
1523 tristate "UML watchdog"
1527 # ISA-based Watchdog Cards
1530 comment "ISA-based Watchdog Cards"
1534 tristate "Berkshire Products ISA-PC Watchdog"
1537 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1538 This card simply watches your kernel to make sure it doesn't freeze,
1539 and if it does, it reboots your computer after a certain amount of
1540 time. This driver is like the WDT501 driver but for different
1541 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1542 watchdog cards can be ordered from <http://www.berkprod.com/>.
1544 To compile this driver as a module, choose M here: the
1545 module will be called pcwd.
1547 Most people will say N.
1550 tristate "Mixcom Watchdog"
1553 This is a driver for the Mixcom hardware watchdog cards. This
1554 watchdog simply watches your kernel to make sure it doesn't freeze,
1555 and if it does, it reboots your computer after a certain amount of
1558 To compile this driver as a module, choose M here: the
1559 module will be called mixcomwd.
1561 Most people will say N.
1564 tristate "WDT Watchdog timer"
1567 If you have a WDT500P or WDT501P watchdog board, say Y here,
1568 otherwise N. It is not possible to probe for this board, which means
1569 that you have to inform the kernel about the IO port and IRQ that
1570 is needed (you can do this via the io and irq parameters)
1572 To compile this driver as a module, choose M here: the
1573 module will be called wdt.
1576 # PCI-based Watchdog Cards
1579 comment "PCI-based Watchdog Cards"
1582 config PCIPCWATCHDOG
1583 tristate "Berkshire Products PCI-PC Watchdog"
1586 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1587 This card simply watches your kernel to make sure it doesn't freeze,
1588 and if it does, it reboots your computer after a certain amount of
1589 time. The card can also monitor the internal temperature of the PC.
1590 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1592 To compile this driver as a module, choose M here: the
1593 module will be called pcwd_pci.
1595 Most people will say N.
1598 tristate "PCI-WDT500/501 Watchdog timer"
1601 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1603 If you have a PCI-WDT501 watchdog board then you can enable the
1604 temperature sensor by setting the type parameter to 501.
1606 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1607 can do this via the tachometer parameter. Only do this if you have a
1608 fan tachometer actually set up.
1610 To compile this driver as a module, choose M here: the
1611 module will be called wdt_pci.
1614 # USB-based Watchdog Cards
1617 comment "USB-based Watchdog Cards"
1620 config USBPCWATCHDOG
1621 tristate "Berkshire Products USB-PC Watchdog"
1624 This is the driver for the Berkshire Products USB-PC Watchdog card.
1625 This card simply watches your kernel to make sure it doesn't freeze,
1626 and if it does, it reboots your computer after a certain amount of
1627 time. The card can also monitor the internal temperature of the PC.
1628 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1630 To compile this driver as a module, choose M here: the
1631 module will be called pcwd_usb.
1633 Most people will say N.