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.
262 config AT32AP700X_WDT
263 tristate "AT32AP700x watchdog"
264 depends on CPU_AT32AP700X
266 Watchdog timer embedded into AT32AP700x devices. This will reboot
267 your system when the timeout is reached.
269 # BLACKFIN Architecture
272 tristate "Blackfin On-Chip Watchdog Timer"
275 If you say yes here you will get support for the Blackfin On-Chip
276 Watchdog Timer. If you have one of these processors and wish to
277 have watchdog support enabled, say Y, otherwise say N.
279 To compile this driver as a module, choose M here: the
280 module will be called bfin_wdt.
288 # X86 (i386 + ia64 + x86_64) Architecture
291 tristate "Acquire SBC Watchdog Timer"
294 This is the driver for the hardware watchdog on Single Board
295 Computers produced by Acquire Inc (and others). This watchdog
296 simply watches your kernel to make sure it doesn't freeze, and if
297 it does, it reboots your computer after a certain amount of time.
299 To compile this driver as a module, choose M here: the
300 module will be called acquirewdt.
302 Most people will say N.
305 tristate "Advantech SBC Watchdog Timer"
308 If you are configuring a Linux kernel for the Advantech single-board
309 computer, say `Y' here to support its built-in watchdog timer
310 feature. More information can be found at
311 <http://www.advantech.com.tw/products/>
314 tristate "ALi M1535 PMU Watchdog Timer"
315 depends on X86 && PCI
317 This is the driver for the hardware watchdog on the ALi M1535 PMU.
319 To compile this driver as a module, choose M here: the
320 module will be called alim1535_wdt.
322 Most people will say N.
325 tristate "ALi M7101 PMU Computer Watchdog"
328 This is the driver for the hardware watchdog on the ALi M7101 PMU
329 as used in the x86 Cobalt servers and also found in some
330 SPARC Netra servers too.
332 To compile this driver as a module, choose M here: the
333 module will be called alim7101_wdt.
335 Most people will say N.
338 tristate "AMD Geode CS5535/CS5536 Watchdog"
341 This driver enables a watchdog capability built into the
342 CS5535/CS5536 companion chips for the AMD Geode GX and LX
343 processors. This watchdog watches your kernel to make sure
344 it doesn't freeze, and if it does, it reboots your computer after
345 a certain amount of time.
347 You can compile this driver directly into the kernel, or use
348 it as a module. The module will be called geodewdt.
351 tristate "AMD Elan SC520 processor Watchdog"
354 This is the driver for the hardware watchdog built in to the
355 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
356 This watchdog simply watches your kernel to make sure it doesn't
357 freeze, and if it does, it reboots your computer after a certain
360 You can compile this driver directly into the kernel, or use
361 it as a module. The module will be called sc520_wdt.
364 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
367 Enable support for the watchdog timer on the Eurotech CPU-1220 and
368 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
369 information are at <http://www.eurotech.it/>.
372 tristate "IB700 SBC Watchdog Timer"
375 This is the driver for the hardware watchdog on the IB700 Single
376 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
377 simply watches your kernel to make sure it doesn't freeze, and if
378 it does, it reboots your computer after a certain amount of time.
380 This driver is like the WDT501 driver but for slightly different hardware.
382 To compile this driver as a module, choose M here: the
383 module will be called ib700wdt.
385 Most people will say N.
388 tristate "IBM Automatic Server Restart"
391 This is the driver for the IBM Automatic Server Restart watchdog
392 timer built-in into some eServer xSeries machines.
394 To compile this driver as a module, choose M here: the
395 module will be called ibmasr.
398 tristate "ICP Single Board Computer Watchdog Timer"
401 This is a driver for the hardware watchdog on the ICP Single
402 Board Computer. This driver is working on (at least) the following
403 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
405 To compile this driver as a module, choose M here: the
406 module will be called wafer5823wdt.
409 tristate "Intel 6300ESB Timer/Watchdog"
410 depends on X86 && PCI
412 Hardware driver for the watchdog timer built into the Intel
413 6300ESB controller hub.
415 To compile this driver as a module, choose M here: the
416 module will be called i6300esb.
419 tristate "Intel TCO Timer/Watchdog"
420 depends on (X86 || IA64) && PCI
422 Hardware driver for the intel TCO timer based watchdog devices.
423 These drivers are included in the Intel 82801 I/O Controller
424 Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
427 The TCO (Total Cost of Ownership) timer is a watchdog timer
428 that will reboot the machine after its second expiration. The
429 expiration time can be configured with the "heartbeat" parameter.
431 On some motherboards the driver may fail to reset the chipset's
432 NO_REBOOT flag which prevents the watchdog from rebooting the
433 machine. If this is the case you will get a kernel message like
434 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
436 To compile this driver as a module, choose M here: the
437 module will be called iTCO_wdt.
439 config ITCO_VENDOR_SUPPORT
440 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
443 Add vendor specific support to the intel TCO timer based watchdog
444 devices. At this moment we only have additional support for some
445 SuperMicro Inc. motherboards.
448 tristate "IT8712F (Smart Guardian) Watchdog Timer"
451 This is the driver for the built-in watchdog timer on the IT8712F
452 Super I/0 chipset used on many motherboards.
454 To compile this driver as a module, choose M here: the
455 module will be called it8712f_wdt.
458 tristate "IT87 Watchdog Timer"
459 depends on X86 && EXPERIMENTAL
461 This is the driver for the hardware watchdog on the ITE IT8716,
462 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
463 simply watches your kernel to make sure it doesn't freeze, and if
464 it does, it reboots your computer after a certain amount of time.
466 To compile this driver as a module, choose M here: the module will
470 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
473 A software monitoring watchdog and NMI sourcing driver. This driver
474 will detect lockups and provide stack trace. Also, when an NMI
475 occurs this driver will make the necessary BIOS calls to log
476 the cause of the NMI. This is a driver that will only load on a
477 HP ProLiant system with a minimum of iLO2 support.
478 To compile this driver as a module, choose M here: the
479 module will be called hpwdt.
482 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
485 This is a driver for National Semiconductor PC87307/PC97307 hardware
486 watchdog cards as found on the SC1200. This watchdog is mainly used
487 for power management purposes and can be used to power down the device
488 during inactivity periods (includes interrupt activity monitoring).
490 To compile this driver as a module, choose M here: the
491 module will be called sc1200wdt.
493 Most people will say N.
496 tristate "National Semiconductor SCx200 Watchdog"
497 depends on SCx200 && PCI
499 Enable the built-in watchdog timer support on the National
500 Semiconductor SCx200 processors.
502 If compiled as a module, it will be called scx200_wdt.
505 tristate "NS PC87413 watchdog"
508 This is the driver for the hardware watchdog on the PC87413 chipset
509 This watchdog simply watches your kernel to make sure it doesn't
510 freeze, and if it does, it reboots your computer after a certain
513 To compile this driver as a module, choose M here: the
514 module will be called pc87413_wdt.
516 Most people will say N.
519 tristate "RDC R-321x SoC watchdog"
520 depends on X86_RDC321X
522 This is the driver for the built in hardware watchdog
523 in the RDC R-321x SoC.
525 To compile this driver as a module, choose M here: the
526 module will be called rdc321x_wdt.
529 tristate "SBC-60XX Watchdog Timer"
532 This driver can be used with the watchdog timer found on some
533 single board computers, namely the 6010 PII based computer.
534 It may well work with other cards. It reads port 0x443 to enable
535 and re-set the watchdog timer, and reads port 0x45 to disable
536 the watchdog. If you have a card that behave in similar ways,
537 you can probably make this driver work with your card as well.
539 You can compile this driver directly into the kernel, or use
540 it as a module. The module will be called sbc60xxwdt.
543 tristate "SBC8360 Watchdog Timer"
547 This is the driver for the hardware watchdog on the SBC8360 Single
548 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
550 To compile this driver as a module, choose M here: the
551 module will be called sbc8360.
553 Most people will say N.
556 tristate "SBC Nano 7240 Watchdog Timer"
559 This is the driver for the hardware watchdog found on the IEI
560 single board computers EPIC Nano 7240 (and likely others). This
561 watchdog simply watches your kernel to make sure it doesn't freeze,
562 and if it does, it reboots your computer after a certain amount of
565 To compile this driver as a module, choose M here: the
566 module will be called sbc7240_wdt.
569 tristate "SMA CPU5 Watchdog"
573 To compile this driver as a module, choose M here: the
574 module will be called cpu5wdt.
576 config SMSC_SCH311X_WDT
577 tristate "SMSC SCH311X Watchdog Timer"
580 This is the driver for the hardware watchdog timer on the
581 SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
582 (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
585 To compile this driver as a module, choose M here: the
586 module will be called sch311x_wdt.
588 config SMSC37B787_WDT
589 tristate "Winbond SMsC37B787 Watchdog Timer"
592 This is the driver for the hardware watchdog component on the
593 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
594 from Vision Systems and maybe others.
596 This watchdog simply watches your kernel to make sure it doesn't
597 freeze, and if it does, it reboots your computer after a certain
600 Usually a userspace daemon will notify the kernel WDT driver that
601 userspace is still alive, at regular intervals.
603 To compile this driver as a module, choose M here: the
604 module will be called smsc37b787_wdt.
606 Most people will say N.
609 tristate "W83627HF Watchdog Timer"
612 This is the driver for the hardware watchdog on the W83627HF chipset
613 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
614 (and likely others). This watchdog simply watches your kernel to
615 make sure it doesn't freeze, and if it does, it reboots your computer
616 after a certain amount of time.
618 To compile this driver as a module, choose M here: the
619 module will be called w83627hf_wdt.
621 Most people will say N.
624 tristate "W83697HF/W83697HG Watchdog Timer"
627 This is the driver for the hardware watchdog on the W83697HF/HG
628 chipset as used in Dedibox/VIA motherboards (and likely others).
629 This watchdog simply watches your kernel to make sure it doesn't
630 freeze, and if it does, it reboots your computer after a certain
633 To compile this driver as a module, choose M here: the
634 module will be called w83697hf_wdt.
636 Most people will say N.
639 tristate "W83697UG/W83697UF Watchdog Timer"
642 This is the driver for the hardware watchdog on the W83697UG/UF
643 chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
644 This watchdog simply watches your kernel to make sure it doesn't
645 freeze, and if it does, it reboots your computer after a certain
648 To compile this driver as a module, choose M here: the
649 module will be called w83697ug_wdt.
651 Most people will say N.
654 tristate "W83877F (EMACS) Watchdog Timer"
657 This is the driver for the hardware watchdog on the W83877F chipset
658 as used in EMACS PC-104 motherboards (and likely others). This
659 watchdog simply watches your kernel to make sure it doesn't freeze,
660 and if it does, it reboots your computer after a certain amount of
663 To compile this driver as a module, choose M here: the
664 module will be called w83877f_wdt.
666 Most people will say N.
669 tristate "W83977F (PCM-5335) Watchdog Timer"
672 This is the driver for the hardware watchdog on the W83977F I/O chip
673 as used in AAEON's PCM-5335 SBC (and likely others). This
674 watchdog simply watches your kernel to make sure it doesn't freeze,
675 and if it does, it reboots your computer after a certain amount of
678 To compile this driver as a module, choose M here: the
679 module will be called w83977f_wdt.
682 tristate "ZF MachZ Watchdog"
685 If you are using a ZF Micro MachZ processor, say Y here, otherwise
686 N. This is the driver for the watchdog timer built-in on that
687 processor using ZF-Logic interface. This watchdog simply watches
688 your kernel to make sure it doesn't freeze, and if it does, it
689 reboots your computer after a certain amount of time.
691 To compile this driver as a module, choose M here: the
692 module will be called machzwd.
694 config SBC_EPX_C3_WATCHDOG
695 tristate "Winsystems SBC EPX-C3 watchdog"
698 This is the driver for the built-in watchdog timer on the EPX-C3
699 Single-board computer made by Winsystems, Inc.
701 *Note*: This hardware watchdog is not probeable and thus there
702 is no way to know if writing to its IO address will corrupt
703 your system or have any real effect. The only way to be sure
704 that this driver does what you want is to make sure you
705 are running it on an EPX-C3 from Winsystems with the watchdog
706 timer at IO address 0x1ee and 0x1ef. It will write to both those
707 IO ports. Basically, the assumption is made that if you compile
708 this driver into your kernel and/or load it as a module, that you
709 know what you are doing and that you are in fact running on an
712 To compile this driver as a module, choose M here: the
713 module will be called sbc_epx_c3.
719 # M68KNOMMU Architecture
724 tristate "IDT RC32434 SoC Watchdog Timer"
725 depends on MIKROTIK_RB532
727 Hardware driver for the IDT RC32434 SoC built-in
730 To compile this driver as a module, choose M here: the
731 module will be called rc32434_wdt.
734 tristate "Indy/I2 Hardware Watchdog"
735 depends on SGI_HAS_INDYDOG
737 Hardware driver for the Indy's/I2's watchdog. This is a
738 watchdog timer that will reboot the machine after a 60 second
739 timer expired and no process has written to /dev/watchdog during
743 tristate "MTX-1 Hardware Watchdog"
746 Hardware driver for the MTX-1 boards. This is a watchdog timer that
747 will reboot the machine after a 100 seconds timer expired.
750 tristate "PNX833x Hardware Watchdog"
751 depends on SOC_PNX8335
753 Hardware driver for the PNX833x's watchdog. This is a
754 watchdog timer that will reboot the machine after a programable
755 timer has expired and no process has written to /dev/watchdog during
759 tristate "RM9000/GPI hardware watchdog"
760 depends on CPU_RM9000
762 Watchdog implementation using the GPI hardware found on
763 PMC-Sierra RM9xxx CPUs.
765 To compile this driver as a module, choose M here: the
766 module will be called rm9k_wdt.
769 tristate "Sibyte SoC hardware watchdog"
772 Watchdog driver for the built in watchdog hardware in Sibyte
773 SoC processors. There are apparently two watchdog timers
774 on such processors; this driver supports only the first one,
775 because currently Linux only supports exporting one watchdog
778 To compile this driver as a loadable module, choose M here.
779 The module will be called sb_wdog.
782 tristate "TI AR7 Watchdog Timer"
785 Hardware driver for the TI AR7 Watchdog Timer.
788 tristate "Toshiba TXx9 Watchdog Timer"
789 depends on CPU_TX39XX || CPU_TX49XX
791 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
793 # PARISC Architecture
795 # POWERPC Architecture
798 tristate "GE Fanuc Watchdog Timer"
799 depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
801 Watchdog timer found in a number of GE Fanuc single board computers.
804 tristate "MPC5200 Watchdog Timer"
805 depends on PPC_MPC52xx
808 tristate "MPC8xxx Platform Watchdog Timer"
809 depends on PPC_8xx || PPC_83xx || PPC_86xx
811 This driver is for a SoC level watchdog that exists on some
812 Freescale PowerPC processors. So far this driver supports:
817 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
820 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
824 tristate "PIKA FPGA Watchdog"
828 This enables the watchdog in the PIKA FPGA. Currently used on
832 bool "PowerPC Book-E Watchdog Timer"
833 depends on BOOKE || 4xx
835 Please see Documentation/watchdog/watchdog-api.txt for
841 tristate "RTAS watchdog"
844 This driver adds watchdog support for the RTAS watchdog.
846 To compile this driver as a module, choose M here. The module
847 will be called wdrtas.
852 tristate "z/VM Watchdog Timer"
855 IBM s/390 and zSeries machines running under z/VM 5.1 or later
856 provide a virtual watchdog timer to their guest that cause a
857 user define Control Program command to be executed after a
860 To compile this driver as a module, choose M here. The module
861 will be called vmwatchdog.
863 # SUPERH (sh + sh64) Architecture
866 tristate "SuperH Watchdog"
867 depends on SUPERH && (CPU_SH3 || CPU_SH4)
869 This driver adds watchdog support for the integrated watchdog in the
870 SuperH processors. If you have one of these processors and wish
871 to have watchdog support enabled, say Y, otherwise say N.
873 As a side note, saying Y here will automatically boost HZ to 1000
874 so that the timer has a chance to clear the overflow counter. On
875 slower systems (such as the SH-2 and SH-3) this will likely yield
876 some performance issues. As such, the WDT should be avoided here
877 unless it is absolutely necessary.
879 To compile this driver as a module, choose M here: the
880 module will be called shwdt.
883 bool "Allow mmap of SH WDT"
887 If you say Y here, user applications will be able to mmap the
892 # SPARC64 Architecture
894 config WATCHDOG_CP1XXX
895 tristate "CP1XXX Hardware Watchdog support"
896 depends on SPARC64 && PCI
898 This is the driver for the hardware watchdog timers present on
899 Sun Microsystems CompactPCI models CP1400 and CP1500.
901 To compile this driver as a module, choose M here: the
902 module will be called cpwatchdog.
904 If you do not have a CompactPCI model CP1400 or CP1500, or
905 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
906 you should say N to this option.
909 tristate "RIO Hardware Watchdog support"
910 depends on SPARC64 && PCI
912 Say Y here to support the hardware watchdog capability on Sun RIO
913 machines. The watchdog timeout period is normally one minute but
914 can be changed with a boot-time parameter.
916 # XTENSA Architecture
919 # ISA-based Watchdog Cards
922 comment "ISA-based Watchdog Cards"
926 tristate "Berkshire Products ISA-PC Watchdog"
929 This is the driver for the Berkshire Products ISA-PC Watchdog card.
930 This card simply watches your kernel to make sure it doesn't freeze,
931 and if it does, it reboots your computer after a certain amount of
932 time. This driver is like the WDT501 driver but for different
933 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
934 watchdog cards can be ordered from <http://www.berkprod.com/>.
936 To compile this driver as a module, choose M here: the
937 module will be called pcwd.
939 Most people will say N.
942 tristate "Mixcom Watchdog"
945 This is a driver for the Mixcom hardware watchdog cards. This
946 watchdog simply watches your kernel to make sure it doesn't freeze,
947 and if it does, it reboots your computer after a certain amount of
950 To compile this driver as a module, choose M here: the
951 module will be called mixcomwd.
953 Most people will say N.
956 tristate "WDT Watchdog timer"
959 If you have a WDT500P or WDT501P watchdog board, say Y here,
960 otherwise N. It is not possible to probe for this board, which means
961 that you have to inform the kernel about the IO port and IRQ that
962 is needed (you can do this via the io and irq parameters)
964 To compile this driver as a module, choose M here: the
965 module will be called wdt.
968 # PCI-based Watchdog Cards
971 comment "PCI-based Watchdog Cards"
975 tristate "Berkshire Products PCI-PC Watchdog"
978 This is the driver for the Berkshire Products PCI-PC Watchdog card.
979 This card simply watches your kernel to make sure it doesn't freeze,
980 and if it does, it reboots your computer after a certain amount of
981 time. The card can also monitor the internal temperature of the PC.
982 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
984 To compile this driver as a module, choose M here: the
985 module will be called pcwd_pci.
987 Most people will say N.
990 tristate "PCI-WDT500/501 Watchdog timer"
993 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
995 To compile this driver as a module, choose M here: the
996 module will be called wdt_pci.
999 bool "PCI-WDT501 features"
1002 Saying Y here and creating a character special file /dev/temperature
1003 with major number 10 and minor number 131 ("man mknod") will give
1004 you a thermometer inside your computer: reading from
1005 /dev/temperature yields one byte, the temperature in degrees
1006 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
1009 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
1010 can do this via the tachometer parameter. Only do this if you have a
1011 fan tachometer actually set up.
1014 # USB-based Watchdog Cards
1017 comment "USB-based Watchdog Cards"
1020 config USBPCWATCHDOG
1021 tristate "Berkshire Products USB-PC Watchdog"
1024 This is the driver for the Berkshire Products USB-PC Watchdog card.
1025 This card simply watches your kernel to make sure it doesn't freeze,
1026 and if it does, it reboots your computer after a certain amount of
1027 time. The card can also monitor the internal temperature of the PC.
1028 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
1030 To compile this driver as a module, choose M here: the
1031 module will be called pcwd_usb.
1033 Most people will say N.