diff options
author | Wim Van Sebroeck <wim@iguana.be> | 2007-08-17 04:38:02 -0400 |
---|---|---|
committer | Wim Van Sebroeck <wim@iguana.be> | 2007-10-18 06:39:03 -0400 |
commit | b7e04f8c61a46d742de23af5d7ca2b41b33e40ac (patch) | |
tree | c52a7ea568648e2d8ed0d423098b42298de2058b /drivers/char/watchdog/Kconfig | |
parent | d85714d81cc0408daddb68c10f7fd69eafe7c213 (diff) |
mv watchdog tree under drivers
move watchdog tree from drivers/char/watchdog to drivers/watchdog.
Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Diffstat (limited to 'drivers/char/watchdog/Kconfig')
-rw-r--r-- | drivers/char/watchdog/Kconfig | 853 |
1 files changed, 0 insertions, 853 deletions
diff --git a/drivers/char/watchdog/Kconfig b/drivers/char/watchdog/Kconfig deleted file mode 100644 index 37bddc1802de..000000000000 --- a/drivers/char/watchdog/Kconfig +++ /dev/null | |||
@@ -1,853 +0,0 @@ | |||
1 | # | ||
2 | # Watchdog device configuration | ||
3 | # | ||
4 | |||
5 | menuconfig 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 <file:Documentation/watchdog/watchdog.txt> | ||
19 | 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 | |||
29 | if WATCHDOG | ||
30 | |||
31 | config 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 | |||
44 | comment "Watchdog Device Drivers" | ||
45 | |||
46 | # Architecture Independent | ||
47 | |||
48 | config 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 | |||
62 | config 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 | |||
69 | config 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 | |||
83 | config 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 | |||
93 | config 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 | |||
104 | config 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 | |||
120 | config 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 | |||
127 | config 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 | |||
143 | config 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 | |||
155 | config 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 | |||
164 | config 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 | |||
174 | config 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 | |||
181 | config 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 | |||
192 | config 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 | |||
208 | config 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 | |||
224 | config 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 | |||
233 | config 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 | |||
252 | config 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 | |||
266 | config 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 | |||
275 | config 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 | |||
286 | config 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 | |||
298 | config 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 | |||
311 | config 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 | |||
319 | config 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 | |||
335 | config 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 | |||
345 | config WAFER_WDT | ||
346 | tristate "ICP Wafer 5823 Single Board Computer Watchdog" | ||
347 | depends on X86 | ||
348 | help | ||
349 | This is a driver for the hardware watchdog on the ICP Wafer 5823 | ||
350 | Single Board Computer (and probably other similar models). | ||
351 | |||
352 | To compile this driver as a module, choose M here: the | ||
353 | module will be called wafer5823wdt. | ||
354 | |||
355 | config I6300ESB_WDT | ||
356 | tristate "Intel 6300ESB Timer/Watchdog" | ||
357 | depends on X86 && PCI | ||
358 | ---help--- | ||
359 | Hardware driver for the watchdog timer built into the Intel | ||
360 | 6300ESB controller hub. | ||
361 | |||
362 | To compile this driver as a module, choose M here: the | ||
363 | module will be called i6300esb. | ||
364 | |||
365 | config ITCO_WDT | ||
366 | tristate "Intel TCO Timer/Watchdog" | ||
367 | depends on (X86 || IA64) && PCI | ||
368 | ---help--- | ||
369 | Hardware driver for the intel TCO timer based watchdog devices. | ||
370 | These drivers are included in the Intel 82801 I/O Controller | ||
371 | Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB | ||
372 | controller hub. | ||
373 | |||
374 | The TCO (Total Cost of Ownership) timer is a watchdog timer | ||
375 | that will reboot the machine after its second expiration. The | ||
376 | expiration time can be configured with the "heartbeat" parameter. | ||
377 | |||
378 | On some motherboards the driver may fail to reset the chipset's | ||
379 | NO_REBOOT flag which prevents the watchdog from rebooting the | ||
380 | machine. If this is the case you will get a kernel message like | ||
381 | "failed to reset NO_REBOOT flag, reboot disabled by hardware". | ||
382 | |||
383 | To compile this driver as a module, choose M here: the | ||
384 | module will be called iTCO_wdt. | ||
385 | |||
386 | config ITCO_VENDOR_SUPPORT | ||
387 | bool "Intel TCO Timer/Watchdog Specific Vendor Support" | ||
388 | depends on ITCO_WDT | ||
389 | ---help--- | ||
390 | Add vendor specific support to the intel TCO timer based watchdog | ||
391 | devices. At this moment we only have additional support for some | ||
392 | SuperMicro Inc. motherboards. | ||
393 | |||
394 | config SC1200_WDT | ||
395 | tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" | ||
396 | depends on X86 | ||
397 | help | ||
398 | This is a driver for National Semiconductor PC87307/PC97307 hardware | ||
399 | watchdog cards as found on the SC1200. This watchdog is mainly used | ||
400 | for power management purposes and can be used to power down the device | ||
401 | during inactivity periods (includes interrupt activity monitoring). | ||
402 | |||
403 | To compile this driver as a module, choose M here: the | ||
404 | module will be called sc1200wdt. | ||
405 | |||
406 | Most people will say N. | ||
407 | |||
408 | config SCx200_WDT | ||
409 | tristate "National Semiconductor SCx200 Watchdog" | ||
410 | depends on SCx200 && PCI | ||
411 | help | ||
412 | Enable the built-in watchdog timer support on the National | ||
413 | Semiconductor SCx200 processors. | ||
414 | |||
415 | If compiled as a module, it will be called scx200_wdt. | ||
416 | |||
417 | config PC87413_WDT | ||
418 | tristate "NS PC87413 watchdog" | ||
419 | depends on X86 | ||
420 | ---help--- | ||
421 | This is the driver for the hardware watchdog on the PC87413 chipset | ||
422 | This watchdog simply watches your kernel to make sure it doesn't | ||
423 | freeze, and if it does, it reboots your computer after a certain | ||
424 | amount of time. | ||
425 | |||
426 | To compile this driver as a module, choose M here: the | ||
427 | module will be called pc87413_wdt. | ||
428 | |||
429 | Most people will say N. | ||
430 | |||
431 | config 60XX_WDT | ||
432 | tristate "SBC-60XX Watchdog Timer" | ||
433 | depends on X86 | ||
434 | help | ||
435 | This driver can be used with the watchdog timer found on some | ||
436 | single board computers, namely the 6010 PII based computer. | ||
437 | It may well work with other cards. It reads port 0x443 to enable | ||
438 | and re-set the watchdog timer, and reads port 0x45 to disable | ||
439 | the watchdog. If you have a card that behave in similar ways, | ||
440 | you can probably make this driver work with your card as well. | ||
441 | |||
442 | You can compile this driver directly into the kernel, or use | ||
443 | it as a module. The module will be called sbc60xxwdt. | ||
444 | |||
445 | config SBC8360_WDT | ||
446 | tristate "SBC8360 Watchdog Timer" | ||
447 | depends on X86 | ||
448 | ---help--- | ||
449 | |||
450 | This is the driver for the hardware watchdog on the SBC8360 Single | ||
451 | Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). | ||
452 | |||
453 | To compile this driver as a module, choose M here: the | ||
454 | module will be called sbc8360.ko. | ||
455 | |||
456 | Most people will say N. | ||
457 | |||
458 | config CPU5_WDT | ||
459 | tristate "SMA CPU5 Watchdog" | ||
460 | depends on X86 | ||
461 | ---help--- | ||
462 | TBD. | ||
463 | To compile this driver as a module, choose M here: the | ||
464 | module will be called cpu5wdt. | ||
465 | |||
466 | config SMSC37B787_WDT | ||
467 | tristate "Winbond SMsC37B787 Watchdog Timer" | ||
468 | depends on X86 | ||
469 | ---help--- | ||
470 | This is the driver for the hardware watchdog component on the | ||
471 | Winbond SMsC37B787 chipset as used on the NetRunner Mainboard | ||
472 | from Vision Systems and maybe others. | ||
473 | |||
474 | This watchdog simply watches your kernel to make sure it doesn't | ||
475 | freeze, and if it does, it reboots your computer after a certain | ||
476 | amount of time. | ||
477 | |||
478 | Usually a userspace daemon will notify the kernel WDT driver that | ||
479 | userspace is still alive, at regular intervals. | ||
480 | |||
481 | To compile this driver as a module, choose M here: the | ||
482 | module will be called smsc37b787_wdt. | ||
483 | |||
484 | Most people will say N. | ||
485 | |||
486 | config W83627HF_WDT | ||
487 | tristate "W83627HF Watchdog Timer" | ||
488 | depends on X86 | ||
489 | ---help--- | ||
490 | This is the driver for the hardware watchdog on the W83627HF chipset | ||
491 | as used in Advantech PC-9578 and Tyan S2721-533 motherboards | ||
492 | (and likely others). This watchdog simply watches your kernel to | ||
493 | make sure it doesn't freeze, and if it does, it reboots your computer | ||
494 | after a certain amount of time. | ||
495 | |||
496 | To compile this driver as a module, choose M here: the | ||
497 | module will be called w83627hf_wdt. | ||
498 | |||
499 | Most people will say N. | ||
500 | |||
501 | config W83697HF_WDT | ||
502 | tristate "W83697HF/W83697HG Watchdog Timer" | ||
503 | depends on X86 | ||
504 | ---help--- | ||
505 | This is the driver for the hardware watchdog on the W83697HF/HG | ||
506 | chipset as used in Dedibox/VIA motherboards (and likely others). | ||
507 | This watchdog simply watches your kernel to make sure it doesn't | ||
508 | freeze, and if it does, it reboots your computer after a certain | ||
509 | amount of time. | ||
510 | |||
511 | To compile this driver as a module, choose M here: the | ||
512 | module will be called w83697hf_wdt. | ||
513 | |||
514 | Most people will say N. | ||
515 | |||
516 | config W83877F_WDT | ||
517 | tristate "W83877F (EMACS) Watchdog Timer" | ||
518 | depends on X86 | ||
519 | ---help--- | ||
520 | This is the driver for the hardware watchdog on the W83877F chipset | ||
521 | as used in EMACS PC-104 motherboards (and likely others). This | ||
522 | watchdog simply watches your kernel to make sure it doesn't freeze, | ||
523 | and if it does, it reboots your computer after a certain amount of | ||
524 | time. | ||
525 | |||
526 | To compile this driver as a module, choose M here: the | ||
527 | module will be called w83877f_wdt. | ||
528 | |||
529 | Most people will say N. | ||
530 | |||
531 | config W83977F_WDT | ||
532 | tristate "W83977F (PCM-5335) Watchdog Timer" | ||
533 | depends on X86 | ||
534 | ---help--- | ||
535 | This is the driver for the hardware watchdog on the W83977F I/O chip | ||
536 | as used in AAEON's PCM-5335 SBC (and likely others). This | ||
537 | watchdog simply watches your kernel to make sure it doesn't freeze, | ||
538 | and if it does, it reboots your computer after a certain amount of | ||
539 | time. | ||
540 | |||
541 | To compile this driver as a module, choose M here: the | ||
542 | module will be called w83977f_wdt. | ||
543 | |||
544 | config MACHZ_WDT | ||
545 | tristate "ZF MachZ Watchdog" | ||
546 | depends on X86 | ||
547 | ---help--- | ||
548 | If you are using a ZF Micro MachZ processor, say Y here, otherwise | ||
549 | N. This is the driver for the watchdog timer built-in on that | ||
550 | processor using ZF-Logic interface. This watchdog simply watches | ||
551 | your kernel to make sure it doesn't freeze, and if it does, it | ||
552 | reboots your computer after a certain amount of time. | ||
553 | |||
554 | To compile this driver as a module, choose M here: the | ||
555 | module will be called machzwd. | ||
556 | |||
557 | config SBC_EPX_C3_WATCHDOG | ||
558 | tristate "Winsystems SBC EPX-C3 watchdog" | ||
559 | depends on X86 | ||
560 | ---help--- | ||
561 | This is the driver for the built-in watchdog timer on the EPX-C3 | ||
562 | Single-board computer made by Winsystems, Inc. | ||
563 | |||
564 | *Note*: This hardware watchdog is not probeable and thus there | ||
565 | is no way to know if writing to its IO address will corrupt | ||
566 | your system or have any real effect. The only way to be sure | ||
567 | that this driver does what you want is to make sure you | ||
568 | are running it on an EPX-C3 from Winsystems with the watchdog | ||
569 | timer at IO address 0x1ee and 0x1ef. It will write to both those | ||
570 | IO ports. Basically, the assumption is made that if you compile | ||
571 | this driver into your kernel and/or load it as a module, that you | ||
572 | know what you are doing and that you are in fact running on an | ||
573 | EPX-C3 board! | ||
574 | |||
575 | To compile this driver as a module, choose M here: the | ||
576 | module will be called sbc_epx_c3. | ||
577 | |||
578 | # M32R Architecture | ||
579 | |||
580 | # M68K Architecture | ||
581 | |||
582 | # M68KNOMMU Architecture | ||
583 | |||
584 | # MIPS Architecture | ||
585 | |||
586 | config INDYDOG | ||
587 | tristate "Indy/I2 Hardware Watchdog" | ||
588 | depends on SGI_IP22 | ||
589 | help | ||
590 | Hardware driver for the Indy's/I2's watchdog. This is a | ||
591 | watchdog timer that will reboot the machine after a 60 second | ||
592 | timer expired and no process has written to /dev/watchdog during | ||
593 | that time. | ||
594 | |||
595 | config WDT_MTX1 | ||
596 | tristate "MTX-1 Hardware Watchdog" | ||
597 | depends on MIPS_MTX1 | ||
598 | help | ||
599 | Hardware driver for the MTX-1 boards. This is a watchdog timer that | ||
600 | will reboot the machine after a 100 seconds timer expired. | ||
601 | |||
602 | config WDT_RM9K_GPI | ||
603 | tristate "RM9000/GPI hardware watchdog" | ||
604 | depends on CPU_RM9000 | ||
605 | help | ||
606 | Watchdog implementation using the GPI hardware found on | ||
607 | PMC-Sierra RM9xxx CPUs. | ||
608 | |||
609 | To compile this driver as a module, choose M here: the | ||
610 | module will be called rm9k_wdt. | ||
611 | |||
612 | # PARISC Architecture | ||
613 | |||
614 | # POWERPC Architecture | ||
615 | |||
616 | config MPC5200_WDT | ||
617 | tristate "MPC5200 Watchdog Timer" | ||
618 | depends on PPC_MPC52xx | ||
619 | |||
620 | config 8xx_WDT | ||
621 | tristate "MPC8xx Watchdog Timer" | ||
622 | depends on 8xx | ||
623 | |||
624 | config 83xx_WDT | ||
625 | tristate "MPC83xx Watchdog Timer" | ||
626 | depends on PPC_83xx | ||
627 | |||
628 | config MV64X60_WDT | ||
629 | tristate "MV64X60 (Marvell Discovery) Watchdog Timer" | ||
630 | depends on MV64X60 | ||
631 | |||
632 | config BOOKE_WDT | ||
633 | bool "PowerPC Book-E Watchdog Timer" | ||
634 | depends on BOOKE || 4xx | ||
635 | ---help--- | ||
636 | Please see Documentation/watchdog/watchdog-api.txt for | ||
637 | more information. | ||
638 | |||
639 | # PPC64 Architecture | ||
640 | |||
641 | config WATCHDOG_RTAS | ||
642 | tristate "RTAS watchdog" | ||
643 | depends on PPC_RTAS | ||
644 | help | ||
645 | This driver adds watchdog support for the RTAS watchdog. | ||
646 | |||
647 | To compile this driver as a module, choose M here. The module | ||
648 | will be called wdrtas. | ||
649 | |||
650 | # S390 Architecture | ||
651 | |||
652 | config ZVM_WATCHDOG | ||
653 | tristate "z/VM Watchdog Timer" | ||
654 | depends on S390 | ||
655 | help | ||
656 | IBM s/390 and zSeries machines running under z/VM 5.1 or later | ||
657 | provide a virtual watchdog timer to their guest that cause a | ||
658 | user define Control Program command to be executed after a | ||
659 | timeout. | ||
660 | |||
661 | To compile this driver as a module, choose M here. The module | ||
662 | will be called vmwatchdog. | ||
663 | |||
664 | # SUPERH (sh + sh64) Architecture | ||
665 | |||
666 | config SH_WDT | ||
667 | tristate "SuperH Watchdog" | ||
668 | depends on SUPERH && (CPU_SH3 || CPU_SH4) | ||
669 | help | ||
670 | This driver adds watchdog support for the integrated watchdog in the | ||
671 | SuperH processors. If you have one of these processors and wish | ||
672 | to have watchdog support enabled, say Y, otherwise say N. | ||
673 | |||
674 | As a side note, saying Y here will automatically boost HZ to 1000 | ||
675 | so that the timer has a chance to clear the overflow counter. On | ||
676 | slower systems (such as the SH-2 and SH-3) this will likely yield | ||
677 | some performance issues. As such, the WDT should be avoided here | ||
678 | unless it is absolutely necessary. | ||
679 | |||
680 | To compile this driver as a module, choose M here: the | ||
681 | module will be called shwdt. | ||
682 | |||
683 | config SH_WDT_MMAP | ||
684 | bool "Allow mmap of SH WDT" | ||
685 | default n | ||
686 | depends on SH_WDT | ||
687 | help | ||
688 | If you say Y here, user applications will be able to mmap the | ||
689 | WDT/CPG registers. | ||
690 | |||
691 | # SPARC Architecture | ||
692 | |||
693 | # SPARC64 Architecture | ||
694 | |||
695 | config WATCHDOG_CP1XXX | ||
696 | tristate "CP1XXX Hardware Watchdog support" | ||
697 | depends on SPARC64 && PCI | ||
698 | ---help--- | ||
699 | This is the driver for the hardware watchdog timers present on | ||
700 | Sun Microsystems CompactPCI models CP1400 and CP1500. | ||
701 | |||
702 | To compile this driver as a module, choose M here: the | ||
703 | module will be called cpwatchdog. | ||
704 | |||
705 | If you do not have a CompactPCI model CP1400 or CP1500, or | ||
706 | another UltraSPARC-IIi-cEngine boardset with hardware watchdog, | ||
707 | you should say N to this option. | ||
708 | |||
709 | config WATCHDOG_RIO | ||
710 | tristate "RIO Hardware Watchdog support" | ||
711 | depends on SPARC64 && PCI | ||
712 | help | ||
713 | Say Y here to support the hardware watchdog capability on Sun RIO | ||
714 | machines. The watchdog timeout period is normally one minute but | ||
715 | can be changed with a boot-time parameter. | ||
716 | |||
717 | # V850 Architecture | ||
718 | |||
719 | # XTENSA Architecture | ||
720 | |||
721 | # | ||
722 | # ISA-based Watchdog Cards | ||
723 | # | ||
724 | |||
725 | comment "ISA-based Watchdog Cards" | ||
726 | depends on ISA | ||
727 | |||
728 | config PCWATCHDOG | ||
729 | tristate "Berkshire Products ISA-PC Watchdog" | ||
730 | depends on ISA | ||
731 | ---help--- | ||
732 | This is the driver for the Berkshire Products ISA-PC Watchdog card. | ||
733 | This card simply watches your kernel to make sure it doesn't freeze, | ||
734 | and if it does, it reboots your computer after a certain amount of | ||
735 | time. This driver is like the WDT501 driver but for different | ||
736 | hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC | ||
737 | watchdog cards can be ordered from <http://www.berkprod.com/>. | ||
738 | |||
739 | To compile this driver as a module, choose M here: the | ||
740 | module will be called pcwd. | ||
741 | |||
742 | Most people will say N. | ||
743 | |||
744 | config MIXCOMWD | ||
745 | tristate "Mixcom Watchdog" | ||
746 | depends on ISA | ||
747 | ---help--- | ||
748 | This is a driver for the Mixcom hardware watchdog cards. This | ||
749 | watchdog simply watches your kernel to make sure it doesn't freeze, | ||
750 | and if it does, it reboots your computer after a certain amount of | ||
751 | time. | ||
752 | |||
753 | To compile this driver as a module, choose M here: the | ||
754 | module will be called mixcomwd. | ||
755 | |||
756 | Most people will say N. | ||
757 | |||
758 | config WDT | ||
759 | tristate "WDT Watchdog timer" | ||
760 | depends on ISA | ||
761 | ---help--- | ||
762 | If you have a WDT500P or WDT501P watchdog board, say Y here, | ||
763 | otherwise N. It is not possible to probe for this board, which means | ||
764 | that you have to inform the kernel about the IO port and IRQ that | ||
765 | is needed (you can do this via the io and irq parameters) | ||
766 | |||
767 | To compile this driver as a module, choose M here: the | ||
768 | module will be called wdt. | ||
769 | |||
770 | config WDT_501 | ||
771 | bool "WDT501 features" | ||
772 | depends on WDT | ||
773 | help | ||
774 | Saying Y here and creating a character special file /dev/temperature | ||
775 | with major number 10 and minor number 131 ("man mknod") will give | ||
776 | you a thermometer inside your computer: reading from | ||
777 | /dev/temperature yields one byte, the temperature in degrees | ||
778 | Fahrenheit. This works only if you have a WDT501P watchdog board | ||
779 | installed. | ||
780 | |||
781 | If you want to enable the Fan Tachometer on the WDT501P, then you | ||
782 | can do this via the tachometer parameter. Only do this if you have a | ||
783 | fan tachometer actually set up. | ||
784 | |||
785 | # | ||
786 | # PCI-based Watchdog Cards | ||
787 | # | ||
788 | |||
789 | comment "PCI-based Watchdog Cards" | ||
790 | depends on PCI | ||
791 | |||
792 | config PCIPCWATCHDOG | ||
793 | tristate "Berkshire Products PCI-PC Watchdog" | ||
794 | depends on PCI | ||
795 | ---help--- | ||
796 | This is the driver for the Berkshire Products PCI-PC Watchdog card. | ||
797 | This card simply watches your kernel to make sure it doesn't freeze, | ||
798 | and if it does, it reboots your computer after a certain amount of | ||
799 | time. The card can also monitor the internal temperature of the PC. | ||
800 | More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>. | ||
801 | |||
802 | To compile this driver as a module, choose M here: the | ||
803 | module will be called pcwd_pci. | ||
804 | |||
805 | Most people will say N. | ||
806 | |||
807 | config WDTPCI | ||
808 | tristate "PCI-WDT500/501 Watchdog timer" | ||
809 | depends on PCI | ||
810 | ---help--- | ||
811 | If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N. | ||
812 | |||
813 | To compile this driver as a module, choose M here: the | ||
814 | module will be called wdt_pci. | ||
815 | |||
816 | config WDT_501_PCI | ||
817 | bool "PCI-WDT501 features" | ||
818 | depends on WDTPCI | ||
819 | help | ||
820 | Saying Y here and creating a character special file /dev/temperature | ||
821 | with major number 10 and minor number 131 ("man mknod") will give | ||
822 | you a thermometer inside your computer: reading from | ||
823 | /dev/temperature yields one byte, the temperature in degrees | ||
824 | Fahrenheit. This works only if you have a PCI-WDT501 watchdog board | ||
825 | installed. | ||
826 | |||
827 | If you want to enable the Fan Tachometer on the PCI-WDT501, then you | ||
828 | can do this via the tachometer parameter. Only do this if you have a | ||
829 | fan tachometer actually set up. | ||
830 | |||
831 | # | ||
832 | # USB-based Watchdog Cards | ||
833 | # | ||
834 | |||
835 | comment "USB-based Watchdog Cards" | ||
836 | depends on USB | ||
837 | |||
838 | config USBPCWATCHDOG | ||
839 | tristate "Berkshire Products USB-PC Watchdog" | ||
840 | depends on USB | ||
841 | ---help--- | ||
842 | This is the driver for the Berkshire Products USB-PC Watchdog card. | ||
843 | This card simply watches your kernel to make sure it doesn't freeze, | ||
844 | and if it does, it reboots your computer after a certain amount of | ||
845 | time. The card can also monitor the internal temperature of the PC. | ||
846 | More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>. | ||
847 | |||
848 | To compile this driver as a module, choose M here: the | ||
849 | module will be called pcwd_usb. | ||
850 | |||
851 | Most people will say N. | ||
852 | |||
853 | endif # WATCHDOG | ||