]>
Commit | Line | Data |
---|---|---|
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 | |
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 | ||
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 | config WM831X_WATCHDOG | |
59 | tristate "WM831x watchdog" | |
60 | depends on MFD_WM831X | |
61 | help | |
62 | Support for the watchdog in the WM831x AudioPlus PMICs. When | |
63 | the watchdog triggers the system will be reset. | |
64 | ||
65 | config WM8350_WATCHDOG | |
66 | tristate "WM8350 watchdog" | |
67 | depends on MFD_WM8350 | |
68 | help | |
69 | Support for the watchdog in the WM8350 AudioPlus PMIC. When | |
70 | the watchdog triggers the system will be reset. | |
71 | ||
72 | # ALPHA Architecture | |
73 | ||
74 | # ARM Architecture | |
75 | ||
76 | config AT91RM9200_WATCHDOG | |
77 | tristate "AT91RM9200 watchdog" | |
78 | depends on ARCH_AT91RM9200 | |
79 | help | |
80 | Watchdog timer embedded into AT91RM9200 chips. This will reboot your | |
81 | system when the timeout is reached. | |
82 | ||
83 | config AT91SAM9X_WATCHDOG | |
84 | tristate "AT91SAM9X / AT91CAP9 watchdog" | |
85 | depends on ARCH_AT91 && !ARCH_AT91RM9200 | |
86 | help | |
87 | Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will | |
88 | reboot your system when the timeout is reached. | |
89 | ||
90 | config 21285_WATCHDOG | |
91 | tristate "DC21285 watchdog" | |
92 | depends on FOOTBRIDGE | |
93 | help | |
94 | The Intel Footbridge chip contains a built-in watchdog circuit. Say Y | |
95 | here if you wish to use this. Alternatively say M to compile the | |
96 | driver as a module, which will be called wdt285. | |
97 | ||
98 | This driver does not work on all machines. In particular, early CATS | |
99 | boards have hardware problems that will cause the machine to simply | |
100 | lock up if the watchdog fires. | |
101 | ||
102 | "If in doubt, leave it out" - say N. | |
103 | ||
104 | config 977_WATCHDOG | |
105 | tristate "NetWinder WB83C977 watchdog" | |
106 | depends on FOOTBRIDGE && ARCH_NETWINDER | |
107 | help | |
108 | Say Y here to include support for the WB977 watchdog included in | |
109 | NetWinder machines. Alternatively say M to compile the driver as | |
110 | a module, which will be called wdt977. | |
111 | ||
112 | Not sure? It's safe to say N. | |
113 | ||
114 | config IXP2000_WATCHDOG | |
115 | tristate "IXP2000 Watchdog" | |
116 | depends on ARCH_IXP2000 | |
117 | help | |
118 | Say Y here if to include support for the watchdog timer | |
119 | in the Intel IXP2000(2400, 2800, 2850) network processors. | |
120 | This driver can be built as a module by choosing M. The module | |
121 | will be called ixp2000_wdt. | |
122 | ||
123 | Say N if you are unsure. | |
124 | ||
125 | config IXP4XX_WATCHDOG | |
126 | tristate "IXP4xx Watchdog" | |
127 | depends on ARCH_IXP4XX | |
128 | help | |
129 | Say Y here if to include support for the watchdog timer | |
130 | in the Intel IXP4xx network processors. This driver can | |
131 | be built as a module by choosing M. The module will | |
132 | be called ixp4xx_wdt. | |
133 | ||
134 | Note: The internal IXP4xx watchdog does a soft CPU reset | |
135 | which doesn't reset any peripherals. There are circumstances | |
136 | where the watchdog will fail to reset the board correctly | |
137 | (e.g., if the boot ROM is in an unreadable state). | |
138 | ||
139 | Say N if you are unsure. | |
140 | ||
141 | config KS8695_WATCHDOG | |
142 | tristate "KS8695 watchdog" | |
143 | depends on ARCH_KS8695 | |
144 | help | |
145 | Watchdog timer embedded into KS8695 processor. This will reboot your | |
146 | system when the timeout is reached. | |
147 | ||
148 | config HAVE_S3C2410_WATCHDOG | |
149 | bool | |
150 | help | |
151 | This will include watchdog timer support for Samsung SoCs. If | |
152 | you want to include watchdog support for any machine, kindly | |
153 | select this in the respective mach-XXXX/Kconfig file. | |
154 | ||
155 | config S3C2410_WATCHDOG | |
156 | tristate "S3C2410 Watchdog" | |
157 | depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG | |
158 | help | |
159 | Watchdog timer block in the Samsung SoCs. This will reboot | |
160 | the system when the timer expires with the watchdog enabled. | |
161 | ||
162 | The driver is limited by the speed of the system's PCLK | |
163 | signal, so with reasonably fast systems (PCLK around 50-66MHz) | |
164 | then watchdog intervals of over approximately 20seconds are | |
165 | unavailable. | |
166 | ||
167 | The driver can be built as a module by choosing M, and will | |
168 | be called s3c2410_wdt | |
169 | ||
170 | config SA1100_WATCHDOG | |
171 | tristate "SA1100/PXA2xx watchdog" | |
172 | depends on ARCH_SA1100 || ARCH_PXA | |
173 | help | |
174 | Watchdog timer embedded into SA11x0 and PXA2xx chips. This will | |
175 | reboot your system when timeout is reached. | |
176 | ||
177 | NOTE: once enabled, this timer cannot be disabled. | |
178 | ||
179 | To compile this driver as a module, choose M here: the | |
180 | module will be called sa1100_wdt. | |
181 | ||
182 | config MPCORE_WATCHDOG | |
183 | tristate "MPcore watchdog" | |
184 | depends on HAVE_ARM_TWD | |
185 | help | |
186 | Watchdog timer embedded into the MPcore system. | |
187 | ||
188 | To compile this driver as a module, choose M here: the | |
189 | module will be called mpcore_wdt. | |
190 | ||
191 | config EP93XX_WATCHDOG | |
192 | tristate "EP93xx Watchdog" | |
193 | depends on ARCH_EP93XX | |
194 | help | |
195 | Say Y here if to include support for the watchdog timer | |
196 | embedded in the Cirrus Logic EP93xx family of devices. | |
197 | ||
198 | To compile this driver as a module, choose M here: the | |
199 | module will be called ep93xx_wdt. | |
200 | ||
201 | config OMAP_WATCHDOG | |
202 | tristate "OMAP Watchdog" | |
203 | depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS | |
204 | help | |
205 | Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y' | |
206 | here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer. | |
207 | ||
208 | config PNX4008_WATCHDOG | |
209 | tristate "PNX4008 Watchdog" | |
210 | depends on ARCH_PNX4008 | |
211 | help | |
212 | Say Y here if to include support for the watchdog timer | |
213 | in the PNX4008 processor. | |
214 | This driver can be built as a module by choosing M. The module | |
215 | will be called pnx4008_wdt. | |
216 | ||
217 | Say N if you are unsure. | |
218 | ||
219 | config IOP_WATCHDOG | |
220 | tristate "IOP Watchdog" | |
221 | depends on PLAT_IOP | |
222 | select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X) | |
223 | help | |
224 | Say Y here if to include support for the watchdog timer | |
225 | in the Intel IOP3XX & IOP13XX I/O Processors. This driver can | |
226 | be built as a module by choosing M. The module will | |
227 | be called iop_wdt. | |
228 | ||
229 | Note: The IOP13XX watchdog does an Internal Bus Reset which will | |
230 | affect both cores and the peripherals of the IOP. The ATU-X | |
231 | and/or ATUe configuration registers will remain intact, but if | |
232 | operating as an Root Complex and/or Central Resource, the PCI-X | |
233 | and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER. | |
234 | ||
235 | config DAVINCI_WATCHDOG | |
236 | tristate "DaVinci watchdog" | |
237 | depends on ARCH_DAVINCI | |
238 | help | |
239 | Say Y here if to include support for the watchdog timer | |
240 | in the DaVinci DM644x/DM646x processors. | |
241 | To compile this driver as a module, choose M here: the | |
242 | module will be called davinci_wdt. | |
243 | ||
244 | NOTE: once enabled, this timer cannot be disabled. | |
245 | Say N if you are unsure. | |
246 | ||
247 | config ORION_WATCHDOG | |
248 | tristate "Orion watchdog" | |
249 | depends on ARCH_ORION5X || ARCH_KIRKWOOD | |
250 | help | |
251 | Say Y here if to include support for the watchdog timer | |
252 | in the Marvell Orion5x and Kirkwood ARM SoCs. | |
253 | To compile this driver as a module, choose M here: the | |
254 | module will be called orion_wdt. | |
255 | ||
256 | config COH901327_WATCHDOG | |
257 | bool "ST-Ericsson COH 901 327 watchdog" | |
258 | depends on ARCH_U300 | |
259 | default y if MACH_U300 | |
260 | help | |
261 | Say Y here to include Watchdog timer support for the | |
262 | watchdog embedded into the ST-Ericsson U300 series platforms. | |
263 | This watchdog is used to reset the system and thus cannot be | |
264 | compiled as a module. | |
265 | ||
266 | config TWL4030_WATCHDOG | |
267 | tristate "TWL4030 Watchdog" | |
268 | depends on TWL4030_CORE | |
269 | help | |
270 | Support for TI TWL4030 watchdog. Say 'Y' here to enable the | |
271 | watchdog timer support for TWL4030 chips. | |
272 | ||
273 | config STMP3XXX_WATCHDOG | |
274 | tristate "Freescale STMP3XXX watchdog" | |
275 | depends on ARCH_STMP3XXX | |
276 | help | |
277 | Say Y here if to include support for the watchdog timer | |
278 | for the Sigmatel STMP37XX/378X SoC. | |
279 | To compile this driver as a module, choose M here: the | |
280 | module will be called stmp3xxx_wdt. | |
281 | ||
282 | config NUC900_WATCHDOG | |
283 | tristate "Nuvoton NUC900 watchdog" | |
284 | depends on ARCH_W90X900 | |
285 | help | |
286 | Say Y here if to include support for the watchdog timer | |
287 | for the Nuvoton NUC900 series SoCs. | |
288 | To compile this driver as a module, choose M here: the | |
289 | module will be called nuc900_wdt. | |
290 | ||
291 | config ADX_WATCHDOG | |
292 | tristate "Avionic Design Xanthos watchdog" | |
293 | depends on ARCH_PXA_ADX | |
294 | help | |
295 | Say Y here if you want support for the watchdog timer on Avionic | |
296 | Design Xanthos boards. | |
297 | ||
298 | config TS72XX_WATCHDOG | |
299 | tristate "TS-72XX SBC Watchdog" | |
300 | depends on MACH_TS72XX | |
301 | help | |
302 | Technologic Systems TS-7200, TS-7250 and TS-7260 boards have | |
303 | watchdog timer implemented in a external CPLD chip. Say Y here | |
304 | if you want to support for the watchdog timer on TS-72XX boards. | |
305 | ||
306 | To compile this driver as a module, choose M here: the | |
307 | module will be called ts72xx_wdt. | |
308 | ||
309 | config MAX63XX_WATCHDOG | |
310 | tristate "Max63xx watchdog" | |
311 | depends on ARM && HAS_IOMEM | |
312 | help | |
313 | Support for memory mapped max63{69,70,71,72,73,74} watchdog timer. | |
314 | ||
315 | config IMX2_WDT | |
316 | tristate "IMX2+ Watchdog" | |
317 | depends on ARCH_MX2 || ARCH_MX25 || ARCH_MX3 || ARCH_MX5 | |
318 | help | |
319 | This is the driver for the hardware watchdog | |
320 | on the Freescale IMX2 and later processors. | |
321 | If you have one of these processors and wish to have | |
322 | watchdog support enabled, say Y, otherwise say N. | |
323 | ||
324 | To compile this driver as a module, choose M here: the | |
325 | module will be called imx2_wdt. | |
326 | ||
327 | # AVR32 Architecture | |
328 | ||
329 | config AT32AP700X_WDT | |
330 | tristate "AT32AP700x watchdog" | |
331 | depends on CPU_AT32AP700X | |
332 | help | |
333 | Watchdog timer embedded into AT32AP700x devices. This will reboot | |
334 | your system when the timeout is reached. | |
335 | ||
336 | # BLACKFIN Architecture | |
337 | ||
338 | config BFIN_WDT | |
339 | tristate "Blackfin On-Chip Watchdog Timer" | |
340 | depends on BLACKFIN | |
341 | ---help--- | |
342 | If you say yes here you will get support for the Blackfin On-Chip | |
343 | Watchdog Timer. If you have one of these processors and wish to | |
344 | have watchdog support enabled, say Y, otherwise say N. | |
345 | ||
346 | To compile this driver as a module, choose M here: the | |
347 | module will be called bfin_wdt. | |
348 | ||
349 | # CRIS Architecture | |
350 | ||
351 | # FRV Architecture | |
352 | ||
353 | # H8300 Architecture | |
354 | ||
355 | # X86 (i386 + ia64 + x86_64) Architecture | |
356 | ||
357 | config ACQUIRE_WDT | |
358 | tristate "Acquire SBC Watchdog Timer" | |
359 | depends on X86 | |
360 | ---help--- | |
361 | This is the driver for the hardware watchdog on Single Board | |
362 | Computers produced by Acquire Inc (and others). This watchdog | |
363 | simply watches your kernel to make sure it doesn't freeze, and if | |
364 | it does, it reboots your computer after a certain amount of time. | |
365 | ||
366 | To compile this driver as a module, choose M here: the | |
367 | module will be called acquirewdt. | |
368 | ||
369 | Most people will say N. | |
370 | ||
371 | config ADVANTECH_WDT | |
372 | tristate "Advantech SBC Watchdog Timer" | |
373 | depends on X86 | |
374 | help | |
375 | If you are configuring a Linux kernel for the Advantech single-board | |
376 | computer, say `Y' here to support its built-in watchdog timer | |
377 | feature. More information can be found at | |
378 | <http://www.advantech.com.tw/products/> | |
379 | ||
380 | config ALIM1535_WDT | |
381 | tristate "ALi M1535 PMU Watchdog Timer" | |
382 | depends on X86 && PCI | |
383 | ---help--- | |
384 | This is the driver for the hardware watchdog on the ALi M1535 PMU. | |
385 | ||
386 | To compile this driver as a module, choose M here: the | |
387 | module will be called alim1535_wdt. | |
388 | ||
389 | Most people will say N. | |
390 | ||
391 | config ALIM7101_WDT | |
392 | tristate "ALi M7101 PMU Computer Watchdog" | |
393 | depends on PCI | |
394 | help | |
395 | This is the driver for the hardware watchdog on the ALi M7101 PMU | |
396 | as used in the x86 Cobalt servers and also found in some | |
397 | SPARC Netra servers too. | |
398 | ||
399 | To compile this driver as a module, choose M here: the | |
400 | module will be called alim7101_wdt. | |
401 | ||
402 | Most people will say N. | |
403 | ||
404 | config GEODE_WDT | |
405 | tristate "AMD Geode CS5535/CS5536 Watchdog" | |
406 | depends on CS5535_MFGPT | |
407 | help | |
408 | This driver enables a watchdog capability built into the | |
409 | CS5535/CS5536 companion chips for the AMD Geode GX and LX | |
410 | processors. This watchdog watches your kernel to make sure | |
411 | it doesn't freeze, and if it does, it reboots your computer after | |
412 | a certain amount of time. | |
413 | ||
414 | You can compile this driver directly into the kernel, or use | |
415 | it as a module. The module will be called geodewdt. | |
416 | ||
417 | config SC520_WDT | |
418 | tristate "AMD Elan SC520 processor Watchdog" | |
419 | depends on X86 | |
420 | help | |
421 | This is the driver for the hardware watchdog built in to the | |
422 | AMD "Elan" SC520 microcomputer commonly used in embedded systems. | |
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 | You can compile this driver directly into the kernel, or use | |
428 | it as a module. The module will be called sc520_wdt. | |
429 | ||
430 | config SBC_FITPC2_WATCHDOG | |
431 | tristate "Compulab SBC-FITPC2 watchdog" | |
432 | depends on X86 | |
433 | ---help--- | |
434 | This is the driver for the built-in watchdog timer on the fit-PC2, | |
435 | fit-PC2i, CM-iAM single-board computers made by Compulab. | |
436 | ||
437 | It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux. | |
438 | When "Watchdog Timer Value" enabled one can set 31-255 s operational range. | |
439 | ||
440 | Entering BIOS setup temporary disables watchdog operation regardless to current state, | |
441 | so system will not be restarted while user in BIOS setup. | |
442 | ||
443 | Once watchdog was enabled the system will be restarted every | |
444 | "Watchdog Timer Value" period, so to prevent it user can restart or | |
445 | disable the watchdog. | |
446 | ||
447 | To compile this driver as a module, choose M here: the | |
448 | module will be called sbc_fitpc2_wdt. | |
449 | ||
450 | Most people will say N. | |
451 | ||
452 | config EUROTECH_WDT | |
453 | tristate "Eurotech CPU-1220/1410 Watchdog Timer" | |
454 | depends on X86 | |
455 | help | |
456 | Enable support for the watchdog timer on the Eurotech CPU-1220 and | |
457 | CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product | |
458 | information are at <http://www.eurotech.it/>. | |
459 | ||
460 | config IB700_WDT | |
461 | tristate "IB700 SBC Watchdog Timer" | |
462 | depends on X86 | |
463 | ---help--- | |
464 | This is the driver for the hardware watchdog on the IB700 Single | |
465 | Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog | |
466 | simply watches your kernel to make sure it doesn't freeze, and if | |
467 | it does, it reboots your computer after a certain amount of time. | |
468 | ||
469 | This driver is like the WDT501 driver but for slightly different hardware. | |
470 | ||
471 | To compile this driver as a module, choose M here: the | |
472 | module will be called ib700wdt. | |
473 | ||
474 | Most people will say N. | |
475 | ||
476 | config IBMASR | |
477 | tristate "IBM Automatic Server Restart" | |
478 | depends on X86 | |
479 | help | |
480 | This is the driver for the IBM Automatic Server Restart watchdog | |
481 | timer built-in into some eServer xSeries machines. | |
482 | ||
483 | To compile this driver as a module, choose M here: the | |
484 | module will be called ibmasr. | |
485 | ||
486 | config WAFER_WDT | |
487 | tristate "ICP Single Board Computer Watchdog Timer" | |
488 | depends on X86 | |
489 | help | |
490 | This is a driver for the hardware watchdog on the ICP Single | |
491 | Board Computer. This driver is working on (at least) the following | |
492 | IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782. | |
493 | ||
494 | To compile this driver as a module, choose M here: the | |
495 | module will be called wafer5823wdt. | |
496 | ||
497 | config I6300ESB_WDT | |
498 | tristate "Intel 6300ESB Timer/Watchdog" | |
499 | depends on X86 && PCI | |
500 | ---help--- | |
501 | Hardware driver for the watchdog timer built into the Intel | |
502 | 6300ESB controller hub. | |
503 | ||
504 | To compile this driver as a module, choose M here: the | |
505 | module will be called i6300esb. | |
506 | ||
507 | config ITCO_WDT | |
508 | tristate "Intel TCO Timer/Watchdog" | |
509 | depends on (X86 || IA64) && PCI | |
510 | ---help--- | |
511 | Hardware driver for the intel TCO timer based watchdog devices. | |
512 | These drivers are included in the Intel 82801 I/O Controller | |
513 | Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB | |
514 | controller hub. | |
515 | ||
516 | The TCO (Total Cost of Ownership) timer is a watchdog timer | |
517 | that will reboot the machine after its second expiration. The | |
518 | expiration time can be configured with the "heartbeat" parameter. | |
519 | ||
520 | On some motherboards the driver may fail to reset the chipset's | |
521 | NO_REBOOT flag which prevents the watchdog from rebooting the | |
522 | machine. If this is the case you will get a kernel message like | |
523 | "failed to reset NO_REBOOT flag, reboot disabled by hardware". | |
524 | ||
525 | To compile this driver as a module, choose M here: the | |
526 | module will be called iTCO_wdt. | |
527 | ||
528 | config ITCO_VENDOR_SUPPORT | |
529 | bool "Intel TCO Timer/Watchdog Specific Vendor Support" | |
530 | depends on ITCO_WDT | |
531 | ---help--- | |
532 | Add vendor specific support to the intel TCO timer based watchdog | |
533 | devices. At this moment we only have additional support for some | |
534 | SuperMicro Inc. motherboards. | |
535 | ||
536 | config IT8712F_WDT | |
537 | tristate "IT8712F (Smart Guardian) Watchdog Timer" | |
538 | depends on X86 | |
539 | ---help--- | |
540 | This is the driver for the built-in watchdog timer on the IT8712F | |
541 | Super I/0 chipset used on many motherboards. | |
542 | ||
543 | To compile this driver as a module, choose M here: the | |
544 | module will be called it8712f_wdt. | |
545 | ||
546 | config IT87_WDT | |
547 | tristate "IT87 Watchdog Timer" | |
548 | depends on X86 && EXPERIMENTAL | |
549 | ---help--- | |
550 | This is the driver for the hardware watchdog on the ITE IT8716, | |
551 | IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog | |
552 | simply watches your kernel to make sure it doesn't freeze, and if | |
553 | it does, it reboots your computer after a certain amount of time. | |
554 | ||
555 | To compile this driver as a module, choose M here: the module will | |
556 | be called it87_wdt. | |
557 | ||
558 | config HP_WATCHDOG | |
559 | tristate "HP Proliant iLO 2 Hardware Watchdog Timer" | |
560 | depends on X86 | |
561 | help | |
562 | A software monitoring watchdog and NMI sourcing driver. This driver | |
563 | will detect lockups and provide stack trace. Also, when an NMI | |
564 | occurs this driver will make the necessary BIOS calls to log | |
565 | the cause of the NMI. This is a driver that will only load on a | |
566 | HP ProLiant system with a minimum of iLO2 support. | |
567 | To compile this driver as a module, choose M here: the | |
568 | module will be called hpwdt. | |
569 | ||
570 | config SC1200_WDT | |
571 | tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" | |
572 | depends on X86 | |
573 | help | |
574 | This is a driver for National Semiconductor PC87307/PC97307 hardware | |
575 | watchdog cards as found on the SC1200. This watchdog is mainly used | |
576 | for power management purposes and can be used to power down the device | |
577 | during inactivity periods (includes interrupt activity monitoring). | |
578 | ||
579 | To compile this driver as a module, choose M here: the | |
580 | module will be called sc1200wdt. | |
581 | ||
582 | Most people will say N. | |
583 | ||
584 | config SCx200_WDT | |
585 | tristate "National Semiconductor SCx200 Watchdog" | |
586 | depends on SCx200 && PCI | |
587 | help | |
588 | Enable the built-in watchdog timer support on the National | |
589 | Semiconductor SCx200 processors. | |
590 | ||
591 | If compiled as a module, it will be called scx200_wdt. | |
592 | ||
593 | config PC87413_WDT | |
594 | tristate "NS PC87413 watchdog" | |
595 | depends on X86 | |
596 | ---help--- | |
597 | This is the driver for the hardware watchdog on the PC87413 chipset | |
598 | This watchdog simply watches your kernel to make sure it doesn't | |
599 | freeze, and if it does, it reboots your computer after a certain | |
600 | amount of time. | |
601 | ||
602 | To compile this driver as a module, choose M here: the | |
603 | module will be called pc87413_wdt. | |
604 | ||
605 | Most people will say N. | |
606 | ||
607 | config RDC321X_WDT | |
608 | tristate "RDC R-321x SoC watchdog" | |
609 | depends on X86_RDC321X | |
610 | help | |
611 | This is the driver for the built in hardware watchdog | |
612 | in the RDC R-321x SoC. | |
613 | ||
614 | To compile this driver as a module, choose M here: the | |
615 | module will be called rdc321x_wdt. | |
616 | ||
617 | config 60XX_WDT | |
618 | tristate "SBC-60XX Watchdog Timer" | |
619 | depends on X86 | |
620 | help | |
621 | This driver can be used with the watchdog timer found on some | |
622 | single board computers, namely the 6010 PII based computer. | |
623 | It may well work with other cards. It reads port 0x443 to enable | |
624 | and re-set the watchdog timer, and reads port 0x45 to disable | |
625 | the watchdog. If you have a card that behave in similar ways, | |
626 | you can probably make this driver work with your card as well. | |
627 | ||
628 | You can compile this driver directly into the kernel, or use | |
629 | it as a module. The module will be called sbc60xxwdt. | |
630 | ||
631 | config SBC8360_WDT | |
632 | tristate "SBC8360 Watchdog Timer" | |
633 | depends on X86 | |
634 | ---help--- | |
635 | ||
636 | This is the driver for the hardware watchdog on the SBC8360 Single | |
637 | Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). | |
638 | ||
639 | To compile this driver as a module, choose M here: the | |
640 | module will be called sbc8360. | |
641 | ||
642 | Most people will say N. | |
643 | ||
644 | config SBC7240_WDT | |
645 | tristate "SBC Nano 7240 Watchdog Timer" | |
646 | depends on X86_32 | |
647 | ---help--- | |
648 | This is the driver for the hardware watchdog found on the IEI | |
649 | single board computers EPIC Nano 7240 (and likely others). This | |
650 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
651 | and if it does, it reboots your computer after a certain amount of | |
652 | time. | |
653 | ||
654 | To compile this driver as a module, choose M here: the | |
655 | module will be called sbc7240_wdt. | |
656 | ||
657 | config CPU5_WDT | |
658 | tristate "SMA CPU5 Watchdog" | |
659 | depends on X86 | |
660 | ---help--- | |
661 | TBD. | |
662 | To compile this driver as a module, choose M here: the | |
663 | module will be called cpu5wdt. | |
664 | ||
665 | config SMSC_SCH311X_WDT | |
666 | tristate "SMSC SCH311X Watchdog Timer" | |
667 | depends on X86 | |
668 | ---help--- | |
669 | This is the driver for the hardware watchdog timer on the | |
670 | SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset | |
671 | (LPC IO with 8042 KBC, Reset Generation, HWM and multiple | |
672 | serial ports). | |
673 | ||
674 | To compile this driver as a module, choose M here: the | |
675 | module will be called sch311x_wdt. | |
676 | ||
677 | config SMSC37B787_WDT | |
678 | tristate "Winbond SMsC37B787 Watchdog Timer" | |
679 | depends on X86 | |
680 | ---help--- | |
681 | This is the driver for the hardware watchdog component on the | |
682 | Winbond SMsC37B787 chipset as used on the NetRunner Mainboard | |
683 | from Vision Systems and maybe others. | |
684 | ||
685 | This watchdog simply watches your kernel to make sure it doesn't | |
686 | freeze, and if it does, it reboots your computer after a certain | |
687 | amount of time. | |
688 | ||
689 | Usually a userspace daemon will notify the kernel WDT driver that | |
690 | userspace is still alive, at regular intervals. | |
691 | ||
692 | To compile this driver as a module, choose M here: the | |
693 | module will be called smsc37b787_wdt. | |
694 | ||
695 | Most people will say N. | |
696 | ||
697 | config W83627HF_WDT | |
698 | tristate "W83627HF Watchdog Timer" | |
699 | depends on X86 | |
700 | ---help--- | |
701 | This is the driver for the hardware watchdog on the W83627HF chipset | |
702 | as used in Advantech PC-9578 and Tyan S2721-533 motherboards | |
703 | (and likely others). This watchdog simply watches your kernel to | |
704 | make sure it doesn't freeze, and if it does, it reboots your computer | |
705 | after a certain amount of time. | |
706 | ||
707 | To compile this driver as a module, choose M here: the | |
708 | module will be called w83627hf_wdt. | |
709 | ||
710 | Most people will say N. | |
711 | ||
712 | config W83697HF_WDT | |
713 | tristate "W83697HF/W83697HG Watchdog Timer" | |
714 | depends on X86 | |
715 | ---help--- | |
716 | This is the driver for the hardware watchdog on the W83697HF/HG | |
717 | chipset as used in Dedibox/VIA motherboards (and likely others). | |
718 | This watchdog simply watches your kernel to make sure it doesn't | |
719 | freeze, and if it does, it reboots your computer after a certain | |
720 | amount of time. | |
721 | ||
722 | To compile this driver as a module, choose M here: the | |
723 | module will be called w83697hf_wdt. | |
724 | ||
725 | Most people will say N. | |
726 | ||
727 | config W83697UG_WDT | |
728 | tristate "W83697UG/W83697UF Watchdog Timer" | |
729 | depends on X86 | |
730 | ---help--- | |
731 | This is the driver for the hardware watchdog on the W83697UG/UF | |
732 | chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others). | |
733 | This watchdog simply watches your kernel to make sure it doesn't | |
734 | freeze, and if it does, it reboots your computer after a certain | |
735 | amount of time. | |
736 | ||
737 | To compile this driver as a module, choose M here: the | |
738 | module will be called w83697ug_wdt. | |
739 | ||
740 | Most people will say N. | |
741 | ||
742 | config W83877F_WDT | |
743 | tristate "W83877F (EMACS) Watchdog Timer" | |
744 | depends on X86 | |
745 | ---help--- | |
746 | This is the driver for the hardware watchdog on the W83877F chipset | |
747 | as used in EMACS PC-104 motherboards (and likely others). This | |
748 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
749 | and if it does, it reboots your computer after a certain amount of | |
750 | time. | |
751 | ||
752 | To compile this driver as a module, choose M here: the | |
753 | module will be called w83877f_wdt. | |
754 | ||
755 | Most people will say N. | |
756 | ||
757 | config W83977F_WDT | |
758 | tristate "W83977F (PCM-5335) Watchdog Timer" | |
759 | depends on X86 | |
760 | ---help--- | |
761 | This is the driver for the hardware watchdog on the W83977F I/O chip | |
762 | as used in AAEON's PCM-5335 SBC (and likely others). This | |
763 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
764 | and if it does, it reboots your computer after a certain amount of | |
765 | time. | |
766 | ||
767 | To compile this driver as a module, choose M here: the | |
768 | module will be called w83977f_wdt. | |
769 | ||
770 | config MACHZ_WDT | |
771 | tristate "ZF MachZ Watchdog" | |
772 | depends on X86 | |
773 | ---help--- | |
774 | If you are using a ZF Micro MachZ processor, say Y here, otherwise | |
775 | N. This is the driver for the watchdog timer built-in on that | |
776 | processor using ZF-Logic interface. This watchdog simply watches | |
777 | your kernel to make sure it doesn't freeze, and if it does, it | |
778 | reboots your computer after a certain amount of time. | |
779 | ||
780 | To compile this driver as a module, choose M here: the | |
781 | module will be called machzwd. | |
782 | ||
783 | config SBC_EPX_C3_WATCHDOG | |
784 | tristate "Winsystems SBC EPX-C3 watchdog" | |
785 | depends on X86 | |
786 | ---help--- | |
787 | This is the driver for the built-in watchdog timer on the EPX-C3 | |
788 | Single-board computer made by Winsystems, Inc. | |
789 | ||
790 | *Note*: This hardware watchdog is not probeable and thus there | |
791 | is no way to know if writing to its IO address will corrupt | |
792 | your system or have any real effect. The only way to be sure | |
793 | that this driver does what you want is to make sure you | |
794 | are running it on an EPX-C3 from Winsystems with the watchdog | |
795 | timer at IO address 0x1ee and 0x1ef. It will write to both those | |
796 | IO ports. Basically, the assumption is made that if you compile | |
797 | this driver into your kernel and/or load it as a module, that you | |
798 | know what you are doing and that you are in fact running on an | |
799 | EPX-C3 board! | |
800 | ||
801 | To compile this driver as a module, choose M here: the | |
802 | module will be called sbc_epx_c3. | |
803 | ||
804 | # M32R Architecture | |
805 | ||
806 | # M68K Architecture | |
807 | ||
808 | # M68KNOMMU Architecture | |
809 | ||
810 | # MIPS Architecture | |
811 | ||
812 | config BCM47XX_WDT | |
813 | tristate "Broadcom BCM47xx Watchdog Timer" | |
814 | depends on BCM47XX | |
815 | help | |
816 | Hardware driver for the Broadcom BCM47xx Watchog Timer. | |
817 | ||
818 | config RC32434_WDT | |
819 | tristate "IDT RC32434 SoC Watchdog Timer" | |
820 | depends on MIKROTIK_RB532 | |
821 | help | |
822 | Hardware driver for the IDT RC32434 SoC built-in | |
823 | watchdog timer. | |
824 | ||
825 | To compile this driver as a module, choose M here: the | |
826 | module will be called rc32434_wdt. | |
827 | ||
828 | config INDYDOG | |
829 | tristate "Indy/I2 Hardware Watchdog" | |
830 | depends on SGI_HAS_INDYDOG | |
831 | help | |
832 | Hardware driver for the Indy's/I2's watchdog. This is a | |
833 | watchdog timer that will reboot the machine after a 60 second | |
834 | timer expired and no process has written to /dev/watchdog during | |
835 | that time. | |
836 | ||
837 | config WDT_MTX1 | |
838 | tristate "MTX-1 Hardware Watchdog" | |
839 | depends on MIPS_MTX1 | |
840 | help | |
841 | Hardware driver for the MTX-1 boards. This is a watchdog timer that | |
842 | will reboot the machine after a 100 seconds timer expired. | |
843 | ||
844 | config PNX833X_WDT | |
845 | tristate "PNX833x Hardware Watchdog" | |
846 | depends on SOC_PNX8335 | |
847 | help | |
848 | Hardware driver for the PNX833x's watchdog. This is a | |
849 | watchdog timer that will reboot the machine after a programable | |
850 | timer has expired and no process has written to /dev/watchdog during | |
851 | that time. | |
852 | ||
853 | config SIBYTE_WDOG | |
854 | tristate "Sibyte SoC hardware watchdog" | |
855 | depends on CPU_SB1 | |
856 | help | |
857 | Watchdog driver for the built in watchdog hardware in Sibyte | |
858 | SoC processors. There are apparently two watchdog timers | |
859 | on such processors; this driver supports only the first one, | |
860 | because currently Linux only supports exporting one watchdog | |
861 | to userspace. | |
862 | ||
863 | To compile this driver as a loadable module, choose M here. | |
864 | The module will be called sb_wdog. | |
865 | ||
866 | config AR7_WDT | |
867 | tristate "TI AR7 Watchdog Timer" | |
868 | depends on AR7 | |
869 | help | |
870 | Hardware driver for the TI AR7 Watchdog Timer. | |
871 | ||
872 | config TXX9_WDT | |
873 | tristate "Toshiba TXx9 Watchdog Timer" | |
874 | depends on CPU_TX39XX || CPU_TX49XX | |
875 | help | |
876 | Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs. | |
877 | ||
878 | # PARISC Architecture | |
879 | ||
880 | # POWERPC Architecture | |
881 | ||
882 | config GEF_WDT | |
883 | tristate "GE Watchdog Timer" | |
884 | depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A | |
885 | ---help--- | |
886 | Watchdog timer found in a number of GE single board computers. | |
887 | ||
888 | config MPC5200_WDT | |
889 | bool "MPC52xx Watchdog Timer" | |
890 | depends on PPC_MPC52xx | |
891 | help | |
892 | Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog. | |
893 | ||
894 | config 8xxx_WDT | |
895 | tristate "MPC8xxx Platform Watchdog Timer" | |
896 | depends on PPC_8xx || PPC_83xx || PPC_86xx | |
897 | help | |
898 | This driver is for a SoC level watchdog that exists on some | |
899 | Freescale PowerPC processors. So far this driver supports: | |
900 | - MPC8xx watchdogs | |
901 | - MPC83xx watchdogs | |
902 | - MPC86xx watchdogs | |
903 | ||
904 | For BookE processors (MPC85xx) use the BOOKE_WDT driver instead. | |
905 | ||
906 | config MV64X60_WDT | |
907 | tristate "MV64X60 (Marvell Discovery) Watchdog Timer" | |
908 | depends on MV64X60 | |
909 | ||
910 | config PIKA_WDT | |
911 | tristate "PIKA FPGA Watchdog" | |
912 | depends on WARP | |
913 | default y | |
914 | help | |
915 | This enables the watchdog in the PIKA FPGA. Currently used on | |
916 | the Warp platform. | |
917 | ||
918 | config BOOKE_WDT | |
919 | bool "PowerPC Book-E Watchdog Timer" | |
920 | depends on BOOKE || 4xx | |
921 | ---help--- | |
922 | Please see Documentation/watchdog/watchdog-api.txt for | |
923 | more information. | |
924 | ||
925 | # PPC64 Architecture | |
926 | ||
927 | config WATCHDOG_RTAS | |
928 | tristate "RTAS watchdog" | |
929 | depends on PPC_RTAS | |
930 | help | |
931 | This driver adds watchdog support for the RTAS watchdog. | |
932 | ||
933 | To compile this driver as a module, choose M here. The module | |
934 | will be called wdrtas. | |
935 | ||
936 | # S390 Architecture | |
937 | ||
938 | config ZVM_WATCHDOG | |
939 | tristate "z/VM Watchdog Timer" | |
940 | depends on S390 | |
941 | help | |
942 | IBM s/390 and zSeries machines running under z/VM 5.1 or later | |
943 | provide a virtual watchdog timer to their guest that cause a | |
944 | user define Control Program command to be executed after a | |
945 | timeout. | |
946 | ||
947 | To compile this driver as a module, choose M here. The module | |
948 | will be called vmwatchdog. | |
949 | ||
950 | # SUPERH (sh + sh64) Architecture | |
951 | ||
952 | config SH_WDT | |
953 | tristate "SuperH Watchdog" | |
954 | depends on SUPERH && (CPU_SH3 || CPU_SH4) | |
955 | help | |
956 | This driver adds watchdog support for the integrated watchdog in the | |
957 | SuperH processors. If you have one of these processors and wish | |
958 | to have watchdog support enabled, say Y, otherwise say N. | |
959 | ||
960 | As a side note, saying Y here will automatically boost HZ to 1000 | |
961 | so that the timer has a chance to clear the overflow counter. On | |
962 | slower systems (such as the SH-2 and SH-3) this will likely yield | |
963 | some performance issues. As such, the WDT should be avoided here | |
964 | unless it is absolutely necessary. | |
965 | ||
966 | To compile this driver as a module, choose M here: the | |
967 | module will be called shwdt. | |
968 | ||
969 | config SH_WDT_MMAP | |
970 | bool "Allow mmap of SH WDT" | |
971 | default n | |
972 | depends on SH_WDT | |
973 | help | |
974 | If you say Y here, user applications will be able to mmap the | |
975 | WDT/CPG registers. | |
976 | ||
977 | # SPARC Architecture | |
978 | ||
979 | # SPARC64 Architecture | |
980 | ||
981 | config WATCHDOG_CP1XXX | |
982 | tristate "CP1XXX Hardware Watchdog support" | |
983 | depends on SPARC64 && PCI | |
984 | ---help--- | |
985 | This is the driver for the hardware watchdog timers present on | |
986 | Sun Microsystems CompactPCI models CP1400 and CP1500. | |
987 | ||
988 | To compile this driver as a module, choose M here: the | |
989 | module will be called cpwatchdog. | |
990 | ||
991 | If you do not have a CompactPCI model CP1400 or CP1500, or | |
992 | another UltraSPARC-IIi-cEngine boardset with hardware watchdog, | |
993 | you should say N to this option. | |
994 | ||
995 | config WATCHDOG_RIO | |
996 | tristate "RIO Hardware Watchdog support" | |
997 | depends on SPARC64 && PCI | |
998 | help | |
999 | Say Y here to support the hardware watchdog capability on Sun RIO | |
1000 | machines. The watchdog timeout period is normally one minute but | |
1001 | can be changed with a boot-time parameter. | |
1002 | ||
1003 | # XTENSA Architecture | |
1004 | ||
1005 | # | |
1006 | # ISA-based Watchdog Cards | |
1007 | # | |
1008 | ||
1009 | comment "ISA-based Watchdog Cards" | |
1010 | depends on ISA | |
1011 | ||
1012 | config PCWATCHDOG | |
1013 | tristate "Berkshire Products ISA-PC Watchdog" | |
1014 | depends on ISA | |
1015 | ---help--- | |
1016 | This is the driver for the Berkshire Products ISA-PC Watchdog card. | |
1017 | This card simply watches your kernel to make sure it doesn't freeze, | |
1018 | and if it does, it reboots your computer after a certain amount of | |
1019 | time. This driver is like the WDT501 driver but for different | |
1020 | hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC | |
1021 | watchdog cards can be ordered from <http://www.berkprod.com/>. | |
1022 | ||
1023 | To compile this driver as a module, choose M here: the | |
1024 | module will be called pcwd. | |
1025 | ||
1026 | Most people will say N. | |
1027 | ||
1028 | config MIXCOMWD | |
1029 | tristate "Mixcom Watchdog" | |
1030 | depends on ISA | |
1031 | ---help--- | |
1032 | This is a driver for the Mixcom hardware watchdog cards. This | |
1033 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
1034 | and if it does, it reboots your computer after a certain amount of | |
1035 | time. | |
1036 | ||
1037 | To compile this driver as a module, choose M here: the | |
1038 | module will be called mixcomwd. | |
1039 | ||
1040 | Most people will say N. | |
1041 | ||
1042 | config WDT | |
1043 | tristate "WDT Watchdog timer" | |
1044 | depends on ISA | |
1045 | ---help--- | |
1046 | If you have a WDT500P or WDT501P watchdog board, say Y here, | |
1047 | otherwise N. It is not possible to probe for this board, which means | |
1048 | that you have to inform the kernel about the IO port and IRQ that | |
1049 | is needed (you can do this via the io and irq parameters) | |
1050 | ||
1051 | To compile this driver as a module, choose M here: the | |
1052 | module will be called wdt. | |
1053 | ||
1054 | # | |
1055 | # PCI-based Watchdog Cards | |
1056 | # | |
1057 | ||
1058 | comment "PCI-based Watchdog Cards" | |
1059 | depends on PCI | |
1060 | ||
1061 | config PCIPCWATCHDOG | |
1062 | tristate "Berkshire Products PCI-PC Watchdog" | |
1063 | depends on PCI | |
1064 | ---help--- | |
1065 | This is the driver for the Berkshire Products PCI-PC Watchdog card. | |
1066 | This card simply watches your kernel to make sure it doesn't freeze, | |
1067 | and if it does, it reboots your computer after a certain amount of | |
1068 | time. The card can also monitor the internal temperature of the PC. | |
1069 | More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>. | |
1070 | ||
1071 | To compile this driver as a module, choose M here: the | |
1072 | module will be called pcwd_pci. | |
1073 | ||
1074 | Most people will say N. | |
1075 | ||
1076 | config WDTPCI | |
1077 | tristate "PCI-WDT500/501 Watchdog timer" | |
1078 | depends on PCI | |
1079 | ---help--- | |
1080 | If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N. | |
1081 | ||
1082 | If you have a PCI-WDT501 watchdog board then you can enable the | |
1083 | temperature sensor by setting the type parameter to 501. | |
1084 | ||
1085 | If you want to enable the Fan Tachometer on the PCI-WDT501, then you | |
1086 | can do this via the tachometer parameter. Only do this if you have a | |
1087 | fan tachometer actually set up. | |
1088 | ||
1089 | To compile this driver as a module, choose M here: the | |
1090 | module will be called wdt_pci. | |
1091 | ||
1092 | # | |
1093 | # USB-based Watchdog Cards | |
1094 | # | |
1095 | ||
1096 | comment "USB-based Watchdog Cards" | |
1097 | depends on USB | |
1098 | ||
1099 | config USBPCWATCHDOG | |
1100 | tristate "Berkshire Products USB-PC Watchdog" | |
1101 | depends on USB | |
1102 | ---help--- | |
1103 | This is the driver for the Berkshire Products USB-PC Watchdog card. | |
1104 | This card simply watches your kernel to make sure it doesn't freeze, | |
1105 | and if it does, it reboots your computer after a certain amount of | |
1106 | time. The card can also monitor the internal temperature of the PC. | |
1107 | More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>. | |
1108 | ||
1109 | To compile this driver as a module, choose M here: the | |
1110 | module will be called pcwd_usb. | |
1111 | ||
1112 | Most people will say N. | |
1113 | ||
1114 | endif # WATCHDOG |