diff options
author | Andrej Picej <andrej.picej@norik.com> | 2021-12-16 13:26:53 +0100 |
---|---|---|
committer | Sascha Hauer <s.hauer@pengutronix.de> | 2022-01-17 14:30:21 +0100 |
commit | c3787a81f26bb1daa82136ddc392c40c36d3317e (patch) | |
tree | e8d35aada92bd89b3152633232f9d43c459b424a /drivers/misc/Makefile | |
parent | 806ab9d9c7a08e41fe40f56ec0a8bd065200e2b8 (diff) | |
download | barebox-c3787a81f26bb1daa82136ddc392c40c36d3317e.tar.gz barebox-c3787a81f26bb1daa82136ddc392c40c36d3317e.tar.xz |
watchdog: imxwd: suspend watchdog timer in low power mode
Watchdog timer should be disabled in low power mode. The problem that
was observed was that when the watchdog is started from barebox, kernel
driver doesn't do its own setup again and in turn this bit is left
unset. Moreover, this bit is write-once and has to be set before
enabling the watchdog, leaving responsibility for proper setup to a
party first using the watchdog timer (e.g. bootloader). Issue manifests
itself later on, when device enters low power mode (e.g. suspend) for
more amount of time than what is maximum watchdog timeout (128s). After
that period of time, device will not recover ever as there is no service
patting the watchdog (CPU is suspended). This means that the device can
hang in suspend mode or it performs an unexpected reset.
Thus to avoid suspend/resume problems when watchdog is started already
in the bootloader, align bootloader driver settings with kernel settings.
Kernel driver has been already setting this bit since 2014.
Signed-off-by: Andrej Picej <andrej.picej@norik.com>
Link: https://lore.barebox.org/20211216122653.2335949-1-andrej.picej@norik.com
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/misc/Makefile')
0 files changed, 0 insertions, 0 deletions