diff options
| author | Stefan Wahren <wahrenst@gmx.net> | 2023-11-12 20:32:51 +0300 |
|---|---|---|
| committer | Wim Van Sebroeck <wim@linux-watchdog.org> | 2023-12-17 18:14:22 +0300 |
| commit | f33f5b1fd1be5f5106d16f831309648cb0f1c31d (patch) | |
| tree | f8626adaec041f34baa90c8edc657a750c73e4c0 /drivers/watchdog/w83877f_wdt.c | |
| parent | 91c437ea47045379db870fd0454d8778573b41e0 (diff) | |
| download | linux-f33f5b1fd1be5f5106d16f831309648cb0f1c31d.tar.xz | |
watchdog: bcm2835_wdt: Fix WDIOC_SETTIMEOUT handling
Users report about the unexpected behavior for setting timeouts above
15 sec on Raspberry Pi. According to watchdog-api.rst the ioctl
WDIOC_SETTIMEOUT shouldn't fail because of hardware limitations.
But looking at the code shows that max_timeout based on the
register value PM_WDOG_TIME_SET, which is the maximum.
Since 664a39236e71 ("watchdog: Introduce hardware maximum heartbeat
in watchdog core") the watchdog core is able to handle this problem.
This fix has been tested with watchdog-test from selftests.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217374
Fixes: 664a39236e71 ("watchdog: Introduce hardware maximum heartbeat in watchdog core")
Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/20231112173251.4827-1-wahrenst@gmx.net
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
Diffstat (limited to 'drivers/watchdog/w83877f_wdt.c')
0 files changed, 0 insertions, 0 deletions