
26 Nov
2017
26 Nov
'17
12:39 p.m.
On 24 November 2017 at 10:37, Philipp Tomsich philipp.tomsich@theobroma-systems.com wrote:
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
drivers/sysreset/sysreset-uclass.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass sjg@chromium.org