diff options
| author | Li Jun <lijun01@kylinos.cn> | 2026-09-17 09:37:10 +0800 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2026-09-18 08:10:45 -0700 |
| commit | 7cb575b71ab98194d2e040bded3a7281e089c5ed (patch) | |
| tree | 794d4d211b745dfbc4f4f7213d149e39fab6c037 /tools/perf/scripts/python/bin | |
| parent | 8f0ca55016a7647109ae2bc91bcb346fc8b13785 (diff) | |
| download | linux-next-7cb575b71ab98194d2e040bded3a7281e089c5ed.tar.gz linux-next-7cb575b71ab98194d2e040bded3a7281e089c5ed.zip | |
watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog
da9063_wdt_suspend() and da9063_wdt_resume() only check watchdog_active(),
when the watchdog is left running by the driver sets
WDOG_HW_RUNNING in da9063_wdt_probe() but userspace never opens the
device, so WDOG_ACTIVE remains cleared, the wdt_disable() will not be
executed in da9063_wdt_suspend. In this case, the suspend callback is
a no-op and the watchdog keeps counting during system suspend,
leading to an unexpected system reset.
Check WDOG_HW_RUNNING and wdd，can fix this issue.
Fixes: a7ceca4398bc8 ("watchdog: da9063: optionally disable watchdog during suspend")
Cc: stable@vger.kernel.org
Signed-off-by: Li Jun <lijun01@kylinos.cn>
Link: https://patch.msgid.link/20260917013710.2754679-1-lijun01@kylinos.cn
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions