summaryrefslogtreecommitdiff
path: root/doc/develop
diff options
context:
space:
mode:
authorHeinrich Schuchardt <[email protected]>2025-05-03 12:12:37 +0200
committerHeinrich Schuchardt <[email protected]>2025-05-11 12:52:56 +0200
commit6e5d3e6e0569f5b9df0f891b1fdab8e3dac6291e (patch)
treede0ee29e2ce7dde4352145d5ea4b917f965e118e /doc/develop
parentfeb55165233623648cb0a74953735b00ec6e322e (diff)
doc: u-boot-test-reset: mention power cycling
Using power cycling is a valid option to implement u-boot-test-reset. Reviewed-by: Mattijs Korpershoek <[email protected]> Signed-off-by: Heinrich Schuchardt <[email protected]>
Diffstat (limited to 'doc/develop')
-rw-r--r--doc/develop/py_testing.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/develop/py_testing.rst b/doc/develop/py_testing.rst
index 217ae447035..5ad7f576ccd 100644
--- a/doc/develop/py_testing.rst
+++ b/doc/develop/py_testing.rst
@@ -377,7 +377,8 @@ this script again to restore U-Boot to an operational state before running the
next test function.
This script will likely be implemented by communicating with some form of
-relay or electronic switch attached to the board's reset signal.
+relay or electronic switch attached to the board's reset signal. Power cycling
+is another option.
The semantics of this script require that when it is executed, U-Boot will
start running from scratch. If the U-Boot binary to be tested has been written