xref: /linux/drivers/watchdog/Kconfig (revision 98366c20a275e957416e9516db5dcb7195b4e101)
1#
2# Watchdog device configuration
3#
4
5menuconfig WATCHDOG
6	bool "Watchdog Timer Support"
7	---help---
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.
20
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
25	  table is full.
26
27	  If unsure, say N.
28
29if WATCHDOG
30
31config WATCHDOG_NOWAYOUT
32	bool "Disable watchdog shutdown on close"
33	help
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
38	  it has been started.
39
40#
41# General Watchdog drivers
42#
43
44comment "Watchdog Device Drivers"
45
46# Architecture Independent
47
48config SOFT_WATCHDOG
49	tristate "Software watchdog"
50	help
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.
54
55	  To compile this driver as a module, choose M here: the
56	  module will be called softdog.
57
58# ALPHA Architecture
59
60# ARM Architecture
61
62config AT91RM9200_WATCHDOG
63	tristate "AT91RM9200 watchdog"
64	depends on ARCH_AT91RM9200
65	help
66	  Watchdog timer embedded into AT91RM9200 chips. This will reboot your
67	  system when the timeout is reached.
68
69config 21285_WATCHDOG
70	tristate "DC21285 watchdog"
71	depends on FOOTBRIDGE
72	help
73	  The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
74	  here if you wish to use this. Alternatively say M to compile the
75	  driver as a module, which will be called wdt285.
76
77	  This driver does not work on all machines. In particular, early CATS
78	  boards have hardware problems that will cause the machine to simply
79	  lock up if the watchdog fires.
80
81	  "If in doubt, leave it out" - say N.
82
83config 977_WATCHDOG
84	tristate "NetWinder WB83C977 watchdog"
85	depends on FOOTBRIDGE && ARCH_NETWINDER
86	help
87	  Say Y here to include support for the WB977 watchdog included in
88	  NetWinder machines. Alternatively say M to compile the driver as
89	  a module, which will be called wdt977.
90
91	  Not sure? It's safe to say N.
92
93config IXP2000_WATCHDOG
94	tristate "IXP2000 Watchdog"
95	depends on ARCH_IXP2000
96	help
97	  Say Y here if to include support for the watchdog timer
98	  in the Intel IXP2000(2400, 2800, 2850) network processors.
99	  This driver can be built as a module by choosing M. The module
100	  will be called ixp2000_wdt.
101
102	  Say N if you are unsure.
103
104config IXP4XX_WATCHDOG
105	tristate "IXP4xx Watchdog"
106	depends on ARCH_IXP4XX
107	help
108	  Say Y here if to include support for the watchdog timer
109	  in the Intel IXP4xx network processors. This driver can
110	  be built as a module by choosing M. The module will
111	  be called ixp4xx_wdt.
112
113	  Note: The internal IXP4xx watchdog does a soft CPU reset
114	  which doesn't reset any peripherals. There are circumstances
115	  where the watchdog will fail to reset the board correctly
116	  (e.g., if the boot ROM is in an unreadable state).
117
118	  Say N if you are unsure.
119
120config KS8695_WATCHDOG
121	tristate "KS8695 watchdog"
122	depends on ARCH_KS8695
123	help
124	  Watchdog timer embedded into KS8695 processor. This will reboot your
125	  system when the timeout is reached.
126
127config S3C2410_WATCHDOG
128	tristate "S3C2410 Watchdog"
129	depends on ARCH_S3C2410
130	help
131	  Watchdog timer block in the Samsung S3C2410 chips. This will
132	  reboot the system when the timer expires with the watchdog
133	  enabled.
134
135	  The driver is limited by the speed of the system's PCLK
136	  signal, so with reasonably fast systems (PCLK around 50-66MHz)
137	  then watchdog intervals of over approximately 20seconds are
138	  unavailable.
139
140	  The driver can be built as a module by choosing M, and will
141	  be called s3c2410_wdt
142
143config SA1100_WATCHDOG
144	tristate "SA1100/PXA2xx watchdog"
145	depends on ARCH_SA1100 || ARCH_PXA
146	help
147	  Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
148	  reboot your system when timeout is reached.
149
150	  NOTE: once enabled, this timer cannot be disabled.
151
152	  To compile this driver as a module, choose M here: the
153	  module will be called sa1100_wdt.
154
155config MPCORE_WATCHDOG
156	tristate "MPcore watchdog"
157	depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
158	help
159	  Watchdog timer embedded into the MPcore system.
160
161	  To compile this driver as a module, choose M here: the
162	  module will be called mpcore_wdt.
163
164config EP93XX_WATCHDOG
165	tristate "EP93xx Watchdog"
166	depends on ARCH_EP93XX
167	help
168	  Say Y here if to include support for the watchdog timer
169	  embedded in the Cirrus Logic EP93xx family of devices.
170
171	  To compile this driver as a module, choose M here: the
172	  module will be called ep93xx_wdt.
173
174config OMAP_WATCHDOG
175	tristate "OMAP Watchdog"
176	depends on ARCH_OMAP16XX || ARCH_OMAP24XX
177	help
178	  Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog.  Say 'Y' here to
179	  enable the OMAP1610/OMAP1710 watchdog timer.
180
181config PNX4008_WATCHDOG
182	tristate "PNX4008 Watchdog"
183	depends on ARCH_PNX4008
184	help
185	  Say Y here if to include support for the watchdog timer
186	  in the PNX4008 processor.
187	  This driver can be built as a module by choosing M. The module
188	  will be called pnx4008_wdt.
189
190	  Say N if you are unsure.
191
192config IOP_WATCHDOG
193	tristate "IOP Watchdog"
194	depends on PLAT_IOP
195	select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
196	help
197	  Say Y here if to include support for the watchdog timer
198	  in the Intel IOP3XX & IOP13XX I/O Processors.  This driver can
199	  be built as a module by choosing M. The module will
200	  be called iop_wdt.
201
202	  Note: The IOP13XX watchdog does an Internal Bus Reset which will
203	  affect both cores and the peripherals of the IOP.  The ATU-X
204	  and/or ATUe configuration registers will remain intact, but if
205	  operating as an Root Complex and/or Central Resource, the PCI-X
206	  and/or PCIe busses will also be reset.  THIS IS A VERY BIG HAMMER.
207
208config DAVINCI_WATCHDOG
209	tristate "DaVinci watchdog"
210	depends on ARCH_DAVINCI
211	help
212	  Say Y here if to include support for the watchdog timer
213	  in the DaVinci DM644x/DM646x processors.
214	  To compile this driver as a module, choose M here: the
215	  module will be called davinci_wdt.
216
217	  NOTE: once enabled, this timer cannot be disabled.
218	  Say N if you are unsure.
219
220# ARM26 Architecture
221
222# AVR32 Architecture
223
224config AT32AP700X_WDT
225	tristate "AT32AP700x watchdog"
226	depends on CPU_AT32AP7000
227	help
228	  Watchdog timer embedded into AT32AP700x devices. This will reboot
229	  your system when the timeout is reached.
230
231# BLACKFIN Architecture
232
233config BFIN_WDT
234	tristate "Blackfin On-Chip Watchdog Timer"
235	depends on BLACKFIN
236	---help---
237	  If you say yes here you will get support for the Blackfin On-Chip
238	  Watchdog Timer. If you have one of these processors and wish to
239	  have watchdog support enabled, say Y, otherwise say N.
240
241	  To compile this driver as a module, choose M here: the
242	  module will be called bfin_wdt.
243
244# CRIS Architecture
245
246# FRV Architecture
247
248# H8300 Architecture
249
250# X86 (i386 + ia64 + x86_64) Architecture
251
252config ACQUIRE_WDT
253	tristate "Acquire SBC Watchdog Timer"
254	depends on X86
255	---help---
256	  This is the driver for the hardware watchdog on Single Board
257	  Computers produced by Acquire Inc (and others). This watchdog
258	  simply watches your kernel to make sure it doesn't freeze, and if
259	  it does, it reboots your computer after a certain amount of time.
260
261	  To compile this driver as a module, choose M here: the
262	  module will be called acquirewdt.
263
264	  Most people will say N.
265
266config ADVANTECH_WDT
267	tristate "Advantech SBC Watchdog Timer"
268	depends on X86
269	help
270	  If you are configuring a Linux kernel for the Advantech single-board
271	  computer, say `Y' here to support its built-in watchdog timer
272	  feature. More information can be found at
273	  <http://www.advantech.com.tw/products/>
274
275config ALIM1535_WDT
276	tristate "ALi M1535 PMU Watchdog Timer"
277	depends on X86 && PCI
278	---help---
279	  This is the driver for the hardware watchdog on the ALi M1535 PMU.
280
281	  To compile this driver as a module, choose M here: the
282	  module will be called alim1535_wdt.
283
284	  Most people will say N.
285
286config ALIM7101_WDT
287	tristate "ALi M7101 PMU Computer Watchdog"
288	depends on X86 && PCI
289	help
290	  This is the driver for the hardware watchdog on the ALi M7101 PMU
291	  as used in the x86 Cobalt servers.
292
293	  To compile this driver as a module, choose M here: the
294	  module will be called alim7101_wdt.
295
296	  Most people will say N.
297
298config SC520_WDT
299	tristate "AMD Elan SC520 processor Watchdog"
300	depends on X86
301	help
302	  This is the driver for the hardware watchdog built in to the
303	  AMD "Elan" SC520 microcomputer commonly used in embedded systems.
304	  This watchdog simply watches your kernel to make sure it doesn't
305	  freeze, and if it does, it reboots your computer after a certain
306	  amount of time.
307
308	  You can compile this driver directly into the kernel, or use
309	  it as a module.  The module will be called sc520_wdt.
310
311config EUROTECH_WDT
312	tristate "Eurotech CPU-1220/1410 Watchdog Timer"
313	depends on X86
314	help
315	  Enable support for the watchdog timer on the Eurotech CPU-1220 and
316	  CPU-1410 cards.  These are PC/104 SBCs. Spec sheets and product
317	  information are at <http://www.eurotech.it/>.
318
319config IB700_WDT
320	tristate "IB700 SBC Watchdog Timer"
321	depends on X86
322	---help---
323	  This is the driver for the hardware watchdog on the IB700 Single
324	  Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
325	  simply watches your kernel to make sure it doesn't freeze, and if
326	  it does, it reboots your computer after a certain amount of time.
327
328	  This driver is like the WDT501 driver but for slightly different hardware.
329
330	  To compile this driver as a module, choose M here: the
331	  module will be called ib700wdt.
332
333	  Most people will say N.
334
335config IBMASR
336	tristate "IBM Automatic Server Restart"
337	depends on X86
338	help
339	  This is the driver for the IBM Automatic Server Restart watchdog
340	  timer built-in into some eServer xSeries machines.
341
342	  To compile this driver as a module, choose M here: the
343	  module will be called ibmasr.
344
345config WAFER_WDT
346	tristate "ICP Single Board Computer Watchdog Timer"
347	depends on X86
348	help
349	  This is a driver for the hardware watchdog on the ICP Single
350	  Board Computer. This driver is working on (at least) the following
351	  IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
352
353	  To compile this driver as a module, choose M here: the
354	  module will be called wafer5823wdt.
355
356config I6300ESB_WDT
357	tristate "Intel 6300ESB Timer/Watchdog"
358	depends on X86 && PCI
359	---help---
360	  Hardware driver for the watchdog timer built into the Intel
361	  6300ESB controller hub.
362
363	  To compile this driver as a module, choose M here: the
364	  module will be called i6300esb.
365
366config ITCO_WDT
367	tristate "Intel TCO Timer/Watchdog"
368	depends on (X86 || IA64) && PCI
369	---help---
370	  Hardware driver for the intel TCO timer based watchdog devices.
371	  These drivers are included in the Intel 82801 I/O Controller
372	  Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
373	  controller hub.
374
375	  The TCO (Total Cost of Ownership) timer is a watchdog timer
376	  that will reboot the machine after its second expiration. The
377	  expiration time can be configured with the "heartbeat" parameter.
378
379	  On some motherboards the driver may fail to reset the chipset's
380	  NO_REBOOT flag which prevents the watchdog from rebooting the
381	  machine. If this is the case you will get a kernel message like
382	  "failed to reset NO_REBOOT flag, reboot disabled by hardware".
383
384	  To compile this driver as a module, choose M here: the
385	  module will be called iTCO_wdt.
386
387config ITCO_VENDOR_SUPPORT
388	bool "Intel TCO Timer/Watchdog Specific Vendor Support"
389	depends on ITCO_WDT
390	---help---
391	  Add vendor specific support to the intel TCO timer based watchdog
392	  devices. At this moment we only have additional support for some
393	  SuperMicro Inc. motherboards.
394
395config SC1200_WDT
396	tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
397	depends on X86
398	help
399	  This is a driver for National Semiconductor PC87307/PC97307 hardware
400	  watchdog cards as found on the SC1200. This watchdog is mainly used
401	  for power management purposes and can be used to power down the device
402	  during inactivity periods (includes interrupt activity monitoring).
403
404	  To compile this driver as a module, choose M here: the
405	  module will be called sc1200wdt.
406
407	  Most people will say N.
408
409config SCx200_WDT
410	tristate "National Semiconductor SCx200 Watchdog"
411	depends on SCx200 && PCI
412	help
413	  Enable the built-in watchdog timer support on the National
414	  Semiconductor SCx200 processors.
415
416	  If compiled as a module, it will be called scx200_wdt.
417
418config PC87413_WDT
419	tristate "NS PC87413 watchdog"
420	depends on X86
421	---help---
422	  This is the driver for the hardware watchdog on the PC87413 chipset
423	  This watchdog simply watches your kernel to make sure it doesn't
424	  freeze, and if it does, it reboots your computer after a certain
425	  amount of time.
426
427	  To compile this driver as a module, choose M here: the
428	  module will be called pc87413_wdt.
429
430	  Most people will say N.
431
432config 60XX_WDT
433	tristate "SBC-60XX Watchdog Timer"
434	depends on X86
435	help
436	  This driver can be used with the watchdog timer found on some
437	  single board computers, namely the 6010 PII based computer.
438	  It may well work with other cards.  It reads port 0x443 to enable
439	  and re-set the watchdog timer, and reads port 0x45 to disable
440	  the watchdog.  If you have a card that behave in similar ways,
441	  you can probably make this driver work with your card as well.
442
443	  You can compile this driver directly into the kernel, or use
444	  it as a module.  The module will be called sbc60xxwdt.
445
446config SBC8360_WDT
447	tristate "SBC8360 Watchdog Timer"
448	depends on X86
449	---help---
450
451	  This is the driver for the hardware watchdog on the SBC8360 Single
452	  Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
453
454	  To compile this driver as a module, choose M here: the
455	  module will be called sbc8360.ko.
456
457	  Most people will say N.
458
459config CPU5_WDT
460	tristate "SMA CPU5 Watchdog"
461	depends on X86
462	---help---
463	  TBD.
464	  To compile this driver as a module, choose M here: the
465	  module will be called cpu5wdt.
466
467config SMSC37B787_WDT
468	tristate "Winbond SMsC37B787 Watchdog Timer"
469	depends on X86
470	---help---
471	  This is the driver for the hardware watchdog component on the
472	  Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
473	  from Vision Systems and maybe others.
474
475	  This watchdog simply watches your kernel to make sure it doesn't
476	  freeze, and if it does, it reboots your computer after a certain
477	  amount of time.
478
479	  Usually a userspace daemon will notify the kernel WDT driver that
480	  userspace is still alive, at regular intervals.
481
482	  To compile this driver as a module, choose M here: the
483	  module will be called smsc37b787_wdt.
484
485	  Most people will say N.
486
487config W83627HF_WDT
488	tristate "W83627HF Watchdog Timer"
489	depends on X86
490	---help---
491	  This is the driver for the hardware watchdog on the W83627HF chipset
492	  as used in Advantech PC-9578 and Tyan S2721-533 motherboards
493	  (and likely others).  This watchdog simply watches your kernel to
494	  make sure it doesn't freeze, and if it does, it reboots your computer
495	  after a certain amount of time.
496
497	  To compile this driver as a module, choose M here: the
498	  module will be called w83627hf_wdt.
499
500	  Most people will say N.
501
502config W83697HF_WDT
503	tristate "W83697HF/W83697HG Watchdog Timer"
504	depends on X86
505	---help---
506	  This is the driver for the hardware watchdog on the W83697HF/HG
507	  chipset as used in Dedibox/VIA motherboards (and likely others).
508	  This watchdog simply watches your kernel to make sure it doesn't
509	  freeze, and if it does, it reboots your computer after a certain
510	  amount of time.
511
512	  To compile this driver as a module, choose M here: the
513	  module will be called w83697hf_wdt.
514
515	  Most people will say N.
516
517config W83877F_WDT
518	tristate "W83877F (EMACS) Watchdog Timer"
519	depends on X86
520	---help---
521	  This is the driver for the hardware watchdog on the W83877F chipset
522	  as used in EMACS PC-104 motherboards (and likely others).  This
523	  watchdog simply watches your kernel to make sure it doesn't freeze,
524	  and if it does, it reboots your computer after a certain amount of
525	  time.
526
527	  To compile this driver as a module, choose M here: the
528	  module will be called w83877f_wdt.
529
530	  Most people will say N.
531
532config W83977F_WDT
533	tristate "W83977F (PCM-5335) Watchdog Timer"
534	depends on X86
535	---help---
536	  This is the driver for the hardware watchdog on the W83977F I/O chip
537	  as used in AAEON's PCM-5335 SBC (and likely others).  This
538	  watchdog simply watches your kernel to make sure it doesn't freeze,
539	  and if it does, it reboots your computer after a certain amount of
540	  time.
541
542	  To compile this driver as a module, choose M here: the
543	  module will be called w83977f_wdt.
544
545config MACHZ_WDT
546	tristate "ZF MachZ Watchdog"
547	depends on X86
548	---help---
549	  If you are using a ZF Micro MachZ processor, say Y here, otherwise
550	  N.  This is the driver for the watchdog timer built-in on that
551	  processor using ZF-Logic interface.  This watchdog simply watches
552	  your kernel to make sure it doesn't freeze, and if it does, it
553	  reboots your computer after a certain amount of time.
554
555	  To compile this driver as a module, choose M here: the
556	  module will be called machzwd.
557
558config SBC_EPX_C3_WATCHDOG
559	tristate "Winsystems SBC EPX-C3 watchdog"
560	depends on X86
561	---help---
562	  This is the driver for the built-in watchdog timer on the EPX-C3
563	  Single-board computer made by Winsystems, Inc.
564
565	  *Note*: This hardware watchdog is not probeable and thus there
566	  is no way to know if writing to its IO address will corrupt
567	  your system or have any real effect.  The only way to be sure
568	  that this driver does what you want is to make sure you
569	  are running it on an EPX-C3 from Winsystems with the watchdog
570	  timer at IO address 0x1ee and 0x1ef.  It will write to both those
571	  IO ports.  Basically, the assumption is made that if you compile
572	  this driver into your kernel and/or load it as a module, that you
573	  know what you are doing and that you are in fact running on an
574	  EPX-C3 board!
575
576	  To compile this driver as a module, choose M here: the
577	  module will be called sbc_epx_c3.
578
579# M32R Architecture
580
581# M68K Architecture
582
583# M68KNOMMU Architecture
584
585# MIPS Architecture
586
587config INDYDOG
588	tristate "Indy/I2 Hardware Watchdog"
589	depends on SGI_IP22
590	help
591	  Hardware driver for the Indy's/I2's watchdog. This is a
592	  watchdog timer that will reboot the machine after a 60 second
593	  timer expired and no process has written to /dev/watchdog during
594	  that time.
595
596config WDT_MTX1
597	tristate "MTX-1 Hardware Watchdog"
598	depends on MIPS_MTX1
599	help
600	  Hardware driver for the MTX-1 boards. This is a watchdog timer that
601	  will reboot the machine after a 100 seconds timer expired.
602
603config WDT_RM9K_GPI
604	tristate "RM9000/GPI hardware watchdog"
605	depends on CPU_RM9000
606	help
607	  Watchdog implementation using the GPI hardware found on
608	  PMC-Sierra RM9xxx CPUs.
609
610	  To compile this driver as a module, choose M here: the
611	  module will be called rm9k_wdt.
612
613config AR7_WDT
614	tristate "TI AR7 Watchdog Timer"
615	depends on AR7
616	help
617	  Hardware driver for the TI AR7 Watchdog Timer.
618
619# PARISC Architecture
620
621# POWERPC Architecture
622
623config MPC5200_WDT
624	tristate "MPC5200 Watchdog Timer"
625	depends on PPC_MPC52xx
626
627config 8xx_WDT
628	tristate "MPC8xx Watchdog Timer"
629	depends on 8xx
630
631config 83xx_WDT
632	tristate "MPC83xx Watchdog Timer"
633	depends on PPC_83xx
634
635config MV64X60_WDT
636	tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
637	depends on MV64X60
638
639config BOOKE_WDT
640	bool "PowerPC Book-E Watchdog Timer"
641	depends on BOOKE || 4xx
642	---help---
643	  Please see Documentation/watchdog/watchdog-api.txt for
644	  more information.
645
646# PPC64 Architecture
647
648config WATCHDOG_RTAS
649	tristate "RTAS watchdog"
650	depends on PPC_RTAS
651	help
652	  This driver adds watchdog support for the RTAS watchdog.
653
654	  To compile this driver as a module, choose M here. The module
655	  will be called wdrtas.
656
657# S390 Architecture
658
659config ZVM_WATCHDOG
660	tristate "z/VM Watchdog Timer"
661	depends on S390
662	help
663	  IBM s/390 and zSeries machines running under z/VM 5.1 or later
664	  provide a virtual watchdog timer to their guest that cause a
665	  user define Control Program command to be executed after a
666	  timeout.
667
668	  To compile this driver as a module, choose M here. The module
669	  will be called vmwatchdog.
670
671# SUPERH (sh + sh64) Architecture
672
673config SH_WDT
674	tristate "SuperH Watchdog"
675	depends on SUPERH && (CPU_SH3 || CPU_SH4)
676	help
677	  This driver adds watchdog support for the integrated watchdog in the
678	  SuperH processors. If you have one of these processors and wish
679	  to have watchdog support enabled, say Y, otherwise say N.
680
681	  As a side note, saying Y here will automatically boost HZ to 1000
682	  so that the timer has a chance to clear the overflow counter. On
683	  slower systems (such as the SH-2 and SH-3) this will likely yield
684	  some performance issues. As such, the WDT should be avoided here
685	  unless it is absolutely necessary.
686
687	  To compile this driver as a module, choose M here: the
688	  module will be called shwdt.
689
690config SH_WDT_MMAP
691	bool "Allow mmap of SH WDT"
692	default n
693	depends on SH_WDT
694	help
695	  If you say Y here, user applications will be able to mmap the
696	  WDT/CPG registers.
697
698# SPARC Architecture
699
700# SPARC64 Architecture
701
702config WATCHDOG_CP1XXX
703	tristate "CP1XXX Hardware Watchdog support"
704	depends on SPARC64 && PCI
705	---help---
706	  This is the driver for the hardware watchdog timers present on
707	  Sun Microsystems CompactPCI models CP1400 and CP1500.
708
709	  To compile this driver as a module, choose M here: the
710	  module will be called cpwatchdog.
711
712	  If you do not have a CompactPCI model CP1400 or CP1500, or
713	  another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
714	  you should say N to this option.
715
716config WATCHDOG_RIO
717	tristate "RIO Hardware Watchdog support"
718	depends on SPARC64 && PCI
719	help
720	  Say Y here to support the hardware watchdog capability on Sun RIO
721	  machines.  The watchdog timeout period is normally one minute but
722	  can be changed with a boot-time parameter.
723
724# V850 Architecture
725
726# XTENSA Architecture
727
728#
729# ISA-based Watchdog Cards
730#
731
732comment "ISA-based Watchdog Cards"
733	depends on ISA
734
735config PCWATCHDOG
736	tristate "Berkshire Products ISA-PC Watchdog"
737	depends on ISA
738	---help---
739	  This is the driver for the Berkshire Products ISA-PC Watchdog card.
740	  This card simply watches your kernel to make sure it doesn't freeze,
741	  and if it does, it reboots your computer after a certain amount of
742	  time. This driver is like the WDT501 driver but for different
743	  hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
744	  watchdog cards can be ordered from <http://www.berkprod.com/>.
745
746	  To compile this driver as a module, choose M here: the
747	  module will be called pcwd.
748
749	  Most people will say N.
750
751config MIXCOMWD
752	tristate "Mixcom Watchdog"
753	depends on ISA
754	---help---
755	  This is a driver for the Mixcom hardware watchdog cards.  This
756	  watchdog simply watches your kernel to make sure it doesn't freeze,
757	  and if it does, it reboots your computer after a certain amount of
758	  time.
759
760	  To compile this driver as a module, choose M here: the
761	  module will be called mixcomwd.
762
763	  Most people will say N.
764
765config WDT
766	tristate "WDT Watchdog timer"
767	depends on ISA
768	---help---
769	  If you have a WDT500P or WDT501P watchdog board, say Y here,
770	  otherwise N. It is not possible to probe for this board, which means
771	  that you have to inform the kernel about the IO port and IRQ that
772	  is needed (you can do this via the io and irq parameters)
773
774	  To compile this driver as a module, choose M here: the
775	  module will be called wdt.
776
777config WDT_501
778	bool "WDT501 features"
779	depends on WDT
780	help
781	  Saying Y here and creating a character special file /dev/temperature
782	  with major number 10 and minor number 131 ("man mknod") will give
783	  you a thermometer inside your computer: reading from
784	  /dev/temperature yields one byte, the temperature in degrees
785	  Fahrenheit. This works only if you have a WDT501P watchdog board
786	  installed.
787
788	  If you want to enable the Fan Tachometer on the WDT501P, then you
789	  can do this via the tachometer parameter. Only do this if you have a
790	  fan tachometer actually set up.
791
792#
793# PCI-based Watchdog Cards
794#
795
796comment "PCI-based Watchdog Cards"
797	depends on PCI
798
799config PCIPCWATCHDOG
800	tristate "Berkshire Products PCI-PC Watchdog"
801	depends on PCI
802	---help---
803	  This is the driver for the Berkshire Products PCI-PC Watchdog card.
804	  This card simply watches your kernel to make sure it doesn't freeze,
805	  and if it does, it reboots your computer after a certain amount of
806	  time. The card can also monitor the internal temperature of the PC.
807	  More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
808
809	  To compile this driver as a module, choose M here: the
810	  module will be called pcwd_pci.
811
812	  Most people will say N.
813
814config WDTPCI
815	tristate "PCI-WDT500/501 Watchdog timer"
816	depends on PCI
817	---help---
818	  If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
819
820	  To compile this driver as a module, choose M here: the
821	  module will be called wdt_pci.
822
823config WDT_501_PCI
824	bool "PCI-WDT501 features"
825	depends on WDTPCI
826	help
827	  Saying Y here and creating a character special file /dev/temperature
828	  with major number 10 and minor number 131 ("man mknod") will give
829	  you a thermometer inside your computer: reading from
830	  /dev/temperature yields one byte, the temperature in degrees
831	  Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
832	  installed.
833
834	  If you want to enable the Fan Tachometer on the PCI-WDT501, then you
835	  can do this via the tachometer parameter. Only do this if you have a
836	  fan tachometer actually set up.
837
838#
839# USB-based Watchdog Cards
840#
841
842comment "USB-based Watchdog Cards"
843	depends on USB
844
845config USBPCWATCHDOG
846	tristate "Berkshire Products USB-PC Watchdog"
847	depends on USB
848	---help---
849	  This is the driver for the Berkshire Products USB-PC Watchdog card.
850	  This card simply watches your kernel to make sure it doesn't freeze,
851	  and if it does, it reboots your computer after a certain amount of
852	  time. The card can also monitor the internal temperature of the PC.
853	  More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
854
855	  To compile this driver as a module, choose M here: the
856	  module will be called pcwd_usb.
857
858	  Most people will say N.
859
860endif # WATCHDOG
861