Kconfig 34 KB

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