daisydog: logs refactor

Additional logs for problem detection.
Corrections to existing logs.

BUG=b:287218810
TEST=manually check if behaviour is correct
TEST=test_that <IP> platform_HWwatchdog
TEST=suspend_stress_test --wake_min 65 --suspend_min 65 -c 100
TEST=tast run <IP> crash.WatchdogCrash

Change-Id: I2ce3de6160609b09c78fab6c19d787e93f14011c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/daisydog/+/5600777
Tested-by: Patryk Busse <pbusse@google.com>
Reviewed-by: Tim Van Patten <timvp@google.com>
Commit-Queue: Patryk Busse <pbusse@google.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
1 file changed
tree: e5278abf3304a828722badebc6be82dfd2c5f9b4
  1. 51-watchdog.rules
  2. COPYING
  3. daisydog.c
  4. daisydog.conf
  5. Makefile
  6. OWNERS
  7. PRESUBMIT.cfg
  8. README.md
README.md

GPL Code is copied with explicit permission from Daniel Widyanto:
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/

The project name is based on Samsung's “daisy” reference board design and I liked this quote from the daisy dog FAQ:

Daisy Dogs are not persnickety little ankle biters

When this daisydog doesn't run, the machine should reset. :)

An alternative code to start with would have been:
https://dev.openwrt.org/ticket/2270

The watchdog project is alot more complicated than what the Chromium OS project needs.