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
31 config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
34 The default watchdog behaviour (which you get if you say N here) is
35 to stop the timer if the process managing it closes the file
36 /dev/watchdog. It's always remotely possible that this process might
37 get killed. If you say Y here, the watchdog cannot be stopped once
41 # General Watchdog drivers
44 comment "Watchdog Device Drivers"
46 # Architecture Independent
49 tristate "Software watchdog"
51 A software monitoring watchdog. This will fail to reboot your system
52 from some situations that the hardware watchdog will recover
53 from. Equally it's a lot cheaper to install.
55 To compile this driver as a module, choose M here: the
56 module will be called softdog.
58 config WM831X_WATCHDOG
59 tristate "WM831x watchdog"
62 Support for the watchdog in the WM831x AudioPlus PMICs. When
63 the watchdog triggers the system will be reset.
65 config WM8350_WATCHDOG
66 tristate "WM8350 watchdog"
69 Support for the watchdog in the WM8350 AudioPlus PMIC. When
70 the watchdog triggers the system will be reset.
77 tristate "RK29 watchdog"
80 Watchdog timer embedded into RK29xx chips. This will reboot your
81 system when the timeout is reached.
83 config RK29_FEED_DOG_BY_INTE
84 bool "feed watchdog by interrupt"
85 depends on RK29_WATCHDOG
87 config RK29_WATCHDOG_ATBOOT
88 bool "start watchdog at system boot"
89 depends on RK29_WATCHDOG
91 config RK29_WATCHDOG_DEFAULT_TIME
92 int "set watchdog time out value (unit second)"
93 depends on RK29_WATCHDOG
95 the real time out value is two times more than the setting value
97 config RK29_WATCHDOG_DEBUG
98 bool "enable watchdog debug"
99 depends on RK29_WATCHDOG
101 config ARM_SP805_WATCHDOG
102 tristate "ARM SP805 Watchdog"
105 ARM Primecell SP805 Watchdog timer. This will reboot your system when
106 the timeout is reached.
108 config AT91RM9200_WATCHDOG
109 tristate "AT91RM9200 watchdog"
110 depends on ARCH_AT91RM9200
112 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
113 system when the timeout is reached.
115 config AT91SAM9X_WATCHDOG
116 tristate "AT91SAM9X / AT91CAP9 watchdog"
117 depends on ARCH_AT91 && !ARCH_AT91RM9200
119 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
120 reboot your system when the timeout is reached.
122 config 21285_WATCHDOG
123 tristate "DC21285 watchdog"
124 depends on FOOTBRIDGE
126 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
127 here if you wish to use this. Alternatively say M to compile the
128 driver as a module, which will be called wdt285.
130 This driver does not work on all machines. In particular, early CATS
131 boards have hardware problems that will cause the machine to simply
132 lock up if the watchdog fires.
134 "If in doubt, leave it out" - say N.
137 tristate "NetWinder WB83C977 watchdog"
138 depends on FOOTBRIDGE && ARCH_NETWINDER
140 Say Y here to include support for the WB977 watchdog included in
141 NetWinder machines. Alternatively say M to compile the driver as
142 a module, which will be called wdt977.
144 Not sure? It's safe to say N.
146 config IXP2000_WATCHDOG
147 tristate "IXP2000 Watchdog"
148 depends on ARCH_IXP2000
150 Say Y here if to include support for the watchdog timer
151 in the Intel IXP2000(2400, 2800, 2850) network processors.
152 This driver can be built as a module by choosing M. The module
153 will be called ixp2000_wdt.
155 Say N if you are unsure.
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 ARCH_S3C2410 || 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.
214 config MPCORE_WATCHDOG
215 tristate "MPcore watchdog"
216 depends on HAVE_ARM_TWD
218 Watchdog timer embedded into the MPcore system.
220 To compile this driver as a module, choose M here: the
221 module will be called mpcore_wdt.
223 config EP93XX_WATCHDOG
224 tristate "EP93xx Watchdog"
225 depends on ARCH_EP93XX
227 Say Y here if to include support for the watchdog timer
228 embedded in the Cirrus Logic EP93xx family of devices.
230 To compile this driver as a module, choose M here: the
231 module will be called ep93xx_wdt.
234 tristate "OMAP Watchdog"
235 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
237 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
238 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
240 config PNX4008_WATCHDOG
241 tristate "PNX4008 and LPC32XX Watchdog"
242 depends on ARCH_PNX4008 || ARCH_LPC32XX
244 Say Y here if to include support for the watchdog timer
245 in the PNX4008 or LPC32XX processor.
246 This driver can be built as a module by choosing M. The module
247 will be called pnx4008_wdt.
249 Say N if you are unsure.
252 tristate "IOP Watchdog"
254 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
256 Say Y here if to include support for the watchdog timer
257 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
258 be built as a module by choosing M. The module will
261 Note: The IOP13XX watchdog does an Internal Bus Reset which will
262 affect both cores and the peripherals of the IOP. The ATU-X
263 and/or ATUe configuration registers will remain intact, but if
264 operating as an Root Complex and/or Central Resource, the PCI-X
265 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
267 config DAVINCI_WATCHDOG
268 tristate "DaVinci watchdog"
269 depends on ARCH_DAVINCI
271 Say Y here if to include support for the watchdog timer
272 in the DaVinci DM644x/DM646x processors.
273 To compile this driver as a module, choose M here: the
274 module will be called davinci_wdt.
276 NOTE: once enabled, this timer cannot be disabled.
277 Say N if you are unsure.
279 config ORION_WATCHDOG
280 tristate "Orion watchdog"
281 depends on ARCH_ORION5X || ARCH_KIRKWOOD
283 Say Y here if to include support for the watchdog timer
284 in the Marvell Orion5x and Kirkwood ARM SoCs.
285 To compile this driver as a module, choose M here: the
286 module will be called orion_wdt.
288 config COH901327_WATCHDOG
289 bool "ST-Ericsson COH 901 327 watchdog"
291 default y if MACH_U300
293 Say Y here to include Watchdog timer support for the
294 watchdog embedded into the ST-Ericsson U300 series platforms.
295 This watchdog is used to reset the system and thus cannot be
296 compiled as a module.
298 config TWL4030_WATCHDOG
299 tristate "TWL4030 Watchdog"
300 depends on TWL4030_CORE
302 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
303 watchdog timer support for TWL4030 chips.
305 config STMP3XXX_WATCHDOG
306 tristate "Freescale STMP3XXX watchdog"
307 depends on ARCH_STMP3XXX
309 Say Y here if to include support for the watchdog timer
310 for the Sigmatel STMP37XX/378X SoC.
311 To compile this driver as a module, choose M here: the
312 module will be called stmp3xxx_wdt.
314 config NUC900_WATCHDOG
315 tristate "Nuvoton NUC900 watchdog"
316 depends on ARCH_W90X900
318 Say Y here if to include support for the watchdog timer
319 for the Nuvoton NUC900 series SoCs.
320 To compile this driver as a module, choose M here: the
321 module will be called nuc900_wdt.
324 tristate "Avionic Design Xanthos watchdog"
325 depends on ARCH_PXA_ADX
327 Say Y here if you want support for the watchdog timer on Avionic
328 Design Xanthos boards.
330 config TS72XX_WATCHDOG
331 tristate "TS-72XX SBC Watchdog"
332 depends on MACH_TS72XX
334 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
335 watchdog timer implemented in a external CPLD chip. Say Y here
336 if you want to support for the watchdog timer on TS-72XX boards.
338 To compile this driver as a module, choose M here: the
339 module will be called ts72xx_wdt.
341 config MAX63XX_WATCHDOG
342 tristate "Max63xx watchdog"
343 depends on ARM && HAS_IOMEM
345 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
348 tristate "IMX2+ Watchdog"
349 depends on ARCH_MX2 || ARCH_MX25 || ARCH_MX3 || ARCH_MX5
351 This is the driver for the hardware watchdog
352 on the Freescale IMX2 and later processors.
353 If you have one of these processors and wish to have
354 watchdog support enabled, say Y, otherwise say N.
356 To compile this driver as a module, choose M here: the
357 module will be called imx2_wdt.
361 config AT32AP700X_WDT
362 tristate "AT32AP700x watchdog"
363 depends on CPU_AT32AP700X
365 Watchdog timer embedded into AT32AP700x devices. This will reboot
366 your system when the timeout is reached.
368 # BLACKFIN Architecture
371 tristate "Blackfin On-Chip Watchdog Timer"
374 If you say yes here you will get support for the Blackfin On-Chip
375 Watchdog Timer. If you have one of these processors and wish to
376 have watchdog support enabled, say Y, otherwise say N.
378 To compile this driver as a module, choose M here: the
379 module will be called bfin_wdt.
387 # X86 (i386 + ia64 + x86_64) Architecture
390 tristate "Acquire SBC Watchdog Timer"
393 This is the driver for the hardware watchdog on Single Board
394 Computers produced by Acquire Inc (and others). This watchdog
395 simply watches your kernel to make sure it doesn't freeze, and if
396 it does, it reboots your computer after a certain amount of time.
398 To compile this driver as a module, choose M here: the
399 module will be called acquirewdt.
401 Most people will say N.
404 tristate "Advantech SBC Watchdog Timer"
407 If you are configuring a Linux kernel for the Advantech single-board
408 computer, say `Y' here to support its built-in watchdog timer
409 feature. More information can be found at
410 <http://www.advantech.com.tw/products/>
413 tristate "ALi M1535 PMU Watchdog Timer"
414 depends on X86 && PCI
416 This is the driver for the hardware watchdog on the ALi M1535 PMU.
418 To compile this driver as a module, choose M here: the
419 module will be called alim1535_wdt.
421 Most people will say N.
424 tristate "ALi M7101 PMU Computer Watchdog"
427 This is the driver for the hardware watchdog on the ALi M7101 PMU
428 as used in the x86 Cobalt servers and also found in some
429 SPARC Netra servers too.
431 To compile this driver as a module, choose M here: the
432 module will be called alim7101_wdt.
434 Most people will say N.
437 tristate "Fintek F71808E and F71882FG Watchdog"
438 depends on X86 && EXPERIMENTAL
440 This is the driver for the hardware watchdog on the Fintek
441 F71808E and F71882FG Super I/O controllers.
443 You can compile this driver directly into the kernel, or use
444 it as a module. The module will be called f71808e_wdt.
448 tristate "AMD Geode CS5535/CS5536 Watchdog"
449 depends on CS5535_MFGPT
451 This driver enables a watchdog capability built into the
452 CS5535/CS5536 companion chips for the AMD Geode GX and LX
453 processors. This watchdog watches your kernel to make sure
454 it doesn't freeze, and if it does, it reboots your computer after
455 a certain amount of time.
457 You can compile this driver directly into the kernel, or use
458 it as a module. The module will be called geodewdt.
461 tristate "AMD Elan SC520 processor Watchdog"
464 This is the driver for the hardware watchdog built in to the
465 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
466 This watchdog simply watches your kernel to make sure it doesn't
467 freeze, and if it does, it reboots your computer after a certain
470 You can compile this driver directly into the kernel, or use
471 it as a module. The module will be called sc520_wdt.
473 config SBC_FITPC2_WATCHDOG
474 tristate "Compulab SBC-FITPC2 watchdog"
477 This is the driver for the built-in watchdog timer on the fit-PC2,
478 fit-PC2i, CM-iAM single-board computers made by Compulab.
480 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
481 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
483 Entering BIOS setup temporary disables watchdog operation regardless to current state,
484 so system will not be restarted while user in BIOS setup.
486 Once watchdog was enabled the system will be restarted every
487 "Watchdog Timer Value" period, so to prevent it user can restart or
488 disable the watchdog.
490 To compile this driver as a module, choose M here: the
491 module will be called sbc_fitpc2_wdt.
493 Most people will say N.
496 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
499 Enable support for the watchdog timer on the Eurotech CPU-1220 and
500 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
501 information are at <http://www.eurotech.it/>.
504 tristate "IB700 SBC Watchdog Timer"
507 This is the driver for the hardware watchdog on the IB700 Single
508 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
509 simply watches your kernel to make sure it doesn't freeze, and if
510 it does, it reboots your computer after a certain amount of time.
512 This driver is like the WDT501 driver but for slightly different hardware.
514 To compile this driver as a module, choose M here: the
515 module will be called ib700wdt.
517 Most people will say N.
520 tristate "IBM Automatic Server Restart"
523 This is the driver for the IBM Automatic Server Restart watchdog
524 timer built-in into some eServer xSeries machines.
526 To compile this driver as a module, choose M here: the
527 module will be called ibmasr.
530 tristate "ICP Single Board Computer Watchdog Timer"
533 This is a driver for the hardware watchdog on the ICP Single
534 Board Computer. This driver is working on (at least) the following
535 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
537 To compile this driver as a module, choose M here: the
538 module will be called wafer5823wdt.
541 tristate "Intel 6300ESB Timer/Watchdog"
542 depends on X86 && PCI
544 Hardware driver for the watchdog timer built into the Intel
545 6300ESB controller hub.
547 To compile this driver as a module, choose M here: the
548 module will be called i6300esb.
551 tristate "Intel TCO Timer/Watchdog"
552 depends on (X86 || IA64) && PCI
554 Hardware driver for the intel TCO timer based watchdog devices.
555 These drivers are included in the Intel 82801 I/O Controller
556 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
559 The TCO (Total Cost of Ownership) timer is a watchdog timer
560 that will reboot the machine after its second expiration. The
561 expiration time can be configured with the "heartbeat" parameter.
563 On some motherboards the driver may fail to reset the chipset's
564 NO_REBOOT flag which prevents the watchdog from rebooting the
565 machine. If this is the case you will get a kernel message like
566 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
568 To compile this driver as a module, choose M here: the
569 module will be called iTCO_wdt.
571 config ITCO_VENDOR_SUPPORT
572 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
575 Add vendor specific support to the intel TCO timer based watchdog
576 devices. At this moment we only have additional support for some
577 SuperMicro Inc. motherboards.
580 tristate "IT8712F (Smart Guardian) Watchdog Timer"
583 This is the driver for the built-in watchdog timer on the IT8712F
584 Super I/0 chipset used on many motherboards.
586 To compile this driver as a module, choose M here: the
587 module will be called it8712f_wdt.
590 tristate "IT87 Watchdog Timer"
591 depends on X86 && EXPERIMENTAL
593 This is the driver for the hardware watchdog on the ITE IT8716,
594 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
595 simply watches your kernel to make sure it doesn't freeze, and if
596 it does, it reboots your computer after a certain amount of time.
598 To compile this driver as a module, choose M here: the module will
602 tristate "HP Proliant iLO2+ Hardware Watchdog Timer"
605 A software monitoring watchdog and NMI sourcing driver. This driver
606 will detect lockups and provide a stack trace. This is a driver that
607 will only load on a HP ProLiant system with a minimum of iLO2 support.
608 To compile this driver as a module, choose M here: the module will be
611 config HPWDT_NMI_DECODING
612 bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
613 depends on HP_WATCHDOG
615 When an NMI occurs this feature will make the necessary BIOS calls to
616 log the cause of the NMI.
619 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
622 This is a driver for National Semiconductor PC87307/PC97307 hardware
623 watchdog cards as found on the SC1200. This watchdog is mainly used
624 for power management purposes and can be used to power down the device
625 during inactivity periods (includes interrupt activity monitoring).
627 To compile this driver as a module, choose M here: the
628 module will be called sc1200wdt.
630 Most people will say N.
633 tristate "National Semiconductor SCx200 Watchdog"
634 depends on SCx200 && PCI
636 Enable the built-in watchdog timer support on the National
637 Semiconductor SCx200 processors.
639 If compiled as a module, it will be called scx200_wdt.
642 tristate "NS PC87413 watchdog"
645 This is the driver for the hardware watchdog on the PC87413 chipset
646 This watchdog simply watches your kernel to make sure it doesn't
647 freeze, and if it does, it reboots your computer after a certain
650 To compile this driver as a module, choose M here: the
651 module will be called pc87413_wdt.
653 Most people will say N.
656 tristate "RDC R-321x SoC watchdog"
657 depends on X86_RDC321X
659 This is the driver for the built in hardware watchdog
660 in the RDC R-321x SoC.
662 To compile this driver as a module, choose M here: the
663 module will be called rdc321x_wdt.
666 tristate "SBC-60XX Watchdog Timer"
669 This driver can be used with the watchdog timer found on some
670 single board computers, namely the 6010 PII based computer.
671 It may well work with other cards. It reads port 0x443 to enable
672 and re-set the watchdog timer, and reads port 0x45 to disable
673 the watchdog. If you have a card that behave in similar ways,
674 you can probably make this driver work with your card as well.
676 You can compile this driver directly into the kernel, or use
677 it as a module. The module will be called sbc60xxwdt.
680 tristate "SBC8360 Watchdog Timer"
684 This is the driver for the hardware watchdog on the SBC8360 Single
685 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
687 To compile this driver as a module, choose M here: the
688 module will be called sbc8360.
690 Most people will say N.
693 tristate "SBC Nano 7240 Watchdog Timer"
696 This is the driver for the hardware watchdog found on the IEI
697 single board computers EPIC Nano 7240 (and likely others). This
698 watchdog simply watches your kernel to make sure it doesn't freeze,
699 and if it does, it reboots your computer after a certain amount of
702 To compile this driver as a module, choose M here: the
703 module will be called sbc7240_wdt.
706 tristate "SMA CPU5 Watchdog"
710 To compile this driver as a module, choose M here: the
711 module will be called cpu5wdt.
713 config SMSC_SCH311X_WDT
714 tristate "SMSC SCH311X Watchdog Timer"
717 This is the driver for the hardware watchdog timer on the
718 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
719 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
722 To compile this driver as a module, choose M here: the
723 module will be called sch311x_wdt.
725 config SMSC37B787_WDT
726 tristate "Winbond SMsC37B787 Watchdog Timer"
729 This is the driver for the hardware watchdog component on the
730 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
731 from Vision Systems and maybe others.
733 This watchdog simply watches your kernel to make sure it doesn't
734 freeze, and if it does, it reboots your computer after a certain
737 Usually a userspace daemon will notify the kernel WDT driver that
738 userspace is still alive, at regular intervals.
740 To compile this driver as a module, choose M here: the
741 module will be called smsc37b787_wdt.
743 Most people will say N.
746 tristate "W83627HF Watchdog Timer"
749 This is the driver for the hardware watchdog on the W83627HF chipset
750 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
751 (and likely others). This watchdog simply watches your kernel to
752 make sure it doesn't freeze, and if it does, it reboots your computer
753 after a certain amount of time.
755 To compile this driver as a module, choose M here: the
756 module will be called w83627hf_wdt.
758 Most people will say N.
761 tristate "W83697HF/W83697HG Watchdog Timer"
764 This is the driver for the hardware watchdog on the W83697HF/HG
765 chipset as used in Dedibox/VIA motherboards (and likely others).
766 This watchdog simply watches your kernel to make sure it doesn't
767 freeze, and if it does, it reboots your computer after a certain
770 To compile this driver as a module, choose M here: the
771 module will be called w83697hf_wdt.
773 Most people will say N.
776 tristate "W83697UG/W83697UF Watchdog Timer"
779 This is the driver for the hardware watchdog on the W83697UG/UF
780 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
781 This watchdog simply watches your kernel to make sure it doesn't
782 freeze, and if it does, it reboots your computer after a certain
785 To compile this driver as a module, choose M here: the
786 module will be called w83697ug_wdt.
788 Most people will say N.
791 tristate "W83877F (EMACS) Watchdog Timer"
794 This is the driver for the hardware watchdog on the W83877F chipset
795 as used in EMACS PC-104 motherboards (and likely others). This
796 watchdog simply watches your kernel to make sure it doesn't freeze,
797 and if it does, it reboots your computer after a certain amount of
800 To compile this driver as a module, choose M here: the
801 module will be called w83877f_wdt.
803 Most people will say N.
806 tristate "W83977F (PCM-5335) Watchdog Timer"
809 This is the driver for the hardware watchdog on the W83977F I/O chip
810 as used in AAEON's PCM-5335 SBC (and likely others). This
811 watchdog simply watches your kernel to make sure it doesn't freeze,
812 and if it does, it reboots your computer after a certain amount of
815 To compile this driver as a module, choose M here: the
816 module will be called w83977f_wdt.
819 tristate "ZF MachZ Watchdog"
822 If you are using a ZF Micro MachZ processor, say Y here, otherwise
823 N. This is the driver for the watchdog timer built-in on that
824 processor using ZF-Logic interface. This watchdog simply watches
825 your kernel to make sure it doesn't freeze, and if it does, it
826 reboots your computer after a certain amount of time.
828 To compile this driver as a module, choose M here: the
829 module will be called machzwd.
831 config SBC_EPX_C3_WATCHDOG
832 tristate "Winsystems SBC EPX-C3 watchdog"
835 This is the driver for the built-in watchdog timer on the EPX-C3
836 Single-board computer made by Winsystems, Inc.
838 *Note*: This hardware watchdog is not probeable and thus there
839 is no way to know if writing to its IO address will corrupt
840 your system or have any real effect. The only way to be sure
841 that this driver does what you want is to make sure you
842 are running it on an EPX-C3 from Winsystems with the watchdog
843 timer at IO address 0x1ee and 0x1ef. It will write to both those
844 IO ports. Basically, the assumption is made that if you compile
845 this driver into your kernel and/or load it as a module, that you
846 know what you are doing and that you are in fact running on an
849 To compile this driver as a module, choose M here: the
850 module will be called sbc_epx_c3.
856 # M68KNOMMU Architecture
861 tristate "Broadcom BCM47xx Watchdog Timer"
864 Hardware driver for the Broadcom BCM47xx Watchog Timer.
867 tristate "IDT RC32434 SoC Watchdog Timer"
868 depends on MIKROTIK_RB532
870 Hardware driver for the IDT RC32434 SoC built-in
873 To compile this driver as a module, choose M here: the
874 module will be called rc32434_wdt.
877 tristate "Indy/I2 Hardware Watchdog"
878 depends on SGI_HAS_INDYDOG
880 Hardware driver for the Indy's/I2's watchdog. This is a
881 watchdog timer that will reboot the machine after a 60 second
882 timer expired and no process has written to /dev/watchdog during
886 tristate "MTX-1 Hardware Watchdog"
889 Hardware driver for the MTX-1 boards. This is a watchdog timer that
890 will reboot the machine after a 100 seconds timer expired.
893 tristate "PNX833x Hardware Watchdog"
894 depends on SOC_PNX8335
896 Hardware driver for the PNX833x's watchdog. This is a
897 watchdog timer that will reboot the machine after a programable
898 timer has expired and no process has written to /dev/watchdog during
902 tristate "Sibyte SoC hardware watchdog"
905 Watchdog driver for the built in watchdog hardware in Sibyte
906 SoC processors. There are apparently two watchdog timers
907 on such processors; this driver supports only the first one,
908 because currently Linux only supports exporting one watchdog
911 To compile this driver as a loadable module, choose M here.
912 The module will be called sb_wdog.
915 tristate "TI AR7 Watchdog Timer"
918 Hardware driver for the TI AR7 Watchdog Timer.
921 tristate "Toshiba TXx9 Watchdog Timer"
922 depends on CPU_TX39XX || CPU_TX49XX
924 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
927 tristate "Cavium OCTEON SOC family Watchdog Timer"
928 depends on CPU_CAVIUM_OCTEON
930 select EXPORT_UASM if OCTEON_WDT = m
932 Hardware driver for OCTEON's on chip watchdog timer.
933 Enables the watchdog for all cores running Linux. It
934 installs a NMI handler and pokes the watchdog based on an
935 interrupt. On first expiration of the watchdog, the
936 interrupt handler pokes it. The second expiration causes an
937 NMI that prints a message. The third expiration causes a
940 When userspace has /dev/watchdog open, no poking is done
941 from the first interrupt, it is then only poked when the
944 # PARISC Architecture
946 # POWERPC Architecture
949 tristate "GE Watchdog Timer"
950 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
952 Watchdog timer found in a number of GE single board computers.
955 bool "MPC52xx Watchdog Timer"
956 depends on PPC_MPC52xx
958 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
961 tristate "MPC8xxx Platform Watchdog Timer"
962 depends on PPC_8xx || PPC_83xx || PPC_86xx
964 This driver is for a SoC level watchdog that exists on some
965 Freescale PowerPC processors. So far this driver supports:
970 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
973 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
977 tristate "PIKA FPGA Watchdog"
981 This enables the watchdog in the PIKA FPGA. Currently used on
985 bool "PowerPC Book-E Watchdog Timer"
986 depends on BOOKE || 4xx
988 Please see Documentation/watchdog/watchdog-api.txt for
994 tristate "RTAS watchdog"
997 This driver adds watchdog support for the RTAS watchdog.
999 To compile this driver as a module, choose M here. The module
1000 will be called wdrtas.
1005 tristate "z/VM Watchdog Timer"
1008 IBM s/390 and zSeries machines running under z/VM 5.1 or later
1009 provide a virtual watchdog timer to their guest that cause a
1010 user define Control Program command to be executed after a
1013 To compile this driver as a module, choose M here. The module
1014 will be called vmwatchdog.
1016 # SUPERH (sh + sh64) Architecture
1019 tristate "SuperH Watchdog"
1020 depends on SUPERH && (CPU_SH3 || CPU_SH4)
1022 This driver adds watchdog support for the integrated watchdog in the
1023 SuperH processors. If you have one of these processors and wish
1024 to have watchdog support enabled, say Y, otherwise say N.
1026 As a side note, saying Y here will automatically boost HZ to 1000
1027 so that the timer has a chance to clear the overflow counter. On
1028 slower systems (such as the SH-2 and SH-3) this will likely yield
1029 some performance issues. As such, the WDT should be avoided here
1030 unless it is absolutely necessary.
1032 To compile this driver as a module, choose M here: the
1033 module will be called shwdt.
1036 bool "Allow mmap of SH WDT"
1040 If you say Y here, user applications will be able to mmap the
1043 # SPARC Architecture
1045 # SPARC64 Architecture
1047 config WATCHDOG_CP1XXX
1048 tristate "CP1XXX Hardware Watchdog support"
1049 depends on SPARC64 && PCI
1051 This is the driver for the hardware watchdog timers present on
1052 Sun Microsystems CompactPCI models CP1400 and CP1500.
1054 To compile this driver as a module, choose M here: the
1055 module will be called cpwatchdog.
1057 If you do not have a CompactPCI model CP1400 or CP1500, or
1058 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
1059 you should say N to this option.
1062 tristate "RIO Hardware Watchdog support"
1063 depends on SPARC64 && PCI
1065 Say Y here to support the hardware watchdog capability on Sun RIO
1066 machines. The watchdog timeout period is normally one minute but
1067 can be changed with a boot-time parameter.
1069 # XTENSA Architecture
1072 # ISA-based Watchdog Cards
1075 comment "ISA-based Watchdog Cards"
1079 tristate "Berkshire Products ISA-PC Watchdog"
1082 This is the driver for the Berkshire Products ISA-PC Watchdog card.
1083 This card simply watches your kernel to make sure it doesn't freeze,
1084 and if it does, it reboots your computer after a certain amount of
1085 time. This driver is like the WDT501 driver but for different
1086 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1087 watchdog cards can be ordered from <http://www.berkprod.com/>.
1089 To compile this driver as a module, choose M here: the
1090 module will be called pcwd.
1092 Most people will say N.
1095 tristate "Mixcom Watchdog"
1098 This is a driver for the Mixcom hardware watchdog cards. This
1099 watchdog simply watches your kernel to make sure it doesn't freeze,
1100 and if it does, it reboots your computer after a certain amount of
1103 To compile this driver as a module, choose M here: the
1104 module will be called mixcomwd.
1106 Most people will say N.
1109 tristate "WDT Watchdog timer"
1112 If you have a WDT500P or WDT501P watchdog board, say Y here,
1113 otherwise N. It is not possible to probe for this board, which means
1114 that you have to inform the kernel about the IO port and IRQ that
1115 is needed (you can do this via the io and irq parameters)
1117 To compile this driver as a module, choose M here: the
1118 module will be called wdt.
1121 # PCI-based Watchdog Cards
1124 comment "PCI-based Watchdog Cards"
1127 config PCIPCWATCHDOG
1128 tristate "Berkshire Products PCI-PC Watchdog"
1131 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1132 This card simply watches your kernel to make sure it doesn't freeze,
1133 and if it does, it reboots your computer after a certain amount of
1134 time. The card can also monitor the internal temperature of the PC.
1135 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1137 To compile this driver as a module, choose M here: the
1138 module will be called pcwd_pci.
1140 Most people will say N.
1143 tristate "PCI-WDT500/501 Watchdog timer"
1146 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1148 If you have a PCI-WDT501 watchdog board then you can enable the
1149 temperature sensor by setting the type parameter to 501.
1151 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1152 can do this via the tachometer parameter. Only do this if you have a
1153 fan tachometer actually set up.
1155 To compile this driver as a module, choose M here: the
1156 module will be called wdt_pci.
1159 # USB-based Watchdog Cards
1162 comment "USB-based Watchdog Cards"
1165 config USBPCWATCHDOG
1166 tristate "Berkshire Products USB-PC Watchdog"
1169 This is the driver for the Berkshire Products USB-PC Watchdog card.
1170 This card simply watches your kernel to make sure it doesn't freeze,
1171 and if it does, it reboots your computer after a certain amount of
1172 time. The card can also monitor the internal temperature of the PC.
1173 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1175 To compile this driver as a module, choose M here: the
1176 module will be called pcwd_usb.
1178 Most people will say N.