Kconfig 28 KB

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