Kconfig 40 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251
  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 WM831X_WATCHDOG
  48. tristate "WM831x watchdog"
  49. depends on MFD_WM831X
  50. help
  51. Support for the watchdog in the WM831x AudioPlus PMICs. When
  52. the watchdog triggers the system will be reset.
  53. config WM8350_WATCHDOG
  54. tristate "WM8350 watchdog"
  55. depends on MFD_WM8350
  56. help
  57. Support for the watchdog in the WM8350 AudioPlus PMIC. When
  58. the watchdog triggers the system will be reset.
  59. # ALPHA Architecture
  60. # ARM Architecture
  61. config ARM_SP805_WATCHDOG
  62. tristate "ARM SP805 Watchdog"
  63. depends on ARM_AMBA
  64. help
  65. ARM Primecell SP805 Watchdog timer. This will reboot your system when
  66. the timeout is reached.
  67. config AT91RM9200_WATCHDOG
  68. tristate "AT91RM9200 watchdog"
  69. depends on ARCH_AT91RM9200
  70. help
  71. Watchdog timer embedded into AT91RM9200 chips. This will reboot your
  72. system when the timeout is reached.
  73. config AT91SAM9X_WATCHDOG
  74. tristate "AT91SAM9X / AT91CAP9 watchdog"
  75. depends on ARCH_AT91 && !ARCH_AT91RM9200
  76. help
  77. Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
  78. reboot your system when the timeout is reached.
  79. config 21285_WATCHDOG
  80. tristate "DC21285 watchdog"
  81. depends on FOOTBRIDGE
  82. help
  83. The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
  84. here if you wish to use this. Alternatively say M to compile the
  85. driver as a module, which will be called wdt285.
  86. This driver does not work on all machines. In particular, early CATS
  87. boards have hardware problems that will cause the machine to simply
  88. lock up if the watchdog fires.
  89. "If in doubt, leave it out" - say N.
  90. config 977_WATCHDOG
  91. tristate "NetWinder WB83C977 watchdog"
  92. depends on FOOTBRIDGE && ARCH_NETWINDER
  93. help
  94. Say Y here to include support for the WB977 watchdog included in
  95. NetWinder machines. Alternatively say M to compile the driver as
  96. a module, which will be called wdt977.
  97. Not sure? It's safe to say N.
  98. config IXP2000_WATCHDOG
  99. tristate "IXP2000 Watchdog"
  100. depends on ARCH_IXP2000
  101. help
  102. Say Y here if to include support for the watchdog timer
  103. in the Intel IXP2000(2400, 2800, 2850) network processors.
  104. This driver can be built as a module by choosing M. The module
  105. will be called ixp2000_wdt.
  106. Say N if you are unsure.
  107. config IXP4XX_WATCHDOG
  108. tristate "IXP4xx Watchdog"
  109. depends on ARCH_IXP4XX
  110. help
  111. Say Y here if to include support for the watchdog timer
  112. in the Intel IXP4xx network processors. This driver can
  113. be built as a module by choosing M. The module will
  114. be called ixp4xx_wdt.
  115. Note: The internal IXP4xx watchdog does a soft CPU reset
  116. which doesn't reset any peripherals. There are circumstances
  117. where the watchdog will fail to reset the board correctly
  118. (e.g., if the boot ROM is in an unreadable state).
  119. Say N if you are unsure.
  120. config KS8695_WATCHDOG
  121. tristate "KS8695 watchdog"
  122. depends on ARCH_KS8695
  123. help
  124. Watchdog timer embedded into KS8695 processor. This will reboot your
  125. system when the timeout is reached.
  126. config HAVE_S3C2410_WATCHDOG
  127. bool
  128. help
  129. This will include watchdog timer support for Samsung SoCs. If
  130. you want to include watchdog support for any machine, kindly
  131. select this in the respective mach-XXXX/Kconfig file.
  132. config S3C2410_WATCHDOG
  133. tristate "S3C2410 Watchdog"
  134. depends on ARCH_S3C2410 || HAVE_S3C2410_WATCHDOG
  135. help
  136. Watchdog timer block in the Samsung SoCs. This will reboot
  137. the system when the timer expires with the watchdog enabled.
  138. The driver is limited by the speed of the system's PCLK
  139. signal, so with reasonably fast systems (PCLK around 50-66MHz)
  140. then watchdog intervals of over approximately 20seconds are
  141. unavailable.
  142. The driver can be built as a module by choosing M, and will
  143. be called s3c2410_wdt
  144. config SA1100_WATCHDOG
  145. tristate "SA1100/PXA2xx watchdog"
  146. depends on ARCH_SA1100 || ARCH_PXA
  147. help
  148. Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
  149. reboot your system when timeout is reached.
  150. NOTE: once enabled, this timer cannot be disabled.
  151. To compile this driver as a module, choose M here: the
  152. module will be called sa1100_wdt.
  153. config MPCORE_WATCHDOG
  154. tristate "MPcore watchdog"
  155. depends on HAVE_ARM_TWD
  156. help
  157. Watchdog timer embedded into the MPcore system.
  158. To compile this driver as a module, choose M here: the
  159. module will be called mpcore_wdt.
  160. config EP93XX_WATCHDOG
  161. tristate "EP93xx Watchdog"
  162. depends on ARCH_EP93XX
  163. help
  164. Say Y here if to include support for the watchdog timer
  165. embedded in the Cirrus Logic EP93xx family of devices.
  166. To compile this driver as a module, choose M here: the
  167. module will be called ep93xx_wdt.
  168. config OMAP_WATCHDOG
  169. tristate "OMAP Watchdog"
  170. depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS
  171. help
  172. Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
  173. here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
  174. config PNX4008_WATCHDOG
  175. tristate "PNX4008 and LPC32XX Watchdog"
  176. depends on ARCH_PNX4008 || ARCH_LPC32XX
  177. help
  178. Say Y here if to include support for the watchdog timer
  179. in the PNX4008 or LPC32XX processor.
  180. This driver can be built as a module by choosing M. The module
  181. will be called pnx4008_wdt.
  182. Say N if you are unsure.
  183. config IOP_WATCHDOG
  184. tristate "IOP Watchdog"
  185. depends on PLAT_IOP
  186. select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
  187. help
  188. Say Y here if to include support for the watchdog timer
  189. in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
  190. be built as a module by choosing M. The module will
  191. be called iop_wdt.
  192. Note: The IOP13XX watchdog does an Internal Bus Reset which will
  193. affect both cores and the peripherals of the IOP. The ATU-X
  194. and/or ATUe configuration registers will remain intact, but if
  195. operating as an Root Complex and/or Central Resource, the PCI-X
  196. and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
  197. config DAVINCI_WATCHDOG
  198. tristate "DaVinci watchdog"
  199. depends on ARCH_DAVINCI
  200. help
  201. Say Y here if to include support for the watchdog timer
  202. in the DaVinci DM644x/DM646x processors.
  203. To compile this driver as a module, choose M here: the
  204. module will be called davinci_wdt.
  205. NOTE: once enabled, this timer cannot be disabled.
  206. Say N if you are unsure.
  207. config ORION_WATCHDOG
  208. tristate "Orion watchdog"
  209. depends on ARCH_ORION5X || ARCH_KIRKWOOD
  210. help
  211. Say Y here if to include support for the watchdog timer
  212. in the Marvell Orion5x and Kirkwood ARM SoCs.
  213. To compile this driver as a module, choose M here: the
  214. module will be called orion_wdt.
  215. config COH901327_WATCHDOG
  216. bool "ST-Ericsson COH 901 327 watchdog"
  217. depends on ARCH_U300
  218. default y if MACH_U300
  219. help
  220. Say Y here to include Watchdog timer support for the
  221. watchdog embedded into the ST-Ericsson U300 series platforms.
  222. This watchdog is used to reset the system and thus cannot be
  223. compiled as a module.
  224. config TWL4030_WATCHDOG
  225. tristate "TWL4030 Watchdog"
  226. depends on TWL4030_CORE
  227. help
  228. Support for TI TWL4030 watchdog. Say 'Y' here to enable the
  229. watchdog timer support for TWL4030 chips.
  230. config STMP3XXX_WATCHDOG
  231. tristate "Freescale STMP3XXX watchdog"
  232. depends on ARCH_STMP3XXX
  233. help
  234. Say Y here if to include support for the watchdog timer
  235. for the Sigmatel STMP37XX/378X SoC.
  236. To compile this driver as a module, choose M here: the
  237. module will be called stmp3xxx_wdt.
  238. config NUC900_WATCHDOG
  239. tristate "Nuvoton NUC900 watchdog"
  240. depends on ARCH_W90X900
  241. help
  242. Say Y here if to include support for the watchdog timer
  243. for the Nuvoton NUC900 series SoCs.
  244. To compile this driver as a module, choose M here: the
  245. module will be called nuc900_wdt.
  246. config ADX_WATCHDOG
  247. tristate "Avionic Design Xanthos watchdog"
  248. depends on ARCH_PXA_ADX
  249. help
  250. Say Y here if you want support for the watchdog timer on Avionic
  251. Design Xanthos boards.
  252. config TS72XX_WATCHDOG
  253. tristate "TS-72XX SBC Watchdog"
  254. depends on MACH_TS72XX
  255. help
  256. Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
  257. watchdog timer implemented in a external CPLD chip. Say Y here
  258. if you want to support for the watchdog timer on TS-72XX boards.
  259. To compile this driver as a module, choose M here: the
  260. module will be called ts72xx_wdt.
  261. config MAX63XX_WATCHDOG
  262. tristate "Max63xx watchdog"
  263. depends on ARM && HAS_IOMEM
  264. help
  265. Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
  266. config IMX2_WDT
  267. tristate "IMX2+ Watchdog"
  268. depends on ARCH_MX2 || ARCH_MX25 || ARCH_MX3 || ARCH_MX5
  269. help
  270. This is the driver for the hardware watchdog
  271. on the Freescale IMX2 and later processors.
  272. If you have one of these processors and wish to have
  273. watchdog support enabled, say Y, otherwise say N.
  274. To compile this driver as a module, choose M here: the
  275. module will be called imx2_wdt.
  276. # AVR32 Architecture
  277. config AT32AP700X_WDT
  278. tristate "AT32AP700x watchdog"
  279. depends on CPU_AT32AP700X
  280. help
  281. Watchdog timer embedded into AT32AP700x devices. This will reboot
  282. your system when the timeout is reached.
  283. # BLACKFIN Architecture
  284. config BFIN_WDT
  285. tristate "Blackfin On-Chip Watchdog Timer"
  286. depends on BLACKFIN
  287. ---help---
  288. If you say yes here you will get support for the Blackfin On-Chip
  289. Watchdog Timer. If you have one of these processors and wish to
  290. have watchdog support enabled, say Y, otherwise say N.
  291. To compile this driver as a module, choose M here: the
  292. module will be called bfin_wdt.
  293. # CRIS Architecture
  294. # FRV Architecture
  295. # H8300 Architecture
  296. # X86 (i386 + ia64 + x86_64) Architecture
  297. config ACQUIRE_WDT
  298. tristate "Acquire SBC Watchdog Timer"
  299. depends on X86
  300. ---help---
  301. This is the driver for the hardware watchdog on Single Board
  302. Computers produced by Acquire Inc (and others). This watchdog
  303. simply watches your kernel to make sure it doesn't freeze, and if
  304. it does, it reboots your computer after a certain amount of time.
  305. To compile this driver as a module, choose M here: the
  306. module will be called acquirewdt.
  307. Most people will say N.
  308. config ADVANTECH_WDT
  309. tristate "Advantech SBC Watchdog Timer"
  310. depends on X86
  311. help
  312. If you are configuring a Linux kernel for the Advantech single-board
  313. computer, say `Y' here to support its built-in watchdog timer
  314. feature. More information can be found at
  315. <http://www.advantech.com.tw/products/>
  316. config ALIM1535_WDT
  317. tristate "ALi M1535 PMU Watchdog Timer"
  318. depends on X86 && PCI
  319. ---help---
  320. This is the driver for the hardware watchdog on the ALi M1535 PMU.
  321. To compile this driver as a module, choose M here: the
  322. module will be called alim1535_wdt.
  323. Most people will say N.
  324. config ALIM7101_WDT
  325. tristate "ALi M7101 PMU Computer Watchdog"
  326. depends on PCI
  327. help
  328. This is the driver for the hardware watchdog on the ALi M7101 PMU
  329. as used in the x86 Cobalt servers and also found in some
  330. SPARC Netra servers too.
  331. To compile this driver as a module, choose M here: the
  332. module will be called alim7101_wdt.
  333. Most people will say N.
  334. config F71808E_WDT
  335. tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
  336. depends on X86 && EXPERIMENTAL
  337. help
  338. This is the driver for the hardware watchdog on the Fintek
  339. F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
  340. You can compile this driver directly into the kernel, or use
  341. it as a module. The module will be called f71808e_wdt.
  342. config SP5100_TCO
  343. tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
  344. depends on X86 && PCI
  345. ---help---
  346. Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
  347. (Total Cost of Ownership) timer is a watchdog timer that will reboot
  348. the machine after its expiration. The expiration time can be
  349. configured with the "heartbeat" parameter.
  350. To compile this driver as a module, choose M here: the
  351. module will be called sp5100_tco.
  352. config GEODE_WDT
  353. tristate "AMD Geode CS5535/CS5536 Watchdog"
  354. depends on CS5535_MFGPT
  355. help
  356. This driver enables a watchdog capability built into the
  357. CS5535/CS5536 companion chips for the AMD Geode GX and LX
  358. processors. This watchdog watches your kernel to make sure
  359. it doesn't freeze, and if it does, it reboots your computer after
  360. a certain amount of time.
  361. You can compile this driver directly into the kernel, or use
  362. it as a module. The module will be called geodewdt.
  363. config SC520_WDT
  364. tristate "AMD Elan SC520 processor Watchdog"
  365. depends on X86
  366. help
  367. This is the driver for the hardware watchdog built in to the
  368. AMD "Elan" SC520 microcomputer commonly used in embedded systems.
  369. This watchdog simply watches your kernel to make sure it doesn't
  370. freeze, and if it does, it reboots your computer after a certain
  371. amount of time.
  372. You can compile this driver directly into the kernel, or use
  373. it as a module. The module will be called sc520_wdt.
  374. config SBC_FITPC2_WATCHDOG
  375. tristate "Compulab SBC-FITPC2 watchdog"
  376. depends on X86
  377. ---help---
  378. This is the driver for the built-in watchdog timer on the fit-PC2,
  379. fit-PC2i, CM-iAM single-board computers made by Compulab.
  380. It`s possible to enable watchdog timer either from BIOS (F2) or from booted Linux.
  381. When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
  382. Entering BIOS setup temporary disables watchdog operation regardless to current state,
  383. so system will not be restarted while user in BIOS setup.
  384. Once watchdog was enabled the system will be restarted every
  385. "Watchdog Timer Value" period, so to prevent it user can restart or
  386. disable the watchdog.
  387. To compile this driver as a module, choose M here: the
  388. module will be called sbc_fitpc2_wdt.
  389. Most people will say N.
  390. config EUROTECH_WDT
  391. tristate "Eurotech CPU-1220/1410 Watchdog Timer"
  392. depends on X86
  393. help
  394. Enable support for the watchdog timer on the Eurotech CPU-1220 and
  395. CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
  396. information are at <http://www.eurotech.it/>.
  397. config IB700_WDT
  398. tristate "IB700 SBC Watchdog Timer"
  399. depends on X86
  400. ---help---
  401. This is the driver for the hardware watchdog on the IB700 Single
  402. Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
  403. simply watches your kernel to make sure it doesn't freeze, and if
  404. it does, it reboots your computer after a certain amount of time.
  405. This driver is like the WDT501 driver but for slightly different hardware.
  406. To compile this driver as a module, choose M here: the
  407. module will be called ib700wdt.
  408. Most people will say N.
  409. config IBMASR
  410. tristate "IBM Automatic Server Restart"
  411. depends on X86
  412. help
  413. This is the driver for the IBM Automatic Server Restart watchdog
  414. timer built-in into some eServer xSeries machines.
  415. To compile this driver as a module, choose M here: the
  416. module will be called ibmasr.
  417. config WAFER_WDT
  418. tristate "ICP Single Board Computer Watchdog Timer"
  419. depends on X86
  420. help
  421. This is a driver for the hardware watchdog on the ICP Single
  422. Board Computer. This driver is working on (at least) the following
  423. IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
  424. To compile this driver as a module, choose M here: the
  425. module will be called wafer5823wdt.
  426. config I6300ESB_WDT
  427. tristate "Intel 6300ESB Timer/Watchdog"
  428. depends on X86 && PCI
  429. ---help---
  430. Hardware driver for the watchdog timer built into the Intel
  431. 6300ESB controller hub.
  432. To compile this driver as a module, choose M here: the
  433. module will be called i6300esb.
  434. config INTEL_SCU_WATCHDOG
  435. bool "Intel SCU Watchdog for Mobile Platforms"
  436. depends on WATCHDOG
  437. depends on INTEL_SCU_IPC
  438. ---help---
  439. Hardware driver for the watchdog time built into the Intel SCU
  440. for Intel Mobile Platforms.
  441. To compile this driver as a module, choose M here.
  442. config ITCO_WDT
  443. tristate "Intel TCO Timer/Watchdog"
  444. depends on (X86 || IA64) && PCI
  445. ---help---
  446. Hardware driver for the intel TCO timer based watchdog devices.
  447. These drivers are included in the Intel 82801 I/O Controller
  448. Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
  449. controller hub.
  450. The TCO (Total Cost of Ownership) timer is a watchdog timer
  451. that will reboot the machine after its second expiration. The
  452. expiration time can be configured with the "heartbeat" parameter.
  453. On some motherboards the driver may fail to reset the chipset's
  454. NO_REBOOT flag which prevents the watchdog from rebooting the
  455. machine. If this is the case you will get a kernel message like
  456. "failed to reset NO_REBOOT flag, reboot disabled by hardware".
  457. To compile this driver as a module, choose M here: the
  458. module will be called iTCO_wdt.
  459. config ITCO_VENDOR_SUPPORT
  460. bool "Intel TCO Timer/Watchdog Specific Vendor Support"
  461. depends on ITCO_WDT
  462. ---help---
  463. Add vendor specific support to the intel TCO timer based watchdog
  464. devices. At this moment we only have additional support for some
  465. SuperMicro Inc. motherboards.
  466. config IT8712F_WDT
  467. tristate "IT8712F (Smart Guardian) Watchdog Timer"
  468. depends on X86
  469. ---help---
  470. This is the driver for the built-in watchdog timer on the IT8712F
  471. Super I/0 chipset used on many motherboards.
  472. If the driver does not work, then make sure that the game port in
  473. the BIOS is enabled.
  474. To compile this driver as a module, choose M here: the
  475. module will be called it8712f_wdt.
  476. config IT87_WDT
  477. tristate "IT87 Watchdog Timer"
  478. depends on X86 && EXPERIMENTAL
  479. ---help---
  480. This is the driver for the hardware watchdog on the ITE IT8702,
  481. IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 Super I/O chips.
  482. This watchdog simply watches your kernel to make sure it doesn't
  483. freeze, and if it does, it reboots your computer after a certain
  484. amount of time.
  485. To compile this driver as a module, choose M here: the module will
  486. be called it87_wdt.
  487. config HP_WATCHDOG
  488. tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
  489. depends on X86
  490. default m
  491. help
  492. A software monitoring watchdog and NMI sourcing driver. This driver
  493. will detect lockups and provide a stack trace. This is a driver that
  494. will only load on an HP ProLiant system with a minimum of iLO2 support.
  495. To compile this driver as a module, choose M here: the module will be
  496. called hpwdt.
  497. config HPWDT_NMI_DECODING
  498. bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
  499. depends on HP_WATCHDOG
  500. default y
  501. help
  502. When an NMI occurs this feature will make the necessary BIOS calls to
  503. log the cause of the NMI.
  504. config SC1200_WDT
  505. tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
  506. depends on X86
  507. help
  508. This is a driver for National Semiconductor PC87307/PC97307 hardware
  509. watchdog cards as found on the SC1200. This watchdog is mainly used
  510. for power management purposes and can be used to power down the device
  511. during inactivity periods (includes interrupt activity monitoring).
  512. To compile this driver as a module, choose M here: the
  513. module will be called sc1200wdt.
  514. Most people will say N.
  515. config SCx200_WDT
  516. tristate "National Semiconductor SCx200 Watchdog"
  517. depends on SCx200 && PCI
  518. help
  519. Enable the built-in watchdog timer support on the National
  520. Semiconductor SCx200 processors.
  521. If compiled as a module, it will be called scx200_wdt.
  522. config PC87413_WDT
  523. tristate "NS PC87413 watchdog"
  524. depends on X86
  525. ---help---
  526. This is the driver for the hardware watchdog on the PC87413 chipset
  527. This watchdog simply watches your kernel to make sure it doesn't
  528. freeze, and if it does, it reboots your computer after a certain
  529. amount of time.
  530. To compile this driver as a module, choose M here: the
  531. module will be called pc87413_wdt.
  532. Most people will say N.
  533. config NV_TCO
  534. tristate "nVidia TCO Timer/Watchdog"
  535. depends on X86 && PCI
  536. ---help---
  537. Hardware driver for the TCO timer built into the nVidia Hub family
  538. (such as the MCP51). The TCO (Total Cost of Ownership) timer is a
  539. watchdog timer that will reboot the machine after its second
  540. expiration. The expiration time can be configured with the
  541. "heartbeat" parameter.
  542. On some motherboards the driver may fail to reset the chipset's
  543. NO_REBOOT flag which prevents the watchdog from rebooting the
  544. machine. If this is the case you will get a kernel message like
  545. "failed to reset NO_REBOOT flag, reboot disabled by hardware".
  546. To compile this driver as a module, choose M here: the
  547. module will be called nv_tco.
  548. config RDC321X_WDT
  549. tristate "RDC R-321x SoC watchdog"
  550. depends on X86_RDC321X
  551. help
  552. This is the driver for the built in hardware watchdog
  553. in the RDC R-321x SoC.
  554. To compile this driver as a module, choose M here: the
  555. module will be called rdc321x_wdt.
  556. config 60XX_WDT
  557. tristate "SBC-60XX Watchdog Timer"
  558. depends on X86
  559. help
  560. This driver can be used with the watchdog timer found on some
  561. single board computers, namely the 6010 PII based computer.
  562. It may well work with other cards. It reads port 0x443 to enable
  563. and re-set the watchdog timer, and reads port 0x45 to disable
  564. the watchdog. If you have a card that behave in similar ways,
  565. you can probably make this driver work with your card as well.
  566. You can compile this driver directly into the kernel, or use
  567. it as a module. The module will be called sbc60xxwdt.
  568. config SBC8360_WDT
  569. tristate "SBC8360 Watchdog Timer"
  570. depends on X86
  571. ---help---
  572. This is the driver for the hardware watchdog on the SBC8360 Single
  573. Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
  574. To compile this driver as a module, choose M here: the
  575. module will be called sbc8360.
  576. Most people will say N.
  577. config SBC7240_WDT
  578. tristate "SBC Nano 7240 Watchdog Timer"
  579. depends on X86_32
  580. ---help---
  581. This is the driver for the hardware watchdog found on the IEI
  582. single board computers EPIC Nano 7240 (and likely others). This
  583. watchdog simply watches your kernel to make sure it doesn't freeze,
  584. and if it does, it reboots your computer after a certain amount of
  585. time.
  586. To compile this driver as a module, choose M here: the
  587. module will be called sbc7240_wdt.
  588. config CPU5_WDT
  589. tristate "SMA CPU5 Watchdog"
  590. depends on X86
  591. ---help---
  592. TBD.
  593. To compile this driver as a module, choose M here: the
  594. module will be called cpu5wdt.
  595. config SMSC_SCH311X_WDT
  596. tristate "SMSC SCH311X Watchdog Timer"
  597. depends on X86
  598. ---help---
  599. This is the driver for the hardware watchdog timer on the
  600. SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
  601. (LPC IO with 8042 KBC, Reset Generation, HWM and multiple
  602. serial ports).
  603. To compile this driver as a module, choose M here: the
  604. module will be called sch311x_wdt.
  605. config SMSC37B787_WDT
  606. tristate "Winbond SMsC37B787 Watchdog Timer"
  607. depends on X86
  608. ---help---
  609. This is the driver for the hardware watchdog component on the
  610. Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
  611. from Vision Systems and maybe others.
  612. This watchdog simply watches your kernel to make sure it doesn't
  613. freeze, and if it does, it reboots your computer after a certain
  614. amount of time.
  615. Usually a userspace daemon will notify the kernel WDT driver that
  616. userspace is still alive, at regular intervals.
  617. To compile this driver as a module, choose M here: the
  618. module will be called smsc37b787_wdt.
  619. Most people will say N.
  620. config W83627HF_WDT
  621. tristate "W83627HF/W83627DHG Watchdog Timer"
  622. depends on X86
  623. ---help---
  624. This is the driver for the hardware watchdog on the W83627HF chipset
  625. as used in Advantech PC-9578 and Tyan S2721-533 motherboards
  626. (and likely others). The driver also supports the W83627DHG chip.
  627. This watchdog simply watches your kernel to make sure it doesn't
  628. freeze, and if it does, it reboots your computer after a certain
  629. amount of time.
  630. To compile this driver as a module, choose M here: the
  631. module will be called w83627hf_wdt.
  632. Most people will say N.
  633. config W83697HF_WDT
  634. tristate "W83697HF/W83697HG Watchdog Timer"
  635. depends on X86
  636. ---help---
  637. This is the driver for the hardware watchdog on the W83697HF/HG
  638. chipset as used in Dedibox/VIA motherboards (and likely others).
  639. This watchdog simply watches your kernel to make sure it doesn't
  640. freeze, and if it does, it reboots your computer after a certain
  641. amount of time.
  642. To compile this driver as a module, choose M here: the
  643. module will be called w83697hf_wdt.
  644. Most people will say N.
  645. config W83697UG_WDT
  646. tristate "W83697UG/W83697UF Watchdog Timer"
  647. depends on X86
  648. ---help---
  649. This is the driver for the hardware watchdog on the W83697UG/UF
  650. chipset as used in MSI Fuzzy CX700 VIA motherboards (and likely others).
  651. This watchdog simply watches your kernel to make sure it doesn't
  652. freeze, and if it does, it reboots your computer after a certain
  653. amount of time.
  654. To compile this driver as a module, choose M here: the
  655. module will be called w83697ug_wdt.
  656. Most people will say N.
  657. config W83877F_WDT
  658. tristate "W83877F (EMACS) Watchdog Timer"
  659. depends on X86
  660. ---help---
  661. This is the driver for the hardware watchdog on the W83877F chipset
  662. as used in EMACS PC-104 motherboards (and likely others). This
  663. watchdog simply watches your kernel to make sure it doesn't freeze,
  664. and if it does, it reboots your computer after a certain amount of
  665. time.
  666. To compile this driver as a module, choose M here: the
  667. module will be called w83877f_wdt.
  668. Most people will say N.
  669. config W83977F_WDT
  670. tristate "W83977F (PCM-5335) Watchdog Timer"
  671. depends on X86
  672. ---help---
  673. This is the driver for the hardware watchdog on the W83977F I/O chip
  674. as used in AAEON's PCM-5335 SBC (and likely others). This
  675. watchdog simply watches your kernel to make sure it doesn't freeze,
  676. and if it does, it reboots your computer after a certain amount of
  677. time.
  678. To compile this driver as a module, choose M here: the
  679. module will be called w83977f_wdt.
  680. config MACHZ_WDT
  681. tristate "ZF MachZ Watchdog"
  682. depends on X86
  683. ---help---
  684. If you are using a ZF Micro MachZ processor, say Y here, otherwise
  685. N. This is the driver for the watchdog timer built-in on that
  686. processor using ZF-Logic interface. This watchdog simply watches
  687. your kernel to make sure it doesn't freeze, and if it does, it
  688. reboots your computer after a certain amount of time.
  689. To compile this driver as a module, choose M here: the
  690. module will be called machzwd.
  691. config SBC_EPX_C3_WATCHDOG
  692. tristate "Winsystems SBC EPX-C3 watchdog"
  693. depends on X86
  694. ---help---
  695. This is the driver for the built-in watchdog timer on the EPX-C3
  696. Single-board computer made by Winsystems, Inc.
  697. *Note*: This hardware watchdog is not probeable and thus there
  698. is no way to know if writing to its IO address will corrupt
  699. your system or have any real effect. The only way to be sure
  700. that this driver does what you want is to make sure you
  701. are running it on an EPX-C3 from Winsystems with the watchdog
  702. timer at IO address 0x1ee and 0x1ef. It will write to both those
  703. IO ports. Basically, the assumption is made that if you compile
  704. this driver into your kernel and/or load it as a module, that you
  705. know what you are doing and that you are in fact running on an
  706. EPX-C3 board!
  707. To compile this driver as a module, choose M here: the
  708. module will be called sbc_epx_c3.
  709. # M32R Architecture
  710. # M68K Architecture
  711. config M54xx_WATCHDOG
  712. tristate "MCF54xx watchdog support"
  713. depends on M548x
  714. help
  715. To compile this driver as a module, choose M here: the
  716. module will be called m54xx_wdt.
  717. # MIPS Architecture
  718. config ATH79_WDT
  719. tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
  720. depends on ATH79
  721. help
  722. Hardware driver for the built-in watchdog timer on the Atheros
  723. AR71XX/AR724X/AR913X SoCs.
  724. config BCM47XX_WDT
  725. tristate "Broadcom BCM47xx Watchdog Timer"
  726. depends on BCM47XX
  727. help
  728. Hardware driver for the Broadcom BCM47xx Watchog Timer.
  729. config RC32434_WDT
  730. tristate "IDT RC32434 SoC Watchdog Timer"
  731. depends on MIKROTIK_RB532
  732. help
  733. Hardware driver for the IDT RC32434 SoC built-in
  734. watchdog timer.
  735. To compile this driver as a module, choose M here: the
  736. module will be called rc32434_wdt.
  737. config INDYDOG
  738. tristate "Indy/I2 Hardware Watchdog"
  739. depends on SGI_HAS_INDYDOG
  740. help
  741. Hardware driver for the Indy's/I2's watchdog. This is a
  742. watchdog timer that will reboot the machine after a 60 second
  743. timer expired and no process has written to /dev/watchdog during
  744. that time.
  745. config JZ4740_WDT
  746. tristate "Ingenic jz4740 SoC hardware watchdog"
  747. depends on MACH_JZ4740
  748. help
  749. Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
  750. config WDT_MTX1
  751. tristate "MTX-1 Hardware Watchdog"
  752. depends on MIPS_MTX1
  753. help
  754. Hardware driver for the MTX-1 boards. This is a watchdog timer that
  755. will reboot the machine after a 100 seconds timer expired.
  756. config PNX833X_WDT
  757. tristate "PNX833x Hardware Watchdog"
  758. depends on SOC_PNX8335
  759. help
  760. Hardware driver for the PNX833x's watchdog. This is a
  761. watchdog timer that will reboot the machine after a programable
  762. timer has expired and no process has written to /dev/watchdog during
  763. that time.
  764. config SIBYTE_WDOG
  765. tristate "Sibyte SoC hardware watchdog"
  766. depends on CPU_SB1
  767. help
  768. Watchdog driver for the built in watchdog hardware in Sibyte
  769. SoC processors. There are apparently two watchdog timers
  770. on such processors; this driver supports only the first one,
  771. because currently Linux only supports exporting one watchdog
  772. to userspace.
  773. To compile this driver as a loadable module, choose M here.
  774. The module will be called sb_wdog.
  775. config AR7_WDT
  776. tristate "TI AR7 Watchdog Timer"
  777. depends on AR7
  778. help
  779. Hardware driver for the TI AR7 Watchdog Timer.
  780. config TXX9_WDT
  781. tristate "Toshiba TXx9 Watchdog Timer"
  782. depends on CPU_TX39XX || CPU_TX49XX
  783. help
  784. Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
  785. config OCTEON_WDT
  786. tristate "Cavium OCTEON SOC family Watchdog Timer"
  787. depends on CPU_CAVIUM_OCTEON
  788. default y
  789. select EXPORT_UASM if OCTEON_WDT = m
  790. help
  791. Hardware driver for OCTEON's on chip watchdog timer.
  792. Enables the watchdog for all cores running Linux. It
  793. installs a NMI handler and pokes the watchdog based on an
  794. interrupt. On first expiration of the watchdog, the
  795. interrupt handler pokes it. The second expiration causes an
  796. NMI that prints a message. The third expiration causes a
  797. global soft reset.
  798. When userspace has /dev/watchdog open, no poking is done
  799. from the first interrupt, it is then only poked when the
  800. device is written.
  801. config BCM63XX_WDT
  802. tristate "Broadcom BCM63xx hardware watchdog"
  803. depends on BCM63XX
  804. help
  805. Watchdog driver for the built in watchdog hardware in Broadcom
  806. BCM63xx SoC.
  807. To compile this driver as a loadable module, choose M here.
  808. The module will be called bcm63xx_wdt.
  809. # PARISC Architecture
  810. # POWERPC Architecture
  811. config GEF_WDT
  812. tristate "GE Watchdog Timer"
  813. depends on GEF_SBC610 || GEF_SBC310 || GEF_PPC9A
  814. ---help---
  815. Watchdog timer found in a number of GE single board computers.
  816. config MPC5200_WDT
  817. bool "MPC52xx Watchdog Timer"
  818. depends on PPC_MPC52xx
  819. help
  820. Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
  821. config 8xxx_WDT
  822. tristate "MPC8xxx Platform Watchdog Timer"
  823. depends on PPC_8xx || PPC_83xx || PPC_86xx
  824. help
  825. This driver is for a SoC level watchdog that exists on some
  826. Freescale PowerPC processors. So far this driver supports:
  827. - MPC8xx watchdogs
  828. - MPC83xx watchdogs
  829. - MPC86xx watchdogs
  830. For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
  831. config MV64X60_WDT
  832. tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
  833. depends on MV64X60
  834. config PIKA_WDT
  835. tristate "PIKA FPGA Watchdog"
  836. depends on WARP
  837. default y
  838. help
  839. This enables the watchdog in the PIKA FPGA. Currently used on
  840. the Warp platform.
  841. config BOOKE_WDT
  842. tristate "PowerPC Book-E Watchdog Timer"
  843. depends on BOOKE || 4xx
  844. ---help---
  845. Watchdog driver for PowerPC Book-E chips, such as the Freescale
  846. MPC85xx SOCs and the IBM PowerPC 440.
  847. Please see Documentation/watchdog/watchdog-api.txt for
  848. more information.
  849. config BOOKE_WDT_DEFAULT_TIMEOUT
  850. int "PowerPC Book-E Watchdog Timer Default Timeout"
  851. depends on BOOKE_WDT
  852. default 38 if FSL_BOOKE
  853. range 0 63 if FSL_BOOKE
  854. default 3 if !FSL_BOOKE
  855. range 0 3 if !FSL_BOOKE
  856. help
  857. Select the default watchdog timer period to be used by the PowerPC
  858. Book-E watchdog driver. A watchdog "event" occurs when the bit
  859. position represented by this number transitions from zero to one.
  860. For Freescale Book-E processors, this is a number between 0 and 63.
  861. For other Book-E processors, this is a number between 0 and 3.
  862. The value can be overidden by the wdt_period command-line parameter.
  863. # PPC64 Architecture
  864. config WATCHDOG_RTAS
  865. tristate "RTAS watchdog"
  866. depends on PPC_RTAS
  867. help
  868. This driver adds watchdog support for the RTAS watchdog.
  869. To compile this driver as a module, choose M here. The module
  870. will be called wdrtas.
  871. # S390 Architecture
  872. config ZVM_WATCHDOG
  873. tristate "z/VM Watchdog Timer"
  874. depends on S390
  875. help
  876. IBM s/390 and zSeries machines running under z/VM 5.1 or later
  877. provide a virtual watchdog timer to their guest that cause a
  878. user define Control Program command to be executed after a
  879. timeout.
  880. To compile this driver as a module, choose M here. The module
  881. will be called vmwatchdog.
  882. # SUPERH (sh + sh64) Architecture
  883. config SH_WDT
  884. tristate "SuperH Watchdog"
  885. depends on SUPERH && (CPU_SH3 || CPU_SH4)
  886. help
  887. This driver adds watchdog support for the integrated watchdog in the
  888. SuperH processors. If you have one of these processors and wish
  889. to have watchdog support enabled, say Y, otherwise say N.
  890. As a side note, saying Y here will automatically boost HZ to 1000
  891. so that the timer has a chance to clear the overflow counter. On
  892. slower systems (such as the SH-2 and SH-3) this will likely yield
  893. some performance issues. As such, the WDT should be avoided here
  894. unless it is absolutely necessary.
  895. To compile this driver as a module, choose M here: the
  896. module will be called shwdt.
  897. # SPARC Architecture
  898. # SPARC64 Architecture
  899. config WATCHDOG_CP1XXX
  900. tristate "CP1XXX Hardware Watchdog support"
  901. depends on SPARC64 && PCI
  902. ---help---
  903. This is the driver for the hardware watchdog timers present on
  904. Sun Microsystems CompactPCI models CP1400 and CP1500.
  905. To compile this driver as a module, choose M here: the
  906. module will be called cpwatchdog.
  907. If you do not have a CompactPCI model CP1400 or CP1500, or
  908. another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
  909. you should say N to this option.
  910. config WATCHDOG_RIO
  911. tristate "RIO Hardware Watchdog support"
  912. depends on SPARC64 && PCI
  913. help
  914. Say Y here to support the hardware watchdog capability on Sun RIO
  915. machines. The watchdog timeout period is normally one minute but
  916. can be changed with a boot-time parameter.
  917. # XTENSA Architecture
  918. # Xen Architecture
  919. config XEN_WDT
  920. tristate "Xen Watchdog support"
  921. depends on XEN
  922. help
  923. Say Y here to support the hypervisor watchdog capability provided
  924. by Xen 4.0 and newer. The watchdog timeout period is normally one
  925. minute but can be changed with a boot-time parameter.
  926. #
  927. # ISA-based Watchdog Cards
  928. #
  929. comment "ISA-based Watchdog Cards"
  930. depends on ISA
  931. config PCWATCHDOG
  932. tristate "Berkshire Products ISA-PC Watchdog"
  933. depends on ISA
  934. ---help---
  935. This is the driver for the Berkshire Products ISA-PC Watchdog card.
  936. This card simply watches your kernel to make sure it doesn't freeze,
  937. and if it does, it reboots your computer after a certain amount of
  938. time. This driver is like the WDT501 driver but for different
  939. hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
  940. watchdog cards can be ordered from <http://www.berkprod.com/>.
  941. To compile this driver as a module, choose M here: the
  942. module will be called pcwd.
  943. Most people will say N.
  944. config MIXCOMWD
  945. tristate "Mixcom Watchdog"
  946. depends on ISA
  947. ---help---
  948. This is a driver for the Mixcom hardware watchdog cards. This
  949. watchdog simply watches your kernel to make sure it doesn't freeze,
  950. and if it does, it reboots your computer after a certain amount of
  951. time.
  952. To compile this driver as a module, choose M here: the
  953. module will be called mixcomwd.
  954. Most people will say N.
  955. config WDT
  956. tristate "WDT Watchdog timer"
  957. depends on ISA
  958. ---help---
  959. If you have a WDT500P or WDT501P watchdog board, say Y here,
  960. otherwise N. It is not possible to probe for this board, which means
  961. that you have to inform the kernel about the IO port and IRQ that
  962. is needed (you can do this via the io and irq parameters)
  963. To compile this driver as a module, choose M here: the
  964. module will be called wdt.
  965. #
  966. # PCI-based Watchdog Cards
  967. #
  968. comment "PCI-based Watchdog Cards"
  969. depends on PCI
  970. config PCIPCWATCHDOG
  971. tristate "Berkshire Products PCI-PC Watchdog"
  972. depends on PCI
  973. ---help---
  974. This is the driver for the Berkshire Products PCI-PC Watchdog card.
  975. This card simply watches your kernel to make sure it doesn't freeze,
  976. and if it does, it reboots your computer after a certain amount of
  977. time. The card can also monitor the internal temperature of the PC.
  978. More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
  979. To compile this driver as a module, choose M here: the
  980. module will be called pcwd_pci.
  981. Most people will say N.
  982. config WDTPCI
  983. tristate "PCI-WDT500/501 Watchdog timer"
  984. depends on PCI
  985. ---help---
  986. If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
  987. If you have a PCI-WDT501 watchdog board then you can enable the
  988. temperature sensor by setting the type parameter to 501.
  989. If you want to enable the Fan Tachometer on the PCI-WDT501, then you
  990. can do this via the tachometer parameter. Only do this if you have a
  991. fan tachometer actually set up.
  992. To compile this driver as a module, choose M here: the
  993. module will be called wdt_pci.
  994. #
  995. # USB-based Watchdog Cards
  996. #
  997. comment "USB-based Watchdog Cards"
  998. depends on USB
  999. config USBPCWATCHDOG
  1000. tristate "Berkshire Products USB-PC Watchdog"
  1001. depends on USB
  1002. ---help---
  1003. This is the driver for the Berkshire Products USB-PC Watchdog card.
  1004. This card simply watches your kernel to make sure it doesn't freeze,
  1005. and if it does, it reboots your computer after a certain amount of
  1006. time. The card can also monitor the internal temperature of the PC.
  1007. More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
  1008. To compile this driver as a module, choose M here: the
  1009. module will be called pcwd_usb.
  1010. Most people will say N.
  1011. endif # WATCHDOG