Kconfig 26 KB

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