summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2019-06-17 16:34:16 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2019-06-19 11:02:10 +0200
commitbf8973f10df5d11033ab4b9420decd3f55a69b4d (patch)
treec4c03fa86b438208c1769e11bcabe4194c1a789f /Documentation
parentbe798d2a129531cdb4cac40ea82bfa6aa5c6bcec (diff)
downloadbarebox-bf8973f10df5d11033ab4b9420decd3f55a69b4d.tar.gz
barebox-bf8973f10df5d11033ab4b9420decd3f55a69b4d.tar.xz
Documentation: reset-reason: document new BROWNOUT reason
Now that enum reset_src_type has been extended by BROWNOUT as a reason, add it to the user documentation. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/user/reset-reason.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/Documentation/user/reset-reason.rst b/Documentation/user/reset-reason.rst
index 26d37f86dd..e46f2ca684 100644
--- a/Documentation/user/reset-reason.rst
+++ b/Documentation/user/reset-reason.rst
@@ -41,6 +41,10 @@ The following values can help to detect the reason why the bootloader runs:
* ``EXT`` (EXTernal): some SoCs have special device pins for external reset
signals other than the ``RST`` one. Application specific how to handle this
state.
+* ``BROWNOUT``: some SoCs detect undervoltage conditions and stay in reset
+ till the supply voltage crosses a predefined threshold voltage. This avoids
+ erratic behavior that may occur when running out-of-spec. Application specific
+ how to handle this state.
It depends on your board/SoC and its features if the hardware is able to detect
these reset reasons. Most of the time only ``POR`` and ``RST`` are supported