diff options
author | Fabrizio Castro <fabrizio.castro.jz@renesas.com> | 2022-11-17 11:49:07 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-03-11 13:55:23 +0100 |
commit | 1bcf3a9846e8e09159ce656146a6f775649d0ea9 (patch) | |
tree | 8b902156cbe39edccfa21d1a7cfaebe8a2d6083e /scripts/coccinelle | |
parent | edaed0cd769589765fc4d84ee6c9c59bea025e55 (diff) | |
download | linux-1bcf3a9846e8e09159ce656146a6f775649d0ea9.tar.gz linux-1bcf3a9846e8e09159ce656146a6f775649d0ea9.tar.bz2 linux-1bcf3a9846e8e09159ce656146a6f775649d0ea9.zip |
watchdog: rzg2l_wdt: Handle TYPE-B reset for RZ/V2M
[ Upstream commit f769f97917c1e756e12ff042a93f6e3167254b5b ]
As per section 48.4 of the HW User Manual, IPs in the RZ/V2M
SoC need either a TYPE-A reset sequence or a TYPE-B reset
sequence. More specifically, the watchdog IP needs a TYPE-B
reset sequence.
If the proper reset sequence isn't implemented, then resetting
IPs may lead to undesired behaviour. In the restart callback of
the watchdog driver the reset has basically no effect on the
desired funcionality, as the register writes following the reset
happen before the IP manages to come out of reset.
Implement the TYPE-B reset sequence in the watchdog driver to
address the issues with the restart callback on RZ/V2M.
Fixes: ec122fd94eeb ("watchdog: rzg2l_wdt: Add rzv2m support")
Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Link: https://lore.kernel.org/r/20221117114907.138583-3-fabrizio.castro.jz@renesas.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Wim Van Sebroeck <wim@linux-watchdog.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/coccinelle')
0 files changed, 0 insertions, 0 deletions