diff options
| author | Ryan Brue <ryanbrue.dev@gmail.com> | 2026-09-23 22:10:41 -0500 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2026-09-25 07:23:36 -0700 |
| commit | 2686e13649a9e846f6c08cf4ada0256ca19c3475 (patch) | |
| tree | 0c24df612e87b1d8cd89d22bad65bb5959f4a9a6 /tools/lib/python/kdoc/python_version.py | |
| parent | 93f51579e7df248780214094418f205253383cc5 (diff) | |
| download | linux-next-2686e13649a9e846f6c08cf4ada0256ca19c3475.tar.gz linux-next-2686e13649a9e846f6c08cf4ada0256ca19c3475.zip | |
watchdog: mediatek: Apply the driver's mode to a watchdog left running
When the bootloader leaves the watchdog enabled, probe only marks it
running and sets the timeout, so WDT_MODE keeps whatever the bootloader
wrote. The Amazon Fire HD 10 (2017) bootloader leaves dual mode with the
bark IRQ enabled, and no pretimeout is configured, so each timeout only
raises the IRQ and restarts the count: with the 20 s timeout systemd
sets, a hung system was reset after 37.95-39.76 s, and after 18.25-20.92 s
once IRQ_EN was cleared by hand.
Program the mode as mtk_wdt_start() does, which also applies
mediatek,disable-extrst and mediatek,reset-by-toprgu to a running
watchdog; read those two properties first.
Fixes: bbece05c0d3a ("watchdog: mtk_wdt: Remove mtk_wdt_stop() in probe() to prevent the system freeze and it doesn't reboot by watchdog problem")
Assisted-by: LLM
Signed-off-by: Ryan Brue <ryanbrue.dev@gmail.com>
Link: https://patch.msgid.link/20260923-rbrue-suez-upstreaming-mtk-wdt-dual-mode-v1-1-0970852315e4@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions