diff options
| author | Philipp Tomsich <philipp.tomsich@theobroma-systems.com> | 2017-11-24 18:37:58 +0100 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2017-12-12 19:53:45 -0700 |
| commit | b53f6992e9cb7f0d892ebc2b1620b55559f461be (patch) | |
| tree | d2211146c7e239b4bdb1eee58879c593ef099f61 /drivers/sysreset | |
| parent | f2faffecb016988a999f26f1dbebc5d88793761b (diff) | |
dm: reset: have the reset-command perform a COLD reset
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().
Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/sysreset')
| -rw-r--r-- | drivers/sysreset/sysreset-uclass.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/sysreset/sysreset-uclass.c b/drivers/sysreset/sysreset-uclass.c index 3566d17fb1..0747c52b60 100644 --- a/drivers/sysreset/sysreset-uclass.c +++ b/drivers/sysreset/sysreset-uclass.c @@ -70,7 +70,7 @@ void reset_cpu(ulong addr) int do_reset(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) { - sysreset_walk_halt(SYSRESET_WARM); + sysreset_walk_halt(SYSRESET_COLD); return 0; } |