Kconfig 32 KB

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