#
# Watchdog device configuration
#
menuconfig [31mCONFIG_WATCHDOG[0m
bool "Watchdog Timer Support"
---help---
If you say Y here (and to one of the following options) and create a
character special file /dev/watchdog with major number 10 and minor
number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
subsequently opening the file and then failing to write to it for
longer than 1 minute will result in rebooting the machine. This
could be useful for a networked machine that needs to come back
on-line as fast as possible after a lock-up. There's both a watchdog
implementation entirely in software (which can sometimes fail to
reboot the machine) and a driver for hardware watchdog boards, which
are more robust and can also keep track of the temperature inside
your computer. For details, read
<file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
The watchdog is usually used together with the watchdog daemon
which is available from
<ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
also monitor NFS connections and can reboot the machine when the process
table is full.
If unsure, say N.
if [31mCONFIG_WATCHDOG[0m
config [31mCONFIG_WATCHDOG_CORE[0m
bool "WatchDog Timer Driver Core"
---help---
Say Y here if you want to use the new watchdog timer driver core.
This driver provides a framework for all watchdog timer drivers
and gives them the /dev/watchdog interface (and later also the
sysfs interface).
config [31mCONFIG_WATCHDOG_NOWAYOUT[0m
bool "Disable watchdog shutdown on close"
help
The default watchdog behaviour (which you get if you say N here) is
to stop the timer if the process managing it closes the file
/dev/watchdog. It's always remotely possible that this process might
get killed. If you say Y here, the watchdog cannot be stopped once
it has been started.
config [31mCONFIG_WATCHDOG_SYSFS[0m
bool "Read different watchdog information through sysfs"
help
Say Y here if you want to enable watchdog device status read through
sysfs attributes.
#
# General Watchdog drivers
#
comment "Watchdog Device Drivers"
# Architecture Independent
config [31mCONFIG_SOFT_WATCHDOG[0m
tristate "Software watchdog"
select [31mCONFIG_WATCHDOG_CORE[0m
help
[31mCONFIG_A[0m software monitoring watchdog. This will fail to reboot your system
from some situations that the hardware watchdog will recover
from. Equally it's a lot cheaper to install.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called softdog.
config [31mCONFIG_DA9052_WATCHDOG[0m
tristate "Dialog DA9052 Watchdog"
depends on [31mCONFIG_PMIC_DA9052[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the watchdog in the DA9052 PMIC. Watchdog trigger
cause system reset.
Say Y here to include support for the DA9052 watchdog.
Alternatively say [31mCONFIG_M[0m to compile the driver as a module,
which will be called da9052_wdt.
config [31mCONFIG_DA9055_WATCHDOG[0m
tristate "Dialog Semiconductor DA9055 Watchdog"
depends on [31mCONFIG_MFD_DA9055[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
If you say yes here you get support for watchdog on the Dialog
Semiconductor DA9055 PMIC.
This driver can also be built as a module. If so, the module
will be called da9055_wdt.
config [31mCONFIG_DA9063_WATCHDOG[0m
tristate "Dialog DA9063 Watchdog"
depends on [31mCONFIG_MFD_DA9063[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the watchdog in the DA9063 PMIC.
This driver can be built as a module. The module name is da9063_wdt.
config [31mCONFIG_DA9062_WATCHDOG[0m
tristate "Dialog DA9062/61 Watchdog"
depends on [31mCONFIG_MFD_DA9062[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the watchdog in the DA9062 and DA9061 PMICs.
This driver can be built as a module. The module name is da9062_wdt.
config [31mCONFIG_GPIO_WATCHDOG[0m
tristate "Watchdog device controlled through GPIO-line"
depends on [31mCONFIG_OF_GPIO[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
If you say yes here you get support for watchdog device
controlled through GPIO-line.
config [31mCONFIG_GPIO_WATCHDOG_ARCH_INITCALL[0m
bool "Register the watchdog as early as possible"
depends on [31mCONFIG_GPIO_WATCHDOG[0m=y
help
In some situations, the default initcall level (module_init)
in not early enough in the boot process to avoid the watchdog
to be triggered.
If you say yes here, the initcall level would be raised to
arch_initcall.
If in doubt, say N.
config [31mCONFIG_MENF21BMC_WATCHDOG[0m
tristate "MEN 14F021P00 BMC Watchdog"
depends on [31mCONFIG_MFD_MENF21BMC[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the MEN 14F021P00 BMC Watchdog.
This driver can also be built as a module. If so the module
will be called menf21bmc_wdt.
config [31mCONFIG_TANGOX_WATCHDOG[0m
tristate "Sigma Designs SMP86xx/SMP87xx watchdog"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_ARCH_TANGO[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
help
Support for the watchdog in Sigma Designs SMP86xx (tango3)
and SMP87xx (tango4) family chips.
This driver can be built as a module. The module name is tangox_wdt.
config [31mCONFIG_WDAT_WDT[0m
tristate "ACPI Watchdog Action Table (WDAT)"
depends on [31mCONFIG_ACPI[0m
select [31mCONFIG_WATCHDOG_CORE[0m
select [31mCONFIG_ACPI_WATCHDOG[0m
help
This driver adds support for systems with [31mCONFIG_ACPI[0m Watchdog Action
Table (WDAT) table. Servers typically have this but it can be
found on some desktop machines as well. This driver will take
over the native iTCO watchdog driver found on many Intel CPUs.
To compile this driver as module, choose [31mCONFIG_M[0m here: the module will
be called wdat_wdt.
config [31mCONFIG_WM831X_WATCHDOG[0m
tristate "WM831x watchdog"
depends on [31mCONFIG_MFD_WM831X[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the watchdog in the WM831x AudioPlus PMICs. When
the watchdog triggers the system will be reset.
config [31mCONFIG_WM8350_WATCHDOG[0m
tristate "WM8350 watchdog"
depends on [31mCONFIG_MFD_WM8350[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the watchdog in the WM8350 AudioPlus PMIC. When
the watchdog triggers the system will be reset.
config [31mCONFIG_XILINX_WATCHDOG[0m
tristate "Xilinx Watchdog timer"
depends on [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Watchdog driver for the xps_timebase_wdt ip core.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called of_xilinx_wdt.
config [31mCONFIG_ZIIRAVE_WATCHDOG[0m
tristate "Zodiac RAVE Watchdog Timer"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Watchdog driver for the Zodiac Aerospace RAVE Switch Watchdog
Processor.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ziirave_wdt.
# [31mCONFIG_ALPHA[0m Architecture
# [31mCONFIG_ARM[0m Architecture
config [31mCONFIG_ARM_SP805_WATCHDOG[0m
tristate "ARM SP805 Watchdog"
depends on ([31mCONFIG_ARM[0m || [31mCONFIG_ARM64[0m) && [31mCONFIG_ARM_AMBA[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
[31mCONFIG_ARM[0m Primecell SP805 Watchdog timer. This will reboot your system when
the timeout is reached.
config [31mCONFIG_ARM_SBSA_WATCHDOG[0m
tristate "ARM SBSA Generic Watchdog"
depends on [31mCONFIG_ARM64[0m
depends on [31mCONFIG_ARM_ARCH_TIMER[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
[31mCONFIG_ARM[0m SBSA Generic Watchdog has two stage timeouts:
the first signal (WS0) is for alerting the system by interrupt,
the second one (WS1) is a real hardware reset.
More details: [31mCONFIG_ARM[0m DEN0029B - Server Base System Architecture (SBSA)
This driver can operate [31mCONFIG_ARM[0m SBSA Generic Watchdog as a single stage
or a two stages watchdog, it depends on the module parameter "action".
Note: the maximum timeout in the two stages mode is half of that in
the single stage mode.
To compile this driver as module, choose [31mCONFIG_M[0m here: The module
will be called sbsa_gwdt.
config [31mCONFIG_ASM9260_WATCHDOG[0m
tristate "Alphascale ASM9260 watchdog"
depends on [31mCONFIG_MACH_ASM9260[0m
depends on [31mCONFIG_OF[0m
select [31mCONFIG_WATCHDOG_CORE[0m
select [31mCONFIG_RESET_CONTROLLER[0m
help
Watchdog timer embedded into Alphascale asm9260 chips. This will reboot your
system when the timeout is reached.
config [31mCONFIG_AT91RM9200_WATCHDOG[0m
tristate "AT91RM9200 watchdog"
depends on [31mCONFIG_SOC_AT91RM9200[0m && [31mCONFIG_MFD_SYSCON[0m
help
Watchdog timer embedded into AT91RM9200 chips. This will reboot your
system when the timeout is reached.
config [31mCONFIG_AT91SAM9X_WATCHDOG[0m
tristate "AT91SAM9X / AT91CAP9 watchdog"
depends on [31mCONFIG_ARCH_AT91[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Watchdog timer embedded into AT91SAM9X and AT91CAP9 chips. This will
reboot your system when the timeout is reached.
config [31mCONFIG_SAMA5D4_WATCHDOG[0m
tristate "Atmel SAMA5D4 Watchdog Timer"
depends on [31mCONFIG_ARCH_AT91[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Atmel SAMA5D4 watchdog timer is embedded into SAMA5D4 chips.
Its Watchdog Timer Mode Register can be written more than once.
This will reboot your system when the timeout is reached.
config [31mCONFIG_CADENCE_WATCHDOG[0m
tristate "Cadence Watchdog Timer"
depends on [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if you want to include support for the watchdog
timer in the Xilinx Zynq.
config [31mCONFIG_21285_WATCHDOG[0m
tristate "DC21285 watchdog"
depends on [31mCONFIG_FOOTBRIDGE[0m
help
The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
here if you wish to use this. Alternatively say [31mCONFIG_M[0m to compile the
driver as a module, which will be called wdt285.
This driver does not work on all machines. In particular, early CATS
boards have hardware problems that will cause the machine to simply
lock up if the watchdog fires.
"If in doubt, leave it out" - say N.
config [31mCONFIG_977_WATCHDOG[0m
tristate "NetWinder WB83C977 watchdog"
depends on [31mCONFIG_FOOTBRIDGE[0m && [31mCONFIG_ARCH_NETWINDER[0m
help
Say Y here to include support for the WB977 watchdog included in
NetWinder machines. Alternatively say [31mCONFIG_M[0m to compile the driver as
a module, which will be called wdt977.
Not sure? It's safe to say N.
config [31mCONFIG_IXP4XX_WATCHDOG[0m
tristate "IXP4xx Watchdog"
depends on [31mCONFIG_ARCH_IXP4XX[0m
help
Say Y here if to include support for the watchdog timer
in the Intel IXP4xx network processors. This driver can
be built as a module by choosing [31mCONFIG_M[0m. The module will
be called ixp4xx_wdt.
Note: The internal IXP4xx watchdog does a soft CPU reset
which doesn't reset any peripherals. There are circumstances
where the watchdog will fail to reset the board correctly
(e.g., if the boot [31mCONFIG_ROM[0m is in an unreadable state).
Say N if you are unsure.
config [31mCONFIG_KS8695_WATCHDOG[0m
tristate "KS8695 watchdog"
depends on [31mCONFIG_ARCH_KS8695[0m
help
Watchdog timer embedded into KS8695 processor. This will reboot your
system when the timeout is reached.
config [31mCONFIG_HAVE_S3C2410_WATCHDOG[0m
bool
help
This will include watchdog timer support for Samsung SoCs. If
you want to include watchdog support for any machine, kindly
select this in the respective mach-XXXX/Kconfig file.
config [31mCONFIG_S3C2410_WATCHDOG[0m
tristate "S3C2410 Watchdog"
depends on [31mCONFIG_HAVE_S3C2410_WATCHDOG[0m
select [31mCONFIG_WATCHDOG_CORE[0m
select [31mCONFIG_MFD_SYSCON[0m if [31mCONFIG_ARCH_EXYNOS5[0m
help
Watchdog timer block in the Samsung SoCs. This will reboot
the system when the timer expires with the watchdog enabled.
The driver is limited by the speed of the system's PCLK
signal, so with reasonably fast systems (PCLK around 50-66MHz)
then watchdog intervals of over approximately 20seconds are
unavailable.
The driver can be built as a module by choosing [31mCONFIG_M[0m, and will
be called s3c2410_wdt
config [31mCONFIG_SA1100_WATCHDOG[0m
tristate "SA1100/PXA2xx watchdog"
depends on [31mCONFIG_ARCH_SA1100[0m || [31mCONFIG_ARCH_PXA[0m
help
Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
reboot your system when timeout is reached.
NOTE: once enabled, this timer cannot be disabled.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sa1100_wdt.
config [31mCONFIG_DW_WATCHDOG[0m
tristate "Synopsys DesignWare watchdog"
depends on [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if to include support for the Synopsys DesignWare
watchdog timer found in many chips.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called dw_wdt.
config [31mCONFIG_EP93XX_WATCHDOG[0m
tristate "EP93xx Watchdog"
depends on [31mCONFIG_ARCH_EP93XX[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if to include support for the watchdog timer
embedded in the Cirrus Logic EP93xx family of devices.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ep93xx_wdt.
config [31mCONFIG_OMAP_WATCHDOG[0m
tristate "OMAP Watchdog"
depends on [31mCONFIG_ARCH_OMAP16XX[0m || [31mCONFIG_ARCH_OMAP2PLUS[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for TI OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog. Say 'Y'
here to enable the OMAP1610/OMAP1710/OMAP2420/OMAP3430/OMAP4430 watchdog timer.
config [31mCONFIG_PNX4008_WATCHDOG[0m
tristate "LPC32XX Watchdog"
depends on [31mCONFIG_ARCH_LPC32XX[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if to include support for the watchdog timer
in the LPC32XX processor.
This driver can be built as a module by choosing [31mCONFIG_M[0m. The module
will be called pnx4008_wdt.
Say N if you are unsure.
config [31mCONFIG_IOP_WATCHDOG[0m
tristate "IOP Watchdog"
depends on [31mCONFIG_ARCH_IOP13XX[0m
select [31mCONFIG_WATCHDOG_NOWAYOUT[0m if ([31mCONFIG_ARCH_IOP32X[0m || [31mCONFIG_ARCH_IOP33X[0m)
help
Say Y here if to include support for the watchdog timer
in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
be built as a module by choosing [31mCONFIG_M[0m. The module will
be called iop_wdt.
Note: The IOP13XX watchdog does an Internal Bus Reset which will
affect both cores and the peripherals of the IOP. The ATU-X
and/or ATUe configuration registers will remain intact, but if
operating as an Root Complex and/or Central Resource, the [31mCONFIG_PCI[0m-X
and/or PCIe busses will also be reset. THIS IS [31mCONFIG_A[0m VERY BIG HAMMER.
config [31mCONFIG_DAVINCI_WATCHDOG[0m
tristate "DaVinci watchdog"
depends on [31mCONFIG_ARCH_DAVINCI[0m || [31mCONFIG_ARCH_KEYSTONE[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if to include support for the watchdog timer
in the DaVinci DM644x/DM646x or Keystone processors.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called davinci_wdt.
NOTE: once enabled, this timer cannot be disabled.
Say N if you are unsure.
config [31mCONFIG_ORION_WATCHDOG[0m
tristate "Orion watchdog"
depends on [31mCONFIG_ARCH_ORION5X[0m || [31mCONFIG_ARCH_DOVE[0m || [31mCONFIG_MACH_DOVE[0m || [31mCONFIG_ARCH_MVEBU[0m
depends on [31mCONFIG_ARM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if to include support for the watchdog timer
in the Marvell Orion5x and Kirkwood [31mCONFIG_ARM[0m SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called orion_wdt.
config [31mCONFIG_RN5T618_WATCHDOG[0m
tristate "Ricoh RN5T618 watchdog"
depends on [31mCONFIG_MFD_RN5T618[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
If you say yes here you get support for watchdog on the Ricoh
RN5T618 PMIC.
This driver can also be built as a module. If so, the module
will be called rn5t618_wdt.
config [31mCONFIG_SUNXI_WATCHDOG[0m
tristate "Allwinner SoCs watchdog support"
depends on [31mCONFIG_ARCH_SUNXI[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
in Allwinner SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sunxi_wdt.
config [31mCONFIG_COH901327_WATCHDOG[0m
bool "ST-Ericsson COH 901 327 watchdog"
depends on [31mCONFIG_ARCH_U300[0m
default y if [31mCONFIG_MACH_U300[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include Watchdog timer support for the
watchdog embedded into the ST-Ericsson U300 series platforms.
This watchdog is used to reset the system and thus cannot be
compiled as a module.
config [31mCONFIG_TWL4030_WATCHDOG[0m
tristate "TWL4030 Watchdog"
depends on [31mCONFIG_TWL4030_CORE[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for TI TWL4030 watchdog. Say 'Y' here to enable the
watchdog timer support for TWL4030 chips.
config [31mCONFIG_STMP3XXX_RTC_WATCHDOG[0m
tristate "Freescale STMP3XXX & i.MX23/28 watchdog"
depends on [31mCONFIG_RTC_DRV_STMP[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer inside
the [31mCONFIG_RTC[0m for the STMP37XX/378X or i.MX23/28 SoC.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called stmp3xxx_rtc_wdt.
config [31mCONFIG_NUC900_WATCHDOG[0m
tristate "Nuvoton NUC900 watchdog"
depends on [31mCONFIG_ARCH_W90X900[0m
help
Say Y here if to include support for the watchdog timer
for the Nuvoton NUC900 series SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called nuc900_wdt.
config [31mCONFIG_TS4800_WATCHDOG[0m
tristate "TS-4800 Watchdog"
depends on [31mCONFIG_HAS_IOMEM[0m && [31mCONFIG_OF[0m
depends on [31mCONFIG_SOC_IMX51[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_WATCHDOG_CORE[0m
select [31mCONFIG_MFD_SYSCON[0m
help
Technologic Systems TS-4800 has watchdog timer implemented in
an external [31mCONFIG_FPGA[0m. Say Y here if you want to support for the
watchdog timer on TS-4800 board.
config [31mCONFIG_TS72XX_WATCHDOG[0m
tristate "TS-72XX SBC Watchdog"
depends on [31mCONFIG_MACH_TS72XX[0m
help
Technologic Systems TS-7200, TS-7250 and TS-7260 boards have
watchdog timer implemented in a external CPLD chip. Say Y here
if you want to support for the watchdog timer on TS-72XX boards.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ts72xx_wdt.
config [31mCONFIG_MAX63XX_WATCHDOG[0m
tristate "Max63xx watchdog"
depends on [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for memory mapped max63{69,70,71,72,73,74} watchdog timer.
config [31mCONFIG_MAX77620_WATCHDOG[0m
tristate "Maxim Max77620 Watchdog Timer"
depends on [31mCONFIG_MFD_MAX77620[0m
help
This is the driver for the Max77620 watchdog timer.
Say 'Y' here to enable the watchdog timer support for
MAX77620 chips. To compile this driver as a module,
choose [31mCONFIG_M[0m here: the module will be called max77620_wdt.
config [31mCONFIG_IMX2_WDT[0m
tristate "IMX2+ Watchdog"
depends on [31mCONFIG_ARCH_MXC[0m || [31mCONFIG_ARCH_LAYERSCAPE[0m
select [31mCONFIG_REGMAP_MMIO[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
This is the driver for the hardware watchdog
on the Freescale IMX2 and later processors.
If you have one of these processors and wish to have
watchdog support enabled, say Y, otherwise say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called imx2_wdt.
config [31mCONFIG_UX500_WATCHDOG[0m
tristate "ST-Ericsson Ux500 watchdog"
depends on [31mCONFIG_MFD_DB8500_PRCMU[0m
select [31mCONFIG_WATCHDOG_CORE[0m
default y
help
Say Y here to include Watchdog timer support for the watchdog
existing in the prcmu of ST-Ericsson Ux500 series platforms.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ux500_wdt.
config [31mCONFIG_RETU_WATCHDOG[0m
tristate "Retu watchdog"
depends on [31mCONFIG_MFD_RETU[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Retu watchdog driver for Nokia Internet Tablets (770, N800,
N810). At least on N800 the watchdog cannot be disabled, so
this driver is essential and you should enable it.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called retu_wdt.
config [31mCONFIG_MOXART_WDT[0m
tristate "MOXART watchdog"
depends on [31mCONFIG_ARCH_MOXART[0m
help
Say Y here to include Watchdog timer support for the watchdog
existing on the MOXA ART SoC series platforms.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called moxart_wdt.
config [31mCONFIG_SIRFSOC_WATCHDOG[0m
tristate "SiRFSOC watchdog"
depends on [31mCONFIG_ARCH_SIRF[0m
select [31mCONFIG_WATCHDOG_CORE[0m
default y
help
Support for CSR SiRFprimaII and SiRFatlasVI watchdog. When
the watchdog triggers the system will be reset.
config [31mCONFIG_ST_LPC_WATCHDOG[0m
tristate "STMicroelectronics LPC Watchdog"
depends on [31mCONFIG_ARCH_STI[0m
depends on [31mCONFIG_OF[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include STMicroelectronics Low Power Controller
(LPC) based Watchdog timer support.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called st_lpc_wdt.
config [31mCONFIG_TEGRA_WATCHDOG[0m
tristate "Tegra watchdog"
depends on ([31mCONFIG_ARCH_TEGRA[0m || [31mCONFIG_COMPILE_TEST[0m) && [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
embedded in NVIDIA Tegra SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called tegra_wdt.
config [31mCONFIG_QCOM_WDT[0m
tristate "QCOM watchdog"
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_ARCH_QCOM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include Watchdog timer support for the watchdog found
on QCOM chipsets. Currently supported targets are the MSM8960,
APQ8064, and IPQ8064.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called qcom_wdt.
config [31mCONFIG_MESON_GXBB_WATCHDOG[0m
tristate "Amlogic Meson GXBB SoCs watchdog support"
depends on [31mCONFIG_ARCH_MESON[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
in Amlogic Meson GXBB SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called meson_gxbb_wdt.
config [31mCONFIG_MESON_WATCHDOG[0m
tristate "Amlogic Meson SoCs watchdog support"
depends on [31mCONFIG_ARCH_MESON[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
in Amlogic Meson SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called meson_wdt.
config [31mCONFIG_MEDIATEK_WATCHDOG[0m
tristate "Mediatek SoCs watchdog support"
depends on [31mCONFIG_ARCH_MEDIATEK[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
in Mediatek SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mtk_wdt.
config [31mCONFIG_DIGICOLOR_WATCHDOG[0m
tristate "Conexant Digicolor SoCs watchdog support"
depends on [31mCONFIG_ARCH_DIGICOLOR[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
in Conexant Digicolor SoCs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called digicolor_wdt.
config [31mCONFIG_LPC18XX_WATCHDOG[0m
tristate "LPC18xx/43xx Watchdog"
depends on [31mCONFIG_ARCH_LPC18XX[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_HAS_IOMEM[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here if to include support for the watchdog timer
in NXP LPC SoCs family, which includes LPC18xx/LPC43xx
processors.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called lpc18xx_wdt.
config [31mCONFIG_ATLAS7_WATCHDOG[0m
tristate "CSRatlas7 watchdog"
depends on [31mCONFIG_ARCH_ATLAS7[0m
help
Say Y here to include Watchdog timer support for the watchdog
existing on the CSRatlas7 series platforms.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called atlas7_wdt.
config [31mCONFIG_RENESAS_WDT[0m
tristate "Renesas WDT Watchdog"
depends on [31mCONFIG_ARCH_RENESAS[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
This driver adds watchdog support for the integrated watchdogs in the
Renesas R-Car and other SH-Mobile SoCs (usually named RWDT or SWDT).
config [31mCONFIG_ASPEED_WATCHDOG[0m
tristate "Aspeed 2400 watchdog support"
depends on [31mCONFIG_ARCH_ASPEED[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Say Y here to include support for the watchdog timer
in Apseed BMC SoCs.
This driver is required to reboot the SoC.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called aspeed_wdt.
# [31mCONFIG_AVR32[0m Architecture
config [31mCONFIG_AT32AP700X_WDT[0m
tristate "AT32AP700x watchdog"
depends on [31mCONFIG_CPU_AT32AP700X[0m
help
Watchdog timer embedded into AT32AP700x devices. This will reboot
your system when the timeout is reached.
# [31mCONFIG_BLACKFIN[0m Architecture
config [31mCONFIG_BFIN_WDT[0m
tristate "Blackfin On-Chip Watchdog Timer"
depends on [31mCONFIG_BLACKFIN[0m
---help---
If you say yes here you will get support for the Blackfin On-Chip
Watchdog Timer. If you have one of these processors and wish to
have watchdog support enabled, say Y, otherwise say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called bfin_wdt.
# [31mCONFIG_CRIS[0m Architecture
# [31mCONFIG_FRV[0m Architecture
# [31mCONFIG_X86[0m (i386 + ia64 + x86_64) Architecture
config [31mCONFIG_ACQUIRE_WDT[0m
tristate "Acquire SBC Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog on Single Board
Computers produced by Acquire Inc (and others). This watchdog
simply watches your kernel to make sure it doesn't freeze, and if
it does, it reboots your computer after a certain amount of time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called acquirewdt.
Most people will say N.
config [31mCONFIG_ADVANTECH_WDT[0m
tristate "Advantech SBC Watchdog Timer"
depends on [31mCONFIG_X86[0m
help
If you are configuring a Linux kernel for the Advantech single-board
computer, say `Y' here to support its built-in watchdog timer
feature. More information can be found at
<http://www.advantech.com.tw/products/>
config [31mCONFIG_ALIM1535_WDT[0m
tristate "ALi M1535 PMU Watchdog Timer"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
---help---
This is the driver for the hardware watchdog on the ALi M1535 PMU.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called alim1535_wdt.
Most people will say N.
config [31mCONFIG_ALIM7101_WDT[0m
tristate "ALi M7101 PMU Computer Watchdog"
depends on [31mCONFIG_PCI[0m
help
This is the driver for the hardware watchdog on the ALi M7101 PMU
as used in the x86 Cobalt servers and also found in some
[31mCONFIG_SPARC[0m Netra servers too.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called alim7101_wdt.
Most people will say N.
config [31mCONFIG_EBC_C384_WDT[0m
tristate "WinSystems EBC-C384 Watchdog Timer"
depends on [31mCONFIG_X86[0m && [31mCONFIG_ISA_BUS_API[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Enables watchdog timer support for the watchdog timer on the
WinSystems EBC-C384 motherboard. The timeout may be configured via
the timeout module parameter.
config [31mCONFIG_F71808E_WDT[0m
tristate "Fintek F71808E, F71862FG, F71869, F71882FG and F71889FG Watchdog"
depends on [31mCONFIG_X86[0m
help
This is the driver for the hardware watchdog on the Fintek
F71808E, F71862FG, F71869, F71882FG and F71889FG Super I/O controllers.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called f71808e_wdt.
config [31mCONFIG_SP5100_TCO[0m
tristate "AMD/ATI SP5100 TCO Timer/Watchdog"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
---help---
Hardware watchdog driver for the AMD/ATI SP5100 chipset. The TCO
(Total Cost of Ownership) timer is a watchdog timer that will reboot
the machine after its expiration. The expiration time can be
configured with the "heartbeat" parameter.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sp5100_tco.
config [31mCONFIG_GEODE_WDT[0m
tristate "AMD Geode CS5535/CS5536 Watchdog"
depends on [31mCONFIG_CS5535_MFGPT[0m
help
This driver enables a watchdog capability built into the
CS5535/[31mCONFIG_CS5536[0m companion chips for the AMD Geode GX and LX
processors. This watchdog watches your kernel to make sure
it doesn't freeze, and if it does, it reboots your computer after
a certain amount of time.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called geodewdt.
config [31mCONFIG_SC520_WDT[0m
tristate "AMD Elan SC520 processor Watchdog"
depends on [31mCONFIG_MELAN[0m
help
This is the driver for the hardware watchdog built in to the
AMD "Elan" SC520 microcomputer commonly used in embedded systems.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called sc520_wdt.
config [31mCONFIG_SBC_FITPC2_WATCHDOG[0m
tristate "Compulab SBC-FITPC2 watchdog"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the built-in watchdog timer on the fit-PC2,
fit-PC2i, CM-iAM single-board computers made by Compulab.
It`s possible to enable watchdog timer either from BIOS ([31mCONFIG_F2[0m) or from booted Linux.
When "Watchdog Timer Value" enabled one can set 31-255 s operational range.
Entering BIOS setup temporary disables watchdog operation regardless to current state,
so system will not be restarted while user in BIOS setup.
Once watchdog was enabled the system will be restarted every
"Watchdog Timer Value" period, so to prevent it user can restart or
disable the watchdog.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sbc_fitpc2_wdt.
Most people will say N.
config [31mCONFIG_EUROTECH_WDT[0m
tristate "Eurotech CPU-1220/1410 Watchdog Timer"
depends on [31mCONFIG_X86[0m
help
Enable support for the watchdog timer on the Eurotech CPU-1220 and
CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
information are at <http://www.eurotech.it/>.
config [31mCONFIG_IB700_WDT[0m
tristate "IB700 SBC Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog on the IB700 Single
Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
simply watches your kernel to make sure it doesn't freeze, and if
it does, it reboots your computer after a certain amount of time.
This driver is like the WDT501 driver but for slightly different hardware.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ib700wdt.
Most people will say N.
config [31mCONFIG_IBMASR[0m
tristate "IBM Automatic Server Restart"
depends on [31mCONFIG_X86[0m
help
This is the driver for the IBM Automatic Server Restart watchdog
timer built-in into some eServer xSeries machines.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ibmasr.
config [31mCONFIG_WAFER_WDT[0m
tristate "ICP Single Board Computer Watchdog Timer"
depends on [31mCONFIG_X86[0m
help
This is a driver for the hardware watchdog on the ICP Single
Board Computer. This driver is working on (at least) the following
IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called wafer5823wdt.
config [31mCONFIG_I6300ESB_WDT[0m
tristate "Intel 6300ESB Timer/Watchdog"
depends on [31mCONFIG_PCI[0m
---help---
Hardware driver for the watchdog timer built into the Intel
6300ESB controller hub.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called i6300esb.
config [31mCONFIG_IE6XX_WDT[0m
tristate "Intel Atom E6xx Watchdog"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
select [31mCONFIG_WATCHDOG_CORE[0m
select [31mCONFIG_MFD_CORE[0m
select [31mCONFIG_LPC_SCH[0m
---help---
Hardware driver for the watchdog timer built into the Intel
Atom E6XX (TunnelCreek) processor.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ie6xx_wdt.
config [31mCONFIG_INTEL_SCU_WATCHDOG[0m
bool "Intel SCU Watchdog for Mobile Platforms"
depends on [31mCONFIG_X86_INTEL_MID[0m
---help---
Hardware driver for the watchdog time built into the Intel SCU
for Intel Mobile Platforms.
To compile this driver as a module, choose [31mCONFIG_M[0m here.
config [31mCONFIG_INTEL_MID_WATCHDOG[0m
tristate "Intel MID Watchdog Timer"
depends on [31mCONFIG_X86_INTEL_MID[0m
select [31mCONFIG_WATCHDOG_CORE[0m
---help---
Watchdog timer driver built into the Intel SCU for Intel MID
Platforms.
This driver currently supports only the watchdog evolution
implementation in SCU, available for Merrifield generation.
To compile this driver as a module, choose [31mCONFIG_M[0m here.
config [31mCONFIG_ITCO_WDT[0m
tristate "Intel TCO Timer/Watchdog"
depends on ([31mCONFIG_X86[0m || [31mCONFIG_IA64[0m) && [31mCONFIG_PCI[0m
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_I2C[0m || [31mCONFIG_I2C[0m=n
select [31mCONFIG_LPC_ICH[0m if ![31mCONFIG_EXPERT[0m
select [31mCONFIG_I2C_I801[0m if ![31mCONFIG_EXPERT[0m && [31mCONFIG_I2C[0m
---help---
Hardware driver for the intel TCO timer based watchdog devices.
These drivers are included in the Intel 82801 I/O Controller
Hub family (from ICH0 up to ICH10) and in the Intel 63xxESB
controller hub.
The TCO (Total Cost of Ownership) timer is a watchdog timer
that will reboot the machine after its second expiration. The
expiration time can be configured with the "heartbeat" parameter.
On some motherboards the driver may fail to reset the chipset's
NO_REBOOT flag which prevents the watchdog from rebooting the
machine. If this is the case you will get a kernel message like
"failed to reset NO_REBOOT flag, reboot disabled by hardware".
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called iTCO_wdt.
config [31mCONFIG_ITCO_VENDOR_SUPPORT[0m
bool "Intel TCO Timer/Watchdog Specific Vendor Support"
depends on [31mCONFIG_ITCO_WDT[0m
---help---
Add vendor specific support to the intel TCO timer based watchdog
devices. At this moment we only have additional support for some
SuperMicro Inc. motherboards.
config [31mCONFIG_IT8712F_WDT[0m
tristate "IT8712F (Smart Guardian) Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the built-in watchdog timer on the IT8712F
Super I/0 chipset used on many motherboards.
If the driver does not work, then make sure that the game port in
the BIOS is enabled.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called it8712f_wdt.
config [31mCONFIG_IT87_WDT[0m
tristate "IT87 Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog on the ITE IT8620,
IT8702, IT8712, IT8716, IT8718, IT8720, IT8721, IT8726 and IT8728
Super I/O chips.
If the driver does not work, then make sure that the game port in
the BIOS is enabled.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called it87_wdt.
config [31mCONFIG_HP_WATCHDOG[0m
tristate "HP ProLiant iLO2+ Hardware Watchdog Timer"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
help
[31mCONFIG_A[0m software monitoring watchdog and NMI sourcing driver. This driver
will detect lockups and provide a stack trace. This is a driver that
will only load on an HP ProLiant system with a minimum of iLO2 support.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called hpwdt.
config [31mCONFIG_KEMPLD_WDT[0m
tristate "Kontron COM Watchdog Timer"
depends on [31mCONFIG_MFD_KEMPLD[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the PLD watchdog on some Kontron ETX and COMexpress
(ETXexpress) modules
This driver can also be built as a module. If so, the module will be
called kempld_wdt.
config [31mCONFIG_HPWDT_NMI_DECODING[0m
bool "NMI decoding support for the HP ProLiant iLO2+ Hardware Watchdog Timer"
depends on [31mCONFIG_HP_WATCHDOG[0m
default y
help
When an NMI occurs this feature will make the necessary BIOS calls to
log the cause of the NMI.
config [31mCONFIG_SC1200_WDT[0m
tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
depends on [31mCONFIG_X86[0m
help
This is a driver for National Semiconductor PC87307/PC97307 hardware
watchdog cards as found on the SC1200. This watchdog is mainly used
for power management purposes and can be used to power down the device
during inactivity periods (includes interrupt activity monitoring).
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sc1200wdt.
Most people will say N.
config [31mCONFIG_SCx200_WDT[0m
tristate "National Semiconductor SCx200 Watchdog"
depends on [31mCONFIG_SCx200[0m && [31mCONFIG_PCI[0m
help
Enable the built-in watchdog timer support on the National
Semiconductor [31mCONFIG_SCx200[0m processors.
If compiled as a module, it will be called scx200_wdt.
config [31mCONFIG_PC87413_WDT[0m
tristate "NS PC87413 watchdog"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog on the PC87413 chipset
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pc87413_wdt.
Most people will say N.
config [31mCONFIG_NV_TCO[0m
tristate "nVidia TCO Timer/Watchdog"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
---help---
Hardware driver for the TCO timer built into the nVidia Hub family
(such as the MCP51). The TCO (Total Cost of Ownership) timer is a
watchdog timer that will reboot the machine after its second
expiration. The expiration time can be configured with the
"heartbeat" parameter.
On some motherboards the driver may fail to reset the chipset's
NO_REBOOT flag which prevents the watchdog from rebooting the
machine. If this is the case you will get a kernel message like
"failed to reset NO_REBOOT flag, reboot disabled by hardware".
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called nv_tco.
config [31mCONFIG_RDC321X_WDT[0m
tristate "RDC R-321x SoC watchdog"
depends on [31mCONFIG_X86_RDC321X[0m
help
This is the driver for the built in hardware watchdog
in the RDC R-321x SoC.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rdc321x_wdt.
config [31mCONFIG_60XX_WDT[0m
tristate "SBC-60XX Watchdog Timer"
depends on [31mCONFIG_X86[0m
help
This driver can be used with the watchdog timer found on some
single board computers, namely the 6010 PII based computer.
It may well work with other cards. It reads port 0x443 to enable
and re-set the watchdog timer, and reads port 0x45 to disable
the watchdog. If you have a card that behave in similar ways,
you can probably make this driver work with your card as well.
You can compile this driver directly into the kernel, or use
it as a module. The module will be called sbc60xxwdt.
config [31mCONFIG_SBC8360_WDT[0m
tristate "SBC8360 Watchdog Timer"
depends on [31mCONFIG_X86_32[0m
---help---
This is the driver for the hardware watchdog on the SBC8360 Single
Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sbc8360.
Most people will say N.
config [31mCONFIG_SBC7240_WDT[0m
tristate "SBC Nano 7240 Watchdog Timer"
depends on [31mCONFIG_X86_32[0m && ![31mCONFIG_UML[0m
---help---
This is the driver for the hardware watchdog found on the IEI
single board computers EPIC Nano 7240 (and likely others). This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sbc7240_wdt.
config [31mCONFIG_CPU5_WDT[0m
tristate "SMA CPU5 Watchdog"
depends on [31mCONFIG_X86[0m
---help---
TBD.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cpu5wdt.
config [31mCONFIG_SMSC_SCH311X_WDT[0m
tristate "SMSC SCH311X Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog timer on the
SMSC SCH3112, SCH3114 and SCH3116 Super IO chipset
(LPC IO with 8042 KBC, Reset Generation, HWM and multiple
serial ports).
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sch311x_wdt.
config [31mCONFIG_SMSC37B787_WDT[0m
tristate "Winbond SMsC37B787 Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog component on the
Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
from Vision Systems and maybe others.
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
Usually a userspace daemon will notify the kernel [31mCONFIG_WDT[0m driver that
userspace is still alive, at regular intervals.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called smsc37b787_wdt.
Most people will say N.
config [31mCONFIG_VIA_WDT[0m
tristate "VIA Watchdog Timer"
depends on [31mCONFIG_X86[0m && [31mCONFIG_PCI[0m
select [31mCONFIG_WATCHDOG_CORE[0m
---help---
This is the driver for the hardware watchdog timer on VIA
southbridge chipset CX700, VX800/VX820 or VX855/VX875.
To compile this driver as a module, choose [31mCONFIG_M[0m here; the module
will be called via_wdt.
Most people will say N.
config [31mCONFIG_W83627HF_WDT[0m
tristate "Watchdog timer for W83627HF/W83627DHG and compatibles"
depends on [31mCONFIG_X86[0m
select [31mCONFIG_WATCHDOG_CORE[0m
---help---
This is the driver for the hardware watchdog on the following
Super I/O chips.
W83627DHG/DHG-P/EHF/EHG/F/[31mCONFIG_G[0m/HF/S/SF/THF/UHG/UG
W83637HF
W83667HG/HG-[31mCONFIG_B[0m
W83687THF
W83697HF
W83697UG
NCT6775
NCT6776
NCT6779
NCT6791
NCT6792
NCT6102D/04D/06D
This watchdog simply watches your kernel to make sure it doesn't
freeze, and if it does, it reboots your computer after a certain
amount of time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called w83627hf_wdt.
Most people will say N.
config [31mCONFIG_W83877F_WDT[0m
tristate "W83877F (EMACS) Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog on the W83877F chipset
as used in EMACS PC-104 motherboards (and likely others). This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called w83877f_wdt.
Most people will say N.
config [31mCONFIG_W83977F_WDT[0m
tristate "W83977F (PCM-5335) Watchdog Timer"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the hardware watchdog on the W83977F I/O chip
as used in AAEON's PCM-5335 SBC (and likely others). This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called w83977f_wdt.
config [31mCONFIG_MACHZ_WDT[0m
tristate "ZF MachZ Watchdog"
depends on [31mCONFIG_X86[0m
---help---
If you are using a ZF Micro MachZ processor, say Y here, otherwise
N. This is the driver for the watchdog timer built-in on that
processor using ZF-Logic interface. This watchdog simply watches
your kernel to make sure it doesn't freeze, and if it does, it
reboots your computer after a certain amount of time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called machzwd.
config [31mCONFIG_SBC_EPX_C3_WATCHDOG[0m
tristate "Winsystems SBC EPX-C3 watchdog"
depends on [31mCONFIG_X86[0m
---help---
This is the driver for the built-in watchdog timer on the EPX-C3
Single-board computer made by Winsystems, Inc.
*Note*: This hardware watchdog is not probeable and thus there
is no way to know if writing to its IO address will corrupt
your system or have any real effect. The only way to be sure
that this driver does what you want is to make sure you
are running it on an EPX-C3 from Winsystems with the watchdog
timer at IO address 0x1ee and 0x1ef. It will write to both those
IO ports. Basically, the assumption is made that if you compile
this driver into your kernel and/or load it as a module, that you
know what you are doing and that you are in fact running on an
EPX-C3 board!
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sbc_epx_c3.
config [31mCONFIG_INTEL_MEI_WDT[0m
tristate "Intel MEI iAMT Watchdog"
depends on [31mCONFIG_INTEL_MEI[0m && [31mCONFIG_X86[0m
select [31mCONFIG_WATCHDOG_CORE[0m
---help---
[31mCONFIG_A[0m device driver for the Intel MEI iAMT watchdog.
The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
Whenever the OS hangs or crashes, iAMT will send an event
to any subscriber to this event. The watchdog doesn't reset the
the platform.
To compile this driver as a module, choose [31mCONFIG_M[0m here:
the module will be called mei_wdt.
config [31mCONFIG_NI903X_WDT[0m
tristate "NI 903x/913x Watchdog"
depends on [31mCONFIG_X86[0m && [31mCONFIG_ACPI[0m
select [31mCONFIG_WATCHDOG_CORE[0m
---help---
This is the driver for the watchdog timer on the National Instruments
903x/913x real-time controllers.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called ni903x_wdt.
# [31mCONFIG_M32R[0m Architecture
# [31mCONFIG_M68K[0m Architecture
config [31mCONFIG_M54xx_WATCHDOG[0m
tristate "MCF54xx watchdog support"
depends on [31mCONFIG_M548x[0m
help
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called m54xx_wdt.
# MicroBlaze Architecture
# [31mCONFIG_MIPS[0m Architecture
config [31mCONFIG_ATH79_WDT[0m
tristate "Atheros AR71XX/AR724X/AR913X hardware watchdog"
depends on [31mCONFIG_ATH79[0m
help
Hardware driver for the built-in watchdog timer on the Atheros
AR71XX/AR724X/AR913X SoCs.
config [31mCONFIG_BCM47XX_WDT[0m
tristate "Broadcom BCM47xx Watchdog Timer"
depends on [31mCONFIG_BCM47XX[0m || [31mCONFIG_ARCH_BCM_5301X[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Hardware driver for the Broadcom BCM47xx Watchdog Timer.
config [31mCONFIG_RC32434_WDT[0m
tristate "IDT RC32434 SoC Watchdog Timer"
depends on [31mCONFIG_MIKROTIK_RB532[0m
help
Hardware driver for the IDT RC32434 SoC built-in
watchdog timer.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rc32434_wdt.
config [31mCONFIG_INDYDOG[0m
tristate "Indy/I2 Hardware Watchdog"
depends on [31mCONFIG_SGI_HAS_INDYDOG[0m
help
Hardware driver for the Indy's/I2's watchdog. This is a
watchdog timer that will reboot the machine after a 60 second
timer expired and no process has written to /dev/watchdog during
that time.
config [31mCONFIG_JZ4740_WDT[0m
tristate "Ingenic jz4740 SoC hardware watchdog"
depends on [31mCONFIG_MACH_JZ4740[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Hardware driver for the built-in watchdog timer on Ingenic jz4740 SoCs.
config [31mCONFIG_WDT_MTX1[0m
tristate "MTX-1 Hardware Watchdog"
depends on [31mCONFIG_MIPS_MTX1[0m
help
Hardware driver for the MTX-1 boards. This is a watchdog timer that
will reboot the machine after a 100 seconds timer expired.
config [31mCONFIG_PNX833X_WDT[0m
tristate "PNX833x Hardware Watchdog"
depends on [31mCONFIG_SOC_PNX8335[0m
help
Hardware driver for the PNX833x's watchdog. This is a
watchdog timer that will reboot the machine after a programmable
timer has expired and no process has written to /dev/watchdog during
that time.
config [31mCONFIG_SIBYTE_WDOG[0m
tristate "Sibyte SoC hardware watchdog"
depends on [31mCONFIG_CPU_SB1[0m
help
Watchdog driver for the built in watchdog hardware in Sibyte
SoC processors. There are apparently two watchdog timers
on such processors; this driver supports only the first one,
because currently Linux only supports exporting one watchdog
to userspace.
To compile this driver as a loadable module, choose [31mCONFIG_M[0m here.
The module will be called sb_wdog.
config [31mCONFIG_AR7_WDT[0m
tristate "TI AR7 Watchdog Timer"
depends on [31mCONFIG_AR7[0m
help
Hardware driver for the TI [31mCONFIG_AR7[0m Watchdog Timer.
config [31mCONFIG_TXX9_WDT[0m
tristate "Toshiba TXx9 Watchdog Timer"
depends on [31mCONFIG_CPU_TX39XX[0m || [31mCONFIG_CPU_TX49XX[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Hardware driver for the built-in watchdog timer on TXx9 [31mCONFIG_MIPS[0m SoCs.
config [31mCONFIG_OCTEON_WDT[0m
tristate "Cavium OCTEON SOC family Watchdog Timer"
depends on [31mCONFIG_CAVIUM_OCTEON_SOC[0m
default y
select [31mCONFIG_WATCHDOG_CORE[0m
select [31mCONFIG_EXPORT_UASM[0m if [31mCONFIG_OCTEON_WDT[0m = m
help
Hardware driver for OCTEON's on chip watchdog timer.
Enables the watchdog for all cores running Linux. It
installs a NMI handler and pokes the watchdog based on an
interrupt. On first expiration of the watchdog, the
interrupt handler pokes it. The second expiration causes an
NMI that prints a message. The third expiration causes a
global soft reset.
When userspace has /dev/watchdog open, no poking is done
from the first interrupt, it is then only poked when the
device is written.
config [31mCONFIG_BCM63XX_WDT[0m
tristate "Broadcom BCM63xx hardware watchdog"
depends on [31mCONFIG_BCM63XX[0m
help
Watchdog driver for the built in watchdog hardware in Broadcom
BCM63xx SoC.
To compile this driver as a loadable module, choose [31mCONFIG_M[0m here.
The module will be called bcm63xx_wdt.
config [31mCONFIG_BCM2835_WDT[0m
tristate "Broadcom BCM2835 hardware watchdog"
depends on [31mCONFIG_ARCH_BCM2835[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Watchdog driver for the built in watchdog hardware in Broadcom
BCM2835 SoC.
To compile this driver as a loadable module, choose [31mCONFIG_M[0m here.
The module will be called bcm2835_wdt.
config [31mCONFIG_BCM_KONA_WDT[0m
tristate "BCM Kona Watchdog"
depends on [31mCONFIG_ARCH_BCM_MOBILE[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Support for the watchdog timer on the following Broadcom BCM281xx
family, which includes BCM11130, BCM11140, BCM11351, BCM28145 and
BCM28155 variants.
Say 'Y' or '[31mCONFIG_M[0m' here to enable the driver. The module will be called
bcm_kona_wdt.
config [31mCONFIG_BCM_KONA_WDT_DEBUG[0m
bool "DEBUGFS support for BCM Kona Watchdog"
depends on [31mCONFIG_BCM_KONA_WDT[0m
help
If enabled, adds /sys/kernel/debug/bcm_kona_wdt/info which provides
access to the driver's internal data structures as well as watchdog
timer hardware registres.
If in doubt, say 'N'.
config [31mCONFIG_BCM7038_WDT[0m
tristate "BCM7038 Watchdog"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_ARCH_BRCMSTB[0m || [31mCONFIG_BMIPS_GENERIC[0m || [31mCONFIG_COMPILE_TEST[0m
help
Watchdog driver for the built-in hardware in Broadcom 7038 and
later SoCs used in set-top boxes. BCM7038 was made public
during the 2004 CES, and since then, many Broadcom chips use this
watchdog block, including some cable modem chips.
config [31mCONFIG_IMGPDC_WDT[0m
tristate "Imagination Technologies PDC Watchdog Timer"
depends on [31mCONFIG_HAS_IOMEM[0m
depends on [31mCONFIG_METAG[0m || [31mCONFIG_MIPS[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Driver for Imagination Technologies PowerDown Controller
Watchdog Timer.
To compile this driver as a loadable module, choose [31mCONFIG_M[0m here.
The module will be called imgpdc_wdt.
config [31mCONFIG_LANTIQ_WDT[0m
tristate "Lantiq SoC watchdog"
depends on [31mCONFIG_LANTIQ[0m
help
Hardware driver for the Lantiq SoC Watchdog Timer.
config [31mCONFIG_LOONGSON1_WDT[0m
tristate "Loongson1 SoC hardware watchdog"
depends on [31mCONFIG_MACH_LOONGSON32[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
Hardware driver for the Loongson1 SoC Watchdog Timer.
config [31mCONFIG_RALINK_WDT[0m
tristate "Ralink SoC watchdog"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_RALINK[0m
help
Hardware driver for the Ralink SoC Watchdog Timer.
config [31mCONFIG_MT7621_WDT[0m
tristate "Mediatek SoC watchdog"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_SOC_MT7620[0m || [31mCONFIG_SOC_MT7621[0m
help
Hardware driver for the Mediatek/Ralink MT7621/8 SoC Watchdog Timer.
config [31mCONFIG_PIC32_WDT[0m
tristate "Microchip PIC32 hardware watchdog"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_MACH_PIC32[0m
help
Watchdog driver for the built in watchdog hardware in a PIC32.
Configuration bits must be set appropriately for the watchdog to be
controlled by this driver.
To compile this driver as a loadable module, choose [31mCONFIG_M[0m here.
The module will be called pic32-wdt.
config [31mCONFIG_PIC32_DMT[0m
tristate "Microchip PIC32 Deadman Timer"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_MACH_PIC32[0m
help
Watchdog driver for PIC32 instruction fetch counting timer. This specific
timer is typically be used in misson critical and safety critical
applications, where any single failure of the software functionality
and sequencing must be detected.
To compile this driver as a loadable module, choose [31mCONFIG_M[0m here.
The module will be called pic32-dmt.
# [31mCONFIG_PARISC[0m Architecture
# POWERPC Architecture
config [31mCONFIG_GEF_WDT[0m
tristate "GE Watchdog Timer"
depends on [31mCONFIG_GE_FPGA[0m
---help---
Watchdog timer found in a number of GE single board computers.
config [31mCONFIG_MPC5200_WDT[0m
bool "MPC52xx Watchdog Timer"
depends on [31mCONFIG_PPC_MPC52xx[0m
help
Use General Purpose Timer (GPT) 0 on the MPC5200 as Watchdog.
config [31mCONFIG_8xxx_WDT[0m
tristate "MPC8xxx Platform Watchdog Timer"
depends on [31mCONFIG_PPC_8xx[0m || [31mCONFIG_PPC_83xx[0m || [31mCONFIG_PPC_86xx[0m || [31mCONFIG_PPC_MPC512x[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
This driver is for a SoC level watchdog that exists on some
Freescale PowerPC processors. So far this driver supports:
- MPC8xx watchdogs
- MPC83xx watchdogs
- MPC86xx watchdogs
For BookE processors (MPC85xx) use the [31mCONFIG_BOOKE_WDT[0m driver instead.
config [31mCONFIG_MV64X60_WDT[0m
tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
depends on [31mCONFIG_MV64X60[0m
config [31mCONFIG_PIKA_WDT[0m
tristate "PIKA FPGA Watchdog"
depends on [31mCONFIG_WARP[0m
default y
help
This enables the watchdog in the PIKA [31mCONFIG_FPGA[0m. Currently used on
the Warp platform.
config [31mCONFIG_BOOKE_WDT[0m
tristate "PowerPC Book-E Watchdog Timer"
depends on [31mCONFIG_BOOKE[0m || [31mCONFIG_4xx[0m
select [31mCONFIG_WATCHDOG_CORE[0m
---help---
Watchdog driver for PowerPC Book-[31mCONFIG_E[0m chips, such as the Freescale
MPC85xx SOCs and the IBM PowerPC 440.
Please see Documentation/watchdog/watchdog-api.txt for
more information.
config [31mCONFIG_BOOKE_WDT_DEFAULT_TIMEOUT[0m
int "PowerPC Book-E Watchdog Timer Default Timeout"
depends on [31mCONFIG_BOOKE_WDT[0m
default 38 if [31mCONFIG_PPC_FSL_BOOK3E[0m
range 0 63 if [31mCONFIG_PPC_FSL_BOOK3E[0m
default 3 if ![31mCONFIG_PPC_FSL_BOOK3E[0m
range 0 3 if ![31mCONFIG_PPC_FSL_BOOK3E[0m
help
Select the default watchdog timer period to be used by the PowerPC
Book-[31mCONFIG_E[0m watchdog driver. [31mCONFIG_A[0m watchdog "event" occurs when the bit
position represented by this number transitions from zero to one.
For Freescale Book-[31mCONFIG_E[0m processors, this is a number between 0 and 63.
For other Book-[31mCONFIG_E[0m processors, this is a number between 0 and 3.
The value can be overridden by the wdt_period command-line parameter.
config [31mCONFIG_MEN_A21_WDT[0m
tristate "MEN A21 VME CPU Carrier Board Watchdog Timer"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Watchdog driver for MEN A21 VMEbus CPU Carrier Boards.
The driver can also be built as a module. If so, the module will be
called mena21_wdt.
If unsure select N here.
# [31mCONFIG_PPC64[0m Architecture
config [31mCONFIG_WATCHDOG_RTAS[0m
tristate "RTAS watchdog"
depends on [31mCONFIG_PPC_RTAS[0m
help
This driver adds watchdog support for the RTAS watchdog.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module
will be called wdrtas.
# [31mCONFIG_S390[0m Architecture
config [31mCONFIG_DIAG288_WATCHDOG[0m
tristate "System z diag288 Watchdog"
depends on [31mCONFIG_S390[0m
select [31mCONFIG_WATCHDOG_CORE[0m
help
IBM s/390 and zSeries machines running under z/VM 5.1 or later
provide a virtual watchdog timer to their guest that cause a
user define Control Program command to be executed after a
timeout.
LPAR provides a very similar interface. This driver handles
both.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module
will be called diag288_wdt.
# [31mCONFIG_SUPERH[0m (sh + sh64) Architecture
config [31mCONFIG_SH_WDT[0m
tristate "SuperH Watchdog"
depends on [31mCONFIG_SUPERH[0m && ([31mCONFIG_CPU_SH3[0m || [31mCONFIG_CPU_SH4[0m)
select [31mCONFIG_WATCHDOG_CORE[0m
help
This driver adds watchdog support for the integrated watchdog in the
SuperH processors. If you have one of these processors and wish
to have watchdog support enabled, say Y, otherwise say N.
As a side note, saying Y here will automatically boost [31mCONFIG_HZ[0m to 1000
so that the timer has a chance to clear the overflow counter. On
slower systems (such as the SH-2 and SH-3) this will likely yield
some performance issues. As such, the [31mCONFIG_WDT[0m should be avoided here
unless it is absolutely necessary.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called shwdt.
# [31mCONFIG_SPARC[0m Architecture
# [31mCONFIG_SPARC64[0m Architecture
config [31mCONFIG_WATCHDOG_CP1XXX[0m
tristate "CP1XXX Hardware Watchdog support"
depends on [31mCONFIG_SPARC64[0m && [31mCONFIG_PCI[0m
---help---
This is the driver for the hardware watchdog timers present on
Sun Microsystems CompactPCI models CP1400 and CP1500.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cpwatchdog.
If you do not have a CompactPCI model CP1400 or CP1500, or
another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
you should say N to this option.
config [31mCONFIG_WATCHDOG_RIO[0m
tristate "RIO Hardware Watchdog support"
depends on [31mCONFIG_SPARC64[0m && [31mCONFIG_PCI[0m
help
Say Y here to support the hardware watchdog capability on Sun RIO
machines. The watchdog timeout period is normally one minute but
can be changed with a boot-time parameter.
config [31mCONFIG_WATCHDOG_SUN4V[0m
tristate "Sun4v Watchdog support"
select [31mCONFIG_WATCHDOG_CORE[0m
depends on [31mCONFIG_SPARC64[0m
help
Say Y here to support the hypervisor watchdog capability embedded
in the [31mCONFIG_SPARC[0m sun4v architecture.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called sun4v_wdt.
# [31mCONFIG_XTENSA[0m Architecture
# Xen Architecture
config [31mCONFIG_XEN_WDT[0m
tristate "Xen Watchdog support"
depends on [31mCONFIG_XEN[0m
help
Say Y here to support the hypervisor watchdog capability provided
by Xen 4.0 and newer. The watchdog timeout period is normally one
minute but can be changed with a boot-time parameter.
config [31mCONFIG_UML_WATCHDOG[0m
tristate "UML watchdog"
depends on [31mCONFIG_UML[0m
#
# [31mCONFIG_ISA[0m-based Watchdog Cards
#
comment "ISA-based Watchdog Cards"
depends on [31mCONFIG_ISA[0m
config [31mCONFIG_PCWATCHDOG[0m
tristate "Berkshire Products ISA-PC Watchdog"
depends on [31mCONFIG_ISA[0m
---help---
This is the driver for the Berkshire Products [31mCONFIG_ISA[0m-PC Watchdog card.
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time. This driver is like the WDT501 driver but for different
hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
watchdog cards can be ordered from <http://www.berkprod.com/>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pcwd.
Most people will say N.
config [31mCONFIG_MIXCOMWD[0m
tristate "Mixcom Watchdog"
depends on [31mCONFIG_ISA[0m
---help---
This is a driver for the Mixcom hardware watchdog cards. This
watchdog simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mixcomwd.
Most people will say N.
config [31mCONFIG_WDT[0m
tristate "WDT Watchdog timer"
depends on [31mCONFIG_ISA[0m
---help---
If you have a WDT500P or WDT501P watchdog board, say Y here,
otherwise N. It is not possible to probe for this board, which means
that you have to inform the kernel about the IO port and IRQ that
is needed (you can do this via the io and irq parameters)
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called wdt.
#
# [31mCONFIG_PCI[0m-based Watchdog Cards
#
comment "PCI-based Watchdog Cards"
depends on [31mCONFIG_PCI[0m
config [31mCONFIG_PCIPCWATCHDOG[0m
tristate "Berkshire Products PCI-PC Watchdog"
depends on [31mCONFIG_PCI[0m
---help---
This is the driver for the Berkshire Products [31mCONFIG_PCI[0m-PC Watchdog card.
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time. The card can also monitor the internal temperature of the PC.
More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pcwd_pci.
Most people will say N.
config [31mCONFIG_WDTPCI[0m
tristate "PCI-WDT500/501 Watchdog timer"
depends on [31mCONFIG_PCI[0m
---help---
If you have a [31mCONFIG_PCI[0m-WDT500/501 watchdog board, say Y here, otherwise N.
If you have a [31mCONFIG_PCI[0m-WDT501 watchdog board then you can enable the
temperature sensor by setting the type parameter to 501.
If you want to enable the Fan Tachometer on the [31mCONFIG_PCI[0m-WDT501, then you
can do this via the tachometer parameter. Only do this if you have a
fan tachometer actually set up.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called wdt_pci.
#
# [31mCONFIG_USB[0m-based Watchdog Cards
#
comment "USB-based Watchdog Cards"
depends on [31mCONFIG_USB[0m
config [31mCONFIG_USBPCWATCHDOG[0m
tristate "Berkshire Products USB-PC Watchdog"
depends on [31mCONFIG_USB[0m
---help---
This is the driver for the Berkshire Products [31mCONFIG_USB[0m-PC Watchdog card.
This card simply watches your kernel to make sure it doesn't freeze,
and if it does, it reboots your computer after a certain amount of
time. The card can also monitor the internal temperature of the PC.
More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pcwd_usb.
Most people will say N.
comment "Watchdog Pretimeout Governors"
config [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV[0m
bool "Enable watchdog pretimeout governors"
help
The option allows to select watchdog pretimeout governors.
if [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV[0m
choice
prompt "Default Watchdog Pretimeout Governor"
default [31mCONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC[0m
help
This option selects a default watchdog pretimeout governor.
The governor takes its action, if a watchdog is capable
to report a pretimeout event.
config [31mCONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP[0m
bool "noop"
select [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP[0m
help
Use noop watchdog pretimeout governor by default. If noop
governor is selected by a user, write a short message to
the kernel log buffer and don't do any system changes.
config [31mCONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC[0m
bool "panic"
select [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC[0m
help
Use panic watchdog pretimeout governor by default, if
a watchdog pretimeout event happens, consider that
a watchdog feeder is dead and reboot is unavoidable.
endchoice
config [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP[0m
tristate "Noop watchdog pretimeout governor"
help
Noop watchdog pretimeout governor, only an informational
message is added to kernel log buffer.
config [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC[0m
tristate "Panic watchdog pretimeout governor"
help
Panic watchdog pretimeout governor, on watchdog pretimeout
event put the kernel into panic.
endif # [31mCONFIG_WATCHDOG_PRETIMEOUT_GOV[0m
endif # [31mCONFIG_WATCHDOG[0m