Files
u-boot/board
Pali Rohár 27b2bff6eb board: freescale: p1_p2_rdb_pc: Add workaround for non-working watchdog
If watchdog timer was already set to non-disabled value then it means that
watchdog timer was already activated, has already expired and caused CPU
reset. If this happened then due to CPLD firmware bug, writing to wd_cfg
register has no effect and therefore it is not possible to reactivate
watchdog timer again. Watchdog starts working again after CPU reset via
non-watchdog method.

Implement this workaround (reset CPU when it was reset by watchdog) to make
watchdog usable again. Watchdog timer logic on these P1/P2 RDB boards is
connected to CPLD, not to SoC itself.

Note that reset does not occur immediately after calling do_reset(), but
after few ms later as real reset is done by CPLD. So it is normal that
function do_reset() returns. Therefore hangs after calling do_reset() to
prevent CPU execution of the rest U-Boot code.

Signed-off-by: Pali Rohár <pali@kernel.org>
Signed-off-by: Peng Fan <peng.fan@nxp.com>
2022-09-06 14:08:33 +08:00
..
2022-08-20 21:18:15 -04:00
2021-11-07 18:36:55 +01:00
2022-08-04 16:18:47 -04:00
2022-07-01 15:55:54 -04:00
2021-10-27 16:38:26 -04:00
2022-08-20 21:18:15 -04:00
2022-04-28 09:26:44 -04:00
2022-08-20 21:18:15 -04:00
2022-07-08 17:57:34 -04:00
2021-09-07 16:22:30 -04:00
2022-08-04 16:18:47 -04:00
2022-04-28 09:26:44 -04:00
2022-04-08 09:05:20 -04:00
2022-07-26 02:30:56 -06:00
2022-08-04 16:18:47 -04:00
2022-08-04 16:18:47 -04:00
2022-04-12 15:36:18 +02:00
2022-08-04 16:18:47 -04:00
2022-01-08 11:16:03 -05:00