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 WM8350_WATCHDOG
59 tristate "WM8350 watchdog"
62 Support for the watchdog in the WM8350 AudioPlus PMIC. When
63 the watchdog triggers the system will be reset.
69 config AT91RM9200_WATCHDOG
70 tristate "AT91RM9200 watchdog"
71 depends on ARCH_AT91RM9200
73 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
74 system when the timeout is reached.
76 config AT91SAM9X_WATCHDOG
77 tristate "AT91SAM9X / AT91CAP9 watchdog"
78 depends on ARCH_AT91 && !ARCH_AT91RM9200
80 Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
81 reboot your system when the timeout is reached.
84 tristate "DC21285 watchdog"
87 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
88 here if you wish to use this. Alternatively say M to compile the
89 driver as a module, which will be called wdt285.
91 This driver does not work on all machines. In particular, early CATS
92 boards have hardware problems that will cause the machine to simply
93 lock up if the watchdog fires.
95 "If in doubt, leave it out" - say N.
98 tristate "NetWinder WB83C977 watchdog"
99 depends on FOOTBRIDGE && ARCH_NETWINDER
101 Say Y here to include support for the WB977 watchdog included in
102 NetWinder machines. Alternatively say M to compile the driver as
103 a module, which will be called wdt977.
105 Not sure? It's safe to say N.
107 config IXP2000_WATCHDOG
108 tristate "IXP2000 Watchdog"
109 depends on ARCH_IXP2000
111 Say Y here if to include support for the watchdog timer
112 in the Intel IXP2000(2400, 2800, 2850) network processors.
113 This driver can be built as a module by choosing M. The module
114 will be called ixp2000_wdt.
116 Say N if you are unsure.
118 config IXP4XX_WATCHDOG
119 tristate "IXP4xx Watchdog"
120 depends on ARCH_IXP4XX
122 Say Y here if to include support for the watchdog timer
123 in the Intel IXP4xx network processors. This driver can
124 be built as a module by choosing M. The module will
125 be called ixp4xx_wdt.
127 Note: The internal IXP4xx watchdog does a soft CPU reset
128 which doesn't reset any peripherals. There are circumstances
129 where the watchdog will fail to reset the board correctly
130 (e.g., if the boot ROM is in an unreadable state).
132 Say N if you are unsure.
134 config KS8695_WATCHDOG
135 tristate "KS8695 watchdog"
136 depends on ARCH_KS8695
138 Watchdog timer embedded into KS8695 processor. This will reboot your
139 system when the timeout is reached.
141 config S3C2410_WATCHDOG
142 tristate "S3C2410 Watchdog"
143 depends on ARCH_S3C2410
145 Watchdog timer block in the Samsung S3C2410 chips. This will
146 reboot the system when the timer expires with the watchdog
149 The driver is limited by the speed of the system's PCLK
150 signal, so with reasonably fast systems (PCLK around 50-66MHz)
151 then watchdog intervals of over approximately 20seconds are
154 The driver can be built as a module by choosing M, and will
155 be called s3c2410_wdt
157 config SA1100_WATCHDOG
158 tristate "SA1100/PXA2xx watchdog"
159 depends on ARCH_SA1100 || ARCH_PXA
161 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
162 reboot your system when timeout is reached.
164 NOTE: once enabled, this timer cannot be disabled.
166 To compile this driver as a module, choose M here: the
167 module will be called sa1100_wdt.
169 config MPCORE_WATCHDOG
170 tristate "MPcore watchdog"
171 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
173 Watchdog timer embedded into the MPcore system.
175 To compile this driver as a module, choose M here: the
176 module will be called mpcore_wdt.
178 config EP93XX_WATCHDOG
179 tristate "EP93xx Watchdog"
180 depends on ARCH_EP93XX
182 Say Y here if to include support for the watchdog timer
183 embedded in the Cirrus Logic EP93xx family of devices.
185 To compile this driver as a module, choose M here: the
186 module will be called ep93xx_wdt.
189 tristate "OMAP Watchdog"
190 depends on ARCH_OMAP16XX || ARCH_OMAP24XX || ARCH_OMAP34XX
192 Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430 watchdog. Say 'Y'
193 here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430 watchdog timer.
195 config PNX4008_WATCHDOG
196 tristate "PNX4008 Watchdog"
197 depends on ARCH_PNX4008
199 Say Y here if to include support for the watchdog timer
200 in the PNX4008 processor.
201 This driver can be built as a module by choosing M. The module
202 will be called pnx4008_wdt.
204 Say N if you are unsure.
207 tristate "IOP Watchdog"
209 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
211 Say Y here if to include support for the watchdog timer
212 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
213 be built as a module by choosing M. The module will
216 Note: The IOP13XX watchdog does an Internal Bus Reset which will
217 affect both cores and the peripherals of the IOP. The ATU-X
218 and/or ATUe configuration registers will remain intact, but if
219 operating as an Root Complex and/or Central Resource, the PCI-X
220 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
222 config DAVINCI_WATCHDOG
223 tristate "DaVinci watchdog"
224 depends on ARCH_DAVINCI
226 Say Y here if to include support for the watchdog timer
227 in the DaVinci DM644x/DM646x processors.
228 To compile this driver as a module, choose M here: the
229 module will be called davinci_wdt.
231 NOTE: once enabled, this timer cannot be disabled.
232 Say N if you are unsure.
234 config ORION_WATCHDOG
235 tristate "Orion watchdog"
236 depends on ARCH_ORION5X || ARCH_KIRKWOOD
238 Say Y here if to include support for the watchdog timer
239 in the Marvell Orion5x and Kirkwood ARM SoCs.
240 To compile this driver as a module, choose M here: the
241 module will be called orion_wdt.
243 config COH901327_WATCHDOG
244 bool "ST-Ericsson COH 901 327 watchdog"
246 default y if MACH_U300
248 Say Y here to include Watchdog timer support for the
249 watchdog embedded into the ST-Ericsson U300 series platforms.
250 This watchdog is used to reset the system and thus cannot be
251 compiled as a module.
253 config TWL4030_WATCHDOG
254 tristate "TWL4030 Watchdog"
255 depends on TWL4030_CORE
257 Support for TI TWL4030 watchdog. Say 'Y' here to enable the
258 watchdog timer support for TWL4030 chips.
260 config STMP3XXX_WATCHDOG
261 tristate "Freescale STMP3XXX watchdog"
262 depends on ARCH_STMP3XXX
264 Say Y here if to include support for the watchdog timer
265 for the Sigmatel STMP37XX/378X SoC.
266 To compile this driver as a module, choose M here: the
267 module will be called stmp3xxx_wdt.
271 config AT32AP700X_WDT
272 tristate "AT32AP700x watchdog"
273 depends on CPU_AT32AP700X
275 Watchdog timer embedded into AT32AP700x devices. This will reboot
276 your system when the timeout is reached.
278 # BLACKFIN Architecture
281 tristate "Blackfin On-Chip Watchdog Timer"
284 If you say yes here you will get support for the Blackfin On-Chip
285 Watchdog Timer. If you have one of these processors and wish to
286 have watchdog support enabled, say Y, otherwise say N.
288 To compile this driver as a module, choose M here: the
289 module will be called bfin_wdt.
297 # X86 (i386 + ia64 + x86_64) Architecture
300 tristate "Acquire SBC Watchdog Timer"
303 This is the driver for the hardware watchdog on Single Board
304 Computers produced by Acquire Inc (and others). This watchdog
305 simply watches your kernel to make sure it doesn't freeze, and if
306 it does, it reboots your computer after a certain amount of time.
308 To compile this driver as a module, choose M here: the
309 module will be called acquirewdt.
311 Most people will say N.
314 tristate "Advantech SBC Watchdog Timer"
317 If you are configuring a Linux kernel for the Advantech single-board
318 computer, say `Y' here to support its built-in watchdog timer
319 feature. More information can be found at
320 <http://www.advantech.com.tw/products/>
323 tristate "ALi M1535 PMU Watchdog Timer"
324 depends on X86 && PCI
326 This is the driver for the hardware watchdog on the ALi M1535 PMU.
328 To compile this driver as a module, choose M here: the
329 module will be called alim1535_wdt.
331 Most people will say N.
334 tristate "ALi M7101 PMU Computer Watchdog"
337 This is the driver for the hardware watchdog on the ALi M7101 PMU
338 as used in the x86 Cobalt servers and also found in some
339 SPARC Netra servers too.
341 To compile this driver as a module, choose M here: the
342 module will be called alim7101_wdt.
344 Most people will say N.
347 tristate "AMD Geode CS5535/CS5536 Watchdog"
350 This driver enables a watchdog capability built into the
351 CS5535/CS5536 companion chips for the AMD Geode GX and LX
352 processors. This watchdog watches your kernel to make sure
353 it doesn't freeze, and if it does, it reboots your computer after
354 a certain amount of time.
356 You can compile this driver directly into the kernel, or use
357 it as a module. The module will be called geodewdt.
360 tristate "AMD Elan SC520 processor Watchdog"
363 This is the driver for the hardware watchdog built in to the
364 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
365 This watchdog simply watches your kernel to make sure it doesn't
366 freeze, and if it does, it reboots your computer after a certain
369 You can compile this driver directly into the kernel, or use
370 it as a module. The module will be called sc520_wdt.
373 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
376 Enable support for the watchdog timer on the Eurotech CPU-1220 and
377 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
378 information are at <http://www.eurotech.it/>.
381 tristate "IB700 SBC Watchdog Timer"
384 This is the driver for the hardware watchdog on the IB700 Single
385 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
386 simply watches your kernel to make sure it doesn't freeze, and if
387 it does, it reboots your computer after a certain amount of time.
389 This driver is like the WDT501 driver but for slightly different hardware.
391 To compile this driver as a module, choose M here: the
392 module will be called ib700wdt.
394 Most people will say N.
397 tristate "IBM Automatic Server Restart"
400 This is the driver for the IBM Automatic Server Restart watchdog
401 timer built-in into some eServer xSeries machines.
403 To compile this driver as a module, choose M here: the
404 module will be called ibmasr.
407 tristate "ICP Single Board Computer Watchdog Timer"
410 This is a driver for the hardware watchdog on the ICP Single
411 Board Computer. This driver is working on (at least) the following
412 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
414 To compile this driver as a module, choose M here: the
415 module will be called wafer5823wdt.
418 tristate "Intel 6300ESB Timer/Watchdog"
419 depends on X86 && PCI
421 Hardware driver for the watchdog timer built into the Intel
422 6300ESB controller hub.
424 To compile this driver as a module, choose M here: the
425 module will be called i6300esb.
428 tristate "Intel TCO Timer/Watchdog"
429 depends on (X86 || IA64) && PCI
431 Hardware driver for the intel TCO timer based watchdog devices.
432 These drivers are included in the Intel 82801 I/O Controller
433 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
436 The TCO (Total Cost of Ownership) timer is a watchdog timer
437 that will reboot the machine after its second expiration. The
438 expiration time can be configured with the "heartbeat" parameter.
440 On some motherboards the driver may fail to reset the chipset's
441 NO_REBOOT flag which prevents the watchdog from rebooting the
442 machine. If this is the case you will get a kernel message like
443 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
445 To compile this driver as a module, choose M here: the
446 module will be called iTCO_wdt.
448 config ITCO_VENDOR_SUPPORT
449 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
452 Add vendor specific support to the intel TCO timer based watchdog
453 devices. At this moment we only have additional support for some
454 SuperMicro Inc. motherboards.
457 tristate "IT8712F (Smart Guardian) Watchdog Timer"
460 This is the driver for the built-in watchdog timer on the IT8712F
461 Super I/0 chipset used on many motherboards.
463 To compile this driver as a module, choose M here: the
464 module will be called it8712f_wdt.
467 tristate "IT87 Watchdog Timer"
468 depends on X86 && EXPERIMENTAL
470 This is the driver for the hardware watchdog on the ITE IT8716,
471 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
472 simply watches your kernel to make sure it doesn't freeze, and if
473 it does, it reboots your computer after a certain amount of time.
475 To compile this driver as a module, choose M here: the module will
479 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
482 A software monitoring watchdog and NMI sourcing driver. This driver
483 will detect lockups and provide stack trace. Also, when an NMI
484 occurs this driver will make the necessary BIOS calls to log
485 the cause of the NMI. This is a driver that will only load on a
486 HP ProLiant system with a minimum of iLO2 support.
487 To compile this driver as a module, choose M here: the
488 module will be called hpwdt.
491 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
494 This is a driver for National Semiconductor PC87307/PC97307 hardware
495 watchdog cards as found on the SC1200. This watchdog is mainly used
496 for power management purposes and can be used to power down the device
497 during inactivity periods (includes interrupt activity monitoring).
499 To compile this driver as a module, choose M here: the
500 module will be called sc1200wdt.
502 Most people will say N.
505 tristate "National Semiconductor SCx200 Watchdog"
506 depends on SCx200 && PCI
508 Enable the built-in watchdog timer support on the National
509 Semiconductor SCx200 processors.
511 If compiled as a module, it will be called scx200_wdt.
514 tristate "NS PC87413 watchdog"
517 This is the driver for the hardware watchdog on the PC87413 chipset
518 This watchdog simply watches your kernel to make sure it doesn't
519 freeze, and if it does, it reboots your computer after a certain
522 To compile this driver as a module, choose M here: the
523 module will be called pc87413_wdt.
525 Most people will say N.
528 tristate "RDC R-321x SoC watchdog"
529 depends on X86_RDC321X
531 This is the driver for the built in hardware watchdog
532 in the RDC R-321x SoC.
534 To compile this driver as a module, choose M here: the
535 module will be called rdc321x_wdt.
538 tristate "SBC-60XX Watchdog Timer"
541 This driver can be used with the watchdog timer found on some
542 single board computers, namely the 6010 PII based computer.
543 It may well work with other cards. It reads port 0x443 to enable
544 and re-set the watchdog timer, and reads port 0x45 to disable
545 the watchdog. If you have a card that behave in similar ways,
546 you can probably make this driver work with your card as well.
548 You can compile this driver directly into the kernel, or use
549 it as a module. The module will be called sbc60xxwdt.
552 tristate "SBC8360 Watchdog Timer"
556 This is the driver for the hardware watchdog on the SBC8360 Single
557 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
559 To compile this driver as a module, choose M here: the
560 module will be called sbc8360.
562 Most people will say N.
565 tristate "SBC Nano 7240 Watchdog Timer"
568 This is the driver for the hardware watchdog found on the IEI
569 single board computers EPIC Nano 7240 (and likely others). This
570 watchdog simply watches your kernel to make sure it doesn't freeze,
571 and if it does, it reboots your computer after a certain amount of
574 To compile this driver as a module, choose M here: the
575 module will be called sbc7240_wdt.
578 tristate "SMA CPU5 Watchdog"
582 To compile this driver as a module, choose M here: the
583 module will be called cpu5wdt.
585 config SMSC_SCH311X_WDT
586 tristate "SMSC SCH311X Watchdog Timer"
589 This is the driver for the hardware watchdog timer on the
590 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
591 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
594 To compile this driver as a module, choose M here: the
595 module will be called sch311x_wdt.
597 config SMSC37B787_WDT
598 tristate "Winbond SMsC37B787 Watchdog Timer"
601 This is the driver for the hardware watchdog component on the
602 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
603 from Vision Systems and maybe others.
605 This watchdog simply watches your kernel to make sure it doesn't
606 freeze, and if it does, it reboots your computer after a certain
609 Usually a userspace daemon will notify the kernel WDT driver that
610 userspace is still alive, at regular intervals.
612 To compile this driver as a module, choose M here: the
613 module will be called smsc37b787_wdt.
615 Most people will say N.
618 tristate "W83627HF Watchdog Timer"
621 This is the driver for the hardware watchdog on the W83627HF chipset
622 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
623 (and likely others). This watchdog simply watches your kernel to
624 make sure it doesn't freeze, and if it does, it reboots your computer
625 after a certain amount of time.
627 To compile this driver as a module, choose M here: the
628 module will be called w83627hf_wdt.
630 Most people will say N.
633 tristate "W83697HF/W83697HG Watchdog Timer"
636 This is the driver for the hardware watchdog on the W83697HF/HG
637 chipset as used in Dedibox/VIA motherboards (and likely others).
638 This watchdog simply watches your kernel to make sure it doesn't
639 freeze, and if it does, it reboots your computer after a certain
642 To compile this driver as a module, choose M here: the
643 module will be called w83697hf_wdt.
645 Most people will say N.
648 tristate "W83697UG/W83697UF Watchdog Timer"
651 This is the driver for the hardware watchdog on the W83697UG/UF
652 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
653 This watchdog simply watches your kernel to make sure it doesn't
654 freeze, and if it does, it reboots your computer after a certain
657 To compile this driver as a module, choose M here: the
658 module will be called w83697ug_wdt.
660 Most people will say N.
663 tristate "W83877F (EMACS) Watchdog Timer"
666 This is the driver for the hardware watchdog on the W83877F chipset
667 as used in EMACS PC-104 motherboards (and likely others). This
668 watchdog simply watches your kernel to make sure it doesn't freeze,
669 and if it does, it reboots your computer after a certain amount of
672 To compile this driver as a module, choose M here: the
673 module will be called w83877f_wdt.
675 Most people will say N.
678 tristate "W83977F (PCM-5335) Watchdog Timer"
681 This is the driver for the hardware watchdog on the W83977F I/O chip
682 as used in AAEON's PCM-5335 SBC (and likely others). This
683 watchdog simply watches your kernel to make sure it doesn't freeze,
684 and if it does, it reboots your computer after a certain amount of
687 To compile this driver as a module, choose M here: the
688 module will be called w83977f_wdt.
691 tristate "ZF MachZ Watchdog"
694 If you are using a ZF Micro MachZ processor, say Y here, otherwise
695 N. This is the driver for the watchdog timer built-in on that
696 processor using ZF-Logic interface. This watchdog simply watches
697 your kernel to make sure it doesn't freeze, and if it does, it
698 reboots your computer after a certain amount of time.
700 To compile this driver as a module, choose M here: the
701 module will be called machzwd.
703 config SBC_EPX_C3_WATCHDOG
704 tristate "Winsystems SBC EPX-C3 watchdog"
707 This is the driver for the built-in watchdog timer on the EPX-C3
708 Single-board computer made by Winsystems, Inc.
710 *Note*: This hardware watchdog is not probeable and thus there
711 is no way to know if writing to its IO address will corrupt
712 your system or have any real effect. The only way to be sure
713 that this driver does what you want is to make sure you
714 are running it on an EPX-C3 from Winsystems with the watchdog
715 timer at IO address 0x1ee and 0x1ef. It will write to both those
716 IO ports. Basically, the assumption is made that if you compile
717 this driver into your kernel and/or load it as a module, that you
718 know what you are doing and that you are in fact running on an
721 To compile this driver as a module, choose M here: the
722 module will be called sbc_epx_c3.
728 # M68KNOMMU Architecture
733 tristate "Broadcom BCM47xx Watchdog Timer"
736 Hardware driver for the Broadcom BCM47xx Watchog Timer.
739 tristate "IDT RC32434 SoC Watchdog Timer"
740 depends on MIKROTIK_RB532
742 Hardware driver for the IDT RC32434 SoC built-in
745 To compile this driver as a module, choose M here: the
746 module will be called rc32434_wdt.
749 tristate "Indy/I2 Hardware Watchdog"
750 depends on SGI_HAS_INDYDOG
752 Hardware driver for the Indy's/I2's watchdog. This is a
753 watchdog timer that will reboot the machine after a 60 second
754 timer expired and no process has written to /dev/watchdog during
758 tristate "MTX-1 Hardware Watchdog"
761 Hardware driver for the MTX-1 boards. This is a watchdog timer that
762 will reboot the machine after a 100 seconds timer expired.
765 tristate "PNX833x Hardware Watchdog"
766 depends on SOC_PNX8335
768 Hardware driver for the PNX833x's watchdog. This is a
769 watchdog timer that will reboot the machine after a programable
770 timer has expired and no process has written to /dev/watchdog during
774 tristate "RM9000/GPI hardware watchdog"
775 depends on CPU_RM9000
777 Watchdog implementation using the GPI hardware found on
778 PMC-Sierra RM9xxx CPUs.
780 To compile this driver as a module, choose M here: the
781 module will be called rm9k_wdt.
784 tristate "Sibyte SoC hardware watchdog"
787 Watchdog driver for the built in watchdog hardware in Sibyte
788 SoC processors. There are apparently two watchdog timers
789 on such processors; this driver supports only the first one,
790 because currently Linux only supports exporting one watchdog
793 To compile this driver as a loadable module, choose M here.
794 The module will be called sb_wdog.
797 tristate "TI AR7 Watchdog Timer"
800 Hardware driver for the TI AR7 Watchdog Timer.
803 tristate "Toshiba TXx9 Watchdog Timer"
804 depends on CPU_TX39XX || CPU_TX49XX
806 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
808 # PARISC Architecture
810 # POWERPC Architecture
813 tristate "GE Fanuc Watchdog Timer"
814 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
816 Watchdog timer found in a number of GE Fanuc single board computers.
819 tristate "MPC5200 Watchdog Timer"
820 depends on PPC_MPC52xx
823 tristate "MPC8xxx Platform Watchdog Timer"
824 depends on PPC_8xx || PPC_83xx || PPC_86xx
826 This driver is for a SoC level watchdog that exists on some
827 Freescale PowerPC processors. So far this driver supports:
832 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
835 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
839 tristate "PIKA FPGA Watchdog"
843 This enables the watchdog in the PIKA FPGA. Currently used on
847 bool "PowerPC Book-E Watchdog Timer"
848 depends on BOOKE || 4xx
850 Please see Documentation/watchdog/watchdog-api.txt for
856 tristate "RTAS watchdog"
859 This driver adds watchdog support for the RTAS watchdog.
861 To compile this driver as a module, choose M here. The module
862 will be called wdrtas.
867 tristate "z/VM Watchdog Timer"
870 IBM s/390 and zSeries machines running under z/VM 5.1 or later
871 provide a virtual watchdog timer to their guest that cause a
872 user define Control Program command to be executed after a
875 To compile this driver as a module, choose M here. The module
876 will be called vmwatchdog.
878 # SUPERH (sh + sh64) Architecture
881 tristate "SuperH Watchdog"
882 depends on SUPERH && (CPU_SH3 || CPU_SH4)
884 This driver adds watchdog support for the integrated watchdog in the
885 SuperH processors. If you have one of these processors and wish
886 to have watchdog support enabled, say Y, otherwise say N.
888 As a side note, saying Y here will automatically boost HZ to 1000
889 so that the timer has a chance to clear the overflow counter. On
890 slower systems (such as the SH-2 and SH-3) this will likely yield
891 some performance issues. As such, the WDT should be avoided here
892 unless it is absolutely necessary.
894 To compile this driver as a module, choose M here: the
895 module will be called shwdt.
898 bool "Allow mmap of SH WDT"
902 If you say Y here, user applications will be able to mmap the
907 # SPARC64 Architecture
909 config WATCHDOG_CP1XXX
910 tristate "CP1XXX Hardware Watchdog support"
911 depends on SPARC64 && PCI
913 This is the driver for the hardware watchdog timers present on
914 Sun Microsystems CompactPCI models CP1400 and CP1500.
916 To compile this driver as a module, choose M here: the
917 module will be called cpwatchdog.
919 If you do not have a CompactPCI model CP1400 or CP1500, or
920 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
921 you should say N to this option.
924 tristate "RIO Hardware Watchdog support"
925 depends on SPARC64 && PCI
927 Say Y here to support the hardware watchdog capability on Sun RIO
928 machines. The watchdog timeout period is normally one minute but
929 can be changed with a boot-time parameter.
931 # XTENSA Architecture
934 # ISA-based Watchdog Cards
937 comment "ISA-based Watchdog Cards"
941 tristate "Berkshire Products ISA-PC Watchdog"
944 This is the driver for the Berkshire Products ISA-PC Watchdog card.
945 This card simply watches your kernel to make sure it doesn't freeze,
946 and if it does, it reboots your computer after a certain amount of
947 time. This driver is like the WDT501 driver but for different
948 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
949 watchdog cards can be ordered from <http://www.berkprod.com/>.
951 To compile this driver as a module, choose M here: the
952 module will be called pcwd.
954 Most people will say N.
957 tristate "Mixcom Watchdog"
960 This is a driver for the Mixcom hardware watchdog cards. This
961 watchdog simply watches your kernel to make sure it doesn't freeze,
962 and if it does, it reboots your computer after a certain amount of
965 To compile this driver as a module, choose M here: the
966 module will be called mixcomwd.
968 Most people will say N.
971 tristate "WDT Watchdog timer"
974 If you have a WDT500P or WDT501P watchdog board, say Y here,
975 otherwise N. It is not possible to probe for this board, which means
976 that you have to inform the kernel about the IO port and IRQ that
977 is needed (you can do this via the io and irq parameters)
979 To compile this driver as a module, choose M here: the
980 module will be called wdt.
983 # PCI-based Watchdog Cards
986 comment "PCI-based Watchdog Cards"
990 tristate "Berkshire Products PCI-PC Watchdog"
993 This is the driver for the Berkshire Products PCI-PC Watchdog card.
994 This card simply watches your kernel to make sure it doesn't freeze,
995 and if it does, it reboots your computer after a certain amount of
996 time. The card can also monitor the internal temperature of the PC.
997 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
999 To compile this driver as a module, choose M here: the
1000 module will be called pcwd_pci.
1002 Most people will say N.
1005 tristate "PCI-WDT500/501 Watchdog timer"
1008 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
1010 If you have a PCI-WDT501 watchdog board then you can enable the
1011 temperature sensor by setting the type parameter to 501.
1013 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1014 can do this via the tachometer parameter. Only do this if you have a
1015 fan tachometer actually set up.
1017 To compile this driver as a module, choose M here: the
1018 module will be called wdt_pci.
1021 # USB-based Watchdog Cards
1024 comment "USB-based Watchdog Cards"
1027 config USBPCWATCHDOG
1028 tristate "Berkshire Products USB-PC Watchdog"
1031 This is the driver for the Berkshire Products USB-PC Watchdog card.
1032 This card simply watches your kernel to make sure it doesn't freeze,
1033 and if it does, it reboots your computer after a certain amount of
1034 time. The card can also monitor the internal temperature of the PC.
1035 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1037 To compile this driver as a module, choose M here: the
1038 module will be called pcwd_usb.
1040 Most people will say N.