Kconfig 35 KB

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