| 1 | # SPDX-License-Identifier: GPL-2.0-only |
| 2 | |
| 3 | # |
| 4 | # Watchdog device configuration |
| 5 | # |
| 6 | |
| 7 | menuconfig WATCHDOG |
| 8 | bool "Watchdog Timer Support" |
| 9 | help |
| 10 | If you say Y here (and to one of the following options) and create a |
| 11 | character special file /dev/watchdog with major number 10 and minor |
| 12 | number 130 using mknod ("man mknod"), you will get a watchdog, i.e.: |
| 13 | subsequently opening the file and then failing to write to it for |
| 14 | longer than 1 minute will result in rebooting the machine. This |
| 15 | could be useful for a networked machine that needs to come back |
| 16 | on-line as fast as possible after a lock-up. There's both a watchdog |
| 17 | implementation entirely in software (which can sometimes fail to |
| 18 | reboot the machine) and a driver for hardware watchdog boards, which |
| 19 | are more robust and can also keep track of the temperature inside |
| 20 | your computer. For details, read |
| 21 | <file:Documentation/watchdog/watchdog-api.rst> in the kernel source. |
| 22 | |
| 23 | The watchdog is usually used together with the watchdog daemon |
| 24 | which is available from |
| 25 | <https://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon |
| 26 | can also monitor NFS connections and can reboot the machine when the |
| 27 | process table is full. |
| 28 | |
| 29 | If unsure, say N. |
| 30 | |
| 31 | if WATCHDOG |
| 32 | |
| 33 | config WATCHDOG_CORE |
| 34 | tristate "WatchDog Timer Driver Core" |
| 35 | help |
| 36 | Say Y here if you want to use the new watchdog timer driver core. |
| 37 | This driver provides a framework for all watchdog timer drivers |
| 38 | and gives them the /dev/watchdog interface (and later also the |
| 39 | sysfs interface). |
| 40 | |
| 41 | config WATCHDOG_NOWAYOUT |
| 42 | bool "Disable watchdog shutdown on close" |
| 43 | help |
| 44 | The default watchdog behaviour (which you get if you say N here) is |
| 45 | to stop the timer if the process managing it closes the file |
| 46 | /dev/watchdog. It's always remotely possible that this process might |
| 47 | get killed. If you say Y here, the watchdog cannot be stopped once |
| 48 | it has been started. |
| 49 | |
| 50 | config WATCHDOG_HANDLE_BOOT_ENABLED |
| 51 | bool "Update boot-enabled watchdog until userspace takes over" |
| 52 | default y |
| 53 | help |
| 54 | The default watchdog behaviour (which you get if you say Y here) is |
| 55 | to ping watchdog devices that were enabled before the driver has |
| 56 | been loaded until control is taken over from userspace using the |
| 57 | /dev/watchdog file. If you say N here, the kernel will not update |
| 58 | the watchdog on its own. Thus if your userspace does not start fast |
| 59 | enough your device will reboot. |
| 60 | |
| 61 | config WATCHDOG_OPEN_TIMEOUT |
| 62 | int "Timeout value for opening watchdog device" |
| 63 | default 0 |
| 64 | help |
| 65 | The maximum time, in seconds, for which the watchdog framework takes |
| 66 | care of pinging a hardware watchdog. A value of 0 means infinite. The |
| 67 | value set here can be overridden by the commandline parameter |
| 68 | "watchdog.open_timeout". |
| 69 | |
| 70 | config WATCHDOG_SYSFS |
| 71 | bool "Read different watchdog information through sysfs" |
| 72 | help |
| 73 | Say Y here if you want to enable watchdog device status read through |
| 74 | sysfs attributes. |
| 75 | |
| 76 | config WATCHDOG_HRTIMER_PRETIMEOUT |
| 77 | bool "Enable watchdog hrtimer-based pretimeouts" |
| 78 | help |
| 79 | Enable this if you want to use a hrtimer timer based pretimeout for |
| 80 | watchdogs that do not natively support pretimeout support. Be aware |
| 81 | that because this pretimeout functionality uses hrtimers, it may not |
| 82 | be able to fire before the actual watchdog fires in some situations. |
| 83 | |
| 84 | comment "Watchdog Pretimeout Governors" |
| 85 | |
| 86 | config WATCHDOG_PRETIMEOUT_GOV |
| 87 | bool "Enable watchdog pretimeout governors" |
| 88 | depends on WATCHDOG_CORE |
| 89 | help |
| 90 | The option allows to select watchdog pretimeout governors. |
| 91 | |
| 92 | config WATCHDOG_PRETIMEOUT_GOV_SEL |
| 93 | tristate |
| 94 | depends on WATCHDOG_PRETIMEOUT_GOV |
| 95 | default m |
| 96 | select WATCHDOG_PRETIMEOUT_GOV_PANIC if \ |
| 97 | WATCHDOG_PRETIMEOUT_GOV_NOOP=n && WATCHDOG_PRETIMEOUT_GOV_DUMP=n |
| 98 | |
| 99 | if WATCHDOG_PRETIMEOUT_GOV |
| 100 | |
| 101 | config WATCHDOG_PRETIMEOUT_GOV_DUMP |
| 102 | tristate "Dump watchdog pretimeout governor" |
| 103 | depends on WATCHDOG_CORE |
| 104 | default WATCHDOG_CORE |
| 105 | help |
| 106 | Dump watchdog pretimeout governor, all cpu backtrace is |
| 107 | added to kernel log buffer. |
| 108 | |
| 109 | config WATCHDOG_PRETIMEOUT_GOV_NOOP |
| 110 | tristate "Noop watchdog pretimeout governor" |
| 111 | depends on WATCHDOG_CORE |
| 112 | default WATCHDOG_CORE |
| 113 | help |
| 114 | Noop watchdog pretimeout governor, only an informational |
| 115 | message is added to kernel log buffer. |
| 116 | |
| 117 | config WATCHDOG_PRETIMEOUT_GOV_PANIC |
| 118 | tristate "Panic watchdog pretimeout governor" |
| 119 | depends on WATCHDOG_CORE |
| 120 | default WATCHDOG_CORE |
| 121 | help |
| 122 | Panic watchdog pretimeout governor, on watchdog pretimeout |
| 123 | event put the kernel into panic. |
| 124 | |
| 125 | choice |
| 126 | prompt "Default Watchdog Pretimeout Governor" |
| 127 | default WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC |
| 128 | help |
| 129 | This option selects a default watchdog pretimeout governor. |
| 130 | The governor takes its action, if a watchdog is capable |
| 131 | to report a pretimeout event. |
| 132 | |
| 133 | config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_DUMP |
| 134 | bool "dump" |
| 135 | depends on WATCHDOG_PRETIMEOUT_GOV_DUMP |
| 136 | help |
| 137 | Use dump watchdog pretimeout governor by default. If dump |
| 138 | governor is selected by a user, dump all cpu backtrace to |
| 139 | the kernel log buffer and don't do any system changes. |
| 140 | |
| 141 | config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP |
| 142 | bool "noop" |
| 143 | depends on WATCHDOG_PRETIMEOUT_GOV_NOOP |
| 144 | help |
| 145 | Use noop watchdog pretimeout governor by default. If noop |
| 146 | governor is selected by a user, write a short message to |
| 147 | the kernel log buffer and don't do any system changes. |
| 148 | |
| 149 | config WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC |
| 150 | bool "panic" |
| 151 | depends on WATCHDOG_PRETIMEOUT_GOV_PANIC |
| 152 | help |
| 153 | Use panic watchdog pretimeout governor by default, if |
| 154 | a watchdog pretimeout event happens, consider that |
| 155 | a watchdog feeder is dead and reboot is unavoidable. |
| 156 | |
| 157 | endchoice |
| 158 | |
| 159 | endif # WATCHDOG_PRETIMEOUT_GOV |
| 160 | |
| 161 | # |
| 162 | # General Watchdog drivers |
| 163 | # |
| 164 | |
| 165 | comment "Watchdog Device Drivers" |
| 166 | |
| 167 | # Architecture Independent |
| 168 | |
| 169 | config SOFT_WATCHDOG |
| 170 | tristate "Software watchdog" |
| 171 | select WATCHDOG_CORE |
| 172 | help |
| 173 | A software monitoring watchdog. This will fail to reboot your system |
| 174 | from some situations that the hardware watchdog will recover |
| 175 | from. Equally it's a lot cheaper to install. |
| 176 | |
| 177 | To compile this driver as a module, choose M here: the |
| 178 | module will be called softdog. |
| 179 | |
| 180 | config SOFT_WATCHDOG_PRETIMEOUT |
| 181 | bool "Software watchdog pretimeout governor support" |
| 182 | depends on SOFT_WATCHDOG && WATCHDOG_PRETIMEOUT_GOV |
| 183 | help |
| 184 | Enable this if you want to use pretimeout governors with the software |
| 185 | watchdog. Be aware that governors might affect the watchdog because it |
| 186 | is purely software, e.g. the panic governor will stall it! |
| 187 | |
| 188 | config BD957XMUF_WATCHDOG |
| 189 | tristate "ROHM BD9576MUF and BD9573MUF PMIC Watchdog" |
| 190 | depends on MFD_ROHM_BD957XMUF |
| 191 | select WATCHDOG_CORE |
| 192 | help |
| 193 | Support for the watchdog in the ROHM BD9576 and BD9573 PMICs. |
| 194 | These PMIC ICs contain watchdog block which can be configured |
| 195 | to toggle reset line if SoC fails to ping watchdog via GPIO. |
| 196 | |
| 197 | Say Y here to include support for the ROHM BD9576 or BD9573 |
| 198 | watchdog. Alternatively say M to compile the driver as a module, |
| 199 | which will be called bd9576_wdt. |
| 200 | |
| 201 | config BD96801_WATCHDOG |
| 202 | tristate "ROHM BD96801 PMIC Watchdog" |
| 203 | depends on MFD_ROHM_BD96801 |
| 204 | select WATCHDOG_CORE |
| 205 | help |
| 206 | Support for the watchdog in the ROHM BD96801 PMIC. Watchdog can be |
| 207 | configured to only generate IRQ or to trigger system reset via reset |
| 208 | pin. |
| 209 | |
| 210 | Say Y here to include support for the ROHM BD96801 watchdog. |
| 211 | Alternatively say M to compile the driver as a module, |
| 212 | which will be called bd96801_wdt. |
| 213 | |
| 214 | config CROS_EC_WATCHDOG |
| 215 | tristate "ChromeOS EC-based watchdog" |
| 216 | select WATCHDOG_CORE |
| 217 | depends on CROS_EC |
| 218 | help |
| 219 | Watchdog driver for Chromebook devices equipped with embedded controller. |
| 220 | Trigger event is recorded in EC and checked on the subsequent boot. |
| 221 | |
| 222 | To compile this driver as a module, choose M here: the |
| 223 | module will be called cros_ec_wdt. |
| 224 | |
| 225 | config DA9052_WATCHDOG |
| 226 | tristate "Dialog DA9052 Watchdog" |
| 227 | depends on PMIC_DA9052 || COMPILE_TEST |
| 228 | select WATCHDOG_CORE |
| 229 | help |
| 230 | Support for the watchdog in the DA9052 PMIC. Watchdog trigger |
| 231 | cause system reset. |
| 232 | |
| 233 | Say Y here to include support for the DA9052 watchdog. |
| 234 | Alternatively say M to compile the driver as a module, |
| 235 | which will be called da9052_wdt. |
| 236 | |
| 237 | config DA9055_WATCHDOG |
| 238 | tristate "Dialog Semiconductor DA9055 Watchdog" |
| 239 | depends on MFD_DA9055 || COMPILE_TEST |
| 240 | select WATCHDOG_CORE |
| 241 | help |
| 242 | If you say yes here you get support for watchdog on the Dialog |
| 243 | Semiconductor DA9055 PMIC. |
| 244 | |
| 245 | This driver can also be built as a module. If so, the module |
| 246 | will be called da9055_wdt. |
| 247 | |
| 248 | config DA9063_WATCHDOG |
| 249 | tristate "Dialog DA9063 Watchdog" |
| 250 | depends on MFD_DA9063 || COMPILE_TEST |
| 251 | depends on I2C |
| 252 | select WATCHDOG_CORE |
| 253 | help |
| 254 | Support for the watchdog in the DA9063 PMIC. |
| 255 | |
| 256 | This driver can be built as a module. The module name is da9063_wdt. |
| 257 | |
| 258 | config DA9062_WATCHDOG |
| 259 | tristate "Dialog DA9062/61 Watchdog" |
| 260 | depends on MFD_DA9062 || COMPILE_TEST |
| 261 | depends on I2C |
| 262 | select WATCHDOG_CORE |
| 263 | help |
| 264 | Support for the watchdog in the DA9062 and DA9061 PMICs. |
| 265 | |
| 266 | This driver can be built as a module. The module name is da9062_wdt. |
| 267 | |
| 268 | config GPIO_WATCHDOG |
| 269 | tristate "Watchdog device controlled through GPIO-line" |
| 270 | depends on GPIOLIB && (ACPI || OF) |
| 271 | select WATCHDOG_CORE |
| 272 | help |
| 273 | If you say yes here you get support for watchdog device |
| 274 | controlled through GPIO-line. |
| 275 | |
| 276 | config GPIO_WATCHDOG_ARCH_INITCALL |
| 277 | bool "Register the watchdog as early as possible" |
| 278 | depends on GPIO_WATCHDOG=y |
| 279 | help |
| 280 | In some situations, the default initcall level (module_init) |
| 281 | in not early enough in the boot process to avoid the watchdog |
| 282 | to be triggered. |
| 283 | If you say yes here, the initcall level would be raised to |
| 284 | arch_initcall. |
| 285 | If in doubt, say N. |
| 286 | |
| 287 | config LENOVO_SE10_WDT |
| 288 | tristate "Lenovo SE10 Watchdog" |
| 289 | depends on (X86 && DMI) || COMPILE_TEST |
| 290 | depends on HAS_IOPORT |
| 291 | select WATCHDOG_CORE |
| 292 | help |
| 293 | If you say yes here you get support for the watchdog |
| 294 | functionality for the Lenovo SE10 platform. |
| 295 | |
| 296 | This driver can also be built as a module. If so, the module |
| 297 | will be called lenovo-se10-wdt. |
| 298 | |
| 299 | config LENOVO_SE30_WDT |
| 300 | tristate "Lenovo SE30 Watchdog" |
| 301 | depends on (X86 && DMI) || COMPILE_TEST |
| 302 | depends on HAS_IOPORT |
| 303 | select WATCHDOG_CORE |
| 304 | help |
| 305 | If you say yes here you get support for the watchdog |
| 306 | functionality for the Lenovo SE30 platform. |
| 307 | |
| 308 | This driver can also be built as a module. If so, the module |
| 309 | will be called lenovo-se30-wdt. |
| 310 | |
| 311 | config LENOVO_SE30G2_SE60_WDT |
| 312 | tristate "Lenovo SE30 Gen 2, SE60 Watchdog" |
| 313 | depends on (X86 && DMI) || COMPILE_TEST |
| 314 | depends on HAS_IOPORT |
| 315 | select WATCHDOG_CORE |
| 316 | help |
| 317 | If you say yes here you get support for the watchdog |
| 318 | functionality for the Lenovo SE30 Gen2 and SE60 platforms. |
| 319 | |
| 320 | This driver can also be built as a module. If so, the module |
| 321 | will be called lenovo-se30g2-se60-wdt. |
| 322 | |
| 323 | config MENF21BMC_WATCHDOG |
| 324 | tristate "MEN 14F021P00 BMC Watchdog" |
| 325 | depends on MFD_MENF21BMC || COMPILE_TEST |
| 326 | depends on I2C |
| 327 | select WATCHDOG_CORE |
| 328 | help |
| 329 | Say Y here to include support for the MEN 14F021P00 BMC Watchdog. |
| 330 | |
| 331 | This driver can also be built as a module. If so the module |
| 332 | will be called menf21bmc_wdt. |
| 333 | |
| 334 | config MENZ069_WATCHDOG |
| 335 | tristate "MEN 16Z069 Watchdog" |
| 336 | depends on MCB |
| 337 | select WATCHDOG_CORE |
| 338 | help |
| 339 | Say Y here to include support for the MEN 16Z069 Watchdog. |
| 340 | |
| 341 | This driver can also be built as a module. If so the module |
| 342 | will be called menz069_wdt. |
| 343 | |
| 344 | config WDAT_WDT |
| 345 | tristate "ACPI Watchdog Action Table (WDAT)" |
| 346 | depends on ACPI |
| 347 | select WATCHDOG_CORE |
| 348 | select ACPI_WATCHDOG |
| 349 | help |
| 350 | This driver adds support for systems with ACPI Watchdog Action |
| 351 | Table (WDAT) table. Servers typically have this but it can be |
| 352 | found on some desktop machines as well. This driver will take |
| 353 | over the native iTCO watchdog driver found on many Intel CPUs. |
| 354 | |
| 355 | To compile this driver as module, choose M here: the module will |
| 356 | be called wdat_wdt. |
| 357 | |
| 358 | config WM831X_WATCHDOG |
| 359 | tristate "WM831x watchdog" |
| 360 | depends on MFD_WM831X |
| 361 | select WATCHDOG_CORE |
| 362 | help |
| 363 | Support for the watchdog in the WM831x AudioPlus PMICs. When |
| 364 | the watchdog triggers the system will be reset. |
| 365 | |
| 366 | config WM8350_WATCHDOG |
| 367 | tristate "WM8350 watchdog" |
| 368 | depends on MFD_WM8350 |
| 369 | select WATCHDOG_CORE |
| 370 | help |
| 371 | Support for the watchdog in the WM8350 AudioPlus PMIC. When |
| 372 | the watchdog triggers the system will be reset. |
| 373 | |
| 374 | config XILINX_WATCHDOG |
| 375 | tristate "Xilinx Watchdog timer" |
| 376 | depends on HAS_IOMEM |
| 377 | select WATCHDOG_CORE |
| 378 | help |
| 379 | Watchdog driver for the xps_timebase_wdt IP core. |
| 380 | |
| 381 | To compile this driver as a module, choose M here: the |
| 382 | module will be called of_xilinx_wdt. |
| 383 | |
| 384 | config XILINX_WINDOW_WATCHDOG |
| 385 | tristate "Xilinx window watchdog timer" |
| 386 | depends on HAS_IOMEM |
| 387 | depends on ARM64 || COMPILE_TEST |
| 388 | select WATCHDOG_CORE |
| 389 | help |
| 390 | Window watchdog driver for the versal_wwdt IP core. |
| 391 | Window watchdog timer(WWDT) contains closed(first) and |
| 392 | open(second) window with 32 bit width. Write to the watchdog |
| 393 | timer within predefined window periods of time. This means |
| 394 | a period that is not too soon and a period that is not too |
| 395 | late. The WWDT has to be restarted within the open window time. |
| 396 | If software tries to restart WWDT outside of the open window |
| 397 | time period, it generates a reset. |
| 398 | |
| 399 | To compile this driver as a module, choose M here: the |
| 400 | module will be called xilinx_wwdt. |
| 401 | |
| 402 | config ZIIRAVE_WATCHDOG |
| 403 | tristate "Zodiac RAVE Watchdog Timer" |
| 404 | depends on I2C |
| 405 | select WATCHDOG_CORE |
| 406 | help |
| 407 | Watchdog driver for the Zodiac Aerospace RAVE Switch Watchdog |
| 408 | Processor. |
| 409 | |
| 410 | To compile this driver as a module, choose M here: the |
| 411 | module will be called ziirave_wdt. |
| 412 | |
| 413 | config RAVE_SP_WATCHDOG |
| 414 | tristate "RAVE SP Watchdog timer" |
| 415 | depends on RAVE_SP_CORE |
| 416 | depends on NVMEM || !NVMEM |
| 417 | select WATCHDOG_CORE |
| 418 | help |
| 419 | Support for the watchdog on RAVE SP device. |
| 420 | |
| 421 | config MLX_WDT |
| 422 | tristate "Mellanox Watchdog" |
| 423 | depends on MELLANOX_PLATFORM || COMPILE_TEST |
| 424 | select WATCHDOG_CORE |
| 425 | select REGMAP |
| 426 | help |
| 427 | This is the driver for the hardware watchdog on Mellanox systems. |
| 428 | If you are going to use it, say Y here, otherwise N. |
| 429 | This driver can be used together with the watchdog daemon. |
| 430 | It can also watch your kernel to make sure it doesn't freeze, |
| 431 | and if it does, it reboots your system after a certain amount of |
| 432 | time. |
| 433 | |
| 434 | To compile this driver as a module, choose M here: the |
| 435 | module will be called mlx-wdt. |
| 436 | |
| 437 | config SL28CPLD_WATCHDOG |
| 438 | tristate "Kontron sl28cpld Watchdog" |
| 439 | depends on MFD_SL28CPLD || COMPILE_TEST |
| 440 | select WATCHDOG_CORE |
| 441 | help |
| 442 | Say Y here to include support for the watchdog timer |
| 443 | on the Kontron sl28 CPLD. |
| 444 | |
| 445 | To compile this driver as a module, choose M here: the |
| 446 | module will be called sl28cpld_wdt. |
| 447 | |
| 448 | # ALPHA Architecture |
| 449 | |
| 450 | # ARM Architecture |
| 451 | |
| 452 | config AIROHA_WATCHDOG |
| 453 | tristate "Airoha EN7581 Watchdog" |
| 454 | depends on ARCH_AIROHA || COMPILE_TEST |
| 455 | select WATCHDOG_CORE |
| 456 | help |
| 457 | Watchdog timer embedded into Airoha SoC. This will reboot your |
| 458 | system when the timeout is reached. |
| 459 | |
| 460 | config ARM_SP805_WATCHDOG |
| 461 | tristate "ARM SP805 Watchdog" |
| 462 | depends on (ARM || ARM64 || COMPILE_TEST) && ARM_AMBA |
| 463 | select WATCHDOG_CORE |
| 464 | help |
| 465 | ARM Primecell SP805 Watchdog timer. This will reboot your system when |
| 466 | the timeout is reached. |
| 467 | |
| 468 | config ARM_SBSA_WATCHDOG |
| 469 | tristate "ARM SBSA Generic Watchdog" |
| 470 | depends on ARM64 |
| 471 | depends on ARM_ARCH_TIMER |
| 472 | select WATCHDOG_CORE |
| 473 | help |
| 474 | ARM SBSA Generic Watchdog has two stage timeouts: |
| 475 | the first signal (WS0) is for alerting the system by interrupt, |
| 476 | the second one (WS1) is a real hardware reset. |
| 477 | More details: ARM DEN0029B - Server Base System Architecture (SBSA) |
| 478 | |
| 479 | This driver can operate ARM SBSA Generic Watchdog as a single stage |
| 480 | or a two stages watchdog, it depends on the module parameter "action". |
| 481 | |
| 482 | Note: the maximum timeout in the two stages mode is half of that in |
| 483 | the single stage mode. |
| 484 | |
| 485 | To compile this driver as module, choose M here: The module |
| 486 | will be called sbsa_gwdt. |
| 487 | |
| 488 | config ARMADA_37XX_WATCHDOG |
| 489 | tristate "Armada 37xx watchdog" |
| 490 | depends on ARCH_MVEBU || COMPILE_TEST |
| 491 | depends on HAS_IOMEM |
| 492 | select MFD_SYSCON |
| 493 | select WATCHDOG_CORE |
| 494 | help |
| 495 | Say Y here to include support for the watchdog timer found on |
| 496 | Marvell Armada 37xx SoCs. |
| 497 | To compile this driver as a module, choose M here: the |
| 498 | module will be called armada_37xx_wdt. |
| 499 | |
| 500 | config ASM9260_WATCHDOG |
| 501 | tristate "Alphascale ASM9260 watchdog" |
| 502 | depends on MACH_ASM9260 || COMPILE_TEST |
| 503 | depends on OF |
| 504 | select WATCHDOG_CORE |
| 505 | select RESET_CONTROLLER |
| 506 | help |
| 507 | Watchdog timer embedded into Alphascale asm9260 chips. This will |
| 508 | reboot your system when the timeout is reached. |
| 509 | |
| 510 | config AT91RM9200_WATCHDOG |
| 511 | tristate "AT91RM9200 watchdog" |
| 512 | depends on (SOC_AT91RM9200 && MFD_SYSCON) || COMPILE_TEST |
| 513 | help |
| 514 | Watchdog timer embedded into AT91RM9200 chips. This will reboot your |
| 515 | system when the timeout is reached. |
| 516 | |
| 517 | config AT91SAM9X_WATCHDOG |
| 518 | tristate "AT91SAM9X / AT91CAP9 watchdog" |
| 519 | depends on ARCH_AT91 || COMPILE_TEST |
| 520 | select WATCHDOG_CORE |
| 521 | help |
| 522 | Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will |
| 523 | reboot your system when the timeout is reached. |
| 524 | |
| 525 | config SAMA5D4_WATCHDOG |
| 526 | tristate "Atmel SAMA5D4 Watchdog Timer" |
| 527 | depends on ARCH_AT91 || COMPILE_TEST |
| 528 | select WATCHDOG_CORE |
| 529 | help |
| 530 | Atmel SAMA5D4 watchdog timer is embedded into SAMA5D4 chips. |
| 531 | Its Watchdog Timer Mode Register can be written more than once. |
| 532 | This will reboot your system when the timeout is reached. |
| 533 | |
| 534 | config CADENCE_WATCHDOG |
| 535 | tristate "Cadence Watchdog Timer" |
| 536 | depends on HAS_IOMEM |
| 537 | select WATCHDOG_CORE |
| 538 | help |
| 539 | Say Y here if you want to include support for the watchdog |
| 540 | timer in the Xilinx Zynq. |
| 541 | |
| 542 | config 21285_WATCHDOG |
| 543 | tristate "DC21285 watchdog" |
| 544 | depends on FOOTBRIDGE |
| 545 | help |
| 546 | The Intel Footbridge chip contains a built-in watchdog circuit. Say Y |
| 547 | here if you wish to use this. Alternatively say M to compile the |
| 548 | driver as a module, which will be called wdt285. |
| 549 | |
| 550 | This driver does not work on all machines. In particular, early CATS |
| 551 | boards have hardware problems that will cause the machine to simply |
| 552 | lock up if the watchdog fires. |
| 553 | |
| 554 | "If in doubt, leave it out" - say N. |
| 555 | |
| 556 | config 977_WATCHDOG |
| 557 | tristate "NetWinder WB83C977 watchdog" |
| 558 | depends on (FOOTBRIDGE && ARCH_NETWINDER) || (ARM && COMPILE_TEST) |
| 559 | depends on HAS_IOPORT |
| 560 | help |
| 561 | Say Y here to include support for the WB977 watchdog included in |
| 562 | NetWinder machines. Alternatively say M to compile the driver as |
| 563 | a module, which will be called wdt977. |
| 564 | |
| 565 | Not sure? It's safe to say N. |
| 566 | |
| 567 | config FTWDT010_WATCHDOG |
| 568 | tristate "Faraday Technology FTWDT010 watchdog" |
| 569 | depends on ARM || COMPILE_TEST |
| 570 | select WATCHDOG_CORE |
| 571 | default ARCH_GEMINI |
| 572 | help |
| 573 | Say Y here if to include support for the Faraday Technology |
| 574 | FTWDT010 watchdog timer embedded in the Cortina Systems Gemini |
| 575 | family of devices. |
| 576 | |
| 577 | To compile this driver as a module, choose M here: the |
| 578 | module will be called ftwdt010_wdt. |
| 579 | |
| 580 | config IXP4XX_WATCHDOG |
| 581 | tristate "IXP4xx Watchdog" |
| 582 | depends on ARCH_IXP4XX || (ARM && COMPILE_TEST) |
| 583 | select WATCHDOG_CORE |
| 584 | help |
| 585 | Say Y here if to include support for the watchdog timer |
| 586 | in the Intel IXP4xx network processors. This driver can |
| 587 | be built as a module by choosing M. The module will |
| 588 | be called ixp4xx_wdt. |
| 589 | |
| 590 | Note: The internal IXP4xx watchdog does a soft CPU reset |
| 591 | which doesn't reset any peripherals. There are circumstances |
| 592 | where the watchdog will fail to reset the board correctly |
| 593 | (e.g., if the boot ROM is in an unreadable state). |
| 594 | |
| 595 | Say N if you are unsure. |
| 596 | |
| 597 | config S3C2410_WATCHDOG |
| 598 | tristate "S3C6410/S5Pv210/Exynos Watchdog" |
| 599 | depends on ARCH_S3C64XX || ARCH_S5PV210 || ARCH_EXYNOS || COMPILE_TEST |
| 600 | select WATCHDOG_CORE |
| 601 | select MFD_SYSCON if ARCH_EXYNOS |
| 602 | help |
| 603 | Watchdog timer block in the Samsung S3C64xx, S5Pv210 and Exynos |
| 604 | SoCs. This will reboot the system when the timer expires with |
| 605 | the watchdog enabled. |
| 606 | |
| 607 | The driver is limited by the speed of the system's PCLK |
| 608 | signal, so with reasonably fast systems (PCLK around 50-66MHz) |
| 609 | then watchdog intervals of over approximately 20seconds are |
| 610 | unavailable. |
| 611 | |
| 612 | Choose Y/M here only if you build for such Samsung SoC. |
| 613 | The driver can be built as a module by choosing M, and will |
| 614 | be called s3c2410_wdt. |
| 615 | |
| 616 | config SA1100_WATCHDOG |
| 617 | tristate "SA1100/PXA2xx watchdog" |
| 618 | depends on ARCH_SA1100 || ARCH_PXA || COMPILE_TEST |
| 619 | help |
| 620 | Watchdog timer embedded into SA11x0 and PXA2xx chips. This will |
| 621 | reboot your system when timeout is reached. |
| 622 | |
| 623 | NOTE: once enabled, this timer cannot be disabled. |
| 624 | |
| 625 | To compile this driver as a module, choose M here: the |
| 626 | module will be called sa1100_wdt. |
| 627 | |
| 628 | config DW_WATCHDOG |
| 629 | tristate "Synopsys DesignWare watchdog" |
| 630 | depends on HAS_IOMEM |
| 631 | select WATCHDOG_CORE |
| 632 | help |
| 633 | Say Y here if to include support for the Synopsys DesignWare |
| 634 | watchdog timer found in many chips. |
| 635 | To compile this driver as a module, choose M here: the |
| 636 | module will be called dw_wdt. |
| 637 | |
| 638 | config EP93XX_WATCHDOG |
| 639 | tristate "EP93xx Watchdog" |
| 640 | depends on ARCH_EP93XX || COMPILE_TEST |
| 641 | select WATCHDOG_CORE |
| 642 | help |
| 643 | Say Y here if to include support for the watchdog timer |
| 644 | embedded in the Cirrus Logic EP93xx family of devices. |
| 645 | |
| 646 | To compile this driver as a module, choose M here: the |
| 647 | module will be called ep93xx_wdt. |
| 648 | |
| 649 | config OMAP_WATCHDOG |
| 650 | tristate "OMAP Watchdog" |
| 651 | depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || COMPILE_TEST |
| 652 | select WATCHDOG_CORE |
| 653 | help |
| 654 | Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. |
| 655 | Say 'Y' here to enable the |
| 656 | OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer. |
| 657 | |
| 658 | config PNX4008_WATCHDOG |
| 659 | tristate "LPC32XX Watchdog" |
| 660 | depends on ARCH_LPC32XX || COMPILE_TEST |
| 661 | select WATCHDOG_CORE |
| 662 | help |
| 663 | Say Y here if to include support for the watchdog timer |
| 664 | in the LPC32XX processor. |
| 665 | This driver can be built as a module by choosing M. The module |
| 666 | will be called pnx4008_wdt. |
| 667 | |
| 668 | Say N if you are unsure. |
| 669 | |
| 670 | config DAVINCI_WATCHDOG |
| 671 | tristate "DaVinci watchdog" |
| 672 | depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST |
| 673 | select WATCHDOG_CORE |
| 674 | help |
| 675 | Say Y here if to include support for the watchdog timer |
| 676 | in the DaVinci DM644x/DM646x or Keystone processors. |
| 677 | To compile this driver as a module, choose M here: the |
| 678 | module will be called davinci_wdt. |
| 679 | |
| 680 | NOTE: once enabled, this timer cannot be disabled. |
| 681 | Say N if you are unsure. |
| 682 | |
| 683 | config K3_RTI_WATCHDOG |
| 684 | tristate "Texas Instruments K3 RTI watchdog" |
| 685 | depends on ARCH_K3 || COMPILE_TEST |
| 686 | select WATCHDOG_CORE |
| 687 | help |
| 688 | Say Y here if you want to include support for the K3 watchdog |
| 689 | timer (RTI module) available in the K3 generation of processors. |
| 690 | |
| 691 | config ORION_WATCHDOG |
| 692 | tristate "Orion watchdog" |
| 693 | depends on ARCH_ORION5X || ARCH_DOVE || MACH_DOVE || ARCH_MVEBU || COMPILE_TEST |
| 694 | depends on ARM |
| 695 | select WATCHDOG_CORE |
| 696 | help |
| 697 | Say Y here if to include support for the watchdog timer |
| 698 | in the Marvell Orion5x and Kirkwood ARM SoCs. |
| 699 | To compile this driver as a module, choose M here: the |
| 700 | module will be called orion_wdt. |
| 701 | |
| 702 | config RN5T618_WATCHDOG |
| 703 | tristate "Ricoh RN5T618 watchdog" |
| 704 | depends on MFD_RN5T618 || COMPILE_TEST |
| 705 | select WATCHDOG_CORE |
| 706 | help |
| 707 | If you say yes here you get support for watchdog on the Ricoh |
| 708 | RN5T618 PMIC. |
| 709 | |
| 710 | This driver can also be built as a module. If so, the module |
| 711 | will be called rn5t618_wdt. |
| 712 | |
| 713 | config SUNXI_WATCHDOG |
| 714 | tristate "Allwinner SoCs watchdog support" |
| 715 | depends on ARCH_SUNXI || COMPILE_TEST |
| 716 | select WATCHDOG_CORE |
| 717 | help |
| 718 | Say Y here to include support for the watchdog timer |
| 719 | in Allwinner SoCs. |
| 720 | To compile this driver as a module, choose M here: the |
| 721 | module will be called sunxi_wdt. |
| 722 | |
| 723 | config NPCM7XX_WATCHDOG |
| 724 | tristate "Nuvoton NPCM750 watchdog" |
| 725 | depends on ARCH_NPCM || COMPILE_TEST |
| 726 | default y if ARCH_NPCM7XX |
| 727 | select WATCHDOG_CORE |
| 728 | help |
| 729 | Say Y here to include Watchdog timer support for the |
| 730 | watchdog embedded into the NPCM7xx. |
| 731 | This watchdog is used to reset the system and thus cannot be |
| 732 | compiled as a module. |
| 733 | |
| 734 | config TWL4030_WATCHDOG |
| 735 | tristate "TWL4030 Watchdog" |
| 736 | depends on TWL4030_CORE |
| 737 | select WATCHDOG_CORE |
| 738 | help |
| 739 | Support for TI TWL4030 watchdog. Say 'Y' here to enable the |
| 740 | watchdog timer support for TWL4030 chips. |
| 741 | |
| 742 | config STMP3XXX_RTC_WATCHDOG |
| 743 | tristate "Freescale STMP3XXX & i.MX23/28 watchdog" |
| 744 | depends on RTC_DRV_STMP || COMPILE_TEST |
| 745 | select WATCHDOG_CORE |
| 746 | help |
| 747 | Say Y here to include support for the watchdog timer inside |
| 748 | the RTC for the STMP37XX/378X or i.MX23/28 SoC. |
| 749 | To compile this driver as a module, choose M here: the |
| 750 | module will be called stmp3xxx_rtc_wdt. |
| 751 | |
| 752 | config MA35D1_WDT |
| 753 | tristate "Nuvoton MA35D1 Watchdog Timer" |
| 754 | depends on ARCH_MA35 || COMPILE_TEST |
| 755 | select WATCHDOG_CORE |
| 756 | help |
| 757 | Say Y here to include support for the watchdog timer |
| 758 | for the Nuvoton MA35D1 series microprocessor. |
| 759 | To compile this driver as a module, choose M here: the |
| 760 | module will be called ma35d1_wdt. |
| 761 | |
| 762 | config TS4800_WATCHDOG |
| 763 | tristate "TS-4800 Watchdog" |
| 764 | depends on HAS_IOMEM && OF |
| 765 | depends on SOC_IMX51 || COMPILE_TEST |
| 766 | select WATCHDOG_CORE |
| 767 | select MFD_SYSCON |
| 768 | help |
| 769 | Technologic Systems TS-4800 has watchdog timer implemented in |
| 770 | an external FPGA. Say Y here if you want to support for the |
| 771 | watchdog timer on TS-4800 board. |
| 772 | |
| 773 | config TS72XX_WATCHDOG |
| 774 | tristate "TS-72XX SBC Watchdog" |
| 775 | depends on MACH_TS72XX || COMPILE_TEST |
| 776 | select WATCHDOG_CORE |
| 777 | help |
| 778 | Technologic Systems TS-7200, TS-7250 and TS-7260 boards have |
| 779 | watchdog timer implemented in a external CPLD chip. Say Y here |
| 780 | if you want to support for the watchdog timer on TS-72XX boards. |
| 781 | |
| 782 | To compile this driver as a module, choose M here: the |
| 783 | module will be called ts72xx_wdt. |
| 784 | |
| 785 | config MAX63XX_WATCHDOG |
| 786 | tristate "Max63xx watchdog" |
| 787 | depends on HAS_IOMEM |
| 788 | select WATCHDOG_CORE |
| 789 | help |
| 790 | Support for memory mapped max63{69,70,71,72,73,74} watchdog timer. |
| 791 | |
| 792 | config MAX77620_WATCHDOG |
| 793 | tristate "Maxim Max77620 Watchdog Timer" |
| 794 | depends on MFD_MAX77620 || MFD_MAX77714 || COMPILE_TEST |
| 795 | select WATCHDOG_CORE |
| 796 | help |
| 797 | This is the driver for the Max77620 watchdog timer. |
| 798 | Say 'Y' here to enable the watchdog timer support for |
| 799 | MAX77620 chips. To compile this driver as a module, |
| 800 | choose M here: the module will be called max77620_wdt. |
| 801 | |
| 802 | config NCT6694_WATCHDOG |
| 803 | tristate "Nuvoton NCT6694 watchdog support" |
| 804 | depends on MFD_NCT6694 |
| 805 | select WATCHDOG_CORE |
| 806 | help |
| 807 | Say Y here to support Nuvoton NCT6694 watchdog timer |
| 808 | functionality. |
| 809 | |
| 810 | This driver can also be built as a module. If so, the module |
| 811 | will be called nct6694_wdt. |
| 812 | |
| 813 | config IMX2_WDT |
| 814 | tristate "IMX2+ Watchdog" |
| 815 | depends on ARCH_MXC || ARCH_LAYERSCAPE || COMPILE_TEST |
| 816 | select REGMAP_MMIO |
| 817 | select WATCHDOG_CORE |
| 818 | help |
| 819 | This is the driver for the hardware watchdog |
| 820 | on the Freescale IMX2 and later processors. |
| 821 | If you have one of these processors and wish to have |
| 822 | watchdog support enabled, say Y, otherwise say N. |
| 823 | |
| 824 | To compile this driver as a module, choose M here: the |
| 825 | module will be called imx2_wdt. |
| 826 | |
| 827 | config IMX_SC_WDT |
| 828 | tristate "IMX SC Watchdog" |
| 829 | depends on HAVE_ARM_SMCCC |
| 830 | depends on IMX_SCU || COMPILE_TEST |
| 831 | select WATCHDOG_CORE |
| 832 | help |
| 833 | This is the driver for the system controller watchdog |
| 834 | on the NXP i.MX SoCs with system controller inside, the |
| 835 | watchdog driver will call ARM SMC API and trap into |
| 836 | ARM-Trusted-Firmware for operations, ARM-Trusted-Firmware |
| 837 | will request system controller to execute the operations. |
| 838 | If you have one of these processors and wish to have |
| 839 | watchdog support enabled, say Y, otherwise say N. |
| 840 | |
| 841 | To compile this driver as a module, choose M here: the |
| 842 | module will be called imx_sc_wdt. |
| 843 | |
| 844 | config IMX7ULP_WDT |
| 845 | tristate "IMX7ULP Watchdog" |
| 846 | depends on ARCH_MXC || COMPILE_TEST |
| 847 | select WATCHDOG_CORE |
| 848 | help |
| 849 | This is the driver for the hardware watchdog on the Freescale |
| 850 | IMX7ULP and later processors. If you have one of these |
| 851 | processors and wish to have watchdog support enabled, |
| 852 | say Y, otherwise say N. |
| 853 | |
| 854 | To compile this driver as a module, choose M here: the |
| 855 | module will be called imx7ulp_wdt. |
| 856 | |
| 857 | config S32G_WDT |
| 858 | tristate "S32G Watchdog" |
| 859 | depends on ARCH_S32 || COMPILE_TEST |
| 860 | select WATCHDOG_CORE |
| 861 | help |
| 862 | This is the driver for the hardware watchdog on the NXP |
| 863 | S32G platforms. If you wish to have watchdog support |
| 864 | enabled, say Y, otherwise say N. |
| 865 | |
| 866 | config DB500_WATCHDOG |
| 867 | tristate "ST-Ericsson DB800 watchdog" |
| 868 | depends on MFD_DB8500_PRCMU |
| 869 | select WATCHDOG_CORE |
| 870 | default y |
| 871 | help |
| 872 | Say Y here to include Watchdog timer support for the watchdog |
| 873 | existing in the prcmu of ST-Ericsson DB8500 platform. |
| 874 | |
| 875 | To compile this driver as a module, choose M here: the |
| 876 | module will be called db500_wdt. |
| 877 | |
| 878 | config RETU_WATCHDOG |
| 879 | tristate "Retu watchdog" |
| 880 | depends on MFD_RETU |
| 881 | select WATCHDOG_CORE |
| 882 | help |
| 883 | Retu watchdog driver for Nokia Internet Tablets (770, N800, |
| 884 | N810). At least on N800 the watchdog cannot be disabled, so |
| 885 | this driver is essential and you should enable it. |
| 886 | |
| 887 | To compile this driver as a module, choose M here: the |
| 888 | module will be called retu_wdt. |
| 889 | |
| 890 | config MOXART_WDT |
| 891 | tristate "MOXART watchdog" |
| 892 | depends on ARCH_MOXART || COMPILE_TEST |
| 893 | help |
| 894 | Say Y here to include Watchdog timer support for the watchdog |
| 895 | existing on the MOXA ART SoC series platforms. |
| 896 | |
| 897 | To compile this driver as a module, choose M here: the |
| 898 | module will be called moxart_wdt. |
| 899 | |
| 900 | config ST_LPC_WATCHDOG |
| 901 | tristate "STMicroelectronics LPC Watchdog" |
| 902 | depends on ARCH_STI || COMPILE_TEST |
| 903 | depends on OF |
| 904 | select WATCHDOG_CORE |
| 905 | help |
| 906 | Say Y here to include STMicroelectronics Low Power Controller |
| 907 | (LPC) based Watchdog timer support. |
| 908 | |
| 909 | To compile this driver as a module, choose M here: the |
| 910 | module will be called st_lpc_wdt. |
| 911 | |
| 912 | config TEGRA_WATCHDOG |
| 913 | tristate "Tegra watchdog" |
| 914 | depends on (ARCH_TEGRA || COMPILE_TEST) && HAS_IOMEM |
| 915 | select WATCHDOG_CORE |
| 916 | help |
| 917 | Say Y here to include support for the watchdog timer |
| 918 | embedded in NVIDIA Tegra SoCs. |
| 919 | |
| 920 | To compile this driver as a module, choose M here: the |
| 921 | module will be called tegra_wdt. |
| 922 | |
| 923 | config QCOM_WDT |
| 924 | tristate "Qualcomm watchdog" |
| 925 | depends on HAS_IOMEM |
| 926 | depends on ARCH_QCOM || COMPILE_TEST |
| 927 | select WATCHDOG_CORE |
| 928 | help |
| 929 | Say Y here to include Watchdog timer support for the watchdog found |
| 930 | on QCOM chipsets. Currently supported targets are the MSM8960, |
| 931 | APQ8064, and IPQ8064. |
| 932 | |
| 933 | To compile this driver as a module, choose M here: the |
| 934 | module will be called qcom_wdt. |
| 935 | |
| 936 | config MESON_GXBB_WATCHDOG |
| 937 | tristate "Amlogic Meson GXBB SoCs watchdog support" |
| 938 | depends on ARCH_MESON || COMPILE_TEST |
| 939 | select WATCHDOG_CORE |
| 940 | help |
| 941 | Say Y here to include support for the watchdog timer |
| 942 | in Amlogic Meson GXBB SoCs. |
| 943 | To compile this driver as a module, choose M here: the |
| 944 | module will be called meson_gxbb_wdt. |
| 945 | |
| 946 | config MESON_WATCHDOG |
| 947 | tristate "Amlogic Meson SoCs watchdog support" |
| 948 | depends on ARCH_MESON || COMPILE_TEST |
| 949 | select WATCHDOG_CORE |
| 950 | help |
| 951 | Say Y here to include support for the watchdog timer |
| 952 | in Amlogic Meson SoCs. |
| 953 | To compile this driver as a module, choose M here: the |
| 954 | module will be called meson_wdt. |
| 955 | |
| 956 | config MEDIATEK_WATCHDOG |
| 957 | tristate "Mediatek SoCs watchdog support" |
| 958 | depends on ARCH_MEDIATEK || COMPILE_TEST |
| 959 | default ARCH_MEDIATEK |
| 960 | select WATCHDOG_CORE |
| 961 | select RESET_CONTROLLER |
| 962 | help |
| 963 | Say Y here to include support for the watchdog timer |
| 964 | in Mediatek SoCs. |
| 965 | To compile this driver as a module, choose M here: the |
| 966 | module will be called mtk_wdt. |
| 967 | |
| 968 | config DIGICOLOR_WATCHDOG |
| 969 | tristate "Conexant Digicolor SoCs watchdog support" |
| 970 | depends on ARCH_DIGICOLOR || COMPILE_TEST |
| 971 | select WATCHDOG_CORE |
| 972 | help |
| 973 | Say Y here to include support for the watchdog timer |
| 974 | in Conexant Digicolor SoCs. |
| 975 | To compile this driver as a module, choose M here: the |
| 976 | module will be called digicolor_wdt. |
| 977 | |
| 978 | config ARM_SMC_WATCHDOG |
| 979 | tristate "ARM Secure Monitor Call based watchdog support" |
| 980 | depends on ARM || ARM64 |
| 981 | depends on OF |
| 982 | depends on HAVE_ARM_SMCCC |
| 983 | select WATCHDOG_CORE |
| 984 | help |
| 985 | Say Y here to include support for a watchdog timer |
| 986 | implemented by the EL3 Secure Monitor on ARM platforms. |
| 987 | Requires firmware support. |
| 988 | To compile this driver as a module, choose M here: the |
| 989 | module will be called arm_smc_wdt. |
| 990 | |
| 991 | config LPC18XX_WATCHDOG |
| 992 | tristate "LPC18xx/43xx Watchdog" |
| 993 | depends on ARCH_LPC18XX || COMPILE_TEST |
| 994 | depends on HAS_IOMEM |
| 995 | select WATCHDOG_CORE |
| 996 | help |
| 997 | Say Y here if to include support for the watchdog timer |
| 998 | in NXP LPC SoCs family, which includes LPC18xx/LPC43xx |
| 999 | processors. |
| 1000 | To compile this driver as a module, choose M here: the |
| 1001 | module will be called lpc18xx_wdt. |
| 1002 | |
| 1003 | config RENESAS_WDT |
| 1004 | tristate "Renesas WDT Watchdog" |
| 1005 | depends on ARCH_RENESAS || COMPILE_TEST |
| 1006 | select WATCHDOG_CORE |
| 1007 | help |
| 1008 | This driver adds watchdog support for the integrated watchdogs in the |
| 1009 | Renesas R-Car and other SH-Mobile SoCs (usually named RWDT or SWDT). |
| 1010 | |
| 1011 | config RENESAS_WWDT |
| 1012 | tristate "Renesas Window WWDT Watchdog" |
| 1013 | depends on ARCH_RENESAS || COMPILE_TEST |
| 1014 | select WATCHDOG_CORE |
| 1015 | help |
| 1016 | This driver adds watchdog support for a window timer found in some |
| 1017 | Renesas R-Car Gen3 and later SoCs. |
| 1018 | |
| 1019 | config RENESAS_RZAWDT |
| 1020 | tristate "Renesas RZ/A WDT Watchdog" |
| 1021 | depends on ARCH_RENESAS || COMPILE_TEST |
| 1022 | select WATCHDOG_CORE |
| 1023 | help |
| 1024 | This driver adds watchdog support for the integrated watchdogs in the |
| 1025 | Renesas RZ/A SoCs. These watchdogs can be used to reset a system. |
| 1026 | |
| 1027 | config RENESAS_RZN1WDT |
| 1028 | tristate "Renesas RZ/N1 watchdog" |
| 1029 | depends on ARCH_RENESAS || COMPILE_TEST |
| 1030 | select WATCHDOG_CORE |
| 1031 | help |
| 1032 | This driver adds watchdog support for the integrated watchdogs in the |
| 1033 | Renesas RZ/N1 SoCs. These watchdogs can be used to reset a system. |
| 1034 | |
| 1035 | config RENESAS_RZG2LWDT |
| 1036 | tristate "Renesas RZ/G2L WDT Watchdog" |
| 1037 | depends on ARCH_RZG2L || ARCH_R9A09G011 || COMPILE_TEST |
| 1038 | depends on PM || COMPILE_TEST |
| 1039 | select WATCHDOG_CORE |
| 1040 | help |
| 1041 | This driver adds watchdog support for the integrated watchdogs in the |
| 1042 | Renesas RZ/G2L SoCs. These watchdogs can be used to reset a system. |
| 1043 | |
| 1044 | config RENESAS_RZV2HWDT |
| 1045 | tristate "Renesas RZ/{G3E,V2H(P)} WDT Watchdog" |
| 1046 | depends on ARCH_RENESAS || COMPILE_TEST |
| 1047 | depends on PM || COMPILE_TEST |
| 1048 | select WATCHDOG_CORE |
| 1049 | help |
| 1050 | This driver adds watchdog support for the integrated watchdogs in the |
| 1051 | Renesas RZ/{G3E,V2H(P)} SoCs. These watchdogs can be used to reset a |
| 1052 | system. |
| 1053 | |
| 1054 | config ASPEED_WATCHDOG |
| 1055 | tristate "Aspeed BMC watchdog support" |
| 1056 | depends on ARCH_ASPEED || COMPILE_TEST |
| 1057 | select WATCHDOG_CORE |
| 1058 | help |
| 1059 | Say Y here to include support for the watchdog timer |
| 1060 | in Aspeed BMC SoCs. |
| 1061 | |
| 1062 | This driver is required to reboot the SoC. |
| 1063 | |
| 1064 | To compile this driver as a module, choose M here: the |
| 1065 | module will be called aspeed_wdt. |
| 1066 | |
| 1067 | config STM32_WATCHDOG |
| 1068 | tristate "STM32 Independent WatchDoG (IWDG) support" |
| 1069 | depends on ARCH_STM32 || COMPILE_TEST |
| 1070 | select WATCHDOG_CORE |
| 1071 | default ARCH_STM32 |
| 1072 | help |
| 1073 | Say Y here to include support for the watchdog timer |
| 1074 | in stm32 SoCs. |
| 1075 | |
| 1076 | To compile this driver as a module, choose M here: the |
| 1077 | module will be called stm32_iwdg. |
| 1078 | |
| 1079 | config STPMIC1_WATCHDOG |
| 1080 | tristate "STPMIC1 PMIC watchdog support" |
| 1081 | depends on MFD_STPMIC1 |
| 1082 | select WATCHDOG_CORE |
| 1083 | help |
| 1084 | Say Y here to include watchdog support embedded into STPMIC1 PMIC. |
| 1085 | If the watchdog timer expires, stpmic1 will shut down all its power |
| 1086 | supplies. |
| 1087 | |
| 1088 | To compile this driver as a module, choose M here: the |
| 1089 | module will be called spmic1_wdt. |
| 1090 | |
| 1091 | config UNIPHIER_WATCHDOG |
| 1092 | tristate "UniPhier watchdog support" |
| 1093 | depends on ARCH_UNIPHIER || COMPILE_TEST |
| 1094 | depends on OF && MFD_SYSCON |
| 1095 | select WATCHDOG_CORE |
| 1096 | help |
| 1097 | Say Y here to include support watchdog timer embedded |
| 1098 | into the UniPhier system. |
| 1099 | |
| 1100 | To compile this driver as a module, choose M here: the |
| 1101 | module will be called uniphier_wdt. |
| 1102 | |
| 1103 | config RTD119X_WATCHDOG |
| 1104 | bool "Realtek RTD119x/RTD129x watchdog support" |
| 1105 | depends on ARCH_REALTEK || COMPILE_TEST |
| 1106 | depends on OF |
| 1107 | select WATCHDOG_CORE |
| 1108 | default ARCH_REALTEK |
| 1109 | help |
| 1110 | Say Y here to include support for the watchdog timer in |
| 1111 | Realtek RTD1295 SoCs. |
| 1112 | |
| 1113 | config REALTEK_OTTO_WDT |
| 1114 | tristate "Realtek Otto MIPS watchdog support" |
| 1115 | depends on MACH_REALTEK_RTL || COMPILE_TEST |
| 1116 | depends on COMMON_CLK |
| 1117 | select WATCHDOG_CORE |
| 1118 | select REGMAP_MMIO |
| 1119 | default MACH_REALTEK_RTL |
| 1120 | help |
| 1121 | Say Y here to include support for the watchdog timer on Realtek |
| 1122 | RTL838x, RTL839x, RTL930x SoCs. This watchdog has pretimeout |
| 1123 | notifications and system reset on timeout. |
| 1124 | |
| 1125 | When built as a module this will be called realtek_otto_wdt. |
| 1126 | |
| 1127 | config SPRD_WATCHDOG |
| 1128 | tristate "Spreadtrum watchdog support" |
| 1129 | depends on ARCH_SPRD || COMPILE_TEST |
| 1130 | select WATCHDOG_CORE |
| 1131 | help |
| 1132 | Say Y here to include watchdog timer supported |
| 1133 | by Spreadtrum system. |
| 1134 | |
| 1135 | config PM8916_WATCHDOG |
| 1136 | tristate "Qualcomm PM8916 pmic watchdog" |
| 1137 | depends on OF && MFD_SPMI_PMIC |
| 1138 | select WATCHDOG_CORE |
| 1139 | help |
| 1140 | Say Y here to include support watchdog timer embedded into the |
| 1141 | pm8916 module. |
| 1142 | |
| 1143 | config VISCONTI_WATCHDOG |
| 1144 | tristate "Toshiba Visconti series watchdog support" |
| 1145 | depends on ARCH_VISCONTI || COMPILE_TEST |
| 1146 | select WATCHDOG_CORE |
| 1147 | help |
| 1148 | Say Y here to include support for the watchdog timer in Toshiba |
| 1149 | Visconti SoCs. |
| 1150 | |
| 1151 | config MSC313E_WATCHDOG |
| 1152 | tristate "MStar MSC313e watchdog" |
| 1153 | depends on ARCH_MSTARV7 || COMPILE_TEST |
| 1154 | select WATCHDOG_CORE |
| 1155 | help |
| 1156 | Say Y here to include support for the Watchdog timer embedded |
| 1157 | into MStar MSC313e chips. This will reboot your system when the |
| 1158 | timeout is reached. |
| 1159 | |
| 1160 | To compile this driver as a module, choose M here: the |
| 1161 | module will be called msc313e_wdt. |
| 1162 | |
| 1163 | config APPLE_WATCHDOG |
| 1164 | tristate "Apple SoC watchdog" |
| 1165 | depends on ARCH_APPLE || COMPILE_TEST |
| 1166 | select WATCHDOG_CORE |
| 1167 | help |
| 1168 | Say Y here to include support for the Watchdog found in Apple |
| 1169 | SoCs such as the M1. Next to the common watchdog features this |
| 1170 | driver is also required in order to reboot these SoCs. |
| 1171 | |
| 1172 | To compile this driver as a module, choose M here: the |
| 1173 | module will be called apple_wdt. |
| 1174 | |
| 1175 | config SUNPLUS_WATCHDOG |
| 1176 | tristate "Sunplus watchdog support" |
| 1177 | depends on ARCH_SUNPLUS || COMPILE_TEST |
| 1178 | select WATCHDOG_CORE |
| 1179 | help |
| 1180 | Say Y here to include support for the watchdog timer |
| 1181 | in Sunplus SoCs. |
| 1182 | |
| 1183 | To compile this driver as a module, choose M here: the |
| 1184 | module will be called sunplus_wdt. |
| 1185 | |
| 1186 | # X86 (i386 + ia64 + x86_64) Architecture |
| 1187 | |
| 1188 | config ACQUIRE_WDT |
| 1189 | tristate "Acquire SBC Watchdog Timer" |
| 1190 | depends on X86 |
| 1191 | help |
| 1192 | This is the driver for the hardware watchdog on Single Board |
| 1193 | Computers produced by Acquire Inc (and others). This watchdog |
| 1194 | simply watches your kernel to make sure it doesn't freeze, and if |
| 1195 | it does, it reboots your computer after a certain amount of time. |
| 1196 | |
| 1197 | To compile this driver as a module, choose M here: the |
| 1198 | module will be called acquirewdt. |
| 1199 | |
| 1200 | Most people will say N. |
| 1201 | |
| 1202 | config ADVANTECH_WDT |
| 1203 | tristate "Advantech SBC Watchdog Timer" |
| 1204 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1205 | help |
| 1206 | If you are configuring a Linux kernel for the Advantech single-board |
| 1207 | computer, say `Y' here to support its built-in watchdog timer |
| 1208 | feature. More information can be found at |
| 1209 | <https://www.advantech.com.tw/products/> |
| 1210 | |
| 1211 | config ADVANTECH_EC_WDT |
| 1212 | tristate "Advantech Embedded Controller Watchdog Timer" |
| 1213 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1214 | select ISA_BUS_API |
| 1215 | select WATCHDOG_CORE |
| 1216 | help |
| 1217 | This driver supports Advantech products with ITE based Embedded Controller. |
| 1218 | It does not support Advantech products with other ECs or without EC. |
| 1219 | |
| 1220 | config ALIM1535_WDT |
| 1221 | tristate "ALi M1535 PMU Watchdog Timer" |
| 1222 | depends on (X86 || COMPILE_TEST) && PCI |
| 1223 | help |
| 1224 | This is the driver for the hardware watchdog on the ALi M1535 PMU. |
| 1225 | |
| 1226 | To compile this driver as a module, choose M here: the |
| 1227 | module will be called alim1535_wdt. |
| 1228 | |
| 1229 | Most people will say N. |
| 1230 | |
| 1231 | config ALIM7101_WDT |
| 1232 | tristate "ALi M7101 PMU Computer Watchdog" |
| 1233 | depends on PCI |
| 1234 | help |
| 1235 | This is the driver for the hardware watchdog on the ALi M7101 PMU |
| 1236 | as used in the x86 Cobalt servers and also found in some |
| 1237 | SPARC Netra servers too. |
| 1238 | |
| 1239 | To compile this driver as a module, choose M here: the |
| 1240 | module will be called alim7101_wdt. |
| 1241 | |
| 1242 | Most people will say N. |
| 1243 | |
| 1244 | config CGBC_WDT |
| 1245 | tristate "Congatec Board Controller Watchdog Timer" |
| 1246 | depends on MFD_CGBC |
| 1247 | select WATCHDOG_CORE |
| 1248 | help |
| 1249 | Enables watchdog timer support for the Congatec Board Controller. |
| 1250 | |
| 1251 | This driver can also be built as a module. If so, the module will be |
| 1252 | called cgbc_wdt. |
| 1253 | |
| 1254 | config EBC_C384_WDT |
| 1255 | tristate "WinSystems EBC-C384 Watchdog Timer" |
| 1256 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1257 | select ISA_BUS_API |
| 1258 | select WATCHDOG_CORE |
| 1259 | help |
| 1260 | Enables watchdog timer support for the watchdog timer on the |
| 1261 | WinSystems EBC-C384 motherboard. The timeout may be configured via |
| 1262 | the timeout module parameter. |
| 1263 | |
| 1264 | config EXAR_WDT |
| 1265 | tristate "Exar Watchdog Timer" |
| 1266 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1267 | select WATCHDOG_CORE |
| 1268 | help |
| 1269 | Enables watchdog timer support for the watchdog timer present |
| 1270 | in some Exar/MaxLinear UART chips like the XR28V38x. |
| 1271 | |
| 1272 | To compile this driver as a module, choose M here: the |
| 1273 | module will be called exar_wdt. |
| 1274 | |
| 1275 | config F71808E_WDT |
| 1276 | tristate "Fintek F718xx, F818xx Super I/O Watchdog" |
| 1277 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1278 | select WATCHDOG_CORE |
| 1279 | help |
| 1280 | This is the driver for the hardware watchdog on the Fintek F71808E, |
| 1281 | F71862FG, F71868, F71869, F71882FG, F71889FG, F81803, F81865, and |
| 1282 | F81866 Super I/O controllers. |
| 1283 | |
| 1284 | You can compile this driver directly into the kernel, or use |
| 1285 | it as a module. The module will be called f71808e_wdt. |
| 1286 | |
| 1287 | config SP5100_TCO |
| 1288 | tristate "AMD/ATI SP5100 TCO Timer/Watchdog" |
| 1289 | depends on (X86 || COMPILE_TEST) && PCI && HAS_IOPORT |
| 1290 | select WATCHDOG_CORE |
| 1291 | help |
| 1292 | Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO |
| 1293 | (Total Cost of Ownership) timer is a watchdog timer that will reboot |
| 1294 | the machine after its expiration. The expiration time can be |
| 1295 | configured with the "heartbeat" parameter. |
| 1296 | |
| 1297 | To compile this driver as a module, choose M here: the |
| 1298 | module will be called sp5100_tco. |
| 1299 | |
| 1300 | config GEODE_WDT |
| 1301 | tristate "AMD Geode CS5535/CS5536 Watchdog" |
| 1302 | depends on CS5535_MFGPT |
| 1303 | help |
| 1304 | This driver enables a watchdog capability built into the |
| 1305 | CS5535/CS5536 companion chips for the AMD Geode GX and LX |
| 1306 | processors. This watchdog watches your kernel to make sure |
| 1307 | it doesn't freeze, and if it does, it reboots your computer after |
| 1308 | a certain amount of time. |
| 1309 | |
| 1310 | You can compile this driver directly into the kernel, or use |
| 1311 | it as a module. The module will be called geodewdt. |
| 1312 | |
| 1313 | config SBC_FITPC2_WATCHDOG |
| 1314 | tristate "Compulab SBC-FITPC2 watchdog" |
| 1315 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1316 | help |
| 1317 | This is the driver for the built-in watchdog timer on the fit-PC2, |
| 1318 | fit-PC2i, CM-iAM single-board computers made by Compulab. |
| 1319 | |
| 1320 | It's possible to enable the watchdog timer either from BIOS (F2) or |
| 1321 | from booted Linux. |
| 1322 | When the "Watchdog Timer Value" is enabled one can set 31-255 seconds |
| 1323 | operational range. |
| 1324 | |
| 1325 | Entering BIOS setup temporarily disables watchdog operation regardless |
| 1326 | of current state, so system will not be restarted while user is in |
| 1327 | BIOS setup. |
| 1328 | |
| 1329 | Once the watchdog is enabled the system will be restarted every |
| 1330 | "Watchdog Timer Value" period, so to prevent it user can restart or |
| 1331 | disable the watchdog. |
| 1332 | |
| 1333 | To compile this driver as a module, choose M here: the |
| 1334 | module will be called sbc_fitpc2_wdt. |
| 1335 | |
| 1336 | Most people will say N. |
| 1337 | |
| 1338 | config EUROTECH_WDT |
| 1339 | tristate "Eurotech CPU-1220/1410 Watchdog Timer" |
| 1340 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1341 | help |
| 1342 | Enable support for the watchdog timer on the Eurotech CPU-1220 and |
| 1343 | CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product |
| 1344 | information are at <http://www.eurotech.it/>. |
| 1345 | |
| 1346 | config IB700_WDT |
| 1347 | tristate "IB700 SBC Watchdog Timer" |
| 1348 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1349 | help |
| 1350 | This is the driver for the hardware watchdog on the IB700 Single |
| 1351 | Board Computer produced by TMC Technology (www.tmc-uk.com). This |
| 1352 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 1353 | and if it does, it reboots your computer after a certain amount of time. |
| 1354 | |
| 1355 | This driver is like the WDT501 driver but for slightly different |
| 1356 | hardware. |
| 1357 | |
| 1358 | To compile this driver as a module, choose M here: the |
| 1359 | module will be called ib700wdt. |
| 1360 | |
| 1361 | Most people will say N. |
| 1362 | |
| 1363 | config IBMASR |
| 1364 | tristate "IBM Automatic Server Restart" |
| 1365 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1366 | help |
| 1367 | This is the driver for the IBM Automatic Server Restart watchdog |
| 1368 | timer built-in into some eServer xSeries machines. |
| 1369 | |
| 1370 | To compile this driver as a module, choose M here: the |
| 1371 | module will be called ibmasr. |
| 1372 | |
| 1373 | config WAFER_WDT |
| 1374 | tristate "ICP Single Board Computer Watchdog Timer" |
| 1375 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1376 | help |
| 1377 | This is a driver for the hardware watchdog on the ICP Single |
| 1378 | Board Computer. This driver is working on (at least) the following |
| 1379 | IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782. |
| 1380 | |
| 1381 | To compile this driver as a module, choose M here: the |
| 1382 | module will be called wafer5823wdt. |
| 1383 | |
| 1384 | config I6300ESB_WDT |
| 1385 | tristate "Intel 6300ESB Timer/Watchdog" |
| 1386 | depends on PCI |
| 1387 | select WATCHDOG_CORE |
| 1388 | help |
| 1389 | Hardware driver for the watchdog timer built into the Intel |
| 1390 | 6300ESB controller hub. |
| 1391 | |
| 1392 | To compile this driver as a module, choose M here: the |
| 1393 | module will be called i6300esb. |
| 1394 | |
| 1395 | config IE6XX_WDT |
| 1396 | tristate "Intel Atom E6xx Watchdog" |
| 1397 | depends on (X86 || COMPILE_TEST) && PCI && HAS_IOPORT |
| 1398 | select WATCHDOG_CORE |
| 1399 | select MFD_CORE |
| 1400 | select LPC_SCH |
| 1401 | help |
| 1402 | Hardware driver for the watchdog timer built into the Intel |
| 1403 | Atom E6XX (TunnelCreek) processor. |
| 1404 | |
| 1405 | To compile this driver as a module, choose M here: the |
| 1406 | module will be called ie6xx_wdt. |
| 1407 | |
| 1408 | config INTEL_MID_WATCHDOG |
| 1409 | tristate "Intel MID Watchdog Timer" |
| 1410 | depends on X86_INTEL_MID |
| 1411 | select WATCHDOG_CORE |
| 1412 | help |
| 1413 | Watchdog timer driver built into the Intel SCU for Intel MID |
| 1414 | Platforms. |
| 1415 | |
| 1416 | This driver currently supports only the watchdog evolution |
| 1417 | implementation in SCU, available for Merrifield generation. |
| 1418 | |
| 1419 | To compile this driver as a module, choose M here. |
| 1420 | |
| 1421 | config INTEL_OC_WATCHDOG |
| 1422 | tristate "Intel OC Watchdog" |
| 1423 | depends on (X86 || COMPILE_TEST) && ACPI && HAS_IOPORT |
| 1424 | select WATCHDOG_CORE |
| 1425 | help |
| 1426 | Hardware driver for Intel Over-Clocking watchdog present in |
| 1427 | Platform Controller Hub (PCH) chipsets. |
| 1428 | |
| 1429 | To compile this driver as a module, choose M here: the |
| 1430 | module will be called intel_oc_wdt. |
| 1431 | |
| 1432 | config ITCO_WDT |
| 1433 | tristate "Intel TCO Timer/Watchdog" |
| 1434 | depends on X86 && PCI |
| 1435 | select WATCHDOG_CORE |
| 1436 | depends on I2C || I2C=n |
| 1437 | depends on MFD_INTEL_PMC_BXT || !MFD_INTEL_PMC_BXT |
| 1438 | depends on HAS_IOPORT # for I2C_I801 |
| 1439 | select LPC_ICH if !EXPERT |
| 1440 | select I2C_I801 if !EXPERT && I2C |
| 1441 | help |
| 1442 | Hardware driver for the intel TCO timer based watchdog devices. |
| 1443 | These drivers are included in the Intel 82801 I/O Controller |
| 1444 | Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB |
| 1445 | controller hub. |
| 1446 | |
| 1447 | The TCO (Total Cost of Ownership) timer is a watchdog timer |
| 1448 | that will reboot the machine after its second expiration. The |
| 1449 | expiration time can be configured with the "heartbeat" parameter. |
| 1450 | |
| 1451 | On some motherboards the driver may fail to reset the chipset's |
| 1452 | NO_REBOOT flag which prevents the watchdog from rebooting the |
| 1453 | machine. If this is the case you will get a kernel message like |
| 1454 | "failed to reset NO_REBOOT flag, reboot disabled by hardware". |
| 1455 | |
| 1456 | To compile this driver as a module, choose M here: the |
| 1457 | module will be called iTCO_wdt. |
| 1458 | |
| 1459 | config IT8712F_WDT |
| 1460 | tristate "IT8712F (Smart Guardian) Watchdog Timer" |
| 1461 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1462 | help |
| 1463 | This is the driver for the built-in watchdog timer on the IT8712F |
| 1464 | Super I/0 chipset used on many motherboards. |
| 1465 | |
| 1466 | If the driver does not work, then make sure that the game port in |
| 1467 | the BIOS is enabled. |
| 1468 | |
| 1469 | To compile this driver as a module, choose M here: the |
| 1470 | module will be called it8712f_wdt. |
| 1471 | |
| 1472 | config IT87_WDT |
| 1473 | tristate "IT87 Watchdog Timer" |
| 1474 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1475 | select WATCHDOG_CORE |
| 1476 | help |
| 1477 | This is the driver for the hardware watchdog on the ITE IT8607, |
| 1478 | IT8620, IT8622, IT8625, IT8628, IT8655, IT8665, IT8686, IT8702, |
| 1479 | IT8712, IT8716, IT8718, IT8720, IT8721, IT8726, IT8728, and |
| 1480 | IT8783 Super I/O chips. |
| 1481 | |
| 1482 | This watchdog simply watches your kernel to make sure it doesn't |
| 1483 | freeze, and if it does, it reboots your computer after a certain |
| 1484 | amount of time. |
| 1485 | |
| 1486 | To compile this driver as a module, choose M here: the module will |
| 1487 | be called it87_wdt. |
| 1488 | |
| 1489 | config HP_WATCHDOG |
| 1490 | tristate "HP ProLiant iLO2+ Hardware Watchdog Timer" |
| 1491 | select WATCHDOG_CORE |
| 1492 | depends on (ARM64 || X86 || COMPILE_TEST) && PCI |
| 1493 | help |
| 1494 | A software monitoring watchdog and NMI handling driver. This driver |
| 1495 | will detect lockups and provide a stack trace. This is a driver that |
| 1496 | will only load on an HP ProLiant system with a minimum of iLO2 support. |
| 1497 | To compile this driver as a module, choose M here: the module will be |
| 1498 | called hpwdt. |
| 1499 | |
| 1500 | config HPWDT_NMI_DECODING |
| 1501 | bool "NMI support for the HP ProLiant iLO2+ Hardware Watchdog Timer" |
| 1502 | depends on X86 && HP_WATCHDOG |
| 1503 | default y |
| 1504 | help |
| 1505 | Enables the NMI handler for the watchdog pretimeout NMI and the iLO |
| 1506 | "Generate NMI to System" virtual button. When an NMI is claimed |
| 1507 | by the driver, panic is called. |
| 1508 | |
| 1509 | config KEMPLD_WDT |
| 1510 | tristate "Kontron COM Watchdog Timer" |
| 1511 | depends on MFD_KEMPLD |
| 1512 | select WATCHDOG_CORE |
| 1513 | help |
| 1514 | Support for the PLD watchdog on some Kontron ETX and COMexpress |
| 1515 | (ETXexpress) modules |
| 1516 | |
| 1517 | This driver can also be built as a module. If so, the module will be |
| 1518 | called kempld_wdt. |
| 1519 | |
| 1520 | config SC1200_WDT |
| 1521 | tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" |
| 1522 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1523 | help |
| 1524 | This is a driver for National Semiconductor PC87307/PC97307 hardware |
| 1525 | watchdog cards as found on the SC1200. This watchdog is mainly used |
| 1526 | for power management purposes and can be used to power down the device |
| 1527 | during inactivity periods (includes interrupt activity monitoring). |
| 1528 | |
| 1529 | To compile this driver as a module, choose M here: the |
| 1530 | module will be called sc1200wdt. |
| 1531 | |
| 1532 | Most people will say N. |
| 1533 | |
| 1534 | config SCx200_WDT |
| 1535 | tristate "National Semiconductor SCx200 Watchdog" |
| 1536 | depends on SCx200 && PCI |
| 1537 | help |
| 1538 | Enable the built-in watchdog timer support on the National |
| 1539 | Semiconductor SCx200 processors. |
| 1540 | |
| 1541 | If compiled as a module, it will be called scx200_wdt. |
| 1542 | |
| 1543 | config PC87413_WDT |
| 1544 | tristate "NS PC87413 watchdog" |
| 1545 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1546 | help |
| 1547 | This is the driver for the hardware watchdog on the PC87413 chipset |
| 1548 | This watchdog simply watches your kernel to make sure it doesn't |
| 1549 | freeze, and if it does, it reboots your computer after a certain |
| 1550 | amount of time. |
| 1551 | |
| 1552 | To compile this driver as a module, choose M here: the |
| 1553 | module will be called pc87413_wdt. |
| 1554 | |
| 1555 | Most people will say N. |
| 1556 | |
| 1557 | config NV_TCO |
| 1558 | tristate "nVidia TCO Timer/Watchdog" |
| 1559 | depends on (X86 || COMPILE_TEST) && PCI && HAS_IOPORT |
| 1560 | help |
| 1561 | Hardware driver for the TCO timer built into the nVidia Hub family |
| 1562 | (such as the MCP51). The TCO (Total Cost of Ownership) timer is a |
| 1563 | watchdog timer that will reboot the machine after its second |
| 1564 | expiration. The expiration time can be configured with the |
| 1565 | "heartbeat" parameter. |
| 1566 | |
| 1567 | On some motherboards the driver may fail to reset the chipset's |
| 1568 | NO_REBOOT flag which prevents the watchdog from rebooting the |
| 1569 | machine. If this is the case you will get a kernel message like |
| 1570 | "failed to reset NO_REBOOT flag, reboot disabled by hardware". |
| 1571 | |
| 1572 | To compile this driver as a module, choose M here: the |
| 1573 | module will be called nv_tco. |
| 1574 | |
| 1575 | config RDC321X_WDT |
| 1576 | tristate "RDC R-321x SoC watchdog" |
| 1577 | depends on X86_32 || COMPILE_TEST |
| 1578 | depends on PCI |
| 1579 | help |
| 1580 | This is the driver for the built in hardware watchdog |
| 1581 | in the RDC R-321x SoC. |
| 1582 | |
| 1583 | To compile this driver as a module, choose M here: the |
| 1584 | module will be called rdc321x_wdt. |
| 1585 | |
| 1586 | config 60XX_WDT |
| 1587 | tristate "SBC-60XX Watchdog Timer" |
| 1588 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1589 | help |
| 1590 | This driver can be used with the watchdog timer found on some |
| 1591 | single board computers, namely the 6010 PII based computer. |
| 1592 | It may well work with other cards. It reads port 0x443 to enable |
| 1593 | and re-set the watchdog timer, and reads port 0x45 to disable |
| 1594 | the watchdog. If you have a card that behave in similar ways, |
| 1595 | you can probably make this driver work with your card as well. |
| 1596 | |
| 1597 | You can compile this driver directly into the kernel, or use |
| 1598 | it as a module. The module will be called sbc60xxwdt. |
| 1599 | |
| 1600 | config SBC8360_WDT |
| 1601 | tristate "SBC8360 Watchdog Timer" |
| 1602 | depends on X86_32 && HAS_IOPORT |
| 1603 | help |
| 1604 | |
| 1605 | This is the driver for the hardware watchdog on the SBC8360 Single |
| 1606 | Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). |
| 1607 | |
| 1608 | To compile this driver as a module, choose M here: the |
| 1609 | module will be called sbc8360. |
| 1610 | |
| 1611 | Most people will say N. |
| 1612 | |
| 1613 | config SBC7240_WDT |
| 1614 | tristate "SBC Nano 7240 Watchdog Timer" |
| 1615 | depends on X86_32 && HAS_IOPORT |
| 1616 | help |
| 1617 | This is the driver for the hardware watchdog found on the IEI |
| 1618 | single board computers EPIC Nano 7240 (and likely others). This |
| 1619 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 1620 | and if it does, it reboots your computer after a certain amount of |
| 1621 | time. |
| 1622 | |
| 1623 | To compile this driver as a module, choose M here: the |
| 1624 | module will be called sbc7240_wdt. |
| 1625 | |
| 1626 | config SMSC_SCH311X_WDT |
| 1627 | tristate "SMSC SCH311X Watchdog Timer" |
| 1628 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1629 | help |
| 1630 | This is the driver for the hardware watchdog timer on the |
| 1631 | SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset |
| 1632 | (LPC IO with 8042 KBC, Reset Generation, HWM and multiple |
| 1633 | serial ports). |
| 1634 | |
| 1635 | To compile this driver as a module, choose M here: the |
| 1636 | module will be called sch311x_wdt. |
| 1637 | |
| 1638 | config SMSC37B787_WDT |
| 1639 | tristate "Winbond SMsC37B787 Watchdog Timer" |
| 1640 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1641 | help |
| 1642 | This is the driver for the hardware watchdog component on the |
| 1643 | Winbond SMsC37B787 chipset as used on the NetRunner Mainboard |
| 1644 | from Vision Systems and maybe others. |
| 1645 | |
| 1646 | This watchdog simply watches your kernel to make sure it doesn't |
| 1647 | freeze, and if it does, it reboots your computer after a certain |
| 1648 | amount of time. |
| 1649 | |
| 1650 | Usually a userspace daemon will notify the kernel WDT driver that |
| 1651 | userspace is still alive, at regular intervals. |
| 1652 | |
| 1653 | To compile this driver as a module, choose M here: the |
| 1654 | module will be called smsc37b787_wdt. |
| 1655 | |
| 1656 | Most people will say N. |
| 1657 | |
| 1658 | config TQMX86_WDT |
| 1659 | tristate "TQ-Systems TQMX86 Watchdog Timer" |
| 1660 | depends on X86 || COMPILE_TEST |
| 1661 | select WATCHDOG_CORE |
| 1662 | help |
| 1663 | This is the driver for the hardware watchdog timer in the TQMX86 IO |
| 1664 | controller found on some of their ComExpress Modules. |
| 1665 | |
| 1666 | To compile this driver as a module, choose M here; the module |
| 1667 | will be called tqmx86_wdt. |
| 1668 | |
| 1669 | Most people will say N. |
| 1670 | |
| 1671 | config VIA_WDT |
| 1672 | tristate "VIA Watchdog Timer" |
| 1673 | depends on (X86 || COMPILE_TEST) && PCI |
| 1674 | select WATCHDOG_CORE |
| 1675 | help |
| 1676 | This is the driver for the hardware watchdog timer on VIA |
| 1677 | southbridge chipset CX700, VX800/VX820 or VX855/VX875. |
| 1678 | |
| 1679 | To compile this driver as a module, choose M here; the module |
| 1680 | will be called via_wdt. |
| 1681 | |
| 1682 | Most people will say N. |
| 1683 | |
| 1684 | config W83627HF_WDT |
| 1685 | tristate "Watchdog timer for W83627HF/W83627DHG and compatibles" |
| 1686 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1687 | select WATCHDOG_CORE |
| 1688 | help |
| 1689 | This is the driver for the hardware watchdog on the following |
| 1690 | Super I/O chips. |
| 1691 | W83627DHG/DHG-P/EHF/EHG/F/G/HF/S/SF/THF/UHG/UG |
| 1692 | W83637HF |
| 1693 | W83667HG/HG-B |
| 1694 | W83687THF |
| 1695 | W83697HF |
| 1696 | W83697UG |
| 1697 | NCT6775 |
| 1698 | NCT6776 |
| 1699 | NCT6779 |
| 1700 | NCT6791 |
| 1701 | NCT6792 |
| 1702 | NCT6102D/04D/06D |
| 1703 | NCT6116D |
| 1704 | |
| 1705 | This watchdog simply watches your kernel to make sure it doesn't |
| 1706 | freeze, and if it does, it reboots your computer after a certain |
| 1707 | amount of time. |
| 1708 | |
| 1709 | To compile this driver as a module, choose M here: the |
| 1710 | module will be called w83627hf_wdt. |
| 1711 | |
| 1712 | Most people will say N. |
| 1713 | |
| 1714 | config W83877F_WDT |
| 1715 | tristate "W83877F (EMACS) Watchdog Timer" |
| 1716 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1717 | help |
| 1718 | This is the driver for the hardware watchdog on the W83877F chipset |
| 1719 | as used in EMACS PC-104 motherboards (and likely others). This |
| 1720 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 1721 | and if it does, it reboots your computer after a certain amount of |
| 1722 | time. |
| 1723 | |
| 1724 | To compile this driver as a module, choose M here: the |
| 1725 | module will be called w83877f_wdt. |
| 1726 | |
| 1727 | Most people will say N. |
| 1728 | |
| 1729 | config W83977F_WDT |
| 1730 | tristate "W83977F (PCM-5335) Watchdog Timer" |
| 1731 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1732 | help |
| 1733 | This is the driver for the hardware watchdog on the W83977F I/O chip |
| 1734 | as used in AAEON's PCM-5335 SBC (and likely others). This |
| 1735 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 1736 | and if it does, it reboots your computer after a certain amount of |
| 1737 | time. |
| 1738 | |
| 1739 | To compile this driver as a module, choose M here: the |
| 1740 | module will be called w83977f_wdt. |
| 1741 | |
| 1742 | config SBC_EPX_C3_WATCHDOG |
| 1743 | tristate "Winsystems SBC EPX-C3 watchdog" |
| 1744 | depends on (X86 || COMPILE_TEST) && HAS_IOPORT |
| 1745 | help |
| 1746 | This is the driver for the built-in watchdog timer on the EPX-C3 |
| 1747 | Single-board computer made by Winsystems, Inc. |
| 1748 | |
| 1749 | *Note*: This hardware watchdog is not probeable and thus there |
| 1750 | is no way to know if writing to its IO address will corrupt |
| 1751 | your system or have any real effect. The only way to be sure |
| 1752 | that this driver does what you want is to make sure you |
| 1753 | are running it on an EPX-C3 from Winsystems with the watchdog |
| 1754 | timer at IO address 0x1ee and 0x1ef. It will write to both those |
| 1755 | IO ports. Basically, the assumption is made that if you compile |
| 1756 | this driver into your kernel and/or load it as a module, that you |
| 1757 | know what you are doing and that you are in fact running on an |
| 1758 | EPX-C3 board! |
| 1759 | |
| 1760 | To compile this driver as a module, choose M here: the |
| 1761 | module will be called sbc_epx_c3. |
| 1762 | |
| 1763 | config INTEL_MEI_WDT |
| 1764 | tristate "Intel MEI iAMT Watchdog" |
| 1765 | depends on INTEL_MEI && X86 |
| 1766 | select WATCHDOG_CORE |
| 1767 | help |
| 1768 | A device driver for the Intel MEI iAMT watchdog. |
| 1769 | |
| 1770 | The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog. |
| 1771 | Whenever the OS hangs or crashes, iAMT will send an event |
| 1772 | to any subscriber to this event. The watchdog doesn't reset the |
| 1773 | the platform. |
| 1774 | |
| 1775 | To compile this driver as a module, choose M here: |
| 1776 | the module will be called mei_wdt. |
| 1777 | |
| 1778 | config NI903X_WDT |
| 1779 | tristate "NI 903x/913x Watchdog" |
| 1780 | depends on X86 && ACPI |
| 1781 | select WATCHDOG_CORE |
| 1782 | help |
| 1783 | This is the driver for the watchdog timer on the National Instruments |
| 1784 | 903x/913x real-time controllers. |
| 1785 | |
| 1786 | To compile this driver as a module, choose M here: the module will be |
| 1787 | called ni903x_wdt. |
| 1788 | |
| 1789 | config NIC7018_WDT |
| 1790 | tristate "NIC7018 Watchdog" |
| 1791 | depends on HAS_IOPORT |
| 1792 | depends on ACPI || COMPILE_TEST |
| 1793 | select WATCHDOG_CORE |
| 1794 | help |
| 1795 | Support for National Instruments NIC7018 Watchdog. |
| 1796 | |
| 1797 | To compile this driver as a module, choose M here: the module will be |
| 1798 | called nic7018_wdt. |
| 1799 | |
| 1800 | config SIEMENS_SIMATIC_IPC_WDT |
| 1801 | tristate "Siemens Simatic IPC Watchdog" |
| 1802 | depends on SIEMENS_SIMATIC_IPC && PCI |
| 1803 | default y |
| 1804 | select WATCHDOG_CORE |
| 1805 | select P2SB if X86 |
| 1806 | help |
| 1807 | This driver adds support for several watchdogs found in Industrial |
| 1808 | PCs from Siemens. |
| 1809 | |
| 1810 | To compile this driver as a module, choose M here: the module will be |
| 1811 | called simatic-ipc-wdt. |
| 1812 | |
| 1813 | # M68K Architecture |
| 1814 | |
| 1815 | config M54xx_WATCHDOG |
| 1816 | tristate "MCF54xx watchdog support" |
| 1817 | depends on M548x |
| 1818 | help |
| 1819 | To compile this driver as a module, choose M here: the |
| 1820 | module will be called m54xx_wdt. |
| 1821 | |
| 1822 | # MicroBlaze Architecture |
| 1823 | |
| 1824 | # MIPS Architecture |
| 1825 | |
| 1826 | config ATH79_WDT |
| 1827 | tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog" |
| 1828 | depends on ATH79 || (ARM && COMPILE_TEST) |
| 1829 | help |
| 1830 | Hardware driver for the built-in watchdog timer on the Atheros |
| 1831 | AR71XX/AR724X/AR913X SoCs. |
| 1832 | |
| 1833 | config BCM47XX_WDT |
| 1834 | tristate "Broadcom BCM47xx Watchdog Timer" |
| 1835 | depends on BCM47XX || ARCH_BCM_5301X || COMPILE_TEST |
| 1836 | select WATCHDOG_CORE |
| 1837 | help |
| 1838 | Hardware driver for the Broadcom BCM47xx Watchdog Timer. |
| 1839 | |
| 1840 | config RC32434_WDT |
| 1841 | tristate "IDT RC32434 SoC Watchdog Timer" |
| 1842 | depends on MIKROTIK_RB532 |
| 1843 | help |
| 1844 | Hardware driver for the IDT RC32434 SoC built-in |
| 1845 | watchdog timer. |
| 1846 | |
| 1847 | To compile this driver as a module, choose M here: the |
| 1848 | module will be called rc32434_wdt. |
| 1849 | |
| 1850 | config INDYDOG |
| 1851 | tristate "Indy/I2 Hardware Watchdog" |
| 1852 | depends on SGI_HAS_INDYDOG |
| 1853 | help |
| 1854 | Hardware driver for the Indy's/I2's watchdog. This is a |
| 1855 | watchdog timer that will reboot the machine after a 60 second |
| 1856 | timer expired and no process has written to /dev/watchdog during |
| 1857 | that time. |
| 1858 | |
| 1859 | config JZ4740_WDT |
| 1860 | tristate "Ingenic jz4740 SoC hardware watchdog" |
| 1861 | depends on MIPS || COMPILE_TEST |
| 1862 | depends on COMMON_CLK |
| 1863 | select WATCHDOG_CORE |
| 1864 | select MFD_SYSCON |
| 1865 | help |
| 1866 | Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs. |
| 1867 | |
| 1868 | config WDT_MTX1 |
| 1869 | tristate "MTX-1 Hardware Watchdog" |
| 1870 | depends on MIPS_MTX1 || (MIPS && COMPILE_TEST) |
| 1871 | help |
| 1872 | Hardware driver for the MTX-1 boards. This is a watchdog timer that |
| 1873 | will reboot the machine after a 100 seconds timer expired. |
| 1874 | |
| 1875 | config SIBYTE_WDOG |
| 1876 | tristate "Sibyte SoC hardware watchdog" |
| 1877 | depends on CPU_SB1 |
| 1878 | help |
| 1879 | Watchdog driver for the built in watchdog hardware in Sibyte |
| 1880 | SoC processors. There are apparently two watchdog timers |
| 1881 | on such processors; this driver supports only the first one, |
| 1882 | because currently Linux only supports exporting one watchdog |
| 1883 | to userspace. |
| 1884 | |
| 1885 | To compile this driver as a loadable module, choose M here. |
| 1886 | The module will be called sb_wdog. |
| 1887 | |
| 1888 | config TXX9_WDT |
| 1889 | tristate "Toshiba TXx9 Watchdog Timer" |
| 1890 | depends on CPU_TX49XX || (MIPS && COMPILE_TEST) |
| 1891 | select WATCHDOG_CORE |
| 1892 | help |
| 1893 | Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs. |
| 1894 | |
| 1895 | config OCTEON_WDT |
| 1896 | tristate "Cavium OCTEON SOC family Watchdog Timer" |
| 1897 | depends on CAVIUM_OCTEON_SOC |
| 1898 | default y |
| 1899 | select WATCHDOG_CORE |
| 1900 | select EXPORT_UASM if OCTEON_WDT = m |
| 1901 | help |
| 1902 | Hardware driver for OCTEON's on chip watchdog timer. |
| 1903 | Enables the watchdog for all cores running Linux. It |
| 1904 | installs a NMI handler and pokes the watchdog based on an |
| 1905 | interrupt. On first expiration of the watchdog, the |
| 1906 | interrupt handler pokes it. The second expiration causes an |
| 1907 | NMI that prints a message. The third expiration causes a |
| 1908 | global soft reset. |
| 1909 | |
| 1910 | When userspace has /dev/watchdog open, no poking is done |
| 1911 | from the first interrupt, it is then only poked when the |
| 1912 | device is written. |
| 1913 | |
| 1914 | config MARVELL_GTI_WDT |
| 1915 | tristate "Marvell GTI Watchdog driver" |
| 1916 | depends on ARCH_THUNDER || (COMPILE_TEST && 64BIT) |
| 1917 | default ARCH_THUNDER |
| 1918 | select WATCHDOG_CORE |
| 1919 | help |
| 1920 | Marvell GTI hardware supports watchdog timer. First timeout |
| 1921 | works as watchdog pretimeout and installed interrupt handler |
| 1922 | will be called on first timeout. Hardware can generate interrupt |
| 1923 | to SCP on second timeout but it is not enabled, so second |
| 1924 | timeout is ignored. If device poke does not happen then system |
| 1925 | will reboot on third timeout. |
| 1926 | |
| 1927 | config BCM2835_WDT |
| 1928 | tristate "Broadcom BCM2835 hardware watchdog" |
| 1929 | depends on ARCH_BCM2835 || (OF && COMPILE_TEST) |
| 1930 | select WATCHDOG_CORE |
| 1931 | help |
| 1932 | Watchdog driver for the built in watchdog hardware in Broadcom |
| 1933 | BCM2835 SoC. |
| 1934 | |
| 1935 | To compile this driver as a loadable module, choose M here. |
| 1936 | The module will be called bcm2835_wdt. |
| 1937 | |
| 1938 | config BCM_KONA_WDT |
| 1939 | tristate "BCM Kona Watchdog" |
| 1940 | depends on ARCH_BCM_MOBILE || COMPILE_TEST |
| 1941 | select WATCHDOG_CORE |
| 1942 | help |
| 1943 | Support for the watchdog timer on the following Broadcom BCM281xx |
| 1944 | family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and |
| 1945 | BCM28155 variants. |
| 1946 | |
| 1947 | Say 'Y' or 'M' here to enable the driver. The module will be called |
| 1948 | bcm_kona_wdt. |
| 1949 | |
| 1950 | config BCM_KONA_WDT_DEBUG |
| 1951 | bool "DEBUGFS support for BCM Kona Watchdog" |
| 1952 | depends on BCM_KONA_WDT || COMPILE_TEST |
| 1953 | help |
| 1954 | If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides |
| 1955 | access to the driver's internal data structures as well as watchdog |
| 1956 | timer hardware registres. |
| 1957 | |
| 1958 | If in doubt, say 'N'. |
| 1959 | |
| 1960 | config BCM7038_WDT |
| 1961 | tristate "BCM63xx/BCM7038 Watchdog" |
| 1962 | select WATCHDOG_CORE |
| 1963 | depends on HAS_IOMEM |
| 1964 | depends on ARCH_BCMBCA || ARCH_BRCMSTB || BMIPS_GENERIC || BCM63XX || COMPILE_TEST |
| 1965 | help |
| 1966 | Watchdog driver for the built-in hardware in Broadcom 7038 and |
| 1967 | later SoCs used in set-top boxes. BCM7038 was made public |
| 1968 | during the 2004 CES, and since then, many Broadcom chips use this |
| 1969 | watchdog block, including some cable modem chips and DSL (63xx) |
| 1970 | chips. |
| 1971 | |
| 1972 | config IMGPDC_WDT |
| 1973 | tristate "Imagination Technologies PDC Watchdog Timer" |
| 1974 | depends on HAS_IOMEM |
| 1975 | depends on MIPS || COMPILE_TEST |
| 1976 | select WATCHDOG_CORE |
| 1977 | help |
| 1978 | Driver for Imagination Technologies PowerDown Controller |
| 1979 | Watchdog Timer. |
| 1980 | |
| 1981 | To compile this driver as a loadable module, choose M here. |
| 1982 | The module will be called imgpdc_wdt. |
| 1983 | |
| 1984 | config LANTIQ_WDT |
| 1985 | tristate "Lantiq SoC watchdog" |
| 1986 | depends on LANTIQ |
| 1987 | select WATCHDOG_CORE |
| 1988 | help |
| 1989 | Hardware driver for the Lantiq SoC Watchdog Timer. |
| 1990 | |
| 1991 | config LOONGSON1_WDT |
| 1992 | tristate "Loongson1 SoC hardware watchdog" |
| 1993 | depends on MACH_LOONGSON32 || MACH_LOONGSON64 || COMPILE_TEST |
| 1994 | select WATCHDOG_CORE |
| 1995 | help |
| 1996 | Hardware driver for the Loongson family Watchdog Timer. |
| 1997 | |
| 1998 | config RALINK_WDT |
| 1999 | tristate "Ralink SoC watchdog" |
| 2000 | select WATCHDOG_CORE |
| 2001 | depends on RALINK |
| 2002 | help |
| 2003 | Hardware driver for the Ralink SoC Watchdog Timer. |
| 2004 | |
| 2005 | config GXP_WATCHDOG |
| 2006 | tristate "HPE GXP watchdog support" |
| 2007 | depends on ARCH_HPE_GXP || COMPILE_TEST |
| 2008 | select WATCHDOG_CORE |
| 2009 | help |
| 2010 | Say Y here to include support for the watchdog timer |
| 2011 | in HPE GXP SoCs. |
| 2012 | |
| 2013 | To compile this driver as a module, choose M here. |
| 2014 | The module will be called gxp-wdt. |
| 2015 | |
| 2016 | config MT7621_WDT |
| 2017 | tristate "Mediatek SoC watchdog" |
| 2018 | select WATCHDOG_CORE |
| 2019 | select REGMAP_MMIO |
| 2020 | select MFD_SYSCON |
| 2021 | depends on SOC_MT7620 || SOC_MT7621 || COMPILE_TEST |
| 2022 | help |
| 2023 | Hardware driver for the Mediatek/Ralink MT7621/8 SoC Watchdog Timer. |
| 2024 | |
| 2025 | config PIC32_WDT |
| 2026 | tristate "Microchip PIC32 hardware watchdog" |
| 2027 | select WATCHDOG_CORE |
| 2028 | depends on MACH_PIC32 || COMPILE_TEST |
| 2029 | help |
| 2030 | Watchdog driver for the built in watchdog hardware in a PIC32. |
| 2031 | |
| 2032 | Configuration bits must be set appropriately for the watchdog to be |
| 2033 | controlled by this driver. |
| 2034 | |
| 2035 | To compile this driver as a loadable module, choose M here. |
| 2036 | The module will be called pic32-wdt. |
| 2037 | |
| 2038 | config PIC32_DMT |
| 2039 | tristate "Microchip PIC32 Deadman Timer" |
| 2040 | select WATCHDOG_CORE |
| 2041 | depends on MACH_PIC32 || COMPILE_TEST |
| 2042 | help |
| 2043 | Watchdog driver for PIC32 instruction fetch counting timer. This |
| 2044 | specific timer is typically be used in mission critical and safety |
| 2045 | critical applications, where any single failure of the software |
| 2046 | functionality and sequencing must be detected. |
| 2047 | |
| 2048 | To compile this driver as a loadable module, choose M here. |
| 2049 | The module will be called pic32-dmt. |
| 2050 | |
| 2051 | # PARISC Architecture |
| 2052 | |
| 2053 | # POWERPC Architecture |
| 2054 | |
| 2055 | config GEF_WDT |
| 2056 | tristate "GE Watchdog Timer" |
| 2057 | depends on GE_FPGA |
| 2058 | help |
| 2059 | Watchdog timer found in a number of GE single board computers. |
| 2060 | |
| 2061 | config MPC5200_WDT |
| 2062 | bool "MPC52xx Watchdog Timer" |
| 2063 | depends on PPC_MPC52xx || COMPILE_TEST |
| 2064 | help |
| 2065 | Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog. |
| 2066 | |
| 2067 | config 8xxx_WDT |
| 2068 | tristate "MPC8xxx Platform Watchdog Timer" |
| 2069 | depends on PPC_8xx || PPC_83xx || PPC_86xx || PPC_MPC512x |
| 2070 | select WATCHDOG_CORE |
| 2071 | help |
| 2072 | This driver is for a SoC level watchdog that exists on some |
| 2073 | Freescale PowerPC processors. So far this driver supports: |
| 2074 | - MPC8xx watchdogs |
| 2075 | - MPC83xx watchdogs |
| 2076 | - MPC86xx watchdogs |
| 2077 | |
| 2078 | For BookE processors (MPC85xx) use the BOOKE_WDT driver instead. |
| 2079 | |
| 2080 | config PIKA_WDT |
| 2081 | tristate "PIKA FPGA Watchdog" |
| 2082 | depends on WARP || (PPC64 && COMPILE_TEST) |
| 2083 | default WARP |
| 2084 | help |
| 2085 | This enables the watchdog in the PIKA FPGA. Currently used on |
| 2086 | the Warp platform. |
| 2087 | |
| 2088 | config BOOKE_WDT |
| 2089 | tristate "PowerPC Book-E Watchdog Timer" |
| 2090 | depends on BOOKE || 4xx |
| 2091 | select WATCHDOG_CORE |
| 2092 | help |
| 2093 | Watchdog driver for PowerPC Book-E chips, such as the Freescale |
| 2094 | MPC85xx SOCs and the IBM PowerPC 440. |
| 2095 | |
| 2096 | Please see Documentation/watchdog/watchdog-api.rst for |
| 2097 | more information. |
| 2098 | |
| 2099 | config BOOKE_WDT_DEFAULT_TIMEOUT |
| 2100 | int "PowerPC Book-E Watchdog Timer Default Timeout" |
| 2101 | depends on BOOKE_WDT |
| 2102 | default 38 if PPC_E500 |
| 2103 | range 0 63 if PPC_E500 |
| 2104 | default 3 if !PPC_E500 |
| 2105 | range 0 3 if !PPC_E500 |
| 2106 | help |
| 2107 | Select the default watchdog timer period to be used by the PowerPC |
| 2108 | Book-E watchdog driver. A watchdog "event" occurs when the bit |
| 2109 | position represented by this number transitions from zero to one. |
| 2110 | |
| 2111 | For Freescale Book-E processors, this is a number between 0 and 63. |
| 2112 | For other Book-E processors, this is a number between 0 and 3. |
| 2113 | |
| 2114 | The value can be overridden by the wdt_period command-line parameter. |
| 2115 | |
| 2116 | config MEN_A21_WDT |
| 2117 | tristate "MEN A21 VME CPU Carrier Board Watchdog Timer" |
| 2118 | select WATCHDOG_CORE |
| 2119 | depends on GPIOLIB || COMPILE_TEST |
| 2120 | help |
| 2121 | Watchdog driver for MEN A21 VMEbus CPU Carrier Boards. |
| 2122 | |
| 2123 | The driver can also be built as a module. If so, the module will be |
| 2124 | called mena21_wdt. |
| 2125 | |
| 2126 | If unsure select N here. |
| 2127 | |
| 2128 | # PPC64 Architecture |
| 2129 | |
| 2130 | config PSERIES_WDT |
| 2131 | tristate "POWER Architecture Platform Watchdog Timer" |
| 2132 | depends on PPC_PSERIES |
| 2133 | select WATCHDOG_CORE |
| 2134 | help |
| 2135 | Driver for virtual watchdog timers provided by PAPR |
| 2136 | hypervisors (e.g. PowerVM, KVM). |
| 2137 | |
| 2138 | config WATCHDOG_RTAS |
| 2139 | tristate "RTAS watchdog" |
| 2140 | depends on PPC_RTAS |
| 2141 | help |
| 2142 | This driver adds watchdog support for the RTAS watchdog. |
| 2143 | |
| 2144 | To compile this driver as a module, choose M here. The module |
| 2145 | will be called wdrtas. |
| 2146 | |
| 2147 | # RISC-V Architecture |
| 2148 | |
| 2149 | config ATCWDT200_WATCHDOG |
| 2150 | tristate "Andes ATCWDT200 Watchdog support" |
| 2151 | depends on ARCH_ANDES || COMPILE_TEST |
| 2152 | help |
| 2153 | Driver for the Andes ATCWDT200 watchdog timer. It provides access to |
| 2154 | programmable reset and interrupt counters with clock-source dependent |
| 2155 | timing. The driver automatically detects the supported IntTime bit-width |
| 2156 | and is fully integrated with the Linux Watchdog Framework. |
| 2157 | |
| 2158 | config STARFIVE_WATCHDOG |
| 2159 | tristate "StarFive Watchdog support" |
| 2160 | depends on ARCH_STARFIVE || COMPILE_TEST |
| 2161 | select WATCHDOG_CORE |
| 2162 | default ARCH_STARFIVE |
| 2163 | help |
| 2164 | Say Y here to support the watchdog of StarFive JH7100 and JH7110 |
| 2165 | SoC. This driver can also be built as a module if choose M. |
| 2166 | |
| 2167 | # S390 Architecture |
| 2168 | |
| 2169 | config DIAG288_WATCHDOG |
| 2170 | tristate "System z diag288 Watchdog" |
| 2171 | depends on S390 |
| 2172 | select WATCHDOG_CORE |
| 2173 | help |
| 2174 | IBM s/390 and zSeries machines running under z/VM 5.1 or later |
| 2175 | provide a virtual watchdog timer to their guest that cause a |
| 2176 | user define Control Program command to be executed after a |
| 2177 | timeout. |
| 2178 | LPAR provides a very similar interface. This driver handles |
| 2179 | both. |
| 2180 | |
| 2181 | To compile this driver as a module, choose M here. The module |
| 2182 | will be called diag288_wdt. |
| 2183 | |
| 2184 | # SUPERH (sh + sh64) Architecture |
| 2185 | |
| 2186 | config SH_WDT |
| 2187 | tristate "SuperH Watchdog" |
| 2188 | depends on SUPERH && (CPU_SH3 || CPU_SH4 || COMPILE_TEST) |
| 2189 | select WATCHDOG_CORE |
| 2190 | help |
| 2191 | This driver adds watchdog support for the integrated watchdog in the |
| 2192 | SuperH processors. If you have one of these processors and wish |
| 2193 | to have watchdog support enabled, say Y, otherwise say N. |
| 2194 | |
| 2195 | As a side note, saying Y here will automatically boost HZ to 1000 |
| 2196 | so that the timer has a chance to clear the overflow counter. On |
| 2197 | slower systems (such as the SH-2 and SH-3) this will likely yield |
| 2198 | some performance issues. As such, the WDT should be avoided here |
| 2199 | unless it is absolutely necessary. |
| 2200 | |
| 2201 | To compile this driver as a module, choose M here: the |
| 2202 | module will be called shwdt. |
| 2203 | |
| 2204 | # SPARC Architecture |
| 2205 | |
| 2206 | # SPARC64 Architecture |
| 2207 | |
| 2208 | config WATCHDOG_CP1XXX |
| 2209 | tristate "CP1XXX Hardware Watchdog support" |
| 2210 | depends on SPARC64 && PCI |
| 2211 | help |
| 2212 | This is the driver for the hardware watchdog timers present on |
| 2213 | Sun Microsystems CompactPCI models CP1400 and CP1500. |
| 2214 | |
| 2215 | To compile this driver as a module, choose M here: the |
| 2216 | module will be called cpwatchdog. |
| 2217 | |
| 2218 | If you do not have a CompactPCI model CP1400 or CP1500, or |
| 2219 | another UltraSPARC-IIi-cEngine boardset with hardware watchdog, |
| 2220 | you should say N to this option. |
| 2221 | |
| 2222 | config WATCHDOG_RIO |
| 2223 | tristate "RIO Hardware Watchdog support" |
| 2224 | depends on SPARC64 && PCI |
| 2225 | help |
| 2226 | Say Y here to support the hardware watchdog capability on Sun RIO |
| 2227 | machines. The watchdog timeout period is normally one minute but |
| 2228 | can be changed with a boot-time parameter. |
| 2229 | |
| 2230 | config WATCHDOG_SUN4V |
| 2231 | tristate "Sun4v Watchdog support" |
| 2232 | select WATCHDOG_CORE |
| 2233 | depends on SPARC64 |
| 2234 | help |
| 2235 | Say Y here to support the hypervisor watchdog capability embedded |
| 2236 | in the SPARC sun4v architecture. |
| 2237 | |
| 2238 | To compile this driver as a module, choose M here. The module will |
| 2239 | be called sun4v_wdt. |
| 2240 | |
| 2241 | # XTENSA Architecture |
| 2242 | |
| 2243 | # Xen Architecture |
| 2244 | |
| 2245 | config XEN_WDT |
| 2246 | tristate "Xen Watchdog support" |
| 2247 | depends on XEN |
| 2248 | select WATCHDOG_CORE |
| 2249 | help |
| 2250 | Say Y here to support the hypervisor watchdog capability provided |
| 2251 | by Xen 4.0 and newer. The watchdog timeout period is normally one |
| 2252 | minute but can be changed with a boot-time parameter. |
| 2253 | |
| 2254 | config UML_WATCHDOG |
| 2255 | tristate "UML watchdog" |
| 2256 | depends on UML || COMPILE_TEST |
| 2257 | |
| 2258 | # |
| 2259 | # ISA-based Watchdog Cards |
| 2260 | # |
| 2261 | |
| 2262 | comment "ISA-based Watchdog Cards" |
| 2263 | depends on ISA |
| 2264 | |
| 2265 | config PCWATCHDOG |
| 2266 | tristate "Berkshire Products ISA-PC Watchdog" |
| 2267 | depends on ISA |
| 2268 | help |
| 2269 | This is the driver for the Berkshire Products ISA-PC Watchdog card. |
| 2270 | This card simply watches your kernel to make sure it doesn't freeze, |
| 2271 | and if it does, it reboots your computer after a certain amount of |
| 2272 | time. This driver is like the WDT501 driver but for different |
| 2273 | hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.rst>. |
| 2274 | The PC watchdog cards can be ordered from <http://www.berkprod.com/>. |
| 2275 | |
| 2276 | To compile this driver as a module, choose M here: the |
| 2277 | module will be called pcwd. |
| 2278 | |
| 2279 | Most people will say N. |
| 2280 | |
| 2281 | config MIXCOMWD |
| 2282 | tristate "Mixcom Watchdog" |
| 2283 | depends on ISA |
| 2284 | help |
| 2285 | This is a driver for the Mixcom hardware watchdog cards. This |
| 2286 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 2287 | and if it does, it reboots your computer after a certain amount of |
| 2288 | time. |
| 2289 | |
| 2290 | To compile this driver as a module, choose M here: the |
| 2291 | module will be called mixcomwd. |
| 2292 | |
| 2293 | Most people will say N. |
| 2294 | |
| 2295 | config WDT |
| 2296 | tristate "ICS WDT500P/501P Watchdog timer" |
| 2297 | depends on ISA |
| 2298 | help |
| 2299 | If you have an Industrial Computer Source (ICS) WDT500P or WDT501P |
| 2300 | watchdog board, say Y here, |
| 2301 | otherwise N. It is not possible to probe for this board, which means |
| 2302 | that you have to inform the kernel about the IO port and IRQ that |
| 2303 | is needed (you can do this via the io and irq parameters) |
| 2304 | |
| 2305 | To compile this driver as a module, choose M here: the |
| 2306 | module will be called wdt. |
| 2307 | |
| 2308 | # |
| 2309 | # PCI-based Watchdog Cards |
| 2310 | # |
| 2311 | |
| 2312 | comment "PCI-based Watchdog Cards" |
| 2313 | depends on PCI |
| 2314 | |
| 2315 | config PCIPCWATCHDOG |
| 2316 | tristate "Berkshire Products PCI-PC Watchdog" |
| 2317 | depends on PCI && HAS_IOPORT |
| 2318 | help |
| 2319 | This is the driver for the Berkshire Products PCI-PC Watchdog card. |
| 2320 | This card simply watches your kernel to make sure it doesn't freeze, |
| 2321 | and if it does, it reboots your computer after a certain amount of |
| 2322 | time. The card can also monitor the internal temperature of the PC. |
| 2323 | More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>. |
| 2324 | |
| 2325 | To compile this driver as a module, choose M here: the |
| 2326 | module will be called pcwd_pci. |
| 2327 | |
| 2328 | Most people will say N. |
| 2329 | |
| 2330 | config WDTPCI |
| 2331 | tristate "ICS PCI-WDT500/501 Watchdog timer" |
| 2332 | depends on PCI && HAS_IOPORT |
| 2333 | help |
| 2334 | If you have an Industrial Computer Source (ICS) PCI-WDT500/501 watchdog |
| 2335 | board, say Y here, otherwise N. |
| 2336 | |
| 2337 | If you have a PCI-WDT501 watchdog board then you can enable the |
| 2338 | temperature sensor by setting the type parameter to 501. |
| 2339 | |
| 2340 | If you want to enable the Fan Tachometer on the PCI-WDT501, then you |
| 2341 | can do this via the tachometer parameter. Only do this if you have a |
| 2342 | fan tachometer actually set up. |
| 2343 | |
| 2344 | To compile this driver as a module, choose M here: the |
| 2345 | module will be called wdt_pci. |
| 2346 | |
| 2347 | # |
| 2348 | # USB-based Watchdog Cards |
| 2349 | # |
| 2350 | |
| 2351 | comment "USB-based Watchdog Cards" |
| 2352 | depends on USB |
| 2353 | |
| 2354 | config USBPCWATCHDOG |
| 2355 | tristate "Berkshire Products USB-PC Watchdog" |
| 2356 | depends on USB |
| 2357 | help |
| 2358 | This is the driver for the Berkshire Products USB-PC Watchdog card. |
| 2359 | This card simply watches your kernel to make sure it doesn't freeze, |
| 2360 | and if it does, it reboots your computer after a certain amount of |
| 2361 | time. The card can also monitor the internal temperature of the PC. |
| 2362 | More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>. |
| 2363 | |
| 2364 | To compile this driver as a module, choose M here: the |
| 2365 | module will be called pcwd_usb. |
| 2366 | |
| 2367 | Most people will say N. |
| 2368 | |
| 2369 | config KEEMBAY_WATCHDOG |
| 2370 | tristate "Intel Keem Bay SoC non-secure watchdog" |
| 2371 | depends on ARCH_KEEMBAY || (ARM64 && COMPILE_TEST) |
| 2372 | select WATCHDOG_CORE |
| 2373 | help |
| 2374 | This option enable support for an In-secure watchdog timer driver for |
| 2375 | Intel Keem Bay SoC. This WDT has a 32 bit timer and decrements in every |
| 2376 | count unit. An interrupt will be triggered, when the count crosses |
| 2377 | the threshold configured in the register. |
| 2378 | |
| 2379 | To compile this driver as a module, choose M here: the |
| 2380 | module will be called keembay_wdt. |
| 2381 | |
| 2382 | config GUNYAH_WATCHDOG |
| 2383 | tristate "Qualcomm Gunyah Watchdog" |
| 2384 | depends on ARCH_QCOM || COMPILE_TEST |
| 2385 | depends on HAVE_ARM_SMCCC |
| 2386 | select WATCHDOG_CORE |
| 2387 | help |
| 2388 | Say Y here to include support for watchdog timer provided by the |
| 2389 | Gunyah hypervisor. The driver uses ARM SMC Calling Convention (SMCCC) |
| 2390 | to interact with Gunyah Watchdog. |
| 2391 | |
| 2392 | To compile this driver as a module, choose M here: the |
| 2393 | module will be called gunyah_wdt. |
| 2394 | |
| 2395 | endif # WATCHDOG |