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 /doc | |
| parent | f2faffecb016988a999f26f1dbebc5d88793761b (diff) | |
| download | u-boot-b53f6992e9cb7f0d892ebc2b1620b55559f461be.zip u-boot-b53f6992e9cb7f0d892ebc2b1620b55559f461be.tar.gz u-boot-b53f6992e9cb7f0d892ebc2b1620b55559f461be.tar.bz2 | |
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 'doc')
0 files changed, 0 insertions, 0 deletions