The SCU firmware watchdog is already configured. If this is the hardware WDT for Linux, it may just be that I need to test that it is functioning properly.
CONFIG_IMX2_WDT=y
CONFIG_IMX_SC_WDT=y
CONFIG_HAVE_ARM_SMCCC=y
CONFIG_IMX_SCU=y
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
config IMX_SC_WDT
tristate "IMX SC Watchdog"
depends on HAVE_ARM_SMCCC
depends on IMX_SCU
select WATCHDOG_CORE
This is the driver for the system controller watchdog
on the NXP i.MX SoCs with system controller inside, the
watchdog driver will call ARM SMC API and trap into
ARM-Trusted-Firmware for operations, ARM-Trusted-Firmware
will request system controller to execute the operations.
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 M here: the
module will be called imx_sc_wdt.
Also, the software WD is not set.
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
If I do an echo >> /dev/watchdog and hit enter twice after killing the watchdog process there is a hard reset. This may be testing the hardware watchdog timer, is that the case and how can I be sure this is testing the hardware watchdog timer?
With this kernel configuration, is the Linux hardware watchdog the same as the NXP i.MX8X SCU watchdog?