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_AT32AP700X 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 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 and also found in some 292 SPARC Netra servers too. 293 294 To compile this driver as a module, choose M here: the 295 module will be called alim7101_wdt. 296 297 Most people will say N. 298 299config GEODE_WDT 300 tristate "AMD Geode CS5535/CS5536 Watchdog" 301 depends on MGEODE_LX 302 help 303 This driver enables a watchdog capability built into the 304 CS5535/CS5536 companion chips for the AMD Geode GX and LX 305 processors. This watchdog watches your kernel to make sure 306 it doesn't freeze, and if it does, it reboots your computer after 307 a certain amount of time. 308 309 You can compile this driver directly into the kernel, or use 310 it as a module. The module will be called geodewdt. 311 312config SC520_WDT 313 tristate "AMD Elan SC520 processor Watchdog" 314 depends on X86 315 help 316 This is the driver for the hardware watchdog built in to the 317 AMD "Elan" SC520 microcomputer commonly used in embedded systems. 318 This watchdog simply watches your kernel to make sure it doesn't 319 freeze, and if it does, it reboots your computer after a certain 320 amount of time. 321 322 You can compile this driver directly into the kernel, or use 323 it as a module. The module will be called sc520_wdt. 324 325config EUROTECH_WDT 326 tristate "Eurotech CPU-1220/1410 Watchdog Timer" 327 depends on X86 328 help 329 Enable support for the watchdog timer on the Eurotech CPU-1220 and 330 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product 331 information are at <http://www.eurotech.it/>. 332 333config IB700_WDT 334 tristate "IB700 SBC Watchdog Timer" 335 depends on X86 336 ---help--- 337 This is the driver for the hardware watchdog on the IB700 Single 338 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog 339 simply watches your kernel to make sure it doesn't freeze, and if 340 it does, it reboots your computer after a certain amount of time. 341 342 This driver is like the WDT501 driver but for slightly different hardware. 343 344 To compile this driver as a module, choose M here: the 345 module will be called ib700wdt. 346 347 Most people will say N. 348 349config IBMASR 350 tristate "IBM Automatic Server Restart" 351 depends on X86 352 help 353 This is the driver for the IBM Automatic Server Restart watchdog 354 timer built-in into some eServer xSeries machines. 355 356 To compile this driver as a module, choose M here: the 357 module will be called ibmasr. 358 359config WAFER_WDT 360 tristate "ICP Single Board Computer Watchdog Timer" 361 depends on X86 362 help 363 This is a driver for the hardware watchdog on the ICP Single 364 Board Computer. This driver is working on (at least) the following 365 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782. 366 367 To compile this driver as a module, choose M here: the 368 module will be called wafer5823wdt. 369 370config I6300ESB_WDT 371 tristate "Intel 6300ESB Timer/Watchdog" 372 depends on X86 && PCI 373 ---help--- 374 Hardware driver for the watchdog timer built into the Intel 375 6300ESB controller hub. 376 377 To compile this driver as a module, choose M here: the 378 module will be called i6300esb. 379 380config ITCO_WDT 381 tristate "Intel TCO Timer/Watchdog" 382 depends on (X86 || IA64) && PCI 383 ---help--- 384 Hardware driver for the intel TCO timer based watchdog devices. 385 These drivers are included in the Intel 82801 I/O Controller 386 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB 387 controller hub. 388 389 The TCO (Total Cost of Ownership) timer is a watchdog timer 390 that will reboot the machine after its second expiration. The 391 expiration time can be configured with the "heartbeat" parameter. 392 393 On some motherboards the driver may fail to reset the chipset's 394 NO_REBOOT flag which prevents the watchdog from rebooting the 395 machine. If this is the case you will get a kernel message like 396 "failed to reset NO_REBOOT flag, reboot disabled by hardware". 397 398 To compile this driver as a module, choose M here: the 399 module will be called iTCO_wdt. 400 401config ITCO_VENDOR_SUPPORT 402 bool "Intel TCO Timer/Watchdog Specific Vendor Support" 403 depends on ITCO_WDT 404 ---help--- 405 Add vendor specific support to the intel TCO timer based watchdog 406 devices. At this moment we only have additional support for some 407 SuperMicro Inc. motherboards. 408 409config IT8712F_WDT 410 tristate "IT8712F (Smart Guardian) Watchdog Timer" 411 depends on X86 412 ---help--- 413 This is the driver for the built-in watchdog timer on the IT8712F 414 Super I/0 chipset used on many motherboards. 415 416 To compile this driver as a module, choose M here: the 417 module will be called it8712f_wdt. 418 419config HP_WATCHDOG 420 tristate "HP Proliant iLO 2 Hardware Watchdog Timer" 421 depends on X86 422 help 423 A software monitoring watchdog and NMI sourcing driver. This driver 424 will detect lockups and provide stack trace. Also, when an NMI 425 occurs this driver will make the necessary BIOS calls to log 426 the cause of the NMI. This is a driver that will only load on a 427 HP ProLiant system with a minimum of iLO2 support. 428 To compile this driver as a module, choose M here: the 429 module will be called hpwdt. 430 431config SC1200_WDT 432 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" 433 depends on X86 434 help 435 This is a driver for National Semiconductor PC87307/PC97307 hardware 436 watchdog cards as found on the SC1200. This watchdog is mainly used 437 for power management purposes and can be used to power down the device 438 during inactivity periods (includes interrupt activity monitoring). 439 440 To compile this driver as a module, choose M here: the 441 module will be called sc1200wdt. 442 443 Most people will say N. 444 445config SCx200_WDT 446 tristate "National Semiconductor SCx200 Watchdog" 447 depends on SCx200 && PCI 448 help 449 Enable the built-in watchdog timer support on the National 450 Semiconductor SCx200 processors. 451 452 If compiled as a module, it will be called scx200_wdt. 453 454config PC87413_WDT 455 tristate "NS PC87413 watchdog" 456 depends on X86 457 ---help--- 458 This is the driver for the hardware watchdog on the PC87413 chipset 459 This watchdog simply watches your kernel to make sure it doesn't 460 freeze, and if it does, it reboots your computer after a certain 461 amount of time. 462 463 To compile this driver as a module, choose M here: the 464 module will be called pc87413_wdt. 465 466 Most people will say N. 467 468config RDC321X_WDT 469 tristate "RDC R-321x SoC watchdog" 470 depends on X86_RDC321X 471 help 472 This is the driver for the built in hardware watchdog 473 in the RDC R-321x SoC. 474 475 To compile this driver as a module, choose M here: the 476 module will be called rdc321x_wdt. 477 478config 60XX_WDT 479 tristate "SBC-60XX Watchdog Timer" 480 depends on X86 481 help 482 This driver can be used with the watchdog timer found on some 483 single board computers, namely the 6010 PII based computer. 484 It may well work with other cards. It reads port 0x443 to enable 485 and re-set the watchdog timer, and reads port 0x45 to disable 486 the watchdog. If you have a card that behave in similar ways, 487 you can probably make this driver work with your card as well. 488 489 You can compile this driver directly into the kernel, or use 490 it as a module. The module will be called sbc60xxwdt. 491 492config SBC8360_WDT 493 tristate "SBC8360 Watchdog Timer" 494 depends on X86 495 ---help--- 496 497 This is the driver for the hardware watchdog on the SBC8360 Single 498 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). 499 500 To compile this driver as a module, choose M here: the 501 module will be called sbc8360.ko. 502 503 Most people will say N. 504 505config SBC7240_WDT 506 tristate "SBC Nano 7240 Watchdog Timer" 507 depends on X86_32 508 ---help--- 509 This is the driver for the hardware watchdog found on the IEI 510 single board computers EPIC Nano 7240 (and likely others). This 511 watchdog simply watches your kernel to make sure it doesn't freeze, 512 and if it does, it reboots your computer after a certain amount of 513 time. 514 515 To compile this driver as a module, choose M here: the 516 module will be called sbc7240_wdt. 517 518config CPU5_WDT 519 tristate "SMA CPU5 Watchdog" 520 depends on X86 521 ---help--- 522 TBD. 523 To compile this driver as a module, choose M here: the 524 module will be called cpu5wdt. 525 526config SMSC37B787_WDT 527 tristate "Winbond SMsC37B787 Watchdog Timer" 528 depends on X86 529 ---help--- 530 This is the driver for the hardware watchdog component on the 531 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard 532 from Vision Systems and maybe others. 533 534 This watchdog simply watches your kernel to make sure it doesn't 535 freeze, and if it does, it reboots your computer after a certain 536 amount of time. 537 538 Usually a userspace daemon will notify the kernel WDT driver that 539 userspace is still alive, at regular intervals. 540 541 To compile this driver as a module, choose M here: the 542 module will be called smsc37b787_wdt. 543 544 Most people will say N. 545 546config W83627HF_WDT 547 tristate "W83627HF Watchdog Timer" 548 depends on X86 549 ---help--- 550 This is the driver for the hardware watchdog on the W83627HF chipset 551 as used in Advantech PC-9578 and Tyan S2721-533 motherboards 552 (and likely others). This watchdog simply watches your kernel to 553 make sure it doesn't freeze, and if it does, it reboots your computer 554 after a certain amount of time. 555 556 To compile this driver as a module, choose M here: the 557 module will be called w83627hf_wdt. 558 559 Most people will say N. 560 561config W83697HF_WDT 562 tristate "W83697HF/W83697HG Watchdog Timer" 563 depends on X86 564 ---help--- 565 This is the driver for the hardware watchdog on the W83697HF/HG 566 chipset as used in Dedibox/VIA motherboards (and likely others). 567 This watchdog simply watches your kernel to make sure it doesn't 568 freeze, and if it does, it reboots your computer after a certain 569 amount of time. 570 571 To compile this driver as a module, choose M here: the 572 module will be called w83697hf_wdt. 573 574 Most people will say N. 575 576config W83877F_WDT 577 tristate "W83877F (EMACS) Watchdog Timer" 578 depends on X86 579 ---help--- 580 This is the driver for the hardware watchdog on the W83877F chipset 581 as used in EMACS PC-104 motherboards (and likely others). This 582 watchdog simply watches your kernel to make sure it doesn't freeze, 583 and if it does, it reboots your computer after a certain amount of 584 time. 585 586 To compile this driver as a module, choose M here: the 587 module will be called w83877f_wdt. 588 589 Most people will say N. 590 591config W83977F_WDT 592 tristate "W83977F (PCM-5335) Watchdog Timer" 593 depends on X86 594 ---help--- 595 This is the driver for the hardware watchdog on the W83977F I/O chip 596 as used in AAEON's PCM-5335 SBC (and likely others). This 597 watchdog simply watches your kernel to make sure it doesn't freeze, 598 and if it does, it reboots your computer after a certain amount of 599 time. 600 601 To compile this driver as a module, choose M here: the 602 module will be called w83977f_wdt. 603 604config MACHZ_WDT 605 tristate "ZF MachZ Watchdog" 606 depends on X86 607 ---help--- 608 If you are using a ZF Micro MachZ processor, say Y here, otherwise 609 N. This is the driver for the watchdog timer built-in on that 610 processor using ZF-Logic interface. This watchdog simply watches 611 your kernel to make sure it doesn't freeze, and if it does, it 612 reboots your computer after a certain amount of time. 613 614 To compile this driver as a module, choose M here: the 615 module will be called machzwd. 616 617config SBC_EPX_C3_WATCHDOG 618 tristate "Winsystems SBC EPX-C3 watchdog" 619 depends on X86 620 ---help--- 621 This is the driver for the built-in watchdog timer on the EPX-C3 622 Single-board computer made by Winsystems, Inc. 623 624 *Note*: This hardware watchdog is not probeable and thus there 625 is no way to know if writing to its IO address will corrupt 626 your system or have any real effect. The only way to be sure 627 that this driver does what you want is to make sure you 628 are running it on an EPX-C3 from Winsystems with the watchdog 629 timer at IO address 0x1ee and 0x1ef. It will write to both those 630 IO ports. Basically, the assumption is made that if you compile 631 this driver into your kernel and/or load it as a module, that you 632 know what you are doing and that you are in fact running on an 633 EPX-C3 board! 634 635 To compile this driver as a module, choose M here: the 636 module will be called sbc_epx_c3. 637 638# M32R Architecture 639 640# M68K Architecture 641 642# M68KNOMMU Architecture 643 644# MIPS Architecture 645 646config RC32434_WDT 647 tristate "IDT RC32434 SoC Watchdog Timer" 648 depends on MIKROTIK_RB532 649 help 650 Hardware driver for the IDT RC32434 SoC built-in 651 watchdog timer. 652 653 To compile this driver as a module, choose M here: the 654 module will be called rc32434_wdt. 655 656config INDYDOG 657 tristate "Indy/I2 Hardware Watchdog" 658 depends on SGI_HAS_INDYDOG 659 help 660 Hardware driver for the Indy's/I2's watchdog. This is a 661 watchdog timer that will reboot the machine after a 60 second 662 timer expired and no process has written to /dev/watchdog during 663 that time. 664 665config WDT_MTX1 666 tristate "MTX-1 Hardware Watchdog" 667 depends on MIPS_MTX1 668 help 669 Hardware driver for the MTX-1 boards. This is a watchdog timer that 670 will reboot the machine after a 100 seconds timer expired. 671 672config WDT_RM9K_GPI 673 tristate "RM9000/GPI hardware watchdog" 674 depends on CPU_RM9000 675 help 676 Watchdog implementation using the GPI hardware found on 677 PMC-Sierra RM9xxx CPUs. 678 679 To compile this driver as a module, choose M here: the 680 module will be called rm9k_wdt. 681 682config SIBYTE_WDOG 683 tristate "Sibyte SoC hardware watchdog" 684 depends on CPU_SB1 685 help 686 Watchdog driver for the built in watchdog hardware in Sibyte 687 SoC processors. There are apparently two watchdog timers 688 on such processors; this driver supports only the first one, 689 because currently Linux only supports exporting one watchdog 690 to userspace. 691 692 To compile this driver as a loadable module, choose M here. 693 The module will be called sb_wdog. 694 695config AR7_WDT 696 tristate "TI AR7 Watchdog Timer" 697 depends on AR7 698 help 699 Hardware driver for the TI AR7 Watchdog Timer. 700 701config TXX9_WDT 702 tristate "Toshiba TXx9 Watchdog Timer" 703 depends on CPU_TX39XX || CPU_TX49XX 704 help 705 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs. 706 707# PARISC Architecture 708 709# POWERPC Architecture 710 711config MPC5200_WDT 712 tristate "MPC5200 Watchdog Timer" 713 depends on PPC_MPC52xx 714 715config 8xxx_WDT 716 tristate "MPC8xxx Platform Watchdog Timer" 717 depends on PPC_8xx || PPC_83xx || PPC_86xx 718 help 719 This driver is for a SoC level watchdog that exists on some 720 Freescale PowerPC processors. So far this driver supports: 721 - MPC8xx watchdogs 722 - MPC83xx watchdogs 723 - MPC86xx watchdogs 724 725 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead. 726 727config MV64X60_WDT 728 tristate "MV64X60 (Marvell Discovery) Watchdog Timer" 729 depends on MV64X60 730 731config BOOKE_WDT 732 bool "PowerPC Book-E Watchdog Timer" 733 depends on BOOKE || 4xx 734 ---help--- 735 Please see Documentation/watchdog/watchdog-api.txt for 736 more information. 737 738# PPC64 Architecture 739 740config WATCHDOG_RTAS 741 tristate "RTAS watchdog" 742 depends on PPC_RTAS 743 help 744 This driver adds watchdog support for the RTAS watchdog. 745 746 To compile this driver as a module, choose M here. The module 747 will be called wdrtas. 748 749# S390 Architecture 750 751config ZVM_WATCHDOG 752 tristate "z/VM Watchdog Timer" 753 depends on S390 754 help 755 IBM s/390 and zSeries machines running under z/VM 5.1 or later 756 provide a virtual watchdog timer to their guest that cause a 757 user define Control Program command to be executed after a 758 timeout. 759 760 To compile this driver as a module, choose M here. The module 761 will be called vmwatchdog. 762 763# SUPERH (sh + sh64) Architecture 764 765config SH_WDT 766 tristate "SuperH Watchdog" 767 depends on SUPERH && (CPU_SH3 || CPU_SH4) 768 help 769 This driver adds watchdog support for the integrated watchdog in the 770 SuperH processors. If you have one of these processors and wish 771 to have watchdog support enabled, say Y, otherwise say N. 772 773 As a side note, saying Y here will automatically boost HZ to 1000 774 so that the timer has a chance to clear the overflow counter. On 775 slower systems (such as the SH-2 and SH-3) this will likely yield 776 some performance issues. As such, the WDT should be avoided here 777 unless it is absolutely necessary. 778 779 To compile this driver as a module, choose M here: the 780 module will be called shwdt. 781 782config SH_WDT_MMAP 783 bool "Allow mmap of SH WDT" 784 default n 785 depends on SH_WDT 786 help 787 If you say Y here, user applications will be able to mmap the 788 WDT/CPG registers. 789 790# SPARC Architecture 791 792# SPARC64 Architecture 793 794config WATCHDOG_CP1XXX 795 tristate "CP1XXX Hardware Watchdog support" 796 depends on SPARC64 && PCI 797 ---help--- 798 This is the driver for the hardware watchdog timers present on 799 Sun Microsystems CompactPCI models CP1400 and CP1500. 800 801 To compile this driver as a module, choose M here: the 802 module will be called cpwatchdog. 803 804 If you do not have a CompactPCI model CP1400 or CP1500, or 805 another UltraSPARC-IIi-cEngine boardset with hardware watchdog, 806 you should say N to this option. 807 808config WATCHDOG_RIO 809 tristate "RIO Hardware Watchdog support" 810 depends on SPARC64 && PCI 811 help 812 Say Y here to support the hardware watchdog capability on Sun RIO 813 machines. The watchdog timeout period is normally one minute but 814 can be changed with a boot-time parameter. 815 816# XTENSA Architecture 817 818# 819# ISA-based Watchdog Cards 820# 821 822comment "ISA-based Watchdog Cards" 823 depends on ISA 824 825config PCWATCHDOG 826 tristate "Berkshire Products ISA-PC Watchdog" 827 depends on ISA 828 ---help--- 829 This is the driver for the Berkshire Products ISA-PC Watchdog card. 830 This card simply watches your kernel to make sure it doesn't freeze, 831 and if it does, it reboots your computer after a certain amount of 832 time. This driver is like the WDT501 driver but for different 833 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC 834 watchdog cards can be ordered from <http://www.berkprod.com/>. 835 836 To compile this driver as a module, choose M here: the 837 module will be called pcwd. 838 839 Most people will say N. 840 841config MIXCOMWD 842 tristate "Mixcom Watchdog" 843 depends on ISA 844 ---help--- 845 This is a driver for the Mixcom hardware watchdog cards. This 846 watchdog simply watches your kernel to make sure it doesn't freeze, 847 and if it does, it reboots your computer after a certain amount of 848 time. 849 850 To compile this driver as a module, choose M here: the 851 module will be called mixcomwd. 852 853 Most people will say N. 854 855config WDT 856 tristate "WDT Watchdog timer" 857 depends on ISA 858 ---help--- 859 If you have a WDT500P or WDT501P watchdog board, say Y here, 860 otherwise N. It is not possible to probe for this board, which means 861 that you have to inform the kernel about the IO port and IRQ that 862 is needed (you can do this via the io and irq parameters) 863 864 To compile this driver as a module, choose M here: the 865 module will be called wdt. 866 867config WDT_501 868 bool "WDT501 features" 869 depends on WDT 870 help 871 Saying Y here and creating a character special file /dev/temperature 872 with major number 10 and minor number 131 ("man mknod") will give 873 you a thermometer inside your computer: reading from 874 /dev/temperature yields one byte, the temperature in degrees 875 Fahrenheit. This works only if you have a WDT501P watchdog board 876 installed. 877 878 If you want to enable the Fan Tachometer on the WDT501P, then you 879 can do this via the tachometer parameter. Only do this if you have a 880 fan tachometer actually set up. 881 882# 883# PCI-based Watchdog Cards 884# 885 886comment "PCI-based Watchdog Cards" 887 depends on PCI 888 889config PCIPCWATCHDOG 890 tristate "Berkshire Products PCI-PC Watchdog" 891 depends on PCI 892 ---help--- 893 This is the driver for the Berkshire Products PCI-PC Watchdog card. 894 This card simply watches your kernel to make sure it doesn't freeze, 895 and if it does, it reboots your computer after a certain amount of 896 time. The card can also monitor the internal temperature of the PC. 897 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>. 898 899 To compile this driver as a module, choose M here: the 900 module will be called pcwd_pci. 901 902 Most people will say N. 903 904config WDTPCI 905 tristate "PCI-WDT500/501 Watchdog timer" 906 depends on PCI 907 ---help--- 908 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N. 909 910 To compile this driver as a module, choose M here: the 911 module will be called wdt_pci. 912 913config WDT_501_PCI 914 bool "PCI-WDT501 features" 915 depends on WDTPCI 916 help 917 Saying Y here and creating a character special file /dev/temperature 918 with major number 10 and minor number 131 ("man mknod") will give 919 you a thermometer inside your computer: reading from 920 /dev/temperature yields one byte, the temperature in degrees 921 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board 922 installed. 923 924 If you want to enable the Fan Tachometer on the PCI-WDT501, then you 925 can do this via the tachometer parameter. Only do this if you have a 926 fan tachometer actually set up. 927 928# 929# USB-based Watchdog Cards 930# 931 932comment "USB-based Watchdog Cards" 933 depends on USB 934 935config USBPCWATCHDOG 936 tristate "Berkshire Products USB-PC Watchdog" 937 depends on USB 938 ---help--- 939 This is the driver for the Berkshire Products USB-PC Watchdog card. 940 This card simply watches your kernel to make sure it doesn't freeze, 941 and if it does, it reboots your computer after a certain amount of 942 time. The card can also monitor the internal temperature of the PC. 943 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>. 944 945 To compile this driver as a module, choose M here: the 946 module will be called pcwd_usb. 947 948 Most people will say N. 949 950endif # WATCHDOG 951