Kconfig 31 KB

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