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.
76 config AT91RM9200_WATCHDOG
77 tristate "AT91RM9200 watchdog"
78 depends on ARCH_AT91RM9200
80 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
81 system when the timeout is reached.
83 config AT91SAM9X_WATCHDOG
84 tristate "AT91SAM9X / AT91CAP9 watchdog"
85 depends on ARCH_AT91 && !ARCH_AT91RM9200
87 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
88 reboot your system when the timeout is reached.
91 tristate "DC21285 watchdog"
94 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
95 here if you wish to use this. Alternatively say M to compile the
96 driver as a module, which will be called wdt285.
98 This driver does not work on all machines. In particular, early CATS
99 boards have hardware problems that will cause the machine to simply
100 lock up if the watchdog fires.
102 "If in doubt, leave it out" - say N.
105 tristate "NetWinder WB83C977 watchdog"
106 depends on FOOTBRIDGE && ARCH_NETWINDER
108 Say Y here to include support for the WB977 watchdog included in
109 NetWinder machines. Alternatively say M to compile the driver as
110 a module, which will be called wdt977.
112 Not sure? It's safe to say N.
114 config IXP2000_WATCHDOG
115 tristate "IXP2000 Watchdog"
116 depends on ARCH_IXP2000
118 Say Y here if to include support for the watchdog timer
119 in the Intel IXP2000(2400, 2800, 2850) network processors.
120 This driver can be built as a module by choosing M. The module
121 will be called ixp2000_wdt.
123 Say N if you are unsure.
125 config IXP4XX_WATCHDOG
126 tristate "IXP4xx Watchdog"
127 depends on ARCH_IXP4XX
129 Say Y here if to include support for the watchdog timer
130 in the Intel IXP4xx network processors. This driver can
131 be built as a module by choosing M. The module will
132 be called ixp4xx_wdt.
134 Note: The internal IXP4xx watchdog does a soft CPU reset
135 which doesn't reset any peripherals. There are circumstances
136 where the watchdog will fail to reset the board correctly
137 (e.g., if the boot ROM is in an unreadable state).
139 Say N if you are unsure.
141 config KS8695_WATCHDOG
142 tristate "KS8695 watchdog"
143 depends on ARCH_KS8695
145 Watchdog timer embedded into KS8695 processor. This will reboot your
146 system when the timeout is reached.
148 config S3C2410_WATCHDOG
149 tristate "S3C2410 Watchdog"
150 depends on ARCH_S3C2410
152 Watchdog timer block in the Samsung S3C2410 chips. This will
153 reboot the system when the timer expires with the watchdog
156 The driver is limited by the speed of the system's PCLK
157 signal, so with reasonably fast systems (PCLK around 50-66MHz)
158 then watchdog intervals of over approximately 20seconds are
161 The driver can be built as a module by choosing M, and will
162 be called s3c2410_wdt
164 config SA1100_WATCHDOG
165 tristate "SA1100/PXA2xx watchdog"
166 depends on ARCH_SA1100 || ARCH_PXA
168 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
169 reboot your system when timeout is reached.
171 NOTE: once enabled, this timer cannot be disabled.
173 To compile this driver as a module, choose M here: the
174 module will be called sa1100_wdt.
176 config MPCORE_WATCHDOG
177 tristate "MPcore watchdog"
178 depends on HAVE_ARM_TWD
180 Watchdog timer embedded into the MPcore system.
182 To compile this driver as a module, choose M here: the
183 module will be called mpcore_wdt.
185 config EP93XX_WATCHDOG
186 tristate "EP93xx Watchdog"
187 depends on ARCH_EP93XX
189 Say Y here if to include support for the watchdog timer
190 embedded in the Cirrus Logic EP93xx family of devices.
192 To compile this driver as a module, choose M here: the
193 module will be called ep93xx_wdt.
196 tristate "OMAP Watchdog"
197 depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
199 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
200 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
202 config PNX4008_WATCHDOG
203 tristate "PNX4008 Watchdog"
204 depends on ARCH_PNX4008
206 Say Y here if to include support for the watchdog timer
207 in the PNX4008 processor.
208 This driver can be built as a module by choosing M. The module
209 will be called pnx4008_wdt.
211 Say N if you are unsure.
214 tristate "IOP Watchdog"
216 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
218 Say Y here if to include support for the watchdog timer
219 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
220 be built as a module by choosing M. The module will
223 Note: The IOP13XX watchdog does an Internal Bus Reset which will
224 affect both cores and the peripherals of the IOP. The ATU-X
225 and/or ATUe configuration registers will remain intact, but if
226 operating as an Root Complex and/or Central Resource, the PCI-X
227 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
229 config DAVINCI_WATCHDOG
230 tristate "DaVinci watchdog"
231 depends on ARCH_DAVINCI
233 Say Y here if to include support for the watchdog timer
234 in the DaVinci DM644x/DM646x processors.
235 To compile this driver as a module, choose M here: the
236 module will be called davinci_wdt.
238 NOTE: once enabled, this timer cannot be disabled.
239 Say N if you are unsure.
241 config ORION_WATCHDOG
242 tristate "Orion watchdog"
243 depends on ARCH_ORION5X || ARCH_KIRKWOOD
245 Say Y here if to include support for the watchdog timer
246 in the Marvell Orion5x and Kirkwood ARM SoCs.
247 To compile this driver as a module, choose M here: the
248 module will be called orion_wdt.
250 config COH901327_WATCHDOG
251 bool "ST-Ericsson COH 901 327 watchdog"
253 default y if MACH_U300
255 Say Y here to include Watchdog timer support for the
256 watchdog embedded into the ST-Ericsson U300 series platforms.
257 This watchdog is used to reset the system and thus cannot be
258 compiled as a module.
260 config TWL4030_WATCHDOG
261 tristate "TWL4030 Watchdog"
262 depends on TWL4030_CORE
264 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
265 watchdog timer support for TWL4030 chips.
267 config STMP3XXX_WATCHDOG
268 tristate "Freescale STMP3XXX watchdog"
269 depends on ARCH_STMP3XXX
271 Say Y here if to include support for the watchdog timer
272 for the Sigmatel STMP37XX/378X SoC.
273 To compile this driver as a module, choose M here: the
274 module will be called stmp3xxx_wdt.
276 config NUC900_WATCHDOG
277 tristate "Nuvoton NUC900 watchdog"
278 depends on ARCH_W90X900
280 Say Y here if to include support for the watchdog timer
281 for the Nuvoton NUC900 series SoCs.
282 To compile this driver as a module, choose M here: the
283 module will be called nuc900_wdt.
286 tristate "Avionic Design Xanthos watchdog"
287 depends on ARCH_PXA_ADX
289 Say Y here if you want support for the watchdog timer on Avionic
290 Design Xanthos boards.
292 config TS72XX_WATCHDOG
293 tristate "TS-72XX SBC Watchdog"
294 depends on MACH_TS72XX
296 Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
297 watchdog timer implemented in a external CPLD chip. Say Y here
298 if you want to support for the watchdog timer on TS-72XX boards.
300 To compile this driver as a module, choose M here: the
301 module will be called ts72xx_wdt.
303 config MAX63XX_WATCHDOG
304 tristate "Max63xx watchdog"
305 depends on ARM && HAS_IOMEM
307 Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
311 config AT32AP700X_WDT
312 tristate "AT32AP700x watchdog"
313 depends on CPU_AT32AP700X
315 Watchdog timer embedded into AT32AP700x devices. This will reboot
316 your system when the timeout is reached.
318 # BLACKFIN Architecture
321 tristate "Blackfin On-Chip Watchdog Timer"
324 If you say yes here you will get support for the Blackfin On-Chip
325 Watchdog Timer. If you have one of these processors and wish to
326 have watchdog support enabled, say Y, otherwise say N.
328 To compile this driver as a module, choose M here: the
329 module will be called bfin_wdt.
337 # X86 (i386 + ia64 + x86_64) Architecture
340 tristate "Acquire SBC Watchdog Timer"
343 This is the driver for the hardware watchdog on Single Board
344 Computers produced by Acquire Inc (and others). This watchdog
345 simply watches your kernel to make sure it doesn't freeze, and if
346 it does, it reboots your computer after a certain amount of time.
348 To compile this driver as a module, choose M here: the
349 module will be called acquirewdt.
351 Most people will say N.
354 tristate "Advantech SBC Watchdog Timer"
357 If you are configuring a Linux kernel for the Advantech single-board
358 computer, say `Y' here to support its built-in watchdog timer
359 feature. More information can be found at
360 <http://www.advantech.com.tw/products/>
363 tristate "ALi M1535 PMU Watchdog Timer"
364 depends on X86 && PCI
366 This is the driver for the hardware watchdog on the ALi M1535 PMU.
368 To compile this driver as a module, choose M here: the
369 module will be called alim1535_wdt.
371 Most people will say N.
374 tristate "ALi M7101 PMU Computer Watchdog"
377 This is the driver for the hardware watchdog on the ALi M7101 PMU
378 as used in the x86 Cobalt servers and also found in some
379 SPARC Netra servers too.
381 To compile this driver as a module, choose M here: the
382 module will be called alim7101_wdt.
384 Most people will say N.
387 tristate "AMD Geode CS5535/CS5536 Watchdog"
388 depends on CS5535_MFGPT
390 This driver enables a watchdog capability built into the
391 CS5535/CS5536 companion chips for the AMD Geode GX and LX
392 processors. This watchdog watches your kernel to make sure
393 it doesn't freeze, and if it does, it reboots your computer after
394 a certain amount of time.
396 You can compile this driver directly into the kernel, or use
397 it as a module. The module will be called geodewdt.
400 tristate "AMD Elan SC520 processor Watchdog"
403 This is the driver for the hardware watchdog built in to the
404 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
405 This watchdog simply watches your kernel to make sure it doesn't
406 freeze, and if it does, it reboots your computer after a certain
409 You can compile this driver directly into the kernel, or use
410 it as a module. The module will be called sc520_wdt.
412 config SBC_FITPC2_WATCHDOG
413 tristate "Compulab SBC-FITPC2 watchdog"
416 This is the driver for the built-in watchdog timer on the fit-PC2,
417 fit-PC2i, CM-iAM single-board computers made by Compulab.
419 It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
420 When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
422 Entering BIOS setup temporary disables watchdog operation regardless to current state,
423 so system will not be restarted while user in BIOS setup.
425 Once watchdog was enabled the system will be restarted every
426 "Watchdog Timer Value" period, so to prevent it user can restart or
427 disable the watchdog.
429 To compile this driver as a module, choose M here: the
430 module will be called sbc_fitpc2_wdt.
432 Most people will say N.
435 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
438 Enable support for the watchdog timer on the Eurotech CPU-1220 and
439 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
440 information are at <http://www.eurotech.it/>.
443 tristate "IB700 SBC Watchdog Timer"
446 This is the driver for the hardware watchdog on the IB700 Single
447 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
448 simply watches your kernel to make sure it doesn't freeze, and if
449 it does, it reboots your computer after a certain amount of time.
451 This driver is like the WDT501 driver but for slightly different hardware.
453 To compile this driver as a module, choose M here: the
454 module will be called ib700wdt.
456 Most people will say N.
459 tristate "IBM Automatic Server Restart"
462 This is the driver for the IBM Automatic Server Restart watchdog
463 timer built-in into some eServer xSeries machines.
465 To compile this driver as a module, choose M here: the
466 module will be called ibmasr.
469 tristate "ICP Single Board Computer Watchdog Timer"
472 This is a driver for the hardware watchdog on the ICP Single
473 Board Computer. This driver is working on (at least) the following
474 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
476 To compile this driver as a module, choose M here: the
477 module will be called wafer5823wdt.
480 tristate "Intel 6300ESB Timer/Watchdog"
481 depends on X86 && PCI
483 Hardware driver for the watchdog timer built into the Intel
484 6300ESB controller hub.
486 To compile this driver as a module, choose M here: the
487 module will be called i6300esb.
490 tristate "Intel TCO Timer/Watchdog"
491 depends on (X86 || IA64) && PCI
493 Hardware driver for the intel TCO timer based watchdog devices.
494 These drivers are included in the Intel 82801 I/O Controller
495 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
498 The TCO (Total Cost of Ownership) timer is a watchdog timer
499 that will reboot the machine after its second expiration. The
500 expiration time can be configured with the "heartbeat" parameter.
502 On some motherboards the driver may fail to reset the chipset's
503 NO_REBOOT flag which prevents the watchdog from rebooting the
504 machine. If this is the case you will get a kernel message like
505 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
507 To compile this driver as a module, choose M here: the
508 module will be called iTCO_wdt.
510 config ITCO_VENDOR_SUPPORT
511 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
514 Add vendor specific support to the intel TCO timer based watchdog
515 devices. At this moment we only have additional support for some
516 SuperMicro Inc. motherboards.
519 tristate "IT8712F (Smart Guardian) Watchdog Timer"
522 This is the driver for the built-in watchdog timer on the IT8712F
523 Super I/0 chipset used on many motherboards.
525 To compile this driver as a module, choose M here: the
526 module will be called it8712f_wdt.
529 tristate "IT87 Watchdog Timer"
530 depends on X86 && EXPERIMENTAL
532 This is the driver for the hardware watchdog on the ITE IT8716,
533 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
534 simply watches your kernel to make sure it doesn't freeze, and if
535 it does, it reboots your computer after a certain amount of time.
537 To compile this driver as a module, choose M here: the module will
541 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
544 A software monitoring watchdog and NMI sourcing driver. This driver
545 will detect lockups and provide stack trace. Also, when an NMI
546 occurs this driver will make the necessary BIOS calls to log
547 the cause of the NMI. This is a driver that will only load on a
548 HP ProLiant system with a minimum of iLO2 support.
549 To compile this driver as a module, choose M here: the
550 module will be called hpwdt.
553 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
556 This is a driver for National Semiconductor PC87307/PC97307 hardware
557 watchdog cards as found on the SC1200. This watchdog is mainly used
558 for power management purposes and can be used to power down the device
559 during inactivity periods (includes interrupt activity monitoring).
561 To compile this driver as a module, choose M here: the
562 module will be called sc1200wdt.
564 Most people will say N.
567 tristate "National Semiconductor SCx200 Watchdog"
568 depends on SCx200 && PCI
570 Enable the built-in watchdog timer support on the National
571 Semiconductor SCx200 processors.
573 If compiled as a module, it will be called scx200_wdt.
576 tristate "NS PC87413 watchdog"
579 This is the driver for the hardware watchdog on the PC87413 chipset
580 This watchdog simply watches your kernel to make sure it doesn't
581 freeze, and if it does, it reboots your computer after a certain
584 To compile this driver as a module, choose M here: the
585 module will be called pc87413_wdt.
587 Most people will say N.
590 tristate "RDC R-321x SoC watchdog"
591 depends on X86_RDC321X
593 This is the driver for the built in hardware watchdog
594 in the RDC R-321x SoC.
596 To compile this driver as a module, choose M here: the
597 module will be called rdc321x_wdt.
600 tristate "SBC-60XX Watchdog Timer"
603 This driver can be used with the watchdog timer found on some
604 single board computers, namely the 6010 PII based computer.
605 It may well work with other cards. It reads port 0x443 to enable
606 and re-set the watchdog timer, and reads port 0x45 to disable
607 the watchdog. If you have a card that behave in similar ways,
608 you can probably make this driver work with your card as well.
610 You can compile this driver directly into the kernel, or use
611 it as a module. The module will be called sbc60xxwdt.
614 tristate "SBC8360 Watchdog Timer"
618 This is the driver for the hardware watchdog on the SBC8360 Single
619 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
621 To compile this driver as a module, choose M here: the
622 module will be called sbc8360.
624 Most people will say N.
627 tristate "SBC Nano 7240 Watchdog Timer"
630 This is the driver for the hardware watchdog found on the IEI
631 single board computers EPIC Nano 7240 (and likely others). This
632 watchdog simply watches your kernel to make sure it doesn't freeze,
633 and if it does, it reboots your computer after a certain amount of
636 To compile this driver as a module, choose M here: the
637 module will be called sbc7240_wdt.
640 tristate "SMA CPU5 Watchdog"
644 To compile this driver as a module, choose M here: the
645 module will be called cpu5wdt.
647 config SMSC_SCH311X_WDT
648 tristate "SMSC SCH311X Watchdog Timer"
651 This is the driver for the hardware watchdog timer on the
652 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
653 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
656 To compile this driver as a module, choose M here: the
657 module will be called sch311x_wdt.
659 config SMSC37B787_WDT
660 tristate "Winbond SMsC37B787 Watchdog Timer"
663 This is the driver for the hardware watchdog component on the
664 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
665 from Vision Systems and maybe others.
667 This watchdog simply watches your kernel to make sure it doesn't
668 freeze, and if it does, it reboots your computer after a certain
671 Usually a userspace daemon will notify the kernel WDT driver that
672 userspace is still alive, at regular intervals.
674 To compile this driver as a module, choose M here: the
675 module will be called smsc37b787_wdt.
677 Most people will say N.
680 tristate "W83627HF Watchdog Timer"
683 This is the driver for the hardware watchdog on the W83627HF chipset
684 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
685 (and likely others). This watchdog simply watches your kernel to
686 make sure it doesn't freeze, and if it does, it reboots your computer
687 after a certain amount of time.
689 To compile this driver as a module, choose M here: the
690 module will be called w83627hf_wdt.
692 Most people will say N.
695 tristate "W83697HF/W83697HG Watchdog Timer"
698 This is the driver for the hardware watchdog on the W83697HF/HG
699 chipset as used in Dedibox/VIA motherboards (and likely others).
700 This watchdog simply watches your kernel to make sure it doesn't
701 freeze, and if it does, it reboots your computer after a certain
704 To compile this driver as a module, choose M here: the
705 module will be called w83697hf_wdt.
707 Most people will say N.
710 tristate "W83697UG/W83697UF Watchdog Timer"
713 This is the driver for the hardware watchdog on the W83697UG/UF
714 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
715 This watchdog simply watches your kernel to make sure it doesn't
716 freeze, and if it does, it reboots your computer after a certain
719 To compile this driver as a module, choose M here: the
720 module will be called w83697ug_wdt.
722 Most people will say N.
725 tristate "W83877F (EMACS) Watchdog Timer"
728 This is the driver for the hardware watchdog on the W83877F chipset
729 as used in EMACS PC-104 motherboards (and likely others). This
730 watchdog simply watches your kernel to make sure it doesn't freeze,
731 and if it does, it reboots your computer after a certain amount of
734 To compile this driver as a module, choose M here: the
735 module will be called w83877f_wdt.
737 Most people will say N.
740 tristate "W83977F (PCM-5335) Watchdog Timer"
743 This is the driver for the hardware watchdog on the W83977F I/O chip
744 as used in AAEON's PCM-5335 SBC (and likely others). This
745 watchdog simply watches your kernel to make sure it doesn't freeze,
746 and if it does, it reboots your computer after a certain amount of
749 To compile this driver as a module, choose M here: the
750 module will be called w83977f_wdt.
753 tristate "ZF MachZ Watchdog"
756 If you are using a ZF Micro MachZ processor, say Y here, otherwise
757 N. This is the driver for the watchdog timer built-in on that
758 processor using ZF-Logic interface. This watchdog simply watches
759 your kernel to make sure it doesn't freeze, and if it does, it
760 reboots your computer after a certain amount of time.
762 To compile this driver as a module, choose M here: the
763 module will be called machzwd.
765 config SBC_EPX_C3_WATCHDOG
766 tristate "Winsystems SBC EPX-C3 watchdog"
769 This is the driver for the built-in watchdog timer on the EPX-C3
770 Single-board computer made by Winsystems, Inc.
772 *Note*: This hardware watchdog is not probeable and thus there
773 is no way to know if writing to its IO address will corrupt
774 your system or have any real effect. The only way to be sure
775 that this driver does what you want is to make sure you
776 are running it on an EPX-C3 from Winsystems with the watchdog
777 timer at IO address 0x1ee and 0x1ef. It will write to both those
778 IO ports. Basically, the assumption is made that if you compile
779 this driver into your kernel and/or load it as a module, that you
780 know what you are doing and that you are in fact running on an
783 To compile this driver as a module, choose M here: the
784 module will be called sbc_epx_c3.
790 # M68KNOMMU Architecture
795 tristate "Broadcom BCM47xx Watchdog Timer"
798 Hardware driver for the Broadcom BCM47xx Watchog Timer.
801 tristate "IDT RC32434 SoC Watchdog Timer"
802 depends on MIKROTIK_RB532
804 Hardware driver for the IDT RC32434 SoC built-in
807 To compile this driver as a module, choose M here: the
808 module will be called rc32434_wdt.
811 tristate "Indy/I2 Hardware Watchdog"
812 depends on SGI_HAS_INDYDOG
814 Hardware driver for the Indy's/I2's watchdog. This is a
815 watchdog timer that will reboot the machine after a 60 second
816 timer expired and no process has written to /dev/watchdog during
820 tristate "MTX-1 Hardware Watchdog"
823 Hardware driver for the MTX-1 boards. This is a watchdog timer that
824 will reboot the machine after a 100 seconds timer expired.
827 tristate "PNX833x Hardware Watchdog"
828 depends on SOC_PNX8335
830 Hardware driver for the PNX833x's watchdog. This is a
831 watchdog timer that will reboot the machine after a programable
832 timer has expired and no process has written to /dev/watchdog during
836 tristate "Sibyte SoC hardware watchdog"
839 Watchdog driver for the built in watchdog hardware in Sibyte
840 SoC processors. There are apparently two watchdog timers
841 on such processors; this driver supports only the first one,
842 because currently Linux only supports exporting one watchdog
845 To compile this driver as a loadable module, choose M here.
846 The module will be called sb_wdog.
849 tristate "TI AR7 Watchdog Timer"
852 Hardware driver for the TI AR7 Watchdog Timer.
855 tristate "Toshiba TXx9 Watchdog Timer"
856 depends on CPU_TX39XX || CPU_TX49XX
858 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
860 # PARISC Architecture
862 # POWERPC Architecture
865 tristate "GE Watchdog Timer"
866 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
868 Watchdog timer found in a number of GE single board computers.
871 bool "MPC52xx Watchdog Timer"
872 depends on PPC_MPC52xx
874 Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
877 tristate "MPC8xxx Platform Watchdog Timer"
878 depends on PPC_8xx || PPC_83xx || PPC_86xx
880 This driver is for a SoC level watchdog that exists on some
881 Freescale PowerPC processors. So far this driver supports:
886 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
889 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
893 tristate "PIKA FPGA Watchdog"
897 This enables the watchdog in the PIKA FPGA. Currently used on
901 bool "PowerPC Book-E Watchdog Timer"
902 depends on BOOKE || 4xx
904 Please see Documentation/watchdog/watchdog-api.txt for
910 tristate "RTAS watchdog"
913 This driver adds watchdog support for the RTAS watchdog.
915 To compile this driver as a module, choose M here. The module
916 will be called wdrtas.
921 tristate "z/VM Watchdog Timer"
924 IBM s/390 and zSeries machines running under z/VM 5.1 or later
925 provide a virtual watchdog timer to their guest that cause a
926 user define Control Program command to be executed after a
929 To compile this driver as a module, choose M here. The module
930 will be called vmwatchdog.
932 # SUPERH (sh + sh64) Architecture
935 tristate "SuperH Watchdog"
936 depends on SUPERH && (CPU_SH3 || CPU_SH4)
938 This driver adds watchdog support for the integrated watchdog in the
939 SuperH processors. If you have one of these processors and wish
940 to have watchdog support enabled, say Y, otherwise say N.
942 As a side note, saying Y here will automatically boost HZ to 1000
943 so that the timer has a chance to clear the overflow counter. On
944 slower systems (such as the SH-2 and SH-3) this will likely yield
945 some performance issues. As such, the WDT should be avoided here
946 unless it is absolutely necessary.
948 To compile this driver as a module, choose M here: the
949 module will be called shwdt.
952 bool "Allow mmap of SH WDT"
956 If you say Y here, user applications will be able to mmap the
961 # SPARC64 Architecture
963 config WATCHDOG_CP1XXX
964 tristate "CP1XXX Hardware Watchdog support"
965 depends on SPARC64 && PCI
967 This is the driver for the hardware watchdog timers present on
968 Sun Microsystems CompactPCI models CP1400 and CP1500.
970 To compile this driver as a module, choose M here: the
971 module will be called cpwatchdog.
973 If you do not have a CompactPCI model CP1400 or CP1500, or
974 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
975 you should say N to this option.
978 tristate "RIO Hardware Watchdog support"
979 depends on SPARC64 && PCI
981 Say Y here to support the hardware watchdog capability on Sun RIO
982 machines. The watchdog timeout period is normally one minute but
983 can be changed with a boot-time parameter.
985 # XTENSA Architecture
988 # ISA-based Watchdog Cards
991 comment "ISA-based Watchdog Cards"
995 tristate "Berkshire Products ISA-PC Watchdog"
998 This is the driver for the Berkshire Products ISA-PC Watchdog card.
999 This card simply watches your kernel to make sure it doesn't freeze,
1000 and if it does, it reboots your computer after a certain amount of
1001 time. This driver is like the WDT501 driver but for different
1002 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
1003 watchdog cards can be ordered from <http://www.berkprod.com/>.
1005 To compile this driver as a module, choose M here: the
1006 module will be called pcwd.
1008 Most people will say N.
1011 tristate "Mixcom Watchdog"
1014 This is a driver for the Mixcom hardware watchdog cards. This
1015 watchdog simply watches your kernel to make sure it doesn't freeze,
1016 and if it does, it reboots your computer after a certain amount of
1019 To compile this driver as a module, choose M here: the
1020 module will be called mixcomwd.
1022 Most people will say N.
1025 tristate "WDT Watchdog timer"
1028 If you have a WDT500P or WDT501P watchdog board, say Y here,
1029 otherwise N. It is not possible to probe for this board, which means
1030 that you have to inform the kernel about the IO port and IRQ that
1031 is needed (you can do this via the io and irq parameters)
1033 To compile this driver as a module, choose M here: the
1034 module will be called wdt.
1037 # PCI-based Watchdog Cards
1040 comment "PCI-based Watchdog Cards"
1043 config PCIPCWATCHDOG
1044 tristate "Berkshire Products PCI-PC Watchdog"
1047 This is the driver for the Berkshire Products PCI-PC Watchdog card.
1048 This card simply watches your kernel to make sure it doesn't freeze,
1049 and if it does, it reboots your computer after a certain amount of
1050 time. The card can also monitor the internal temperature of the PC.
1051 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
1053 To compile this driver as a module, choose M here: the
1054 module will be called pcwd_pci.
1056 Most people will say N.
1059 tristate "PCI-WDT500/501 Watchdog timer"
1062 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1064 If you have a PCI-WDT501 watchdog board then you can enable the
1065 temperature sensor by setting the type parameter to 501.
1067 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1068 can do this via the tachometer parameter. Only do this if you have a
1069 fan tachometer actually set up.
1071 To compile this driver as a module, choose M here: the
1072 module will be called wdt_pci.
1075 # USB-based Watchdog Cards
1078 comment "USB-based Watchdog Cards"
1081 config USBPCWATCHDOG
1082 tristate "Berkshire Products USB-PC Watchdog"
1085 This is the driver for the Berkshire Products USB-PC Watchdog card.
1086 This card simply watches your kernel to make sure it doesn't freeze,
1087 and if it does, it reboots your computer after a certain amount of
1088 time. The card can also monitor the internal temperature of the PC.
1089 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1091 To compile this driver as a module, choose M here: the
1092 module will be called pcwd_usb.
1094 Most people will say N.