13e1d84013
The DM version of do_reset has been issuing a warm-reset, which (on some platforms keeps GPIOs and other parts of the platform active). This may cause unintended behaviour, as calling do_reset usually indicates a desire to reset the board/platform and not just the CPU. This changes do_reset to always request a COLD reset. Note that programmatic uses can still invoke a WARM reset through reset_cpu() or using sysreset_walk(). Change-Id: I65a8ac8e62582866e23e6451315090fdb2781ef4 Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Kever Yang <kever.yang@rock-chips.com> (cherry picked from commit b53f6992e9cb7f0d892ebc2b1620b55559f461be) |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| sysreset-uclass.c | ||
| sysreset_ast.c | ||
| sysreset_psci.c | ||
| sysreset_rockchip.c | ||
| sysreset_sandbox.c | ||
| sysreset_snapdragon.c | ||
| sysreset_sti.c | ||
| sysreset_syscon.c | ||
| sysreset_watchdog.c | ||
| sysreset_xtfpga.c | ||