Kconfig 36 KB

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