Kconfig 35 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096
  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_OMAP2PLUS
  160. help
  161. Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
  162. here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 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. config TS72XX_WATCHDOG
  242. tristate "TS-72XX SBC Watchdog"
  243. depends on MACH_TS72XX
  244. help
  245. Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
  246. watchdog timer implemented in a external CPLD chip. Say Y here
  247. if you want to support for the watchdog timer on TS-72XX boards.
  248. To compile this driver as a module, choose M here: the
  249. module will be called ts72xx_wdt.
  250. config MAX63XX_WATCHDOG
  251. tristate "Max63xx watchdog"
  252. depends on ARM && HAS_IOMEM
  253. help
  254. Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
  255. # AVR32 Architecture
  256. config AT32AP700X_WDT
  257. tristate "AT32AP700x watchdog"
  258. depends on CPU_AT32AP700X
  259. help
  260. Watchdog timer embedded into AT32AP700x devices. This will reboot
  261. your system when the timeout is reached.
  262. # BLACKFIN Architecture
  263. config BFIN_WDT
  264. tristate "Blackfin On-Chip Watchdog Timer"
  265. depends on BLACKFIN
  266. ---help---
  267. If you say yes here you will get support for the Blackfin On-Chip
  268. Watchdog Timer. If you have one of these processors and wish to
  269. have watchdog support enabled, say Y, otherwise say N.
  270. To compile this driver as a module, choose M here: the
  271. module will be called bfin_wdt.
  272. # CRIS Architecture
  273. # FRV Architecture
  274. # H8300 Architecture
  275. # X86 (i386 + ia64 + x86_64) Architecture
  276. config ACQUIRE_WDT
  277. tristate "Acquire SBC Watchdog Timer"
  278. depends on X86
  279. ---help---
  280. This is the driver for the hardware watchdog on Single Board
  281. Computers produced by Acquire Inc (and others). This watchdog
  282. simply watches your kernel to make sure it doesn't freeze, and if
  283. it does, it reboots your computer after a certain amount of time.
  284. To compile this driver as a module, choose M here: the
  285. module will be called acquirewdt.
  286. Most people will say N.
  287. config ADVANTECH_WDT
  288. tristate "Advantech SBC Watchdog Timer"
  289. depends on X86
  290. help
  291. If you are configuring a Linux kernel for the Advantech single-board
  292. computer, say `Y' here to support its built-in watchdog timer
  293. feature. More information can be found at
  294. <http://www.advantech.com.tw/products/>
  295. config ALIM1535_WDT
  296. tristate "ALi M1535 PMU Watchdog Timer"
  297. depends on X86 && PCI
  298. ---help---
  299. This is the driver for the hardware watchdog on the ALi M1535 PMU.
  300. To compile this driver as a module, choose M here: the
  301. module will be called alim1535_wdt.
  302. Most people will say N.
  303. config ALIM7101_WDT
  304. tristate "ALi M7101 PMU Computer Watchdog"
  305. depends on PCI
  306. help
  307. This is the driver for the hardware watchdog on the ALi M7101 PMU
  308. as used in the x86 Cobalt servers and also found in some
  309. SPARC Netra servers too.
  310. To compile this driver as a module, choose M here: the
  311. module will be called alim7101_wdt.
  312. Most people will say N.
  313. config GEODE_WDT
  314. tristate "AMD Geode CS5535/CS5536 Watchdog"
  315. depends on CS5535_MFGPT
  316. help
  317. This driver enables a watchdog capability built into the
  318. CS5535/CS5536 companion chips for the AMD Geode GX and LX
  319. processors. This watchdog watches your kernel to make sure
  320. it doesn't freeze, and if it does, it reboots your computer after
  321. a certain amount of time.
  322. You can compile this driver directly into the kernel, or use
  323. it as a module. The module will be called geodewdt.
  324. config SC520_WDT
  325. tristate "AMD Elan SC520 processor Watchdog"
  326. depends on X86
  327. help
  328. This is the driver for the hardware watchdog built in to the
  329. AMD "Elan" SC520 microcomputer commonly used in embedded systems.
  330. This watchdog simply watches your kernel to make sure it doesn't
  331. freeze, and if it does, it reboots your computer after a certain
  332. amount of time.
  333. You can compile this driver directly into the kernel, or use
  334. it as a module. The module will be called sc520_wdt.
  335. config SBC_FITPC2_WATCHDOG
  336. tristate "Compulab SBC-FITPC2 watchdog"
  337. depends on X86
  338. ---help---
  339. This is the driver for the built-in watchdog timer on the fit-PC2,
  340. fit-PC2i, CM-iAM single-board computers made by Compulab.
  341. It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
  342. When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
  343. Entering BIOS setup temporary disables watchdog operation regardless to current state,
  344. so system will not be restarted while user in BIOS setup.
  345. Once watchdog was enabled the system will be restarted every
  346. "Watchdog Timer Value" period, so to prevent it user can restart or
  347. disable the watchdog.
  348. To compile this driver as a module, choose M here: the
  349. module will be called sbc_fitpc2_wdt.
  350. Most people will say N.
  351. config EUROTECH_WDT
  352. tristate "Eurotech CPU-1220/1410 Watchdog Timer"
  353. depends on X86
  354. help
  355. Enable support for the watchdog timer on the Eurotech CPU-1220 and
  356. CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
  357. information are at <http://www.eurotech.it/>.
  358. config IB700_WDT
  359. tristate "IB700 SBC Watchdog Timer"
  360. depends on X86
  361. ---help---
  362. This is the driver for the hardware watchdog on the IB700 Single
  363. Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
  364. simply watches your kernel to make sure it doesn't freeze, and if
  365. it does, it reboots your computer after a certain amount of time.
  366. This driver is like the WDT501 driver but for slightly different hardware.
  367. To compile this driver as a module, choose M here: the
  368. module will be called ib700wdt.
  369. Most people will say N.
  370. config IBMASR
  371. tristate "IBM Automatic Server Restart"
  372. depends on X86
  373. help
  374. This is the driver for the IBM Automatic Server Restart watchdog
  375. timer built-in into some eServer xSeries machines.
  376. To compile this driver as a module, choose M here: the
  377. module will be called ibmasr.
  378. config WAFER_WDT
  379. tristate "ICP Single Board Computer Watchdog Timer"
  380. depends on X86
  381. help
  382. This is a driver for the hardware watchdog on the ICP Single
  383. Board Computer. This driver is working on (at least) the following
  384. IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
  385. To compile this driver as a module, choose M here: the
  386. module will be called wafer5823wdt.
  387. config I6300ESB_WDT
  388. tristate "Intel 6300ESB Timer/Watchdog"
  389. depends on X86 && PCI
  390. ---help---
  391. Hardware driver for the watchdog timer built into the Intel
  392. 6300ESB controller hub.
  393. To compile this driver as a module, choose M here: the
  394. module will be called i6300esb.
  395. config ITCO_WDT
  396. tristate "Intel TCO Timer/Watchdog"
  397. depends on (X86 || IA64) && PCI
  398. ---help---
  399. Hardware driver for the intel TCO timer based watchdog devices.
  400. These drivers are included in the Intel 82801 I/O Controller
  401. Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
  402. controller hub.
  403. The TCO (Total Cost of Ownership) timer is a watchdog timer
  404. that will reboot the machine after its second expiration. The
  405. expiration time can be configured with the "heartbeat" parameter.
  406. On some motherboards the driver may fail to reset the chipset's
  407. NO_REBOOT flag which prevents the watchdog from rebooting the
  408. machine. If this is the case you will get a kernel message like
  409. "failed to reset NO_REBOOT flag, reboot disabled by hardware".
  410. To compile this driver as a module, choose M here: the
  411. module will be called iTCO_wdt.
  412. config ITCO_VENDOR_SUPPORT
  413. bool "Intel TCO Timer/Watchdog Specific Vendor Support"
  414. depends on ITCO_WDT
  415. ---help---
  416. Add vendor specific support to the intel TCO timer based watchdog
  417. devices. At this moment we only have additional support for some
  418. SuperMicro Inc. motherboards.
  419. config IT8712F_WDT
  420. tristate "IT8712F (Smart Guardian) Watchdog Timer"
  421. depends on X86
  422. ---help---
  423. This is the driver for the built-in watchdog timer on the IT8712F
  424. Super I/0 chipset used on many motherboards.
  425. To compile this driver as a module, choose M here: the
  426. module will be called it8712f_wdt.
  427. config IT87_WDT
  428. tristate "IT87 Watchdog Timer"
  429. depends on X86 && EXPERIMENTAL
  430. ---help---
  431. This is the driver for the hardware watchdog on the ITE IT8716,
  432. IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
  433. simply watches your kernel to make sure it doesn't freeze, and if
  434. it does, it reboots your computer after a certain amount of time.
  435. To compile this driver as a module, choose M here: the module will
  436. be called it87_wdt.
  437. config HP_WATCHDOG
  438. tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
  439. depends on X86
  440. help
  441. A software monitoring watchdog and NMI sourcing driver. This driver
  442. will detect lockups and provide stack trace. Also, when an NMI
  443. occurs this driver will make the necessary BIOS calls to log
  444. the cause of the NMI. This is a driver that will only load on a
  445. HP ProLiant system with a minimum of iLO2 support.
  446. To compile this driver as a module, choose M here: the
  447. module will be called hpwdt.
  448. config SC1200_WDT
  449. tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
  450. depends on X86
  451. help
  452. This is a driver for National Semiconductor PC87307/PC97307 hardware
  453. watchdog cards as found on the SC1200. This watchdog is mainly used
  454. for power management purposes and can be used to power down the device
  455. during inactivity periods (includes interrupt activity monitoring).
  456. To compile this driver as a module, choose M here: the
  457. module will be called sc1200wdt.
  458. Most people will say N.
  459. config SCx200_WDT
  460. tristate "National Semiconductor SCx200 Watchdog"
  461. depends on SCx200 && PCI
  462. help
  463. Enable the built-in watchdog timer support on the National
  464. Semiconductor SCx200 processors.
  465. If compiled as a module, it will be called scx200_wdt.
  466. config PC87413_WDT
  467. tristate "NS PC87413 watchdog"
  468. depends on X86
  469. ---help---
  470. This is the driver for the hardware watchdog on the PC87413 chipset
  471. This watchdog simply watches your kernel to make sure it doesn't
  472. freeze, and if it does, it reboots your computer after a certain
  473. amount of time.
  474. To compile this driver as a module, choose M here: the
  475. module will be called pc87413_wdt.
  476. Most people will say N.
  477. config RDC321X_WDT
  478. tristate "RDC R-321x SoC watchdog"
  479. depends on X86_RDC321X
  480. help
  481. This is the driver for the built in hardware watchdog
  482. in the RDC R-321x SoC.
  483. To compile this driver as a module, choose M here: the
  484. module will be called rdc321x_wdt.
  485. config 60XX_WDT
  486. tristate "SBC-60XX Watchdog Timer"
  487. depends on X86
  488. help
  489. This driver can be used with the watchdog timer found on some
  490. single board computers, namely the 6010 PII based computer.
  491. It may well work with other cards. It reads port 0x443 to enable
  492. and re-set the watchdog timer, and reads port 0x45 to disable
  493. the watchdog. If you have a card that behave in similar ways,
  494. you can probably make this driver work with your card as well.
  495. You can compile this driver directly into the kernel, or use
  496. it as a module. The module will be called sbc60xxwdt.
  497. config SBC8360_WDT
  498. tristate "SBC8360 Watchdog Timer"
  499. depends on X86
  500. ---help---
  501. This is the driver for the hardware watchdog on the SBC8360 Single
  502. Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
  503. To compile this driver as a module, choose M here: the
  504. module will be called sbc8360.
  505. Most people will say N.
  506. config SBC7240_WDT
  507. tristate "SBC Nano 7240 Watchdog Timer"
  508. depends on X86_32
  509. ---help---
  510. This is the driver for the hardware watchdog found on the IEI
  511. single board computers EPIC Nano 7240 (and likely others). This
  512. watchdog simply watches your kernel to make sure it doesn't freeze,
  513. and if it does, it reboots your computer after a certain amount of
  514. time.
  515. To compile this driver as a module, choose M here: the
  516. module will be called sbc7240_wdt.
  517. config CPU5_WDT
  518. tristate "SMA CPU5 Watchdog"
  519. depends on X86
  520. ---help---
  521. TBD.
  522. To compile this driver as a module, choose M here: the
  523. module will be called cpu5wdt.
  524. config SMSC_SCH311X_WDT
  525. tristate "SMSC SCH311X Watchdog Timer"
  526. depends on X86
  527. ---help---
  528. This is the driver for the hardware watchdog timer on the
  529. SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
  530. (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
  531. serial ports).
  532. To compile this driver as a module, choose M here: the
  533. module will be called sch311x_wdt.
  534. config SMSC37B787_WDT
  535. tristate "Winbond SMsC37B787 Watchdog Timer"
  536. depends on X86
  537. ---help---
  538. This is the driver for the hardware watchdog component on the
  539. Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
  540. from Vision Systems and maybe others.
  541. This watchdog simply watches your kernel to make sure it doesn't
  542. freeze, and if it does, it reboots your computer after a certain
  543. amount of time.
  544. Usually a userspace daemon will notify the kernel WDT driver that
  545. userspace is still alive, at regular intervals.
  546. To compile this driver as a module, choose M here: the
  547. module will be called smsc37b787_wdt.
  548. Most people will say N.
  549. config W83627HF_WDT
  550. tristate "W83627HF Watchdog Timer"
  551. depends on X86
  552. ---help---
  553. This is the driver for the hardware watchdog on the W83627HF chipset
  554. as used in Advantech PC-9578 and Tyan S2721-533 motherboards
  555. (and likely others). This watchdog simply watches your kernel to
  556. make sure it doesn't freeze, and if it does, it reboots your computer
  557. after a certain amount of time.
  558. To compile this driver as a module, choose M here: the
  559. module will be called w83627hf_wdt.
  560. Most people will say N.
  561. config W83697HF_WDT
  562. tristate "W83697HF/W83697HG Watchdog Timer"
  563. depends on X86
  564. ---help---
  565. This is the driver for the hardware watchdog on the W83697HF/HG
  566. chipset as used in Dedibox/VIA motherboards (and likely others).
  567. This watchdog simply watches your kernel to make sure it doesn't
  568. freeze, and if it does, it reboots your computer after a certain
  569. amount of time.
  570. To compile this driver as a module, choose M here: the
  571. module will be called w83697hf_wdt.
  572. Most people will say N.
  573. config W83697UG_WDT
  574. tristate "W83697UG/W83697UF Watchdog Timer"
  575. depends on X86
  576. ---help---
  577. This is the driver for the hardware watchdog on the W83697UG/UF
  578. chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
  579. This watchdog simply watches your kernel to make sure it doesn't
  580. freeze, and if it does, it reboots your computer after a certain
  581. amount of time.
  582. To compile this driver as a module, choose M here: the
  583. module will be called w83697ug_wdt.
  584. Most people will say N.
  585. config W83877F_WDT
  586. tristate "W83877F (EMACS) Watchdog Timer"
  587. depends on X86
  588. ---help---
  589. This is the driver for the hardware watchdog on the W83877F chipset
  590. as used in EMACS PC-104 motherboards (and likely others). This
  591. watchdog simply watches your kernel to make sure it doesn't freeze,
  592. and if it does, it reboots your computer after a certain amount of
  593. time.
  594. To compile this driver as a module, choose M here: the
  595. module will be called w83877f_wdt.
  596. Most people will say N.
  597. config W83977F_WDT
  598. tristate "W83977F (PCM-5335) Watchdog Timer"
  599. depends on X86
  600. ---help---
  601. This is the driver for the hardware watchdog on the W83977F I/O chip
  602. as used in AAEON's PCM-5335 SBC (and likely others). This
  603. watchdog simply watches your kernel to make sure it doesn't freeze,
  604. and if it does, it reboots your computer after a certain amount of
  605. time.
  606. To compile this driver as a module, choose M here: the
  607. module will be called w83977f_wdt.
  608. config MACHZ_WDT
  609. tristate "ZF MachZ Watchdog"
  610. depends on X86
  611. ---help---
  612. If you are using a ZF Micro MachZ processor, say Y here, otherwise
  613. N. This is the driver for the watchdog timer built-in on that
  614. processor using ZF-Logic interface. This watchdog simply watches
  615. your kernel to make sure it doesn't freeze, and if it does, it
  616. reboots your computer after a certain amount of time.
  617. To compile this driver as a module, choose M here: the
  618. module will be called machzwd.
  619. config SBC_EPX_C3_WATCHDOG
  620. tristate "Winsystems SBC EPX-C3 watchdog"
  621. depends on X86
  622. ---help---
  623. This is the driver for the built-in watchdog timer on the EPX-C3
  624. Single-board computer made by Winsystems, Inc.
  625. *Note*: This hardware watchdog is not probeable and thus there
  626. is no way to know if writing to its IO address will corrupt
  627. your system or have any real effect. The only way to be sure
  628. that this driver does what you want is to make sure you
  629. are running it on an EPX-C3 from Winsystems with the watchdog
  630. timer at IO address 0x1ee and 0x1ef. It will write to both those
  631. IO ports. Basically, the assumption is made that if you compile
  632. this driver into your kernel and/or load it as a module, that you
  633. know what you are doing and that you are in fact running on an
  634. EPX-C3 board!
  635. To compile this driver as a module, choose M here: the
  636. module will be called sbc_epx_c3.
  637. # M32R Architecture
  638. # M68K Architecture
  639. # M68KNOMMU Architecture
  640. # MIPS Architecture
  641. config BCM47XX_WDT
  642. tristate "Broadcom BCM47xx Watchdog Timer"
  643. depends on BCM47XX
  644. help
  645. Hardware driver for the Broadcom BCM47xx Watchog Timer.
  646. config RC32434_WDT
  647. tristate "IDT RC32434 SoC Watchdog Timer"
  648. depends on MIKROTIK_RB532
  649. help
  650. Hardware driver for the IDT RC32434 SoC built-in
  651. watchdog timer.
  652. To compile this driver as a module, choose M here: the
  653. module will be called rc32434_wdt.
  654. config INDYDOG
  655. tristate "Indy/I2 Hardware Watchdog"
  656. depends on SGI_HAS_INDYDOG
  657. help
  658. Hardware driver for the Indy's/I2's watchdog. This is a
  659. watchdog timer that will reboot the machine after a 60 second
  660. timer expired and no process has written to /dev/watchdog during
  661. that time.
  662. config WDT_MTX1
  663. tristate "MTX-1 Hardware Watchdog"
  664. depends on MIPS_MTX1
  665. help
  666. Hardware driver for the MTX-1 boards. This is a watchdog timer that
  667. will reboot the machine after a 100 seconds timer expired.
  668. config PNX833X_WDT
  669. tristate "PNX833x Hardware Watchdog"
  670. depends on SOC_PNX8335
  671. help
  672. Hardware driver for the PNX833x's watchdog. This is a
  673. watchdog timer that will reboot the machine after a programable
  674. timer has expired and no process has written to /dev/watchdog during
  675. that time.
  676. config SIBYTE_WDOG
  677. tristate "Sibyte SoC hardware watchdog"
  678. depends on CPU_SB1
  679. help
  680. Watchdog driver for the built in watchdog hardware in Sibyte
  681. SoC processors. There are apparently two watchdog timers
  682. on such processors; this driver supports only the first one,
  683. because currently Linux only supports exporting one watchdog
  684. to userspace.
  685. To compile this driver as a loadable module, choose M here.
  686. The module will be called sb_wdog.
  687. config AR7_WDT
  688. tristate "TI AR7 Watchdog Timer"
  689. depends on AR7
  690. help
  691. Hardware driver for the TI AR7 Watchdog Timer.
  692. config TXX9_WDT
  693. tristate "Toshiba TXx9 Watchdog Timer"
  694. depends on CPU_TX39XX || CPU_TX49XX
  695. help
  696. Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
  697. # PARISC Architecture
  698. # POWERPC Architecture
  699. config GEF_WDT
  700. tristate "GE Watchdog Timer"
  701. depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
  702. ---help---
  703. Watchdog timer found in a number of GE single board computers.
  704. config MPC5200_WDT
  705. bool "MPC52xx Watchdog Timer"
  706. depends on PPC_MPC52xx
  707. help
  708. Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
  709. config 8xxx_WDT
  710. tristate "MPC8xxx Platform Watchdog Timer"
  711. depends on PPC_8xx || PPC_83xx || PPC_86xx
  712. help
  713. This driver is for a SoC level watchdog that exists on some
  714. Freescale PowerPC processors. So far this driver supports:
  715. - MPC8xx watchdogs
  716. - MPC83xx watchdogs
  717. - MPC86xx watchdogs
  718. For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
  719. config MV64X60_WDT
  720. tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
  721. depends on MV64X60
  722. config PIKA_WDT
  723. tristate "PIKA FPGA Watchdog"
  724. depends on WARP
  725. default y
  726. help
  727. This enables the watchdog in the PIKA FPGA. Currently used on
  728. the Warp platform.
  729. config BOOKE_WDT
  730. bool "PowerPC Book-E Watchdog Timer"
  731. depends on BOOKE || 4xx
  732. ---help---
  733. Please see Documentation/watchdog/watchdog-api.txt for
  734. more information.
  735. # PPC64 Architecture
  736. config WATCHDOG_RTAS
  737. tristate "RTAS watchdog"
  738. depends on PPC_RTAS
  739. help
  740. This driver adds watchdog support for the RTAS watchdog.
  741. To compile this driver as a module, choose M here. The module
  742. will be called wdrtas.
  743. # S390 Architecture
  744. config ZVM_WATCHDOG
  745. tristate "z/VM Watchdog Timer"
  746. depends on S390
  747. help
  748. IBM s/390 and zSeries machines running under z/VM 5.1 or later
  749. provide a virtual watchdog timer to their guest that cause a
  750. user define Control Program command to be executed after a
  751. timeout.
  752. To compile this driver as a module, choose M here. The module
  753. will be called vmwatchdog.
  754. # SUPERH (sh + sh64) Architecture
  755. config SH_WDT
  756. tristate "SuperH Watchdog"
  757. depends on SUPERH && (CPU_SH3 || CPU_SH4)
  758. help
  759. This driver adds watchdog support for the integrated watchdog in the
  760. SuperH processors. If you have one of these processors and wish
  761. to have watchdog support enabled, say Y, otherwise say N.
  762. As a side note, saying Y here will automatically boost HZ to 1000
  763. so that the timer has a chance to clear the overflow counter. On
  764. slower systems (such as the SH-2 and SH-3) this will likely yield
  765. some performance issues. As such, the WDT should be avoided here
  766. unless it is absolutely necessary.
  767. To compile this driver as a module, choose M here: the
  768. module will be called shwdt.
  769. config SH_WDT_MMAP
  770. bool "Allow mmap of SH WDT"
  771. default n
  772. depends on SH_WDT
  773. help
  774. If you say Y here, user applications will be able to mmap the
  775. WDT/CPG registers.
  776. # SPARC Architecture
  777. # SPARC64 Architecture
  778. config WATCHDOG_CP1XXX
  779. tristate "CP1XXX Hardware Watchdog support"
  780. depends on SPARC64 && PCI
  781. ---help---
  782. This is the driver for the hardware watchdog timers present on
  783. Sun Microsystems CompactPCI models CP1400 and CP1500.
  784. To compile this driver as a module, choose M here: the
  785. module will be called cpwatchdog.
  786. If you do not have a CompactPCI model CP1400 or CP1500, or
  787. another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
  788. you should say N to this option.
  789. config WATCHDOG_RIO
  790. tristate "RIO Hardware Watchdog support"
  791. depends on SPARC64 && PCI
  792. help
  793. Say Y here to support the hardware watchdog capability on Sun RIO
  794. machines. The watchdog timeout period is normally one minute but
  795. can be changed with a boot-time parameter.
  796. # XTENSA Architecture
  797. #
  798. # ISA-based Watchdog Cards
  799. #
  800. comment "ISA-based Watchdog Cards"
  801. depends on ISA
  802. config PCWATCHDOG
  803. tristate "Berkshire Products ISA-PC Watchdog"
  804. depends on ISA
  805. ---help---
  806. This is the driver for the Berkshire Products ISA-PC Watchdog card.
  807. This card simply watches your kernel to make sure it doesn't freeze,
  808. and if it does, it reboots your computer after a certain amount of
  809. time. This driver is like the WDT501 driver but for different
  810. hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
  811. watchdog cards can be ordered from <http://www.berkprod.com/>.
  812. To compile this driver as a module, choose M here: the
  813. module will be called pcwd.
  814. Most people will say N.
  815. config MIXCOMWD
  816. tristate "Mixcom Watchdog"
  817. depends on ISA
  818. ---help---
  819. This is a driver for the Mixcom hardware watchdog cards. This
  820. watchdog simply watches your kernel to make sure it doesn't freeze,
  821. and if it does, it reboots your computer after a certain amount of
  822. time.
  823. To compile this driver as a module, choose M here: the
  824. module will be called mixcomwd.
  825. Most people will say N.
  826. config WDT
  827. tristate "WDT Watchdog timer"
  828. depends on ISA
  829. ---help---
  830. If you have a WDT500P or WDT501P watchdog board, say Y here,
  831. otherwise N. It is not possible to probe for this board, which means
  832. that you have to inform the kernel about the IO port and IRQ that
  833. is needed (you can do this via the io and irq parameters)
  834. To compile this driver as a module, choose M here: the
  835. module will be called wdt.
  836. #
  837. # PCI-based Watchdog Cards
  838. #
  839. comment "PCI-based Watchdog Cards"
  840. depends on PCI
  841. config PCIPCWATCHDOG
  842. tristate "Berkshire Products PCI-PC Watchdog"
  843. depends on PCI
  844. ---help---
  845. This is the driver for the Berkshire Products PCI-PC Watchdog card.
  846. This card simply watches your kernel to make sure it doesn't freeze,
  847. and if it does, it reboots your computer after a certain amount of
  848. time. The card can also monitor the internal temperature of the PC.
  849. More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
  850. To compile this driver as a module, choose M here: the
  851. module will be called pcwd_pci.
  852. Most people will say N.
  853. config WDTPCI
  854. tristate "PCI-WDT500/501 Watchdog timer"
  855. depends on PCI
  856. ---help---
  857. If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
  858. If you have a PCI-WDT501 watchdog board then you can enable the
  859. temperature sensor by setting the type parameter to 501.
  860. If you want to enable the Fan Tachometer on the PCI-WDT501, then you
  861. can do this via the tachometer parameter. Only do this if you have a
  862. fan tachometer actually set up.
  863. To compile this driver as a module, choose M here: the
  864. module will be called wdt_pci.
  865. #
  866. # USB-based Watchdog Cards
  867. #
  868. comment "USB-based Watchdog Cards"
  869. depends on USB
  870. config USBPCWATCHDOG
  871. tristate "Berkshire Products USB-PC Watchdog"
  872. depends on USB
  873. ---help---
  874. This is the driver for the Berkshire Products USB-PC Watchdog card.
  875. This card simply watches your kernel to make sure it doesn't freeze,
  876. and if it does, it reboots your computer after a certain amount of
  877. time. The card can also monitor the internal temperature of the PC.
  878. More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
  879. To compile this driver as a module, choose M here: the
  880. module will be called pcwd_usb.
  881. Most people will say N.
  882. endif # WATCHDOG