Kconfig 31 KB

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