Kconfig 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559
  1. #
  2. # Watchdog device configuration
  3. #
  4. menu "Watchdog Cards"
  5. config WATCHDOG
  6. bool "Watchdog Timer Support"
  7. ---help---
  8. If you say Y here (and to one of the following options) and create a
  9. character special file /dev/watchdog with major number 10 and minor
  10. number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
  11. subsequently opening the file and then failing to write to it for
  12. longer than 1 minute will result in rebooting the machine. This
  13. could be useful for a networked machine that needs to come back
  14. online as fast as possible after a lock-up. There's both a watchdog
  15. implementation entirely in software (which can sometimes fail to
  16. reboot the machine) and a driver for hardware watchdog boards, which
  17. are more robust and can also keep track of the temperature inside
  18. your computer. For details, read <file:Documentation/watchdog/watchdog.txt>
  19. in the kernel source.
  20. The watchdog is usually used together with the watchdog daemon
  21. which is available from
  22. <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
  23. also monitor NFS connections and can reboot the machine when the process
  24. table is full.
  25. If unsure, say N.
  26. config WATCHDOG_NOWAYOUT
  27. bool "Disable watchdog shutdown on close"
  28. depends on WATCHDOG
  29. help
  30. The default watchdog behaviour (which you get if you say N here) is
  31. to stop the timer if the process managing it closes the file
  32. /dev/watchdog. It's always remotely possible that this process might
  33. get killed. If you say Y here, the watchdog cannot be stopped once
  34. it has been started.
  35. #
  36. # General Watchdog drivers
  37. #
  38. comment "Watchdog Device Drivers"
  39. depends on WATCHDOG
  40. # Architecture Independant
  41. config SOFT_WATCHDOG
  42. tristate "Software watchdog"
  43. depends on WATCHDOG
  44. help
  45. A software monitoring watchdog. This will fail to reboot your system
  46. from some situations that the hardware watchdog will recover
  47. from. Equally it's a lot cheaper to install.
  48. To compile this driver as a module, choose M here: the
  49. module will be called softdog.
  50. # ARM Architecture
  51. config 21285_WATCHDOG
  52. tristate "DC21285 watchdog"
  53. depends on WATCHDOG && FOOTBRIDGE
  54. help
  55. The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
  56. here if you wish to use this. Alternatively say M to compile the
  57. driver as a module, which will be called wdt285.
  58. This driver does not work on all machines. In particular, early CATS
  59. boards have hardware problems that will cause the machine to simply
  60. lock up if the watchdog fires.
  61. "If in doubt, leave it out" - say N.
  62. config 977_WATCHDOG
  63. tristate "NetWinder WB83C977 watchdog"
  64. depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER
  65. help
  66. Say Y here to include support for the WB977 watchdog included in
  67. NetWinder machines. Alternatively say M to compile the driver as
  68. a module, which will be called wdt977.
  69. Not sure? It's safe to say N.
  70. config IXP4XX_WATCHDOG
  71. tristate "IXP4xx Watchdog"
  72. depends on WATCHDOG && ARCH_IXP4XX
  73. help
  74. Say Y here if to include support for the watchdog timer
  75. in the Intel IXP4xx network processors. This driver can
  76. be built as a module by choosing M. The module will
  77. be called ixp4xx_wdt.
  78. Note: The internal IXP4xx watchdog does a soft CPU reset
  79. which doesn't reset any peripherals. There are circumstances
  80. where the watchdog will fail to reset the board correctly
  81. (e.g., if the boot ROM is in an unreadable state).
  82. Say N if you are unsure.
  83. config IXP2000_WATCHDOG
  84. tristate "IXP2000 Watchdog"
  85. depends on WATCHDOG && ARCH_IXP2000
  86. help
  87. Say Y here if to include support for the watchdog timer
  88. in the Intel IXP2000(2400, 2800, 2850) network processors.
  89. This driver can be built as a module by choosing M. The module
  90. will be called ixp2000_wdt.
  91. Say N if you are unsure.
  92. config S3C2410_WATCHDOG
  93. tristate "S3C2410 Watchdog"
  94. depends on WATCHDOG && ARCH_S3C2410
  95. help
  96. Watchdog timer block in the Samsung S3C2410 chips. This will
  97. reboot the system when the timer expires with the watchdog
  98. enabled.
  99. The driver is limited by the speed of the system's PCLK
  100. signal, so with reasonbaly fast systems (PCLK around 50-66MHz)
  101. then watchdog intervals of over approximately 20seconds are
  102. unavailable.
  103. The driver can be built as a module by choosing M, and will
  104. be called s3c2410_wdt
  105. config SA1100_WATCHDOG
  106. tristate "SA1100/PXA2xx watchdog"
  107. depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA )
  108. help
  109. Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
  110. reboot your system when timeout is reached.
  111. NOTE: once enabled, this timer cannot be disabled.
  112. To compile this driver as a module, choose M here: the
  113. module will be called sa1100_wdt.
  114. # X86 (i386 + ia64 + x86_64) Architecture
  115. config ACQUIRE_WDT
  116. tristate "Acquire SBC Watchdog Timer"
  117. depends on WATCHDOG && X86
  118. ---help---
  119. This is the driver for the hardware watchdog on Single Board
  120. Computers produced by Acquire Inc (and others). This watchdog
  121. simply watches your kernel to make sure it doesn't freeze, and if
  122. it does, it reboots your computer after a certain amount of time.
  123. To compile this driver as a module, choose M here: the
  124. module will be called acquirewdt.
  125. Most people will say N.
  126. config ADVANTECH_WDT
  127. tristate "Advantech SBC Watchdog Timer"
  128. depends on WATCHDOG && X86
  129. help
  130. If you are configuring a Linux kernel for the Advantech single-board
  131. computer, say `Y' here to support its built-in watchdog timer
  132. feature. More information can be found at
  133. <http://www.advantech.com.tw/products/>
  134. config ALIM1535_WDT
  135. tristate "ALi M1535 PMU Watchdog Timer"
  136. depends on WATCHDOG && X86 && PCI
  137. ---help---
  138. This is the driver for the hardware watchdog on the ALi M1535 PMU.
  139. To compile this driver as a module, choose M here: the
  140. module will be called alim1535_wdt.
  141. Most people will say N.
  142. config ALIM7101_WDT
  143. tristate "ALi M7101 PMU Computer Watchdog"
  144. depends on WATCHDOG && X86 && PCI
  145. help
  146. This is the driver for the hardware watchdog on the ALi M7101 PMU
  147. as used in the x86 Cobalt servers.
  148. To compile this driver as a module, choose M here: the
  149. module will be called alim7101_wdt.
  150. Most people will say N.
  151. config SC520_WDT
  152. tristate "AMD Elan SC520 processor Watchdog"
  153. depends on WATCHDOG && X86
  154. help
  155. This is the driver for the hardware watchdog built in to the
  156. AMD "Elan" SC520 microcomputer commonly used in embedded systems.
  157. This watchdog simply watches your kernel to make sure it doesn't
  158. freeze, and if it does, it reboots your computer after a certain
  159. amount of time.
  160. You can compile this driver directly into the kernel, or use
  161. it as a module. The module will be called sc520_wdt.
  162. config EUROTECH_WDT
  163. tristate "Eurotech CPU-1220/1410 Watchdog Timer"
  164. depends on WATCHDOG && X86
  165. help
  166. Enable support for the watchdog timer on the Eurotech CPU-1220 and
  167. CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
  168. information are at <http://www.eurotech.it/>.
  169. config IB700_WDT
  170. tristate "IB700 SBC Watchdog Timer"
  171. depends on WATCHDOG && X86
  172. ---help---
  173. This is the driver for the hardware watchdog on the IB700 Single
  174. Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
  175. simply watches your kernel to make sure it doesn't freeze, and if
  176. it does, it reboots your computer after a certain amount of time.
  177. This driver is like the WDT501 driver but for slightly different hardware.
  178. To compile this driver as a module, choose M here: the
  179. module will be called ib700wdt.
  180. Most people will say N.
  181. config WAFER_WDT
  182. tristate "ICP Wafer 5823 Single Board Computer Watchdog"
  183. depends on WATCHDOG && X86
  184. help
  185. This is a driver for the hardware watchdog on the ICP Wafer 5823
  186. Single Board Computer (and probably other similar models).
  187. To compile this driver as a module, choose M here: the
  188. module will be called wafer5823wdt.
  189. config I8XX_TCO
  190. tristate "Intel i8xx TCO Timer/Watchdog"
  191. depends on WATCHDOG && (X86 || IA64) && PCI
  192. ---help---
  193. Hardware driver for the TCO timer built into the Intel 82801
  194. I/O Controller Hub family. The TCO (Total Cost of Ownership)
  195. timer is a watchdog timer that will reboot the machine after
  196. its second expiration. The expiration time can be configured
  197. with the "heartbeat" parameter.
  198. On some motherboards the driver may fail to reset the chipset's
  199. NO_REBOOT flag which prevents the watchdog from rebooting the
  200. machine. If this is the case you will get a kernel message like
  201. "failed to reset NO_REBOOT flag, reboot disabled by hardware".
  202. To compile this driver as a module, choose M here: the
  203. module will be called i8xx_tco.
  204. config SC1200_WDT
  205. tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
  206. depends on WATCHDOG && X86
  207. help
  208. This is a driver for National Semiconductor PC87307/PC97307 hardware
  209. watchdog cards as found on the SC1200. This watchdog is mainly used
  210. for power management purposes and can be used to power down the device
  211. during inactivity periods (includes interrupt activity monitoring).
  212. To compile this driver as a module, choose M here: the
  213. module will be called sc1200wdt.
  214. Most people will say N.
  215. config SCx200_WDT
  216. tristate "National Semiconductor SCx200 Watchdog"
  217. depends on WATCHDOG && SCx200 && PCI
  218. help
  219. Enable the built-in watchdog timer support on the National
  220. Semiconductor SCx200 processors.
  221. If compiled as a module, it will be called scx200_wdt.
  222. config 60XX_WDT
  223. tristate "SBC-60XX Watchdog Timer"
  224. depends on WATCHDOG && X86
  225. help
  226. This driver can be used with the watchdog timer found on some
  227. single board computers, namely the 6010 PII based computer.
  228. It may well work with other cards. It reads port 0x443 to enable
  229. and re-set the watchdog timer, and reads port 0x45 to disable
  230. the watchdog. If you have a card that behave in similar ways,
  231. you can probably make this driver work with your card as well.
  232. You can compile this driver directly into the kernel, or use
  233. it as a module. The module will be called sbc60xxwdt.
  234. config CPU5_WDT
  235. tristate "SMA CPU5 Watchdog"
  236. depends on WATCHDOG && X86
  237. ---help---
  238. TBD.
  239. To compile this driver as a module, choose M here: the
  240. module will be called cpu5wdt.
  241. config W83627HF_WDT
  242. tristate "W83627HF Watchdog Timer"
  243. depends on WATCHDOG && X86
  244. ---help---
  245. This is the driver for the hardware watchdog on the W83627HF chipset
  246. as used in Advantech PC-9578 and Tyan S2721-533 motherboards
  247. (and likely others). This watchdog simply watches your kernel to
  248. make sure it doesn't freeze, and if it does, it reboots your computer
  249. after a certain amount of time.
  250. To compile this driver as a module, choose M here: the
  251. module will be called w83627hf_wdt.
  252. Most people will say N.
  253. config W83877F_WDT
  254. tristate "W83877F (EMACS) Watchdog Timer"
  255. depends on WATCHDOG && X86
  256. ---help---
  257. This is the driver for the hardware watchdog on the W83877F chipset
  258. as used in EMACS PC-104 motherboards (and likely others). This
  259. watchdog simply watches your kernel to make sure it doesn't freeze,
  260. and if it does, it reboots your computer after a certain amount of
  261. time.
  262. To compile this driver as a module, choose M here: the
  263. module will be called w83877f_wdt.
  264. Most people will say N.
  265. config MACHZ_WDT
  266. tristate "ZF MachZ Watchdog"
  267. depends on WATCHDOG && X86
  268. ---help---
  269. If you are using a ZF Micro MachZ processor, say Y here, otherwise
  270. N. This is the driver for the watchdog timer builtin on that
  271. processor using ZF-Logic interface. This watchdog simply watches
  272. your kernel to make sure it doesn't freeze, and if it does, it
  273. reboots your computer after a certain amount of time.
  274. To compile this driver as a module, choose M here: the
  275. module will be called machzwd.
  276. # PowerPC Architecture
  277. config 8xx_WDT
  278. tristate "MPC8xx Watchdog Timer"
  279. depends on WATCHDOG && 8xx
  280. # MIPS Architecture
  281. config INDYDOG
  282. tristate "Indy/I2 Hardware Watchdog"
  283. depends on WATCHDOG && SGI_IP22
  284. help
  285. Hardwaredriver for the Indy's/I2's watchdog. This is a
  286. watchdog timer that will reboot the machine after a 60 second
  287. timer expired and no process has written to /dev/watchdog during
  288. that time.
  289. # S390 Architecture
  290. config ZVM_WATCHDOG
  291. tristate "z/VM Watchdog Timer"
  292. depends on WATCHDOG && ARCH_S390
  293. help
  294. IBM s/390 and zSeries machines running under z/VM 5.1 or later
  295. provide a virtual watchdog timer to their guest that cause a
  296. user define Control Program command to be executed after a
  297. timeout.
  298. To compile this driver as a module, choose M here. The module
  299. will be called vmwatchdog.
  300. # SUPERH Architecture
  301. config SH_WDT
  302. tristate "SuperH Watchdog"
  303. depends on WATCHDOG && SUPERH
  304. help
  305. This driver adds watchdog support for the integrated watchdog in the
  306. SuperH processors. If you have one of these processors and wish
  307. to have watchdog support enabled, say Y, otherwise say N.
  308. As a side note, saying Y here will automatically boost HZ to 1000
  309. so that the timer has a chance to clear the overflow counter. On
  310. slower systems (such as the SH-2 and SH-3) this will likely yield
  311. some performance issues. As such, the WDT should be avoided here
  312. unless it is absolutely necessary.
  313. To compile this driver as a module, choose M here: the
  314. module will be called shwdt.
  315. # SPARC64 Architecture
  316. config WATCHDOG_CP1XXX
  317. tristate "CP1XXX Hardware Watchdog support"
  318. depends on WATCHDOG && SPARC64 && PCI
  319. ---help---
  320. This is the driver for the hardware watchdog timers present on
  321. Sun Microsystems CompactPCI models CP1400 and CP1500.
  322. To compile this driver as a module, choose M here: the
  323. module will be called cpwatchdog.
  324. If you do not have a CompactPCI model CP1400 or CP1500, or
  325. another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
  326. you should say N to this option.
  327. config WATCHDOG_RIO
  328. tristate "RIO Hardware Watchdog support"
  329. depends on WATCHDOG && SPARC64 && PCI
  330. help
  331. Say Y here to support the hardware watchdog capability on Sun RIO
  332. machines. The watchdog timeout period is normally one minute but
  333. can be changed with a boot-time parameter.
  334. # ppc64 RTAS watchdog
  335. config WATCHDOG_RTAS
  336. tristate "RTAS watchdog"
  337. depends on WATCHDOG && PPC_RTAS
  338. help
  339. This driver adds watchdog support for the RTAS watchdog.
  340. To compile this driver as a module, choose M here. The module
  341. will be called wdrtas.
  342. #
  343. # ISA-based Watchdog Cards
  344. #
  345. comment "ISA-based Watchdog Cards"
  346. depends on WATCHDOG && ISA
  347. config PCWATCHDOG
  348. tristate "Berkshire Products ISA-PC Watchdog"
  349. depends on WATCHDOG && ISA
  350. ---help---
  351. This is the driver for the Berkshire Products ISA-PC Watchdog card.
  352. This card simply watches your kernel to make sure it doesn't freeze,
  353. and if it does, it reboots your computer after a certain amount of
  354. time. This driver is like the WDT501 driver but for different
  355. hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
  356. watchdog cards can be ordered from <http://www.berkprod.com/>.
  357. To compile this driver as a module, choose M here: the
  358. module will be called pcwd.
  359. Most people will say N.
  360. config MIXCOMWD
  361. tristate "Mixcom Watchdog"
  362. depends on WATCHDOG && ISA
  363. ---help---
  364. This is a driver for the Mixcom hardware watchdog cards. This
  365. watchdog simply watches your kernel to make sure it doesn't freeze,
  366. and if it does, it reboots your computer after a certain amount of
  367. time.
  368. To compile this driver as a module, choose M here: the
  369. module will be called mixcomwd.
  370. Most people will say N.
  371. config WDT
  372. tristate "WDT Watchdog timer"
  373. depends on WATCHDOG && ISA
  374. ---help---
  375. If you have a WDT500P or WDT501P watchdog board, say Y here,
  376. otherwise N. It is not possible to probe for this board, which means
  377. that you have to inform the kernel about the IO port and IRQ that
  378. is needed (you can do this via the io and irq parameters)
  379. To compile this driver as a module, choose M here: the
  380. module will be called wdt.
  381. config WDT_501
  382. bool "WDT501 features"
  383. depends on WDT
  384. help
  385. Saying Y here and creating a character special file /dev/temperature
  386. with major number 10 and minor number 131 ("man mknod") will give
  387. you a thermometer inside your computer: reading from
  388. /dev/temperature yields one byte, the temperature in degrees
  389. Fahrenheit. This works only if you have a WDT501P watchdog board
  390. installed.
  391. If you want to enable the Fan Tachometer on the WDT501P, then you
  392. can do this via the tachometer parameter. Only do this if you have a
  393. fan tachometer actually set up.
  394. #
  395. # PCI-based Watchdog Cards
  396. #
  397. comment "PCI-based Watchdog Cards"
  398. depends on WATCHDOG && PCI
  399. config PCIPCWATCHDOG
  400. tristate "Berkshire Products PCI-PC Watchdog"
  401. depends on WATCHDOG && PCI
  402. ---help---
  403. This is the driver for the Berkshire Products PCI-PC Watchdog card.
  404. This card simply watches your kernel to make sure it doesn't freeze,
  405. and if it does, it reboots your computer after a certain amount of
  406. time. The card can also monitor the internal temperature of the PC.
  407. More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
  408. To compile this driver as a module, choose M here: the
  409. module will be called pcwd_pci.
  410. Most people will say N.
  411. config WDTPCI
  412. tristate "PCI-WDT500/501 Watchdog timer"
  413. depends on WATCHDOG && PCI
  414. ---help---
  415. If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
  416. To compile this driver as a module, choose M here: the
  417. module will be called wdt_pci.
  418. config WDT_501_PCI
  419. bool "PCI-WDT501 features"
  420. depends on WDTPCI
  421. help
  422. Saying Y here and creating a character special file /dev/temperature
  423. with major number 10 and minor number 131 ("man mknod") will give
  424. you a thermometer inside your computer: reading from
  425. /dev/temperature yields one byte, the temperature in degrees
  426. Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
  427. installed.
  428. If you want to enable the Fan Tachometer on the PCI-WDT501, then you
  429. can do this via the tachometer parameter. Only do this if you have a
  430. fan tachometer actually set up.
  431. #
  432. # USB-based Watchdog Cards
  433. #
  434. comment "USB-based Watchdog Cards"
  435. depends on WATCHDOG && USB
  436. config USBPCWATCHDOG
  437. tristate "Berkshire Products USB-PC Watchdog"
  438. depends on WATCHDOG && USB
  439. ---help---
  440. This is the driver for the Berkshire Products USB-PC Watchdog card.
  441. This card simply watches your kernel to make sure it doesn't freeze,
  442. and if it does, it reboots your computer after a certain amount of
  443. time. The card can also monitor the internal temperature of the PC.
  444. More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
  445. To compile this driver as a module, choose M here: the
  446. module will be called pcwd_usb.
  447. Most people will say N.
  448. endmenu