watchdog: orion: use 0 for unset heartbeat
authorChris Packham <chris.packham@alliedtelesis.co.nz>
Fri, 13 Mar 2020 03:13:12 +0000 (16:13 +1300)
committerWim Van Sebroeck <wim@linux-watchdog.org>
Wed, 1 Apr 2020 09:35:22 +0000 (11:35 +0200)
commitbb914088bd8a91c382f54d469367b2e5508b5493
treef95ac51bb305868ad0775c13acf380c4ed4aa9b7
parentf667421324ed89a545b8d7efc69284059ea28d21
watchdog: orion: use 0 for unset heartbeat

If the heartbeat module param is not specified we would get an error
message

  watchdog: f1020300.watchdog: driver supplied timeout (4294967295) out of range
  watchdog: f1020300.watchdog: falling back to default timeout (171)

This is because we were initialising heartbeat to -1. By removing the
initialisation (thus letting the C run time initialise it to 0) we
silence the warning message and the default timeout is still used.

Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/20200313031312.1485-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>
drivers/watchdog/orion_wdt.c