Kconfig 41 KB

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