Kconfig 34 KB

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