summaryrefslogtreecommitdiff
path: root/drivers/watchdog/aspeed_wdt.c
diff options
context:
space:
mode:
authorChris Packham <chris.packham@alliedtelesis.co.nz>2019-08-30 00:52:24 +0300
committerWim Van Sebroeck <wim@linux-watchdog.org>2019-09-17 09:59:13 +0300
commite07a4c79ca75bf41d73ba74c06f7220cd2741bc9 (patch)
tree1c439762a849dd0e785250034fcc2ee4857ee081 /drivers/watchdog/aspeed_wdt.c
parent41b630f41bf744b0eed92a53ff8c716cfc71920a (diff)
downloadlinux-e07a4c79ca75bf41d73ba74c06f7220cd2741bc9.tar.xz
watchdog: orion_wdt: use timer1 as a pretimeout
The orion watchdog can either reset the CPU or generate an interrupt. The interrupt would be useful for debugging as it provides panic() output about the watchdog expiry, however if the interrupt is used the watchdog can't reset the CPU in the event of being stuck in a loop with interrupts disabled or if the CPU is prevented from accessing memory (e.g. an unterminated DMA). The Armada SoCs have spare timers that aren't currently used by the Linux kernel. We can use timer1 to provide a pre-timeout ahead of the watchdog timer and provide the possibility of gathering debug before the reset triggers. Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Link: https://lore.kernel.org/r/20190829215224.27956-1-chris.packham@alliedtelesis.co.nz Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
Diffstat (limited to 'drivers/watchdog/aspeed_wdt.c')
0 files changed, 0 insertions, 0 deletions